Executive summary
ssseasonnn/RxDownload falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 56 out of 100 and is rated Adequate, and it has no critical findings.
Production Readiness, at 42, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 14 files no active contributor knows, worth about 10 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 65.
Most of the eight serious findings are in Code Health.
The product code is 3,126 lines, about €3,400 to rebuild.
If Production Readiness rose from 42 to 70, the lowest score rated Strong, the score would rise from 56 to about 65.
New since the last survey: 3 findings
- Code Duplication · Edited copy of a member (15 corresponding lines) rxdownload4/src/main/java/zlc/season/rxdownload4/RxDownload.kt
- Code Duplication · Duplicated block (10 lines × 2) rxdownload4/src/main/java/zlc/season/rxdownload4/downloader/NormalDownloader.kt
- Code Duplication · Edited copy of a member (13 corresponding lines) demo/src/main/java/zlc/season/rxdownload/demo/list/DemoListItem.kt
Fixed since the last survey: 1 finding
- Code Duplication · Duplicated block (10 lines × 2) rxdownload4/src/main/java/zlc/season/rxdownload4/downloader/NormalDownloader.kt
Rebuild cost: about €3,400 · Estimate
| Cost to rebuild | €1,100 to €5,600, for 19 to 59 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,126 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 downloader.NormalDownloader | 2 downloader.RangeTmpFile | 3 downloader.RangeTmpFile.FileHeader | 4 downloader.RangeTmpFile.Segment | 5 recorder.StatusConverter | 6 request.RequestImpl | 7 utils | 8 validator | 9 request | 10 storage | 11 watcher | 12 downloader.RangeDownloader | 13 task | 14 downloader | 15 notification.NotificationActionService | 16 storage.MemoryStorage | 17 zlc.season.rxdownload4 | 18 manager | 19 manager.BasicTaskLimitation | 20 notification.SimpleNotificationCreator | 21 recorder | 22 notification | 23 recorder.TaskDataBase |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 downloader.NormalDownloader | |||||||||||||||||||||||
| 2 downloader.RangeTmpFile | |||||||||||||||||||||||
| 3 downloader.RangeTmpFile.FileHeader | |||||||||||||||||||||||
| 4 downloader.RangeTmpFile.Segment | |||||||||||||||||||||||
| 5 recorder.StatusConverter | |||||||||||||||||||||||
| 6 request.RequestImpl | |||||||||||||||||||||||
| 7 utils | |||||||||||||||||||||||
| 8 validator | |||||||||||||||||||||||
| 9 request | 1 | ||||||||||||||||||||||
| 10 storage | 3 | ||||||||||||||||||||||
| 11 watcher | 2 | ||||||||||||||||||||||
| 12 downloader.RangeDownloader | 1 | 1 | |||||||||||||||||||||
| 13 task | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||
| 14 downloader | 3 | 4 | 3 | ||||||||||||||||||||
| 15 notification.NotificationActionService | 1 | ||||||||||||||||||||||
| 16 storage.MemoryStorage | 1 | ||||||||||||||||||||||
| 17 zlc.season.rxdownload4 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||
| 18 manager | 2 | 2 | 3 | 2 | 8 | 2 | 3 | ||||||||||||||||
| 19 manager.BasicTaskLimitation | 2 | ||||||||||||||||||||||
| 20 notification.SimpleNotificationCreator | 1 | 1 | |||||||||||||||||||||
| 21 recorder | 3 | 1 | 8 | ||||||||||||||||||||
| 22 notification | 2 | 1 | 2 | 1 | |||||||||||||||||||
| 23 recorder.TaskDataBase | 1 |
9→6 request uses request.RequestImpl✕
- Connections
- 1 pair of types, where a type in request uses a type in request.RequestImpl.
- The types involved
zlc.season.rxdownload4.request.RequestImpl→zlc.season.rxdownload4.request.RequestImpl.Api
- Direction
- request uses request.RequestImpl, so a change to request.RequestImpl can break request, while a change to request can't break request.RequestImpl.
- Position
- Below the diagonal: request uses a module listed above it, which is the healthy direction.
10→13 storage uses task part of a loop✕
- Connections
- 3 pairs of types, where a type in storage uses a type in task.
- The types involved
zlc.season.rxdownload4.storage.MemoryStorage→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.storage.SimpleStorage→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.storage.Storage→zlc.season.rxdownload4.task.Task
- Direction
- storage uses task, so a change to task can break storage, while a change to storage can't break task.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→13 watcher uses task part of a loop✕
- Connections
- 2 pairs of types, where a type in watcher uses a type in task.
- The types involved
zlc.season.rxdownload4.watcher.Watcher→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.watcher.WatcherImpl→zlc.season.rxdownload4.task.Task
- Direction
- watcher uses task, so a change to task can break watcher, while a change to watcher can't break task.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→2 downloader.RangeDownloader uses downloader.RangeTmpFile✕
- Connections
- 1 pair of types, where a type in downloader.RangeDownloader uses a type in downloader.RangeTmpFile.
- The types involved
zlc.season.rxdownload4.downloader.RangeDownloader.InnerDownloader→zlc.season.rxdownload4.downloader.RangeTmpFile.Segment
- Direction
- downloader.RangeDownloader uses downloader.RangeTmpFile, so a change to downloader.RangeTmpFile can break downloader.RangeDownloader, while a change to downloader.RangeDownloader can't break downloader.RangeTmpFile.
- Position
- Below the diagonal: downloader.RangeDownloader uses a module listed above it, which is the healthy direction.
12→9 downloader.RangeDownloader uses request✕
- Connections
- 1 pair of types, where a type in downloader.RangeDownloader uses a type in request.
- The types involved
zlc.season.rxdownload4.downloader.RangeDownloader.InnerDownloader→zlc.season.rxdownload4.request.Request
- Direction
- downloader.RangeDownloader uses request, so a change to request can break downloader.RangeDownloader, while a change to downloader.RangeDownloader can't break request.
- Position
- Below the diagonal: downloader.RangeDownloader uses a module listed above it, which is the healthy direction.
13→8 task uses validator✕
- Connections
- 1 pair of types, where a type in task uses a type in validator.
- The types involved
zlc.season.rxdownload4.task.TaskInfo→zlc.season.rxdownload4.validator.Validator
- Direction
- task uses validator, so a change to validator can break task, while a change to task can't break validator.
- Position
- Below the diagonal: task uses a module listed above it, which is the healthy direction.
13→9 task uses request✕
- Connections
- 1 pair of types, where a type in task uses a type in request.
- The types involved
zlc.season.rxdownload4.task.TaskInfo→zlc.season.rxdownload4.request.Request
- Direction
- task uses request, so a change to request can break task, while a change to task can't break request.
- Position
- Below the diagonal: task uses a module listed above it, which is the healthy direction.
13→10 task uses storage✕
- Connections
- 1 pair of types, where a type in task uses a type in storage.
- The types involved
zlc.season.rxdownload4.task.TaskInfo→zlc.season.rxdownload4.storage.Storage
- Direction
- task uses storage, so a change to storage can break task, while a change to task can't break storage.
- Position
- Below the diagonal: task uses a module listed above it, which is the healthy direction.
13→11 task uses watcher✕
- Connections
- 1 pair of types, where a type in task uses a type in watcher.
- The types involved
zlc.season.rxdownload4.task.TaskInfo→zlc.season.rxdownload4.watcher.Watcher
- Direction
- task uses watcher, so a change to watcher can break task, while a change to task can't break watcher.
- Position
- Below the diagonal: task uses a module listed above it, which is the healthy direction.
13→14 task uses downloader part of a loop✕
- Connections
- 1 pair of types, where a type in task uses a type in downloader.
- The types involved
zlc.season.rxdownload4.task.TaskInfo→zlc.season.rxdownload4.downloader.Dispatcher
- Direction
- task uses downloader, so a change to downloader can break task, while a change to task can't break downloader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→17 task uses zlc.season.rxdownload4 part of a loop✕
- Connections
- 1 pair of types, where a type in task uses a type in zlc.season.rxdownload4.
- The types involved
zlc.season.rxdownload4.task.TaskInfo→zlc.season.rxdownload4.Progress
- Direction
- task uses zlc.season.rxdownload4, so a change to zlc.season.rxdownload4 can break task, while a change to task can't break zlc.season.rxdownload4.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 downloader uses downloader.RangeTmpFile✕
- Connections
- 3 pairs of types, where a type in downloader uses a type in downloader.RangeTmpFile.
- The types involved
zlc.season.rxdownload4.downloader.RangeTmpFile→zlc.season.rxdownload4.downloader.RangeTmpFile.FileContentzlc.season.rxdownload4.downloader.RangeTmpFile→zlc.season.rxdownload4.downloader.RangeTmpFile.FileHeaderzlc.season.rxdownload4.downloader.RangeTmpFile→zlc.season.rxdownload4.downloader.RangeTmpFile.Segment
- Direction
- downloader uses downloader.RangeTmpFile, so a change to downloader.RangeTmpFile can break downloader, while a change to downloader can't break downloader.RangeTmpFile.
- Position
- Below the diagonal: downloader uses a module listed above it, which is the healthy direction.
14→13 downloader uses task✕
- Connections
- 4 pairs of types, where a type in downloader uses a type in task.
- The types involved
zlc.season.rxdownload4.downloader.Downloader→zlc.season.rxdownload4.task.TaskInfozlc.season.rxdownload4.downloader.NormalDownloader→zlc.season.rxdownload4.task.TaskInfozlc.season.rxdownload4.downloader.RangeDownloader→zlc.season.rxdownload4.task.TaskInfozlc.season.rxdownload4.downloader.RangeTmpFile→zlc.season.rxdownload4.task.TaskInfo
- Direction
- downloader uses task, so a change to task can break downloader, while a change to downloader can't break task.
- Position
- Below the diagonal: downloader uses a module listed above it, which is the healthy direction.
14→17 downloader uses zlc.season.rxdownload4 part of a loop✕
- Connections
- 3 pairs of types, where a type in downloader uses a type in zlc.season.rxdownload4.
- The types involved
zlc.season.rxdownload4.downloader.Downloader→zlc.season.rxdownload4.Progresszlc.season.rxdownload4.downloader.NormalDownloader→zlc.season.rxdownload4.Progresszlc.season.rxdownload4.downloader.RangeDownloader→zlc.season.rxdownload4.Progress
- Direction
- downloader uses zlc.season.rxdownload4, so a change to zlc.season.rxdownload4 can break downloader, while a change to downloader can't break zlc.season.rxdownload4.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→13 notification.NotificationActionService uses task✕
- Connections
- 1 pair of types, where a type in notification.NotificationActionService uses a type in task.
- The types involved
zlc.season.rxdownload4.notification.NotificationActionService.Companion→zlc.season.rxdownload4.task.Task
- Direction
- notification.NotificationActionService uses task, so a change to task can break notification.NotificationActionService, while a change to notification.NotificationActionService can't break task.
- Position
- Below the diagonal: notification.NotificationActionService uses a module listed above it, which is the healthy direction.
16→13 storage.MemoryStorage uses task✕
- Connections
- 1 pair of types, where a type in storage.MemoryStorage uses a type in task.
- The types involved
zlc.season.rxdownload4.storage.MemoryStorage.Companion→zlc.season.rxdownload4.task.Task
- Direction
- storage.MemoryStorage uses task, so a change to task can break storage.MemoryStorage, while a change to storage.MemoryStorage can't break task.
- Position
- Below the diagonal: storage.MemoryStorage uses a module listed above it, which is the healthy direction.
17→8 zlc.season.rxdownload4 uses validator✕
- Connections
- 1 pair of types, where a type in zlc.season.rxdownload4 uses a type in validator.
- The types involved
zlc.season.rxdownload4.RxDownloadKt→zlc.season.rxdownload4.validator.Validator
- Direction
- zlc.season.rxdownload4 uses validator, so a change to validator can break zlc.season.rxdownload4, while a change to zlc.season.rxdownload4 can't break validator.
- Position
- Below the diagonal: zlc.season.rxdownload4 uses a module listed above it, which is the healthy direction.
17→9 zlc.season.rxdownload4 uses request✕
- Connections
- 1 pair of types, where a type in zlc.season.rxdownload4 uses a type in request.
- The types involved
zlc.season.rxdownload4.RxDownloadKt→zlc.season.rxdownload4.request.Request
- Direction
- zlc.season.rxdownload4 uses request, so a change to request can break zlc.season.rxdownload4, while a change to zlc.season.rxdownload4 can't break request.
- Position
- Below the diagonal: zlc.season.rxdownload4 uses a module listed above it, which is the healthy direction.
17→10 zlc.season.rxdownload4 uses storage✕
- Connections
- 1 pair of types, where a type in zlc.season.rxdownload4 uses a type in storage.
- The types involved
zlc.season.rxdownload4.RxDownloadKt→zlc.season.rxdownload4.storage.Storage
- Direction
- zlc.season.rxdownload4 uses storage, so a change to storage can break zlc.season.rxdownload4, while a change to zlc.season.rxdownload4 can't break storage.
- Position
- Below the diagonal: zlc.season.rxdownload4 uses a module listed above it, which is the healthy direction.
17→11 zlc.season.rxdownload4 uses watcher✕
- Connections
- 1 pair of types, where a type in zlc.season.rxdownload4 uses a type in watcher.
- The types involved
zlc.season.rxdownload4.RxDownloadKt→zlc.season.rxdownload4.watcher.Watcher
- Direction
- zlc.season.rxdownload4 uses watcher, so a change to watcher can break zlc.season.rxdownload4, while a change to zlc.season.rxdownload4 can't break watcher.
- Position
- Below the diagonal: zlc.season.rxdownload4 uses a module listed above it, which is the healthy direction.
17→14 zlc.season.rxdownload4 uses downloader✕
- Connections
- 1 pair of types, where a type in zlc.season.rxdownload4 uses a type in downloader.
- The types involved
zlc.season.rxdownload4.RxDownloadKt→zlc.season.rxdownload4.downloader.Dispatcher
- Direction
- zlc.season.rxdownload4 uses downloader, so a change to downloader can break zlc.season.rxdownload4, while a change to zlc.season.rxdownload4 can't break downloader.
- Position
- Below the diagonal: zlc.season.rxdownload4 uses a module listed above it, which is the healthy direction.
18→8 manager uses validator✕
- Connections
- 2 pairs of types, where a type in manager uses a type in validator.
- The types involved
zlc.season.rxdownload4.manager.RxDownloadManagerKt→zlc.season.rxdownload4.validator.Validatorzlc.season.rxdownload4.manager.TaskManagerPool→zlc.season.rxdownload4.validator.Validator
- Direction
- manager uses validator, so a change to validator can break manager, while a change to manager can't break validator.
- Position
- Below the diagonal: manager uses a module listed above it, which is the healthy direction.
18→9 manager uses request✕
- Connections
- 2 pairs of types, where a type in manager uses a type in request.
- The types involved
zlc.season.rxdownload4.manager.RxDownloadManagerKt→zlc.season.rxdownload4.request.Requestzlc.season.rxdownload4.manager.TaskManagerPool→zlc.season.rxdownload4.request.Request
- Direction
- manager uses request, so a change to request can break manager, while a change to manager can't break request.
- Position
- Below the diagonal: manager uses a module listed above it, which is the healthy direction.
18→10 manager uses storage✕
- Connections
- 3 pairs of types, where a type in manager uses a type in storage.
- The types involved
zlc.season.rxdownload4.manager.RxDownloadManagerKt→zlc.season.rxdownload4.storage.Storagezlc.season.rxdownload4.manager.TaskManager→zlc.season.rxdownload4.storage.Storagezlc.season.rxdownload4.manager.TaskManagerPool→zlc.season.rxdownload4.storage.Storage
- Direction
- manager uses storage, so a change to storage can break manager, while a change to manager can't break storage.
- Position
- Below the diagonal: manager uses a module listed above it, which is the healthy direction.
18→11 manager uses watcher✕
- Connections
- 2 pairs of types, where a type in manager uses a type in watcher.
- The types involved
zlc.season.rxdownload4.manager.RxDownloadManagerKt→zlc.season.rxdownload4.watcher.Watcherzlc.season.rxdownload4.manager.TaskManagerPool→zlc.season.rxdownload4.watcher.Watcher
- Direction
- manager uses watcher, so a change to watcher can break manager, while a change to manager can't break watcher.
- Position
- Below the diagonal: manager uses a module listed above it, which is the healthy direction.
18→13 manager uses task✕
- Connections
- 8 pairs of types, where a type in manager uses a type in task.
- The types involved
zlc.season.rxdownload4.manager.EmptyNotification→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.manager.EmptyRecorder→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.manager.NotificationCreator→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.manager.NotificationHelperKt→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.manager.StatusHandler→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.manager.TaskManager→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.manager.TaskManagerPool→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.manager.TaskRecorder→zlc.season.rxdownload4.task.Task
- Direction
- manager uses task, so a change to task can break manager, while a change to manager can't break task.
- Position
- Below the diagonal: manager uses a module listed above it, which is the healthy direction.
18→14 manager uses downloader✕
- Connections
- 2 pairs of types, where a type in manager uses a type in downloader.
- The types involved
zlc.season.rxdownload4.manager.RxDownloadManagerKt→zlc.season.rxdownload4.downloader.Dispatcherzlc.season.rxdownload4.manager.TaskManagerPool→zlc.season.rxdownload4.downloader.Dispatcher
- Direction
- manager uses downloader, so a change to downloader can break manager, while a change to manager can't break downloader.
- Position
- Below the diagonal: manager uses a module listed above it, which is the healthy direction.
18→17 manager uses zlc.season.rxdownload4✕
- Connections
- 3 pairs of types, where a type in manager uses a type in zlc.season.rxdownload4.
- The types involved
zlc.season.rxdownload4.manager.Status→zlc.season.rxdownload4.Progresszlc.season.rxdownload4.manager.StatusHandler→zlc.season.rxdownload4.Progresszlc.season.rxdownload4.manager.TaskManager→zlc.season.rxdownload4.Progress
- Direction
- manager uses zlc.season.rxdownload4, so a change to zlc.season.rxdownload4 can break manager, while a change to manager can't break zlc.season.rxdownload4.
- Position
- Below the diagonal: manager uses a module listed above it, which is the healthy direction.
19→18 manager.BasicTaskLimitation uses manager✕
- Connections
- 2 pairs of types, where a type in manager.BasicTaskLimitation uses a type in manager.
- The types involved
zlc.season.rxdownload4.manager.BasicTaskLimitation.Companion→zlc.season.rxdownload4.manager.BasicTaskLimitationzlc.season.rxdownload4.manager.BasicTaskLimitation.Companion→zlc.season.rxdownload4.manager.TaskLimitation
- Direction
- manager.BasicTaskLimitation uses manager, so a change to manager can break manager.BasicTaskLimitation, while a change to manager.BasicTaskLimitation can't break manager.
- Position
- Below the diagonal: manager.BasicTaskLimitation uses a module listed above it, which is the healthy direction.
20→13 notification.SimpleNotificationCreator uses task✕
- Connections
- 1 pair of types, where a type in notification.SimpleNotificationCreator uses a type in task.
- The types involved
zlc.season.rxdownload4.notification.SimpleNotificationCreator.BuilderHelper→zlc.season.rxdownload4.task.Task
- Direction
- notification.SimpleNotificationCreator uses task, so a change to task can break notification.SimpleNotificationCreator, while a change to notification.SimpleNotificationCreator can't break task.
- Position
- Below the diagonal: notification.SimpleNotificationCreator uses a module listed above it, which is the healthy direction.
20→18 notification.SimpleNotificationCreator uses manager✕
- Connections
- 1 pair of types, where a type in notification.SimpleNotificationCreator uses a type in manager.
- The types involved
zlc.season.rxdownload4.notification.SimpleNotificationCreator.BuilderHelper→zlc.season.rxdownload4.manager.Status
- Direction
- notification.SimpleNotificationCreator uses manager, so a change to manager can break notification.SimpleNotificationCreator, while a change to notification.SimpleNotificationCreator can't break manager.
- Position
- Below the diagonal: notification.SimpleNotificationCreator uses a module listed above it, which is the healthy direction.
21→13 recorder uses task✕
- Connections
- 3 pairs of types, where a type in recorder uses a type in task.
- The types involved
zlc.season.rxdownload4.recorder.RoomRecorder→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.recorder.RxDownloadRecorder→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.recorder.TaskEntity→zlc.season.rxdownload4.task.Task
- Direction
- recorder uses task, so a change to task can break recorder, while a change to recorder can't break task.
- Position
- Below the diagonal: recorder uses a module listed above it, which is the healthy direction.
21→17 recorder uses zlc.season.rxdownload4✕
- Connections
- 1 pair of types, where a type in recorder uses a type in zlc.season.rxdownload4.
- The types involved
zlc.season.rxdownload4.recorder.TaskEntity→zlc.season.rxdownload4.Progress
- Direction
- recorder uses zlc.season.rxdownload4, so a change to zlc.season.rxdownload4 can break recorder, while a change to recorder can't break zlc.season.rxdownload4.
- Position
- Below the diagonal: recorder uses a module listed above it, which is the healthy direction.
21→18 recorder uses manager✕
- Connections
- 8 pairs of types, where a type in recorder uses a type in manager.
- The types involved
zlc.season.rxdownload4.recorder.RecorderUtilKt→zlc.season.rxdownload4.manager.Statuszlc.season.rxdownload4.recorder.RoomRecorder→zlc.season.rxdownload4.manager.Statuszlc.season.rxdownload4.recorder.RoomRecorder→zlc.season.rxdownload4.manager.TaskRecorderzlc.season.rxdownload4.recorder.RxDownloadRecorder→zlc.season.rxdownload4.manager.Statuszlc.season.rxdownload4.recorder.RxDownloadRecorder→zlc.season.rxdownload4.manager.TaskManagerzlc.season.rxdownload4.recorder.StatusConverter→zlc.season.rxdownload4.manager.Statuszlc.season.rxdownload4.recorder.TaskDao→zlc.season.rxdownload4.manager.Statuszlc.season.rxdownload4.recorder.TaskEntity→zlc.season.rxdownload4.manager.Status
- Direction
- recorder uses manager, so a change to manager can break recorder, while a change to recorder can't break manager.
- Position
- Below the diagonal: recorder uses a module listed above it, which is the healthy direction.
22→13 notification uses task✕
- Connections
- 2 pairs of types, where a type in notification uses a type in task.
- The types involved
zlc.season.rxdownload4.notification.NotificationUtilKt→zlc.season.rxdownload4.task.Taskzlc.season.rxdownload4.notification.SimpleNotificationCreator→zlc.season.rxdownload4.task.Task
- Direction
- notification uses task, so a change to task can break notification, while a change to notification can't break task.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
22→17 notification uses zlc.season.rxdownload4✕
- Connections
- 1 pair of types, where a type in notification uses a type in zlc.season.rxdownload4.
- The types involved
zlc.season.rxdownload4.notification.NotificationUtilKt→zlc.season.rxdownload4.Progress
- Direction
- notification uses zlc.season.rxdownload4, so a change to zlc.season.rxdownload4 can break notification, while a change to notification can't break zlc.season.rxdownload4.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
22→18 notification uses manager✕
- Connections
- 2 pairs of types, where a type in notification uses a type in manager.
- The types involved
zlc.season.rxdownload4.notification.SimpleNotificationCreator→zlc.season.rxdownload4.manager.NotificationCreatorzlc.season.rxdownload4.notification.SimpleNotificationCreator→zlc.season.rxdownload4.manager.Status
- Direction
- notification uses manager, so a change to manager can break notification, while a change to notification can't break manager.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
22→20 notification uses notification.SimpleNotificationCreator✕
- Connections
- 1 pair of types, where a type in notification uses a type in notification.SimpleNotificationCreator.
- The types involved
zlc.season.rxdownload4.notification.SimpleNotificationCreator→zlc.season.rxdownload4.notification.SimpleNotificationCreator.BuilderHelper
- Direction
- notification uses notification.SimpleNotificationCreator, so a change to notification.SimpleNotificationCreator can break notification, while a change to notification can't break notification.SimpleNotificationCreator.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
23→21 recorder.TaskDataBase uses recorder✕
- Connections
- 1 pair of types, where a type in recorder.TaskDataBase uses a type in recorder.
- The types involved
zlc.season.rxdownload4.recorder.TaskDataBase.Companion→zlc.season.rxdownload4.recorder.TaskDataBase
- Direction
- recorder.TaskDataBase uses recorder, so a change to recorder can break recorder.TaskDataBase, while a change to recorder.TaskDataBase can't break recorder.
- Position
- Below the diagonal: recorder.TaskDataBase 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
Roadmap
Top priorities: Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with SafeIterableMap.java, RangeDownloader.kt, RangeTmpFile.kt; Add a CI workflow that builds and runs the test suite on every push/PR; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with SafeIterableMap.java, RangeDownloader.kt, RangeTmpFile.kt. | +10.3 pts | Medium | Knowledge Freshness |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +7.8 pts | Medium | CI/CD gates |
| 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. | +6.9 pts | Medium | Architecture documentation |
| Swallowed exception (empty catch) | +2.7 pts | Medium | Exception handling |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.9 pts | Low | Knowledge Freshness |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.6 pts | Medium | Documentation (README) |
| Resolve the 1 Off the main sequence finding(s) in Coupling. | +0.1 pts | Low | Coupling |
| Resolve the 1 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with DemoListItem.kt. | +0.1 pts | Low | Code Duplication |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| rxdownload4/src/main/java/zlc/season/rxdownload4/RxDownload.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (15 corresponding lines) |
| rxdownload4/src/main/java/zlc/season/rxdownload4/downloader/NormalDownloader.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| demo/src/main/java/zlc/season/rxdownload/demo/list/DemoListItem.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (13 corresponding lines) |
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 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 36 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, 23 of 29 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java, .kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java, .kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 6 Maven/Gradle manifest(s) were read, stating a version for 37 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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 598 commit(s) sampled, automation and bot accounts excluded). One of them holds 92% of the history; the other 9 hold 0.9% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (rxdownload4-recorder/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected. 2.3 % of the production lines (72 of 3,126) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 3 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 1 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with RxDownload.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with NormalDownloader.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with DemoListItem.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
5 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 4 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 17 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 16 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 6 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 13 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 3126 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 4 build units (Gradle) flagged as possibly oversized/incoherent.
D27 · Navigability
27 % of calls cross a namespace and 17 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `gradlew` (lines 140–141, line 142, line 143, …) — 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.
D34 · Knowledge Freshness
14 of 14 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is rxdownload4-manager/src/main/java/zlc/season/rxdownload4/manager/SafeIterableMap.java. Counted over 14 of the 53 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with SafeIterableMap.java, RangeDownloader.kt, RangeTmpFile.kt. — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: RxDownload.kt↔NormalDownloader.kt 50%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with RxDownload.kt. — One of this dimension's main actionable groups (1 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 37 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
- 1 public type in `zlc.season.rxdownload4.request` is marked as implementation by its own namespace, folder or name: `RequestImpl` (rxdownload4/src/main/java/zlc/season/rxdownload4/request/RequestImpl.kt:11, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — rxdownload4/src/main/java/zlc/season/rxdownload4/request/RequestImpl.kt:11
- 1 public type in `zlc.season.rxdownload4.watcher` is marked as implementation by its own namespace, folder or name: `WatcherImpl` (rxdownload4/src/main/java/zlc/season/rxdownload4/watcher/WatcherImpl.kt:6, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — rxdownload4/src/main/java/zlc/season/rxdownload4/watcher/WatcherImpl.kt:6
What to do
- Hide `zlc.season.rxdownload4.request` (`RequestImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `zlc.season.rxdownload4.watcher` (`WatcherImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `RandomAccessFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.setLength` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `RandomAccessFile(…).use { r -> … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — rxdownload4/src/main/java/zlc/season/rxdownload4/utils/FileUtils.kt:30
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
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. — rxdownload4/src/main/java/zlc/season/rxdownload4/utils/HttpUtil.kt:14
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80% | Strong | Solid. |
| Architecture | 98% | Exemplary | Solid. |
| Maturity | 49% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 42% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 78 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java 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; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~201 lines of test source are present (.java, .kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 6 Maven/Gradle manifest(s) were read, stating a version for 37 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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 — N/A — too few peers to establish a naming convention (852 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Java, Kotlin surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 4 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's JVM source (4 module(s), 47 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — 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
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Serious — 8 finding(s)
- Change coupling: RxDownload.kt ↔ NormalDownloader.kt rxdownload4/src/main/java/zlc/season/rxdownload4/RxDownload.kt:1
- Edited copy of a member (15 corresponding lines) rxdownload4/src/main/java/zlc/season/rxdownload4/RxDownload.kt:44
- Duplicated block (10 lines × 2) rxdownload4/src/main/java/zlc/season/rxdownload4/downloader/NormalDownloader.kt:46
- Edited copy of a member (13 corresponding lines) demo/src/main/java/zlc/season/rxdownload/demo/list/DemoListItem.kt:47
- Off the main sequence: :rxdownload4
- No CI pipeline
- Disposable created and abandoned in the function that made it rxdownload4/src/main/java/zlc/season/rxdownload4/utils/FileUtils.kt:30
- Swallowed exception (empty catch) rxdownload4/src/main/java/zlc/season/rxdownload4/utils/HttpUtil.kt:14
Minor — 21 finding(s)
- Orphaned file rxdownload4-manager/src/main/java/zlc/season/rxdownload4/manager/SafeIterableMap.java:1
- Orphaned file rxdownload4/src/main/java/zlc/season/rxdownload4/downloader/RangeDownloader.kt:1
- Orphaned file rxdownload4/src/main/java/zlc/season/rxdownload4/downloader/RangeTmpFile.kt:1
- Orphaned file rxdownload4-manager/src/main/java/zlc/season/rxdownload4/manager/TaskManager.kt:1
- Orphaned file rxdownload4-recorder/src/main/java/zlc/season/rxdownload4/recorder/RxDownloadRecorder.kt:1
- Orphaned file rxdownload4-notification/src/main/java/zlc/season/rxdownload4/notification/SimpleNotificationCreator.kt:1
- Orphaned file rxdownload4-manager/src/main/java/zlc/season/rxdownload4/manager/RxDownloadManager.kt:1
- Orphaned file rxdownload4/src/main/java/zlc/season/rxdownload4/RxDownload.kt:1
- Orphaned file rxdownload4-manager/src/main/java/zlc/season/rxdownload4/manager/StatusHandler.kt:1
- Orphaned file rxdownload4/src/main/java/zlc/season/rxdownload4/downloader/NormalDownloader.kt:1
- Orphaned file rxdownload4-manager/src/main/java/zlc/season/rxdownload4/manager/TaskManagerPool.kt:1
- Orphaned file rxdownload4-notification/src/main/java/zlc/season/rxdownload4/notification/NotificationActionService.kt:1
- Orphaned file rxdownload4/src/main/java/zlc/season/rxdownload4/utils/HttpUtil.kt:1
- Orphaned file rxdownload4-notification/src/main/java/zlc/season/rxdownload4/notification/NotificationUtil.kt:1
- Implementation type on the public API rxdownload4/src/main/java/zlc/season/rxdownload4/request/RequestImpl.kt:11
- Implementation type on the public API rxdownload4/src/main/java/zlc/season/rxdownload4/watcher/WatcherImpl.kt:6
- Orphaned files with no living knowledge
- No ADRs
- No architecture diagram/doc
- No SAST
- Duplicated predicate rxdownload4/src/main/java/zlc/season/rxdownload4/downloader/NormalDownloader.kt:47
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-9a63e9ba26884296aa1d6a7c47f9ea09/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-9a63e9ba26884296aa1d6a7c47f9ea09/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |