Executive summary
hrkfdn/ncspot is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because it has pipeline tools referenced by a changeable name. It scores 65 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 57, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Restricting the build's access tokens would lift Security and Compliance itself, worth about 2 points. Raising Security and Compliance to 70 would lift the score to about 68.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four pipeline steps run downloads nobody checks, and two known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, checking each download against a checksum and updating the vulnerable packages would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 13,365 lines, about €16,000 to rebuild.
If Security and Compliance rose from 57 to 70, the lowest score rated Strong, the score would rise from 65 to about 68.
New since the last survey: 43 findings
- Cognitive Complexity · Library::fetch_playlists (cognitive 18) src/library.rs
- God Classes · FileTooLong: src/spotify_api.rs src/spotify_api.rs
- Code Duplication · Near-duplicate member pair (31 shared lines) src/model/track.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/spotify_api.rs
- Code Duplication · Edited copy of a member (40 corresponding lines) src/model/album.rs
- Code Duplication · Edited copy of a member (39 corresponding lines) src/library.rs
- Code Duplication · Edited copy of a member (25 corresponding lines) src/model/album.rs
- Code Duplication · Edited copy of a member (36 corresponding lines) src/library.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/model/artist.rs
- Code Duplication · Edited copies of one member (4 members, 25+ corresponding lines) src/library.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/model/artist.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/model/track.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/library.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/authentication.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/ui/playlist.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/model/album.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/serialization.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) src/model/artist.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/sharing.rs
- Code Duplication · Edited copy of a member (6 corresponding lines) src/spotify_api.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/serialization.rs
- Code Duplication · Edited copies of one member (8 members, 10+ corresponding lines) src/spotify_api.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/model/playlist.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/model/album.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/model/album.rs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/model/episode.rs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/model/episode.rs
- Code Duplication · Duplicated block (14 lines × 2) src/ui/cover.rs
- Code Duplication · Duplicated block (12 lines × 6) src/ui/search_results.rs
- Code Duplication · Duplicated block (10–11 lines × 3) src/model/album.rs
- Code Duplication · Duplicated block (11 lines × 2) src/library.rs
- Code Duplication · Duplicated block (11 lines × 2) src/mpris.rs
- Code Duplication · Duplicated block (9–10 lines × 4) src/spotify_api.rs
- Code Duplication · Duplicated block (10 lines × 3) src/model/track.rs
- Code Duplication · Duplicated block (8 lines × 2) src/model/album.rs
- Code Duplication · Duplicated block (7 lines × 3) src/model/album.rs
- Code Duplication · Duplicated block (2–7 lines × 3) src/model/track.rs
- Code Duplication · Duplicated block (7 lines × 2) src/model/track.rs
- Code Duplication · Duplicated block (9 lines × 2) src/ui/listview.rs
- Code Duplication · Duplicated block (5 lines × 2) src/model/album.rs
- Code Duplication · Duplicated block (9 lines × 2) src/model/album.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 20 findings
- Code Duplication · Near-duplicate member pair (31 shared lines) src/model/track.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/spotify_api.rs
- Code Duplication · Duplicated block (13 lines × 2) src/ui/cover.rs
- Code Duplication · Duplicated block (12 lines × 6) src/ui/search_results.rs
- Code Duplication · Duplicated block (10–11 lines × 3) src/model/album.rs
- Code Duplication · Duplicated block (11 lines × 2) src/library.rs
- Code Duplication · Duplicated block (10 lines × 3) src/model/track.rs
- Code Duplication · Duplicated block (10 lines × 2) src/mpris.rs
- Code Duplication · Duplicated block (9 lines × 3) src/model/track.rs
- Code Duplication · Duplicated block (8 lines × 4) src/spotify_api.rs
- Code Duplication · Duplicated block (8 lines × 2) src/model/album.rs
- Code Duplication · Duplicated block (7 lines × 3) src/model/album.rs
- Code Duplication · Duplicated block (2–7 lines × 3) src/model/track.rs
- Code Duplication · Duplicated block (7 lines × 2) src/model/track.rs
- Code Duplication · Duplicated block (5 lines × 2) src/ui/listview.rs
- Code Duplication · Duplicated block (5 lines × 2) src/model/album.rs
- Code Duplication · Duplicated block (9 lines × 3) src/model/album.rs
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0346 REDACTED
- Documentation (README) · README may be stale
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,200 to €26,000, for 87 to 275 hours of work, about 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.9 at a score of 65. 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: 13,365 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 command | 2 events | 3 mpris | 4 spotify_worker | 5 ui.modal | 6 ui.pagination | 7 spotify_api | 8 spotify | 9 queue | 10 traits | 11 model.episode | 12 model.playlist | 13 model.track | 14 ui.help | 15 ui.tabbedview | 16 model.artist | 17 model.show | 18 model.album | 19 library | 20 model.category | 21 model.playable | 22 ui.album | 23 ui.contextmenu | 24 ui.library | 25 ui.listview | 26 ui.search | 27 ui.search_results | 28 config | 29 ipc | 30 ui.artist | 31 ui.browse | 32 ui.playlist | 33 ui.playlists | 34 ui.queue | 35 ui.show | 36 ui.statusbar | 37 commands | 38 ui.cover | 39 ui.layout | 40 application |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 command | ||||||||||||||||||||||||||||||||||||||||
| 2 events | ||||||||||||||||||||||||||||||||||||||||
| 3 mpris | 2 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 4 spotify_worker | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 5 ui.modal | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 ui.pagination | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 spotify_api | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 spotify | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 9 queue | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 10 traits | 2 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 11 model.episode | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 model.playlist | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 13 model.track | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 14 ui.help | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 ui.tabbedview | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 model.artist | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 17 model.show | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 18 model.album | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 19 library | 1 | 1 | 2 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||
| 20 model.category | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 model.playable | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 22 ui.album | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 23 ui.contextmenu | 5 | 5 | 1 | 1 | 4 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 24 ui.library | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 ui.listview | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 26 ui.search | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 27 ui.search_results | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||
| 28 config | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 ipc | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 30 ui.artist | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 31 ui.browse | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 ui.playlist | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 33 ui.playlists | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 34 ui.queue | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 35 ui.show | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 ui.statusbar | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 commands | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 ui.cover | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 ui.layout | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 application | 1 | 1 | 1 | 1 | 1 |
3→2 mpris uses events✕
- Connections
- 2 pairs of types, where a type in mpris uses a type in events.
- The types involved
ncspot.mpris.MprisManager→ncspot.events.EventManagerncspot.mpris.MprisPlayer→ncspot.events.EventManager
- Direction
- mpris uses events, so a change to events can break mpris, while a change to mpris can't break events.
- Position
- Below the diagonal: mpris uses a module listed above it, which is the healthy direction.
3→8 mpris uses spotify part of a loop✕
- Connections
- 2 pairs of types, where a type in mpris uses a type in spotify.
- The types involved
ncspot.mpris.MprisManager→ncspot.spotify.Spotifyncspot.mpris.MprisPlayer→ncspot.spotify.Spotify
- Direction
- mpris uses spotify, so a change to spotify can break mpris, while a change to mpris can't break spotify.
- 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.
3→9 mpris uses queue part of a loop✕
- Connections
- 2 pairs of types, where a type in mpris uses a type in queue.
- The types involved
ncspot.mpris.MprisManager→ncspot.queue.Queuencspot.mpris.MprisPlayer→ncspot.queue.Queue
- Direction
- mpris uses queue, so a change to queue can break mpris, while a change to mpris can't break queue.
- 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.
3→19 mpris uses library part of a loop✕
- Connections
- 2 pairs of types, where a type in mpris uses a type in library.
- The types involved
ncspot.mpris.MprisManager→ncspot.library.Libraryncspot.mpris.MprisPlayer→ncspot.library.Library
- Direction
- mpris uses library, so a change to library can break mpris, while a change to mpris can't break library.
- 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.
4→2 spotify_worker uses events✕
- Connections
- 1 pair of types, where a type in spotify_worker uses a type in events.
- The types involved
ncspot.spotify_worker.Worker→ncspot.events.EventManager
- Direction
- spotify_worker uses events, so a change to events can break spotify_worker, while a change to spotify_worker can't break events.
- Position
- Below the diagonal: spotify_worker uses a module listed above it, which is the healthy direction.
4→28 spotify_worker uses config part of a loop✕
- Connections
- 1 pair of types, where a type in spotify_worker uses a type in config.
- The types involved
ncspot.spotify_worker.Worker→ncspot.config.Config
- Direction
- spotify_worker uses config, so a change to config can break spotify_worker, while a change to spotify_worker can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→2 ui.modal uses events✕
- Connections
- 1 pair of types, where a type in ui.modal uses a type in events.
- The types involved
ncspot.ui.modal.Modal→ncspot.events.Event
- Direction
- ui.modal uses events, so a change to events can break ui.modal, while a change to ui.modal can't break events.
- Position
- Below the diagonal: ui.modal uses a module listed above it, which is the healthy direction.
6→19 ui.pagination uses library part of a loop✕
- Connections
- 1 pair of types, where a type in ui.pagination uses a type in library.
- The types involved
ncspot.ui.pagination.Pagination→ncspot.library.Library
- Direction
- ui.pagination uses library, so a change to library can break ui.pagination, while a change to ui.pagination can't break library.
- 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.
7→6 spotify_api uses ui.pagination✕
- Connections
- 1 pair of types, where a type in spotify_api uses a type in ui.pagination.
- The types involved
ncspot.spotify_api.WebApi→ncspot.ui.pagination.ApiResult
- Direction
- spotify_api uses ui.pagination, so a change to ui.pagination can break spotify_api, while a change to spotify_api can't break ui.pagination.
- Position
- Below the diagonal: spotify_api uses a module listed above it, which is the healthy direction.
8→2 spotify uses events✕
- Connections
- 1 pair of types, where a type in spotify uses a type in events.
- The types involved
ncspot.spotify.Spotify→ncspot.events.EventManager
- Direction
- spotify uses events, so a change to events can break spotify, while a change to spotify can't break events.
- Position
- Below the diagonal: spotify uses a module listed above it, which is the healthy direction.
8→3 spotify uses mpris✕
- Connections
- 2 pairs of types, where a type in spotify uses a type in mpris.
- The types involved
ncspot.spotify.Spotify→ncspot.mpris.MprisCommandncspot.spotify.Spotify→ncspot.mpris.MprisManager
- Direction
- spotify uses mpris, so a change to mpris can break spotify, while a change to spotify can't break mpris.
- Position
- Below the diagonal: spotify uses a module listed above it, which is the healthy direction.
8→4 spotify uses spotify_worker✕
- Connections
- 1 pair of types, where a type in spotify uses a type in spotify_worker.
- The types involved
ncspot.spotify.Spotify→ncspot.spotify_worker.WorkerCommand
- Direction
- spotify uses spotify_worker, so a change to spotify_worker can break spotify, while a change to spotify can't break spotify_worker.
- Position
- Below the diagonal: spotify uses a module listed above it, which is the healthy direction.
8→7 spotify uses spotify_api✕
- Connections
- 1 pair of types, where a type in spotify uses a type in spotify_api.
- The types involved
ncspot.spotify.Spotify→ncspot.spotify_api.WebApi
- Direction
- spotify uses spotify_api, so a change to spotify_api can break spotify, while a change to spotify can't break spotify_api.
- Position
- Below the diagonal: spotify uses a module listed above it, which is the healthy direction.
8→21 spotify uses model.playable part of a loop✕
- Connections
- 1 pair of types, where a type in spotify uses a type in model.playable.
- The types involved
ncspot.spotify.Spotify→ncspot.model.playable.Playable
- Direction
- spotify uses model.playable, so a change to model.playable can break spotify, while a change to spotify can't break model.playable.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→28 spotify uses config part of a loop✕
- Connections
- 1 pair of types, where a type in spotify uses a type in config.
- The types involved
ncspot.spotify.Spotify→ncspot.config.Config
- Direction
- spotify uses config, so a change to config can break spotify, while a change to spotify can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→8 queue uses spotify✕
- Connections
- 1 pair of types, where a type in queue uses a type in spotify.
- The types involved
ncspot.queue.Queue→ncspot.spotify.Spotify
- Direction
- queue uses spotify, so a change to spotify can break queue, while a change to queue can't break spotify.
- Position
- Below the diagonal: queue uses a module listed above it, which is the healthy direction.
9→19 queue uses library part of a loop✕
- Connections
- 1 pair of types, where a type in queue uses a type in library.
- The types involved
ncspot.queue.Queue→ncspot.library.Library
- Direction
- queue uses library, so a change to library can break queue, while a change to queue can't break library.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→21 queue uses model.playable part of a loop✕
- Connections
- 1 pair of types, where a type in queue uses a type in model.playable.
- The types involved
ncspot.queue.Queue→ncspot.model.playable.Playable
- Direction
- queue uses model.playable, so a change to model.playable can break queue, while a change to queue can't break model.playable.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→28 queue uses config part of a loop✕
- Connections
- 1 pair of types, where a type in queue uses a type in config.
- The types involved
ncspot.queue.Queue→ncspot.config.Config
- Direction
- queue uses config, so a change to config can break queue, while a change to queue can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 traits uses command✕
- Connections
- 2 pairs of types, where a type in traits uses a type in command.
- The types involved
ncspot.traits.BoxedViewExt→ncspot.command.Commandncspot.traits.ViewExt→ncspot.command.Command
- Direction
- traits uses command, so a change to command can break traits, while a change to traits can't break command.
- Position
- Below the diagonal: traits uses a module listed above it, which is the healthy direction.
10→2 traits uses events✕
- Connections
- 1 pair of types, where a type in traits uses a type in events.
- The types involved
ncspot.traits.BoxedViewExt→ncspot.events.Event
- Direction
- traits uses events, so a change to events can break traits, while a change to traits can't break events.
- Position
- Below the diagonal: traits uses a module listed above it, which is the healthy direction.
10→9 traits uses queue✕
- Connections
- 1 pair of types, where a type in traits uses a type in queue.
- The types involved
ncspot.traits.ListItem→ncspot.queue.Queue
- Direction
- traits uses queue, so a change to queue can break traits, while a change to traits can't break queue.
- Position
- Below the diagonal: traits uses a module listed above it, which is the healthy direction.
10→13 traits uses model.track part of a loop✕
- Connections
- 1 pair of types, where a type in traits uses a type in model.track.
- The types involved
ncspot.traits.ListItem→ncspot.model.track.Track
- Direction
- traits uses model.track, so a change to model.track can break traits, while a change to traits can't break model.track.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→16 traits uses model.artist part of a loop✕
- Connections
- 1 pair of types, where a type in traits uses a type in model.artist.
- The types involved
ncspot.traits.ListItem→ncspot.model.artist.Artist
- Direction
- traits uses model.artist, so a change to model.artist can break traits, while a change to traits can't break model.artist.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→18 traits uses model.album part of a loop✕
- Connections
- 1 pair of types, where a type in traits uses a type in model.album.
- The types involved
ncspot.traits.ListItem→ncspot.model.album.Album
- Direction
- traits uses model.album, so a change to model.album can break traits, while a change to traits can't break model.album.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→19 traits uses library part of a loop✕
- Connections
- 1 pair of types, where a type in traits uses a type in library.
- The types involved
ncspot.traits.ListItem→ncspot.library.Library
- Direction
- traits uses library, so a change to library can break traits, while a change to traits can't break library.
- 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→9 model.episode uses queue✕
- Connections
- 1 pair of types, where a type in model.episode uses a type in queue.
- The types involved
ncspot.model.episode.Episode→ncspot.queue.Queue
- Direction
- model.episode uses queue, so a change to queue can break model.episode, while a change to model.episode can't break queue.
- Position
- Below the diagonal: model.episode uses a module listed above it, which is the healthy direction.
11→10 model.episode uses traits✕
- Connections
- 1 pair of types, where a type in model.episode uses a type in traits.
- The types involved
ncspot.model.episode.Episode→ncspot.traits.ListItem
- Direction
- model.episode uses traits, so a change to traits can break model.episode, while a change to model.episode can't break traits.
- Position
- Below the diagonal: model.episode uses a module listed above it, which is the healthy direction.
11→19 model.episode uses library part of a loop✕
- Connections
- 1 pair of types, where a type in model.episode uses a type in library.
- The types involved
ncspot.model.episode.Episode→ncspot.library.Library
- Direction
- model.episode uses library, so a change to library can break model.episode, while a change to model.episode can't break library.
- 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→1 model.playlist uses command✕
- Connections
- 2 pairs of types, where a type in model.playlist uses a type in command.
- The types involved
ncspot.model.playlist.Playlist→ncspot.command.SortDirectionncspot.model.playlist.Playlist→ncspot.command.SortKey
- Direction
- model.playlist uses command, so a change to command can break model.playlist, while a change to model.playlist can't break command.
- Position
- Below the diagonal: model.playlist uses a module listed above it, which is the healthy direction.
12→8 model.playlist uses spotify✕
- Connections
- 1 pair of types, where a type in model.playlist uses a type in spotify.
- The types involved
ncspot.model.playlist.Playlist→ncspot.spotify.Spotify
- Direction
- model.playlist uses spotify, so a change to spotify can break model.playlist, while a change to model.playlist can't break spotify.
- Position
- Below the diagonal: model.playlist uses a module listed above it, which is the healthy direction.
12→9 model.playlist uses queue✕
- Connections
- 1 pair of types, where a type in model.playlist uses a type in queue.
- The types involved
ncspot.model.playlist.Playlist→ncspot.queue.Queue
- Direction
- model.playlist uses queue, so a change to queue can break model.playlist, while a change to model.playlist can't break queue.
- Position
- Below the diagonal: model.playlist uses a module listed above it, which is the healthy direction.
12→10 model.playlist uses traits✕
- Connections
- 1 pair of types, where a type in model.playlist uses a type in traits.
- The types involved
ncspot.model.playlist.Playlist→ncspot.traits.ListItem
- Direction
- model.playlist uses traits, so a change to traits can break model.playlist, while a change to model.playlist can't break traits.
- Position
- Below the diagonal: model.playlist uses a module listed above it, which is the healthy direction.
12→19 model.playlist uses library part of a loop✕
- Connections
- 1 pair of types, where a type in model.playlist uses a type in library.
- The types involved
ncspot.model.playlist.Playlist→ncspot.library.Library
- Direction
- model.playlist uses library, so a change to library can break model.playlist, while a change to model.playlist can't break library.
- 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→21 model.playlist uses model.playable part of a loop✕
- Connections
- 1 pair of types, where a type in model.playlist uses a type in model.playable.
- The types involved
ncspot.model.playlist.Playlist→ncspot.model.playable.Playable
- Direction
- model.playlist uses model.playable, so a change to model.playable can break model.playlist, while a change to model.playlist can't break model.playable.
- 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→9 model.track uses queue✕
- Connections
- 1 pair of types, where a type in model.track uses a type in queue.
- The types involved
ncspot.model.track.Track→ncspot.queue.Queue
- Direction
- model.track uses queue, so a change to queue can break model.track, while a change to model.track can't break queue.
- Position
- Below the diagonal: model.track uses a module listed above it, which is the healthy direction.
13→10 model.track uses traits✕
- Connections
- 1 pair of types, where a type in model.track uses a type in traits.
- The types involved
ncspot.model.track.Track→ncspot.traits.ListItem
- Direction
- model.track uses traits, so a change to traits can break model.track, while a change to model.track can't break traits.
- Position
- Below the diagonal: model.track uses a module listed above it, which is the healthy direction.
13→16 model.track uses model.artist part of a loop✕
- Connections
- 1 pair of types, where a type in model.track uses a type in model.artist.
- The types involved
ncspot.model.track.Track→ncspot.model.artist.Artist
- Direction
- model.track uses model.artist, so a change to model.artist can break model.track, while a change to model.track can't break model.artist.
- 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→18 model.track uses model.album part of a loop✕
- Connections
- 1 pair of types, where a type in model.track uses a type in model.album.
- The types involved
ncspot.model.track.Track→ncspot.model.album.Album
- Direction
- model.track uses model.album, so a change to model.album can break model.track, while a change to model.track can't break model.album.
- 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→19 model.track uses library part of a loop✕
- Connections
- 1 pair of types, where a type in model.track uses a type in library.
- The types involved
ncspot.model.track.Track→ncspot.library.Library
- Direction
- model.track uses library, so a change to library can break model.track, while a change to model.track can't break library.
- 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→1 ui.help uses command✕
- Connections
- 1 pair of types, where a type in ui.help uses a type in command.
- The types involved
ncspot.ui.help.HelpView→ncspot.command.Command
- Direction
- ui.help uses command, so a change to command can break ui.help, while a change to ui.help can't break command.
- Position
- Below the diagonal: ui.help uses a module listed above it, which is the healthy direction.
14→10 ui.help uses traits✕
- Connections
- 1 pair of types, where a type in ui.help uses a type in traits.
- The types involved
ncspot.ui.help.HelpView→ncspot.traits.ViewExt
- Direction
- ui.help uses traits, so a change to traits can break ui.help, while a change to ui.help can't break traits.
- Position
- Below the diagonal: ui.help uses a module listed above it, which is the healthy direction.
15→1 ui.tabbedview uses command✕
- Connections
- 1 pair of types, where a type in ui.tabbedview uses a type in command.
- The types involved
ncspot.ui.tabbedview.TabbedView→ncspot.command.Command
- Direction
- ui.tabbedview uses command, so a change to command can break ui.tabbedview, while a change to ui.tabbedview can't break command.
- Position
- Below the diagonal: ui.tabbedview uses a module listed above it, which is the healthy direction.
15→2 ui.tabbedview uses events✕
- Connections
- 1 pair of types, where a type in ui.tabbedview uses a type in events.
- The types involved
ncspot.ui.tabbedview.TabbedView→ncspot.events.Event
- Direction
- ui.tabbedview uses events, so a change to events can break ui.tabbedview, while a change to ui.tabbedview can't break events.
- Position
- Below the diagonal: ui.tabbedview uses a module listed above it, which is the healthy direction.
15→10 ui.tabbedview uses traits✕
- Connections
- 1 pair of types, where a type in ui.tabbedview uses a type in traits.
- The types involved
ncspot.ui.tabbedview.TabbedView→ncspot.traits.ViewExt
- Direction
- ui.tabbedview uses traits, so a change to traits can break ui.tabbedview, while a change to ui.tabbedview can't break traits.
- Position
- Below the diagonal: ui.tabbedview uses a module listed above it, which is the healthy direction.
16→8 model.artist uses spotify✕
- Connections
- 1 pair of types, where a type in model.artist uses a type in spotify.
- The types involved
ncspot.model.artist.Artist→ncspot.spotify.Spotify
- Direction
- model.artist uses spotify, so a change to spotify can break model.artist, while a change to model.artist can't break spotify.
- Position
- Below the diagonal: model.artist uses a module listed above it, which is the healthy direction.
16→9 model.artist uses queue✕
- Connections
- 1 pair of types, where a type in model.artist uses a type in queue.
- The types involved
ncspot.model.artist.Artist→ncspot.queue.Queue
- Direction
- model.artist uses queue, so a change to queue can break model.artist, while a change to model.artist can't break queue.
- Position
- Below the diagonal: model.artist uses a module listed above it, which is the healthy direction.
16→10 model.artist uses traits✕
- Connections
- 1 pair of types, where a type in model.artist uses a type in traits.
- The types involved
ncspot.model.artist.Artist→ncspot.traits.ListItem
- Direction
- model.artist uses traits, so a change to traits can break model.artist, while a change to model.artist can't break traits.
- Position
- Below the diagonal: model.artist uses a module listed above it, which is the healthy direction.
16→13 model.artist uses model.track✕
- Connections
- 1 pair of types, where a type in model.artist uses a type in model.track.
- The types involved
ncspot.model.artist.Artist→ncspot.model.track.Track
- Direction
- model.artist uses model.track, so a change to model.track can break model.artist, while a change to model.artist can't break model.track.
- Position
- Below the diagonal: model.artist uses a module listed above it, which is the healthy direction.
16→19 model.artist uses library part of a loop✕
- Connections
- 1 pair of types, where a type in model.artist uses a type in library.
- The types involved
ncspot.model.artist.Artist→ncspot.library.Library
- Direction
- model.artist uses library, so a change to library can break model.artist, while a change to model.artist can't break library.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→8 model.show uses spotify✕
- Connections
- 1 pair of types, where a type in model.show uses a type in spotify.
- The types involved
ncspot.model.show.Show→ncspot.spotify.Spotify
- Direction
- model.show uses spotify, so a change to spotify can break model.show, while a change to model.show can't break spotify.
- Position
- Below the diagonal: model.show uses a module listed above it, which is the healthy direction.
17→9 model.show uses queue✕
- Connections
- 1 pair of types, where a type in model.show uses a type in queue.
- The types involved
ncspot.model.show.Show→ncspot.queue.Queue
- Direction
- model.show uses queue, so a change to queue can break model.show, while a change to model.show can't break queue.
- Position
- Below the diagonal: model.show uses a module listed above it, which is the healthy direction.
17→10 model.show uses traits✕
- Connections
- 1 pair of types, where a type in model.show uses a type in traits.
- The types involved
ncspot.model.show.Show→ncspot.traits.ListItem
- Direction
- model.show uses traits, so a change to traits can break model.show, while a change to model.show can't break traits.
- Position
- Below the diagonal: model.show uses a module listed above it, which is the healthy direction.
17→11 model.show uses model.episode✕
- Connections
- 1 pair of types, where a type in model.show uses a type in model.episode.
- The types involved
ncspot.model.show.Show→ncspot.model.episode.Episode
- Direction
- model.show uses model.episode, so a change to model.episode can break model.show, while a change to model.show can't break model.episode.
- Position
- Below the diagonal: model.show uses a module listed above it, which is the healthy direction.
17→19 model.show uses library part of a loop✕
- Connections
- 1 pair of types, where a type in model.show uses a type in library.
- The types involved
ncspot.model.show.Show→ncspot.library.Library
- Direction
- model.show uses library, so a change to library can break model.show, while a change to model.show can't break library.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→8 model.album uses spotify✕
- Connections
- 1 pair of types, where a type in model.album uses a type in spotify.
- The types involved
ncspot.model.album.Album→ncspot.spotify.Spotify
- Direction
- model.album uses spotify, so a change to spotify can break model.album, while a change to model.album can't break spotify.
- Position
- Below the diagonal: model.album uses a module listed above it, which is the healthy direction.
18→9 model.album uses queue✕
- Connections
- 1 pair of types, where a type in model.album uses a type in queue.
- The types involved
ncspot.model.album.Album→ncspot.queue.Queue
- Direction
- model.album uses queue, so a change to queue can break model.album, while a change to model.album can't break queue.
- Position
- Below the diagonal: model.album uses a module listed above it, which is the healthy direction.
18→10 model.album uses traits✕
- Connections
- 1 pair of types, where a type in model.album uses a type in traits.
- The types involved
ncspot.model.album.Album→ncspot.traits.ListItem
- Direction
- model.album uses traits, so a change to traits can break model.album, while a change to model.album can't break traits.
- Position
- Below the diagonal: model.album uses a module listed above it, which is the healthy direction.
18→13 model.album uses model.track✕
- Connections
- 1 pair of types, where a type in model.album uses a type in model.track.
- The types involved
ncspot.model.album.Album→ncspot.model.track.Track
- Direction
- model.album uses model.track, so a change to model.track can break model.album, while a change to model.album can't break model.track.
- Position
- Below the diagonal: model.album uses a module listed above it, which is the healthy direction.
18→16 model.album uses model.artist✕
- Connections
- 1 pair of types, where a type in model.album uses a type in model.artist.
- The types involved
ncspot.model.album.Album→ncspot.model.artist.Artist
- Direction
- model.album uses model.artist, so a change to model.artist can break model.album, while a change to model.album can't break model.artist.
- Position
- Below the diagonal: model.album uses a module listed above it, which is the healthy direction.
18→19 model.album uses library part of a loop✕
- Connections
- 1 pair of types, where a type in model.album uses a type in library.
- The types involved
ncspot.model.album.Album→ncspot.library.Library
- Direction
- model.album uses library, so a change to library can break model.album, while a change to model.album can't break library.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→2 library uses events✕
- Connections
- 1 pair of types, where a type in library uses a type in events.
- The types involved
ncspot.library.Library→ncspot.events.EventManager
- Direction
- library uses events, so a change to events can break library, while a change to library can't break events.
- Position
- Below the diagonal: library uses a module listed above it, which is the healthy direction.
19→8 library uses spotify✕
- Connections
- 1 pair of types, where a type in library uses a type in spotify.
- The types involved
ncspot.library.Library→ncspot.spotify.Spotify
- Direction
- library uses spotify, so a change to spotify can break library, while a change to library can't break spotify.
- Position
- Below the diagonal: library uses a module listed above it, which is the healthy direction.
19→12 library uses model.playlist✕
- Connections
- 2 pairs of types, where a type in library uses a type in model.playlist.
- The types involved
ncspot.library.Library→ncspot.model.playlist.Playlistncspot.library.library$module→ncspot.model.playlist.Playlist
- Direction
- library uses model.playlist, so a change to model.playlist can break library, while a change to library can't break model.playlist.
- Position
- Below the diagonal: library uses a module listed above it, which is the healthy direction.
19→13 library uses model.track✕
- Connections
- 1 pair of types, where a type in library uses a type in model.track.
- The types involved
ncspot.library.Library→ncspot.model.track.Track
- Direction
- library uses model.track, so a change to model.track can break library, while a change to library can't break model.track.
- Position
- Below the diagonal: library uses a module listed above it, which is the healthy direction.
19→16 library uses model.artist✕
- Connections
- 1 pair of types, where a type in library uses a type in model.artist.
- The types involved
ncspot.library.Library→ncspot.model.artist.Artist
- Direction
- library uses model.artist, so a change to model.artist can break library, while a change to library can't break model.artist.
- Position
- Below the diagonal: library uses a module listed above it, which is the healthy direction.
19→17 library uses model.show✕
- Connections
- 1 pair of types, where a type in library uses a type in model.show.
- The types involved
ncspot.library.Library→ncspot.model.show.Show
- Direction
- library uses model.show, so a change to model.show can break library, while a change to library can't break model.show.
- Position
- Below the diagonal: library uses a module listed above it, which is the healthy direction.
19→18 library uses model.album✕
- Connections
- 2 pairs of types, where a type in library uses a type in model.album.
- The types involved
ncspot.library.Library→ncspot.model.album.Albumncspot.library.library$module→ncspot.model.album.Album
- Direction
- library uses model.album, so a change to model.album can break library, while a change to library can't break model.album.
- Position
- Below the diagonal: library uses a module listed above it, which is the healthy direction.
19→21 library uses model.playable part of a loop✕
- Connections
- 1 pair of types, where a type in library uses a type in model.playable.
- The types involved
ncspot.library.Library→ncspot.model.playable.Playable
- Direction
- library uses model.playable, so a change to model.playable can break library, while a change to library can't break model.playable.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→28 library uses config part of a loop✕
- Connections
- 1 pair of types, where a type in library uses a type in config.
- The types involved
ncspot.library.Library→ncspot.config.Config
- Direction
- library uses config, so a change to config can break library, while a change to library can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→9 model.category uses queue✕
- Connections
- 1 pair of types, where a type in model.category uses a type in queue.
- The types involved
ncspot.model.category.Category→ncspot.queue.Queue
- Direction
- model.category uses queue, so a change to queue can break model.category, while a change to model.category can't break queue.
- Position
- Below the diagonal: model.category uses a module listed above it, which is the healthy direction.
20→10 model.category uses traits✕
- Connections
- 1 pair of types, where a type in model.category uses a type in traits.
- The types involved
ncspot.model.category.Category→ncspot.traits.ListItem
- Direction
- model.category uses traits, so a change to traits can break model.category, while a change to model.category can't break traits.
- Position
- Below the diagonal: model.category uses a module listed above it, which is the healthy direction.
20→19 model.category uses library✕
- Connections
- 1 pair of types, where a type in model.category uses a type in library.
- The types involved
ncspot.model.category.Category→ncspot.library.Library
- Direction
- model.category uses library, so a change to library can break model.category, while a change to model.category can't break library.
- Position
- Below the diagonal: model.category uses a module listed above it, which is the healthy direction.
21→9 model.playable uses queue✕
- Connections
- 1 pair of types, where a type in model.playable uses a type in queue.
- The types involved
ncspot.model.playable.Playable→ncspot.queue.Queue
- Direction
- model.playable uses queue, so a change to queue can break model.playable, while a change to model.playable can't break queue.
- Position
- Below the diagonal: model.playable uses a module listed above it, which is the healthy direction.
21→10 model.playable uses traits✕
- Connections
- 1 pair of types, where a type in model.playable uses a type in traits.
- The types involved
ncspot.model.playable.Playable→ncspot.traits.ListItem
- Direction
- model.playable uses traits, so a change to traits can break model.playable, while a change to model.playable can't break traits.
- Position
- Below the diagonal: model.playable uses a module listed above it, which is the healthy direction.
21→13 model.playable uses model.track✕
- Connections
- 1 pair of types, where a type in model.playable uses a type in model.track.
- The types involved
ncspot.model.playable.Playable→ncspot.model.track.Track
- Direction
- model.playable uses model.track, so a change to model.track can break model.playable, while a change to model.playable can't break model.track.
- Position
- Below the diagonal: model.playable uses a module listed above it, which is the healthy direction.
21→16 model.playable uses model.artist✕
- Connections
- 1 pair of types, where a type in model.playable uses a type in model.artist.
- The types involved
ncspot.model.playable.Playable→ncspot.model.artist.Artist
- Direction
- model.playable uses model.artist, so a change to model.artist can break model.playable, while a change to model.playable can't break model.artist.
- Position
- Below the diagonal: model.playable uses a module listed above it, which is the healthy direction.
21→18 model.playable uses model.album✕
- Connections
- 1 pair of types, where a type in model.playable uses a type in model.album.
- The types involved
ncspot.model.playable.Playable→ncspot.model.album.Album
- Direction
- model.playable uses model.album, so a change to model.album can break model.playable, while a change to model.playable can't break model.album.
- Position
- Below the diagonal: model.playable uses a module listed above it, which is the healthy direction.
21→19 model.playable uses library✕
- Connections
- 1 pair of types, where a type in model.playable uses a type in library.
- The types involved
ncspot.model.playable.Playable→ncspot.library.Library
- Direction
- model.playable uses library, so a change to library can break model.playable, while a change to model.playable can't break library.
- Position
- Below the diagonal: model.playable uses a module listed above it, which is the healthy direction.
22→1 ui.album uses command✕
- Connections
- 1 pair of types, where a type in ui.album uses a type in command.
- The types involved
ncspot.ui.album.AlbumView→ncspot.command.Command
- Direction
- ui.album uses command, so a change to command can break ui.album, while a change to ui.album can't break command.
- Position
- Below the diagonal: ui.album uses a module listed above it, which is the healthy direction.
22→9 ui.album uses queue✕
- Connections
- 1 pair of types, where a type in ui.album uses a type in queue.
- The types involved
ncspot.ui.album.AlbumView→ncspot.queue.Queue
- Direction
- ui.album uses queue, so a change to queue can break ui.album, while a change to ui.album can't break queue.
- Position
- Below the diagonal: ui.album uses a module listed above it, which is the healthy direction.
22→10 ui.album uses traits✕
- Connections
- 1 pair of types, where a type in ui.album uses a type in traits.
- The types involved
ncspot.ui.album.AlbumView→ncspot.traits.ViewExt
- Direction
- ui.album uses traits, so a change to traits can break ui.album, while a change to ui.album can't break traits.
- Position
- Below the diagonal: ui.album uses a module listed above it, which is the healthy direction.
22→15 ui.album uses ui.tabbedview✕
- Connections
- 1 pair of types, where a type in ui.album uses a type in ui.tabbedview.
- The types involved
ncspot.ui.album.AlbumView→ncspot.ui.tabbedview.TabbedView
- Direction
- ui.album uses ui.tabbedview, so a change to ui.tabbedview can break ui.album, while a change to ui.album can't break ui.tabbedview.
- Position
- Below the diagonal: ui.album uses a module listed above it, which is the healthy direction.
22→18 ui.album uses model.album✕
- Connections
- 1 pair of types, where a type in ui.album uses a type in model.album.
- The types involved
ncspot.ui.album.AlbumView→ncspot.model.album.Album
- Direction
- ui.album uses model.album, so a change to model.album can break ui.album, while a change to ui.album can't break model.album.
- Position
- Below the diagonal: ui.album uses a module listed above it, which is the healthy direction.
22→19 ui.album uses library✕
- Connections
- 1 pair of types, where a type in ui.album uses a type in library.
- The types involved
ncspot.ui.album.AlbumView→ncspot.library.Library
- Direction
- ui.album uses library, so a change to library can break ui.album, while a change to ui.album can't break library.
- Position
- Below the diagonal: ui.album uses a module listed above it, which is the healthy direction.
23→1 ui.contextmenu uses command✕
- Connections
- 5 pairs of types, where a type in ui.contextmenu uses a type in command.
- The types involved
ncspot.ui.contextmenu.AddToPlaylistMenu→ncspot.command.Commandncspot.ui.contextmenu.ContextMenu→ncspot.command.Commandncspot.ui.contextmenu.SelectArtistActionMenu→ncspot.command.Commandncspot.ui.contextmenu.SelectArtistMenu→ncspot.command.Commandncspot.ui.contextmenu.contextmenu$module→ncspot.command.Command
- Direction
- ui.contextmenu uses command, so a change to command can break ui.contextmenu, while a change to ui.contextmenu can't break command.
- Position
- Below the diagonal: ui.contextmenu uses a module listed above it, which is the healthy direction.
23→5 ui.contextmenu uses ui.modal✕
- Connections
- 5 pairs of types, where a type in ui.contextmenu uses a type in ui.modal.
- The types involved
ncspot.ui.contextmenu.AddToPlaylistMenu→ncspot.ui.modal.Modalncspot.ui.contextmenu.ContextMenu→ncspot.ui.modal.Modalncspot.ui.contextmenu.SelectArtistActionMenu→ncspot.ui.modal.Modalncspot.ui.contextmenu.SelectArtistMenu→ncspot.ui.modal.Modalncspot.ui.contextmenu.contextmenu$module→ncspot.ui.modal.Modal
- Direction
- ui.contextmenu uses ui.modal, so a change to ui.modal can break ui.contextmenu, while a change to ui.contextmenu can't break ui.modal.
- Position
- Below the diagonal: ui.contextmenu uses a module listed above it, which is the healthy direction.
23→8 ui.contextmenu uses spotify✕
- Connections
- 1 pair of types, where a type in ui.contextmenu uses a type in spotify.
- The types involved
ncspot.ui.contextmenu.ContextMenu→ncspot.spotify.Spotify
- Direction
- ui.contextmenu uses spotify, so a change to spotify can break ui.contextmenu, while a change to ui.contextmenu can't break spotify.
- Position
- Below the diagonal: ui.contextmenu uses a module listed above it, which is the healthy direction.
23→9 ui.contextmenu uses queue✕
- Connections
- 1 pair of types, where a type in ui.contextmenu uses a type in queue.
- The types involved
ncspot.ui.contextmenu.ContextMenu→ncspot.queue.Queue
- Direction
- ui.contextmenu uses queue, so a change to queue can break ui.contextmenu, while a change to ui.contextmenu can't break queue.
- Position
- Below the diagonal: ui.contextmenu uses a module listed above it, which is the healthy direction.
23→10 ui.contextmenu uses traits✕
- Connections
- 4 pairs of types, where a type in ui.contextmenu uses a type in traits.
- The types involved
ncspot.ui.contextmenu.AddToPlaylistMenu→ncspot.traits.ViewExtncspot.ui.contextmenu.ContextMenu→ncspot.traits.ViewExtncspot.ui.contextmenu.SelectArtistActionMenu→ncspot.traits.ViewExtncspot.ui.contextmenu.SelectArtistMenu→ncspot.traits.ViewExt
- Direction
- ui.contextmenu uses traits, so a change to traits can break ui.contextmenu, while a change to ui.contextmenu can't break traits.
- Position
- Below the diagonal: ui.contextmenu uses a module listed above it, which is the healthy direction.
23→13 ui.contextmenu uses model.track✕
- Connections
- 1 pair of types, where a type in ui.contextmenu uses a type in model.track.
- The types involved
ncspot.ui.contextmenu.ContextMenu→ncspot.model.track.Track
- Direction
- ui.contextmenu uses model.track, so a change to model.track can break ui.contextmenu, while a change to ui.contextmenu can't break model.track.
- Position
- Below the diagonal: ui.contextmenu uses a module listed above it, which is the healthy direction.
23→16 ui.contextmenu uses model.artist✕
- Connections
- 1 pair of types, where a type in ui.contextmenu uses a type in model.artist.
- The types involved
ncspot.ui.contextmenu.ContextMenu→ncspot.model.artist.Artist
- Direction
- ui.contextmenu uses model.artist, so a change to model.artist can break ui.contextmenu, while a change to ui.contextmenu can't break model.artist.
- Position
- Below the diagonal: ui.contextmenu uses a module listed above it, which is the healthy direction.
23→19 ui.contextmenu uses library✕
- Connections
- 1 pair of types, where a type in ui.contextmenu uses a type in library.
- The types involved
ncspot.ui.contextmenu.ContextMenu→ncspot.library.Library
- Direction
- ui.contextmenu uses library, so a change to library can break ui.contextmenu, while a change to ui.contextmenu can't break library.
- Position
- Below the diagonal: ui.contextmenu uses a module listed above it, which is the healthy direction.
24→1 ui.library uses command✕
- Connections
- 1 pair of types, where a type in ui.library uses a type in command.
- The types involved
ncspot.ui.library.LibraryView→ncspot.command.Command
- Direction
- ui.library uses command, so a change to command can break ui.library, while a change to ui.library can't break command.
- Position
- Below the diagonal: ui.library uses a module listed above it, which is the healthy direction.
24→9 ui.library uses queue✕
- Connections
- 1 pair of types, where a type in ui.library uses a type in queue.
- The types involved
ncspot.ui.library.LibraryView→ncspot.queue.Queue
- Direction
- ui.library uses queue, so a change to queue can break ui.library, while a change to ui.library can't break queue.
- Position
- Below the diagonal: ui.library uses a module listed above it, which is the healthy direction.
24→10 ui.library uses traits✕
- Connections
- 1 pair of types, where a type in ui.library uses a type in traits.
- The types involved
ncspot.ui.library.LibraryView→ncspot.traits.ViewExt
- Direction
- ui.library uses traits, so a change to traits can break ui.library, while a change to ui.library can't break traits.
- Position
- Below the diagonal: ui.library uses a module listed above it, which is the healthy direction.
24→15 ui.library uses ui.tabbedview✕
- Connections
- 1 pair of types, where a type in ui.library uses a type in ui.tabbedview.
- The types involved
ncspot.ui.library.LibraryView→ncspot.ui.tabbedview.TabbedView
- Direction
- ui.library uses ui.tabbedview, so a change to ui.tabbedview can break ui.library, while a change to ui.library can't break ui.tabbedview.
- Position
- Below the diagonal: ui.library uses a module listed above it, which is the healthy direction.
24→19 ui.library uses library✕
- Connections
- 1 pair of types, where a type in ui.library uses a type in library.
- The types involved
ncspot.ui.library.LibraryView→ncspot.library.Library
- Direction
- ui.library uses library, so a change to library can break ui.library, while a change to ui.library can't break library.
- Position
- Below the diagonal: ui.library uses a module listed above it, which is the healthy direction.
25→1 ui.listview uses command✕
- Connections
- 1 pair of types, where a type in ui.listview uses a type in command.
- The types involved
ncspot.ui.listview.ListView→ncspot.command.Command
- Direction
- ui.listview uses command, so a change to command can break ui.listview, while a change to ui.listview can't break command.
- Position
- Below the diagonal: ui.listview uses a module listed above it, which is the healthy direction.
25→2 ui.listview uses events✕
- Connections
- 1 pair of types, where a type in ui.listview uses a type in events.
- The types involved
ncspot.ui.listview.ListView→ncspot.events.Event
- Direction
- ui.listview uses events, so a change to events can break ui.listview, while a change to ui.listview can't break events.
- Position
- Below the diagonal: ui.listview uses a module listed above it, which is the healthy direction.
25→6 ui.listview uses ui.pagination✕
- Connections
- 1 pair of types, where a type in ui.listview uses a type in ui.pagination.
- The types involved
ncspot.ui.listview.ListView→ncspot.ui.pagination.Pagination
- Direction
- ui.listview uses ui.pagination, so a change to ui.pagination can break ui.listview, while a change to ui.listview can't break ui.pagination.
- Position
- Below the diagonal: ui.listview uses a module listed above it, which is the healthy direction.
25→9 ui.listview uses queue✕
- Connections
- 1 pair of types, where a type in ui.listview uses a type in queue.
- The types involved
ncspot.ui.listview.ListView→ncspot.queue.Queue
- Direction
- ui.listview uses queue, so a change to queue can break ui.listview, while a change to ui.listview can't break queue.
- Position
- Below the diagonal: ui.listview uses a module listed above it, which is the healthy direction.
25→10 ui.listview uses traits✕
- Connections
- 1 pair of types, where a type in ui.listview uses a type in traits.
- The types involved
ncspot.ui.listview.ListView→ncspot.traits.ViewExt
- Direction
- ui.listview uses traits, so a change to traits can break ui.listview, while a change to ui.listview can't break traits.
- Position
- Below the diagonal: ui.listview uses a module listed above it, which is the healthy direction.
25→19 ui.listview uses library✕
- Connections
- 1 pair of types, where a type in ui.listview uses a type in library.
- The types involved
ncspot.ui.listview.ListView→ncspot.library.Library
- Direction
- ui.listview uses library, so a change to library can break ui.listview, while a change to ui.listview can't break library.
- Position
- Below the diagonal: ui.listview uses a module listed above it, which is the healthy direction.
26→1 ui.search uses command✕
- Connections
- 1 pair of types, where a type in ui.search uses a type in command.
- The types involved
ncspot.ui.search.SearchView→ncspot.command.Command
- Direction
- ui.search uses command, so a change to command can break ui.search, while a change to ui.search can't break command.
- Position
- Below the diagonal: ui.search uses a module listed above it, which is the healthy direction.
26→2 ui.search uses events✕
- Connections
- 2 pairs of types, where a type in ui.search uses a type in events.
- The types involved
ncspot.ui.search.SearchView→ncspot.events.Eventncspot.ui.search.SearchView→ncspot.events.EventManager
- Direction
- ui.search uses events, so a change to events can break ui.search, while a change to ui.search can't break events.
- Position
- Below the diagonal: ui.search uses a module listed above it, which is the healthy direction.
26→9 ui.search uses queue✕
- Connections
- 1 pair of types, where a type in ui.search uses a type in queue.
- The types involved
ncspot.ui.search.SearchView→ncspot.queue.Queue
- Direction
- ui.search uses queue, so a change to queue can break ui.search, while a change to ui.search can't break queue.
- Position
- Below the diagonal: ui.search uses a module listed above it, which is the healthy direction.
26→10 ui.search uses traits✕
- Connections
- 1 pair of types, where a type in ui.search uses a type in traits.
- The types involved
ncspot.ui.search.SearchView→ncspot.traits.ViewExt
- Direction
- ui.search uses traits, so a change to traits can break ui.search, while a change to ui.search can't break traits.
- Position
- Below the diagonal: ui.search uses a module listed above it, which is the healthy direction.
26→19 ui.search uses library✕
- Connections
- 1 pair of types, where a type in ui.search uses a type in library.
- The types involved
ncspot.ui.search.SearchView→ncspot.library.Library
- Direction
- ui.search uses library, so a change to library can break ui.search, while a change to ui.search can't break library.
- Position
- Below the diagonal: ui.search uses a module listed above it, which is the healthy direction.
27→1 ui.search_results uses command✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in command.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.command.Command
- Direction
- ui.search_results uses command, so a change to command can break ui.search_results, while a change to ui.search_results can't break command.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→2 ui.search_results uses events✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in events.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.events.EventManager
- Direction
- ui.search_results uses events, so a change to events can break ui.search_results, while a change to ui.search_results can't break events.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→6 ui.search_results uses ui.pagination✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in ui.pagination.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.ui.pagination.Pagination
- Direction
- ui.search_results uses ui.pagination, so a change to ui.pagination can break ui.search_results, while a change to ui.search_results can't break ui.pagination.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→8 ui.search_results uses spotify✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in spotify.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.spotify.Spotify
- Direction
- ui.search_results uses spotify, so a change to spotify can break ui.search_results, while a change to ui.search_results can't break spotify.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→9 ui.search_results uses queue✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in queue.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.queue.Queue
- Direction
- ui.search_results uses queue, so a change to queue can break ui.search_results, while a change to ui.search_results can't break queue.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→10 ui.search_results uses traits✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in traits.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.traits.ViewExt
- Direction
- ui.search_results uses traits, so a change to traits can break ui.search_results, while a change to ui.search_results can't break traits.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→11 ui.search_results uses model.episode✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in model.episode.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.model.episode.Episode
- Direction
- ui.search_results uses model.episode, so a change to model.episode can break ui.search_results, while a change to ui.search_results can't break model.episode.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→12 ui.search_results uses model.playlist✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in model.playlist.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.model.playlist.Playlist
- Direction
- ui.search_results uses model.playlist, so a change to model.playlist can break ui.search_results, while a change to ui.search_results can't break model.playlist.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→13 ui.search_results uses model.track✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in model.track.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.model.track.Track
- Direction
- ui.search_results uses model.track, so a change to model.track can break ui.search_results, while a change to ui.search_results can't break model.track.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→15 ui.search_results uses ui.tabbedview✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in ui.tabbedview.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.ui.tabbedview.TabbedView
- Direction
- ui.search_results uses ui.tabbedview, so a change to ui.tabbedview can break ui.search_results, while a change to ui.search_results can't break ui.tabbedview.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→16 ui.search_results uses model.artist✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in model.artist.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.model.artist.Artist
- Direction
- ui.search_results uses model.artist, so a change to model.artist can break ui.search_results, while a change to ui.search_results can't break model.artist.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→17 ui.search_results uses model.show✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in model.show.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.model.show.Show
- Direction
- ui.search_results uses model.show, so a change to model.show can break ui.search_results, while a change to ui.search_results can't break model.show.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→18 ui.search_results uses model.album✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in model.album.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.model.album.Album
- Direction
- ui.search_results uses model.album, so a change to model.album can break ui.search_results, while a change to ui.search_results can't break model.album.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
27→19 ui.search_results uses library✕
- Connections
- 1 pair of types, where a type in ui.search_results uses a type in library.
- The types involved
ncspot.ui.search_results.SearchResultsView→ncspot.library.Library
- Direction
- ui.search_results uses library, so a change to library can break ui.search_results, while a change to ui.search_results can't break library.
- Position
- Below the diagonal: ui.search_results uses a module listed above it, which is the healthy direction.
28→1 config uses command✕
- Connections
- 2 pairs of types, where a type in config uses a type in command.
- The types involved
ncspot.config.SortingOrder→ncspot.command.SortDirectionncspot.config.SortingOrder→ncspot.command.SortKey
- Direction
- config uses command, so a change to command can break config, while a change to config can't break command.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→9 config uses queue✕
- Connections
- 2 pairs of types, where a type in config uses a type in queue.
- The types involved
ncspot.config.ConfigValues→ncspot.queue.RepeatSettingncspot.config.UserState→ncspot.queue.RepeatSetting
- Direction
- config uses queue, so a change to queue can break config, while a change to config can't break queue.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→21 config uses model.playable✕
- Connections
- 1 pair of types, where a type in config uses a type in model.playable.
- The types involved
ncspot.config.QueueState→ncspot.model.playable.Playable
- Direction
- config uses model.playable, so a change to model.playable can break config, while a change to config can't break model.playable.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
29→2 ipc uses events✕
- Connections
- 1 pair of types, where a type in ipc uses a type in events.
- The types involved
ncspot.ipc.IpcSocket→ncspot.events.EventManager
- Direction
- ipc uses events, so a change to events can break ipc, while a change to ipc can't break events.
- Position
- Below the diagonal: ipc uses a module listed above it, which is the healthy direction.
29→8 ipc uses spotify✕
- Connections
- 2 pairs of types, where a type in ipc uses a type in spotify.
- The types involved
ncspot.ipc.IpcSocket→ncspot.spotify.PlayerEventncspot.ipc.Status→ncspot.spotify.PlayerEvent
- Direction
- ipc uses spotify, so a change to spotify can break ipc, while a change to ipc can't break spotify.
- Position
- Below the diagonal: ipc uses a module listed above it, which is the healthy direction.
29→21 ipc uses model.playable✕
- Connections
- 2 pairs of types, where a type in ipc uses a type in model.playable.
- The types involved
ncspot.ipc.IpcSocket→ncspot.model.playable.Playablencspot.ipc.Status→ncspot.model.playable.Playable
- Direction
- ipc uses model.playable, so a change to model.playable can break ipc, while a change to ipc can't break model.playable.
- Position
- Below the diagonal: ipc uses a module listed above it, which is the healthy direction.
30→1 ui.artist uses command✕
- Connections
- 1 pair of types, where a type in ui.artist uses a type in command.
- The types involved
ncspot.ui.artist.ArtistView→ncspot.command.Command
- Direction
- ui.artist uses command, so a change to command can break ui.artist, while a change to ui.artist can't break command.
- Position
- Below the diagonal: ui.artist uses a module listed above it, which is the healthy direction.
30→9 ui.artist uses queue✕
- Connections
- 1 pair of types, where a type in ui.artist uses a type in queue.
- The types involved
ncspot.ui.artist.ArtistView→ncspot.queue.Queue
- Direction
- ui.artist uses queue, so a change to queue can break ui.artist, while a change to ui.artist can't break queue.
- Position
- Below the diagonal: ui.artist uses a module listed above it, which is the healthy direction.
30→10 ui.artist uses traits✕
- Connections
- 1 pair of types, where a type in ui.artist uses a type in traits.
- The types involved
ncspot.ui.artist.ArtistView→ncspot.traits.ViewExt
- Direction
- ui.artist uses traits, so a change to traits can break ui.artist, while a change to ui.artist can't break traits.
- Position
- Below the diagonal: ui.artist uses a module listed above it, which is the healthy direction.
30→15 ui.artist uses ui.tabbedview✕
- Connections
- 1 pair of types, where a type in ui.artist uses a type in ui.tabbedview.
- The types involved
ncspot.ui.artist.ArtistView→ncspot.ui.tabbedview.TabbedView
- Direction
- ui.artist uses ui.tabbedview, so a change to ui.tabbedview can break ui.artist, while a change to ui.artist can't break ui.tabbedview.
- Position
- Below the diagonal: ui.artist uses a module listed above it, which is the healthy direction.
30→16 ui.artist uses model.artist✕
- Connections
- 1 pair of types, where a type in ui.artist uses a type in model.artist.
- The types involved
ncspot.ui.artist.ArtistView→ncspot.model.artist.Artist
- Direction
- ui.artist uses model.artist, so a change to model.artist can break ui.artist, while a change to ui.artist can't break model.artist.
- Position
- Below the diagonal: ui.artist uses a module listed above it, which is the healthy direction.
30→19 ui.artist uses library✕
- Connections
- 1 pair of types, where a type in ui.artist uses a type in library.
- The types involved
ncspot.ui.artist.ArtistView→ncspot.library.Library
- Direction
- ui.artist uses library, so a change to library can break ui.artist, while a change to ui.artist can't break library.
- Position
- Below the diagonal: ui.artist uses a module listed above it, which is the healthy direction.
30→25 ui.artist uses ui.listview✕
- Connections
- 1 pair of types, where a type in ui.artist uses a type in ui.listview.
- The types involved
ncspot.ui.artist.ArtistView→ncspot.ui.listview.ListView
- Direction
- ui.artist uses ui.listview, so a change to ui.listview can break ui.artist, while a change to ui.artist can't break ui.listview.
- Position
- Below the diagonal: ui.artist uses a module listed above it, which is the healthy direction.
31→1 ui.browse uses command✕
- Connections
- 1 pair of types, where a type in ui.browse uses a type in command.
- The types involved
ncspot.ui.browse.BrowseView→ncspot.command.Command
- Direction
- ui.browse uses command, so a change to command can break ui.browse, while a change to ui.browse can't break command.
- Position
- Below the diagonal: ui.browse uses a module listed above it, which is the healthy direction.
31→9 ui.browse uses queue✕
- Connections
- 1 pair of types, where a type in ui.browse uses a type in queue.
- The types involved
ncspot.ui.browse.BrowseView→ncspot.queue.Queue
- Direction
- ui.browse uses queue, so a change to queue can break ui.browse, while a change to ui.browse can't break queue.
- Position
- Below the diagonal: ui.browse uses a module listed above it, which is the healthy direction.
31→10 ui.browse uses traits✕
- Connections
- 1 pair of types, where a type in ui.browse uses a type in traits.
- The types involved
ncspot.ui.browse.BrowseView→ncspot.traits.ViewExt
- Direction
- ui.browse uses traits, so a change to traits can break ui.browse, while a change to ui.browse can't break traits.
- Position
- Below the diagonal: ui.browse uses a module listed above it, which is the healthy direction.
31→19 ui.browse uses library✕
- Connections
- 1 pair of types, where a type in ui.browse uses a type in library.
- The types involved
ncspot.ui.browse.BrowseView→ncspot.library.Library
- Direction
- ui.browse uses library, so a change to library can break ui.browse, while a change to ui.browse can't break library.
- Position
- Below the diagonal: ui.browse uses a module listed above it, which is the healthy direction.
31→25 ui.browse uses ui.listview✕
- Connections
- 1 pair of types, where a type in ui.browse uses a type in ui.listview.
- The types involved
ncspot.ui.browse.BrowseView→ncspot.ui.listview.ListView
- Direction
- ui.browse uses ui.listview, so a change to ui.listview can break ui.browse, while a change to ui.browse can't break ui.listview.
- Position
- Below the diagonal: ui.browse uses a module listed above it, which is the healthy direction.
32→1 ui.playlist uses command✕
- Connections
- 1 pair of types, where a type in ui.playlist uses a type in command.
- The types involved
ncspot.ui.playlist.PlaylistView→ncspot.command.Command
- Direction
- ui.playlist uses command, so a change to command can break ui.playlist, while a change to ui.playlist can't break command.
- Position
- Below the diagonal: ui.playlist uses a module listed above it, which is the healthy direction.
32→8 ui.playlist uses spotify✕
- Connections
- 1 pair of types, where a type in ui.playlist uses a type in spotify.
- The types involved
ncspot.ui.playlist.PlaylistView→ncspot.spotify.Spotify
- Direction
- ui.playlist uses spotify, so a change to spotify can break ui.playlist, while a change to ui.playlist can't break spotify.
- Position
- Below the diagonal: ui.playlist uses a module listed above it, which is the healthy direction.
32→9 ui.playlist uses queue✕
- Connections
- 1 pair of types, where a type in ui.playlist uses a type in queue.
- The types involved
ncspot.ui.playlist.PlaylistView→ncspot.queue.Queue
- Direction
- ui.playlist uses queue, so a change to queue can break ui.playlist, while a change to ui.playlist can't break queue.
- Position
- Below the diagonal: ui.playlist uses a module listed above it, which is the healthy direction.
32→10 ui.playlist uses traits✕
- Connections
- 1 pair of types, where a type in ui.playlist uses a type in traits.
- The types involved
ncspot.ui.playlist.PlaylistView→ncspot.traits.ViewExt
- Direction
- ui.playlist uses traits, so a change to traits can break ui.playlist, while a change to ui.playlist can't break traits.
- Position
- Below the diagonal: ui.playlist uses a module listed above it, which is the healthy direction.
32→12 ui.playlist uses model.playlist✕
- Connections
- 1 pair of types, where a type in ui.playlist uses a type in model.playlist.
- The types involved
ncspot.ui.playlist.PlaylistView→ncspot.model.playlist.Playlist
- Direction
- ui.playlist uses model.playlist, so a change to model.playlist can break ui.playlist, while a change to ui.playlist can't break model.playlist.
- Position
- Below the diagonal: ui.playlist uses a module listed above it, which is the healthy direction.
32→19 ui.playlist uses library✕
- Connections
- 1 pair of types, where a type in ui.playlist uses a type in library.
- The types involved
ncspot.ui.playlist.PlaylistView→ncspot.library.Library
- Direction
- ui.playlist uses library, so a change to library can break ui.playlist, while a change to ui.playlist can't break library.
- Position
- Below the diagonal: ui.playlist uses a module listed above it, which is the healthy direction.
32→25 ui.playlist uses ui.listview✕
- Connections
- 1 pair of types, where a type in ui.playlist uses a type in ui.listview.
- The types involved
ncspot.ui.playlist.PlaylistView→ncspot.ui.listview.ListView
- Direction
- ui.playlist uses ui.listview, so a change to ui.listview can break ui.playlist, while a change to ui.playlist can't break ui.listview.
- Position
- Below the diagonal: ui.playlist uses a module listed above it, which is the healthy direction.
33→1 ui.playlists uses command✕
- Connections
- 1 pair of types, where a type in ui.playlists uses a type in command.
- The types involved
ncspot.ui.playlists.PlaylistsView→ncspot.command.Command
- Direction
- ui.playlists uses command, so a change to command can break ui.playlists, while a change to ui.playlists can't break command.
- Position
- Below the diagonal: ui.playlists uses a module listed above it, which is the healthy direction.
33→5 ui.playlists uses ui.modal✕
- Connections
- 1 pair of types, where a type in ui.playlists uses a type in ui.modal.
- The types involved
ncspot.ui.playlists.PlaylistsView→ncspot.ui.modal.Modal
- Direction
- ui.playlists uses ui.modal, so a change to ui.modal can break ui.playlists, while a change to ui.playlists can't break ui.modal.
- Position
- Below the diagonal: ui.playlists uses a module listed above it, which is the healthy direction.
33→9 ui.playlists uses queue✕
- Connections
- 1 pair of types, where a type in ui.playlists uses a type in queue.
- The types involved
ncspot.ui.playlists.PlaylistsView→ncspot.queue.Queue
- Direction
- ui.playlists uses queue, so a change to queue can break ui.playlists, while a change to ui.playlists can't break queue.
- Position
- Below the diagonal: ui.playlists uses a module listed above it, which is the healthy direction.
33→10 ui.playlists uses traits✕
- Connections
- 1 pair of types, where a type in ui.playlists uses a type in traits.
- The types involved
ncspot.ui.playlists.PlaylistsView→ncspot.traits.ViewExt
- Direction
- ui.playlists uses traits, so a change to traits can break ui.playlists, while a change to ui.playlists can't break traits.
- Position
- Below the diagonal: ui.playlists uses a module listed above it, which is the healthy direction.
33→19 ui.playlists uses library✕
- Connections
- 1 pair of types, where a type in ui.playlists uses a type in library.
- The types involved
ncspot.ui.playlists.PlaylistsView→ncspot.library.Library
- Direction
- ui.playlists uses library, so a change to library can break ui.playlists, while a change to ui.playlists can't break library.
- Position
- Below the diagonal: ui.playlists uses a module listed above it, which is the healthy direction.
33→25 ui.playlists uses ui.listview✕
- Connections
- 1 pair of types, where a type in ui.playlists uses a type in ui.listview.
- The types involved
ncspot.ui.playlists.PlaylistsView→ncspot.ui.listview.ListView
- Direction
- ui.playlists uses ui.listview, so a change to ui.listview can break ui.playlists, while a change to ui.playlists can't break ui.listview.
- Position
- Below the diagonal: ui.playlists uses a module listed above it, which is the healthy direction.
34→1 ui.queue uses command✕
- Connections
- 1 pair of types, where a type in ui.queue uses a type in command.
- The types involved
ncspot.ui.queue.QueueView→ncspot.command.Command
- Direction
- ui.queue uses command, so a change to command can break ui.queue, while a change to ui.queue can't break command.
- Position
- Below the diagonal: ui.queue uses a module listed above it, which is the healthy direction.
34→2 ui.queue uses events✕
- Connections
- 1 pair of types, where a type in ui.queue uses a type in events.
- The types involved
ncspot.ui.queue.QueueView→ncspot.events.Event
- Direction
- ui.queue uses events, so a change to events can break ui.queue, while a change to ui.queue can't break events.
- Position
- Below the diagonal: ui.queue uses a module listed above it, which is the healthy direction.
34→5 ui.queue uses ui.modal✕
- Connections
- 1 pair of types, where a type in ui.queue uses a type in ui.modal.
- The types involved
ncspot.ui.queue.QueueView→ncspot.ui.modal.Modal
- Direction
- ui.queue uses ui.modal, so a change to ui.modal can break ui.queue, while a change to ui.queue can't break ui.modal.
- Position
- Below the diagonal: ui.queue uses a module listed above it, which is the healthy direction.
34→9 ui.queue uses queue✕
- Connections
- 1 pair of types, where a type in ui.queue uses a type in queue.
- The types involved
ncspot.ui.queue.QueueView→ncspot.queue.Queue
- Direction
- ui.queue uses queue, so a change to queue can break ui.queue, while a change to ui.queue can't break queue.
- Position
- Below the diagonal: ui.queue uses a module listed above it, which is the healthy direction.
34→10 ui.queue uses traits✕
- Connections
- 1 pair of types, where a type in ui.queue uses a type in traits.
- The types involved
ncspot.ui.queue.QueueView→ncspot.traits.ViewExt
- Direction
- ui.queue uses traits, so a change to traits can break ui.queue, while a change to ui.queue can't break traits.
- Position
- Below the diagonal: ui.queue uses a module listed above it, which is the healthy direction.
34→19 ui.queue uses library✕
- Connections
- 1 pair of types, where a type in ui.queue uses a type in library.
- The types involved
ncspot.ui.queue.QueueView→ncspot.library.Library
- Direction
- ui.queue uses library, so a change to library can break ui.queue, while a change to ui.queue can't break library.
- Position
- Below the diagonal: ui.queue uses a module listed above it, which is the healthy direction.
34→25 ui.queue uses ui.listview✕
- Connections
- 1 pair of types, where a type in ui.queue uses a type in ui.listview.
- The types involved
ncspot.ui.queue.QueueView→ncspot.ui.listview.ListView
- Direction
- ui.queue uses ui.listview, so a change to ui.listview can break ui.queue, while a change to ui.queue can't break ui.listview.
- Position
- Below the diagonal: ui.queue uses a module listed above it, which is the healthy direction.
35→1 ui.show uses command✕
- Connections
- 1 pair of types, where a type in ui.show uses a type in command.
- The types involved
ncspot.ui.show.ShowView→ncspot.command.Command
- Direction
- ui.show uses command, so a change to command can break ui.show, while a change to ui.show can't break command.
- Position
- Below the diagonal: ui.show uses a module listed above it, which is the healthy direction.
35→9 ui.show uses queue✕
- Connections
- 1 pair of types, where a type in ui.show uses a type in queue.
- The types involved
ncspot.ui.show.ShowView→ncspot.queue.Queue
- Direction
- ui.show uses queue, so a change to queue can break ui.show, while a change to ui.show can't break queue.
- Position
- Below the diagonal: ui.show uses a module listed above it, which is the healthy direction.
35→10 ui.show uses traits✕
- Connections
- 1 pair of types, where a type in ui.show uses a type in traits.
- The types involved
ncspot.ui.show.ShowView→ncspot.traits.ViewExt
- Direction
- ui.show uses traits, so a change to traits can break ui.show, while a change to ui.show can't break traits.
- Position
- Below the diagonal: ui.show uses a module listed above it, which is the healthy direction.
35→17 ui.show uses model.show✕
- Connections
- 1 pair of types, where a type in ui.show uses a type in model.show.
- The types involved
ncspot.ui.show.ShowView→ncspot.model.show.Show
- Direction
- ui.show uses model.show, so a change to model.show can break ui.show, while a change to ui.show can't break model.show.
- Position
- Below the diagonal: ui.show uses a module listed above it, which is the healthy direction.
35→19 ui.show uses library✕
- Connections
- 1 pair of types, where a type in ui.show uses a type in library.
- The types involved
ncspot.ui.show.ShowView→ncspot.library.Library
- Direction
- ui.show uses library, so a change to library can break ui.show, while a change to ui.show can't break library.
- Position
- Below the diagonal: ui.show uses a module listed above it, which is the healthy direction.
35→25 ui.show uses ui.listview✕
- Connections
- 1 pair of types, where a type in ui.show uses a type in ui.listview.
- The types involved
ncspot.ui.show.ShowView→ncspot.ui.listview.ListView
- Direction
- ui.show uses ui.listview, so a change to ui.listview can break ui.show, while a change to ui.show can't break ui.listview.
- Position
- Below the diagonal: ui.show uses a module listed above it, which is the healthy direction.
36→2 ui.statusbar uses events✕
- Connections
- 1 pair of types, where a type in ui.statusbar uses a type in events.
- The types involved
ncspot.ui.statusbar.StatusBar→ncspot.events.Event
- Direction
- ui.statusbar uses events, so a change to events can break ui.statusbar, while a change to ui.statusbar can't break events.
- Position
- Below the diagonal: ui.statusbar uses a module listed above it, which is the healthy direction.
36→8 ui.statusbar uses spotify✕
- Connections
- 1 pair of types, where a type in ui.statusbar uses a type in spotify.
- The types involved
ncspot.ui.statusbar.StatusBar→ncspot.spotify.Spotify
- Direction
- ui.statusbar uses spotify, so a change to spotify can break ui.statusbar, while a change to ui.statusbar can't break spotify.
- Position
- Below the diagonal: ui.statusbar uses a module listed above it, which is the healthy direction.
36→9 ui.statusbar uses queue✕
- Connections
- 1 pair of types, where a type in ui.statusbar uses a type in queue.
- The types involved
ncspot.ui.statusbar.StatusBar→ncspot.queue.Queue
- Direction
- ui.statusbar uses queue, so a change to queue can break ui.statusbar, while a change to ui.statusbar can't break queue.
- Position
- Below the diagonal: ui.statusbar uses a module listed above it, which is the healthy direction.
36→19 ui.statusbar uses library✕
- Connections
- 1 pair of types, where a type in ui.statusbar uses a type in library.
- The types involved
ncspot.ui.statusbar.StatusBar→ncspot.library.Library
- Direction
- ui.statusbar uses library, so a change to library can break ui.statusbar, while a change to ui.statusbar can't break library.
- Position
- Below the diagonal: ui.statusbar uses a module listed above it, which is the healthy direction.
36→21 ui.statusbar uses model.playable✕
- Connections
- 1 pair of types, where a type in ui.statusbar uses a type in model.playable.
- The types involved
ncspot.ui.statusbar.StatusBar→ncspot.model.playable.Playable
- Direction
- ui.statusbar uses model.playable, so a change to model.playable can break ui.statusbar, while a change to ui.statusbar can't break model.playable.
- Position
- Below the diagonal: ui.statusbar uses a module listed above it, which is the healthy direction.
37→1 commands uses command✕
- Connections
- 1 pair of types, where a type in commands uses a type in command.
- The types involved
ncspot.commands.CommandManager→ncspot.command.Command
- Direction
- commands uses command, so a change to command can break commands, while a change to commands can't break command.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
37→2 commands uses events✕
- Connections
- 2 pairs of types, where a type in commands uses a type in events.
- The types involved
ncspot.commands.CommandManager→ncspot.events.Eventncspot.commands.CommandManager→ncspot.events.EventManager
- Direction
- commands uses events, so a change to events can break commands, while a change to commands can't break events.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
37→8 commands uses spotify✕
- Connections
- 1 pair of types, where a type in commands uses a type in spotify.
- The types involved
ncspot.commands.CommandManager→ncspot.spotify.Spotify
- Direction
- commands uses spotify, so a change to spotify can break commands, while a change to commands can't break spotify.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
37→9 commands uses queue✕
- Connections
- 1 pair of types, where a type in commands uses a type in queue.
- The types involved
ncspot.commands.CommandManager→ncspot.queue.Queue
- Direction
- commands uses queue, so a change to queue can break commands, while a change to commands can't break queue.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
37→19 commands uses library✕
- Connections
- 1 pair of types, where a type in commands uses a type in library.
- The types involved
ncspot.commands.CommandManager→ncspot.library.Library
- Direction
- commands uses library, so a change to library can break commands, while a change to commands can't break library.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
37→28 commands uses config✕
- Connections
- 1 pair of types, where a type in commands uses a type in config.
- The types involved
ncspot.commands.CommandManager→ncspot.config.Config
- Direction
- commands uses config, so a change to config can break commands, while a change to commands can't break config.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→1 ui.cover uses command✕
- Connections
- 1 pair of types, where a type in ui.cover uses a type in command.
- The types involved
ncspot.ui.cover.CoverView→ncspot.command.Command
- Direction
- ui.cover uses command, so a change to command can break ui.cover, while a change to ui.cover can't break command.
- Position
- Below the diagonal: ui.cover uses a module listed above it, which is the healthy direction.
38→9 ui.cover uses queue✕
- Connections
- 1 pair of types, where a type in ui.cover uses a type in queue.
- The types involved
ncspot.ui.cover.CoverView→ncspot.queue.Queue
- Direction
- ui.cover uses queue, so a change to queue can break ui.cover, while a change to ui.cover can't break queue.
- Position
- Below the diagonal: ui.cover uses a module listed above it, which is the healthy direction.
38→10 ui.cover uses traits✕
- Connections
- 1 pair of types, where a type in ui.cover uses a type in traits.
- The types involved
ncspot.ui.cover.CoverView→ncspot.traits.ViewExt
- Direction
- ui.cover uses traits, so a change to traits can break ui.cover, while a change to ui.cover can't break traits.
- Position
- Below the diagonal: ui.cover uses a module listed above it, which is the healthy direction.
38→19 ui.cover uses library✕
- Connections
- 1 pair of types, where a type in ui.cover uses a type in library.
- The types involved
ncspot.ui.cover.CoverView→ncspot.library.Library
- Direction
- ui.cover uses library, so a change to library can break ui.cover, while a change to ui.cover can't break library.
- Position
- Below the diagonal: ui.cover uses a module listed above it, which is the healthy direction.
38→28 ui.cover uses config✕
- Connections
- 1 pair of types, where a type in ui.cover uses a type in config.
- The types involved
ncspot.ui.cover.CoverView→ncspot.config.Config
- Direction
- ui.cover uses config, so a change to config can break ui.cover, while a change to ui.cover can't break config.
- Position
- Below the diagonal: ui.cover uses a module listed above it, which is the healthy direction.
39→1 ui.layout uses command✕
- Connections
- 1 pair of types, where a type in ui.layout uses a type in command.
- The types involved
ncspot.ui.layout.Layout→ncspot.command.Command
- Direction
- ui.layout uses command, so a change to command can break ui.layout, while a change to ui.layout can't break command.
- Position
- Below the diagonal: ui.layout uses a module listed above it, which is the healthy direction.
39→2 ui.layout uses events✕
- Connections
- 2 pairs of types, where a type in ui.layout uses a type in events.
- The types involved
ncspot.ui.layout.Layout→ncspot.events.Eventncspot.ui.layout.Layout→ncspot.events.EventManager
- Direction
- ui.layout uses events, so a change to events can break ui.layout, while a change to ui.layout can't break events.
- Position
- Below the diagonal: ui.layout uses a module listed above it, which is the healthy direction.
39→10 ui.layout uses traits✕
- Connections
- 1 pair of types, where a type in ui.layout uses a type in traits.
- The types involved
ncspot.ui.layout.Layout→ncspot.traits.ViewExt
- Direction
- ui.layout uses traits, so a change to traits can break ui.layout, while a change to ui.layout can't break traits.
- Position
- Below the diagonal: ui.layout uses a module listed above it, which is the healthy direction.
39→28 ui.layout uses config✕
- Connections
- 1 pair of types, where a type in ui.layout uses a type in config.
- The types involved
ncspot.ui.layout.Layout→ncspot.config.Config
- Direction
- ui.layout uses config, so a change to config can break ui.layout, while a change to ui.layout can't break config.
- Position
- Below the diagonal: ui.layout uses a module listed above it, which is the healthy direction.
40→2 application uses events✕
- Connections
- 1 pair of types, where a type in application uses a type in events.
- The types involved
ncspot.application.Application→ncspot.events.EventManager
- Direction
- application uses events, so a change to events can break application, while a change to application can't break events.
- Position
- Below the diagonal: application uses a module listed above it, which is the healthy direction.
40→8 application uses spotify✕
- Connections
- 1 pair of types, where a type in application uses a type in spotify.
- The types involved
ncspot.application.Application→ncspot.spotify.Spotify
- Direction
- application uses spotify, so a change to spotify can break application, while a change to application can't break spotify.
- Position
- Below the diagonal: application uses a module listed above it, which is the healthy direction.
40→9 application uses queue✕
- Connections
- 1 pair of types, where a type in application uses a type in queue.
- The types involved
ncspot.application.Application→ncspot.queue.Queue
- Direction
- application uses queue, so a change to queue can break application, while a change to application can't break queue.
- Position
- Below the diagonal: application uses a module listed above it, which is the healthy direction.
40→29 application uses ipc✕
- Connections
- 1 pair of types, where a type in application uses a type in ipc.
- The types involved
ncspot.application.Application→ncspot.ipc.IpcSocket
- Direction
- application uses ipc, so a change to ipc can break application, while a change to application can't break ipc.
- Position
- Below the diagonal: application uses a module listed above it, which is the healthy direction.
40→37 application uses commands✕
- Connections
- 1 pair of types, where a type in application uses a type in commands.
- The types involved
ncspot.application.UserDataInner→ncspot.commands.CommandManager
- Direction
- application uses commands, so a change to commands can break application, while a change to application can't break commands.
- Position
- Below the diagonal: application 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 — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 22 | High / Critical |
| A05:2025 — Injection | 17 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs; 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; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +6.2 pts | Low | ADR Quality |
| 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. | +5.4 pts | Medium | Architecture documentation |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.9 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. | +1.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Banned license finding(s) in License Compliance. | +1.4 pts | Low | License Compliance |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +1.0 pts | Low | Static Analysis (SAST) |
| 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. | +2.0 pts | Medium | Documentation (README) |
| Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.0 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| src/model/track.rs | 5.6 | Mixed | Code Duplication: Near-duplicate member pair (31 shared lines) |
| src/command.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/ui/layout.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/spotify_api.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/spotify.rs | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/ui/listview.rs | 7.0 | Mixed | Cyclomatic Complexity: ListView::on_command (cyclomatic 58) |
| src/library.rs | 7.0 | Mixed | Cognitive Complexity: Library::populate_artists (cognitive 25) |
| src/model/album.rs | 7.0 | Mixed | Cognitive Complexity: Album::load_all_tracks (cognitive 22) |
| src/commands.rs | 7.0 | Mixed | Cyclomatic Complexity: CommandManager::handle_default_commands (cyclomatic 35) |
| src/ui/search_results.rs | 7.2 | Mixed | God Classes: MethodTooLong: SearchResultsView.run_search |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/ui/pagination.rs | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/spotify_worker.rs | 7.4 | Mixed | Cyclomatic Complexity: Worker::run_loop (cyclomatic 42) |
| src/mpris.rs | 7.4 | Mixed | Cyclomatic Complexity: MprisPlayer::open_uri (cyclomatic 18) |
| src/application.rs | 7.4 | Mixed | Cyclomatic Complexity: Application::run (cyclomatic 16) |
| src/model/artist.rs | 7.4 | Mixed | Code Duplication: Edited copy of a member (21 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 42 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 — 42 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, 153 of 170 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: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, 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 (.rs) and this repository declares a Cargo test suite (repository root, 12 test files), 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.
- 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.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust 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.
- X12 Unreachable branch — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — 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, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — 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, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — 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, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — 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 Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust 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.
- X23 Unguarded diagnostic materialisation — 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, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — 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, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — 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 PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust 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.
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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
11 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was ncspot::command::parse at 99. A further 2 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Command::basename at 43 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with ncspot::command::parse (cyclomatic 99). — Refactoring it lifts Cyclomatic Complexity from 7.1 to about 7.7/10.
D2 · Cognitive Complexity
17 function(s) exceeded the cognitive complexity threshold of 15; the worst was ncspot::command::parse at 92.
What to do
- Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with ncspot::command::parse (cognitive 92), ListView::on_command (cognitive 86), Worker::run_loop (cognitive 75). — 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.6 to about 7.9/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
19 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 6 MethodTooLong finding(s) in God Classes — start with commands.rs (2), listview.rs, spotify_worker.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 FileTooLong finding(s) in God Classes — start with command.rs, library.rs, commands.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 ClassTooLong finding(s) in God Classes — start with library.rs, listview.rs, commands.rs. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
28 duplicated block group(s) detected. 9.4 % of the production lines (1,257 of 13,365) are in a reported copy. A further 26 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with album.rs (2), show.rs, listview.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with artist.rs, track.rs, authentication.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with sharing.rs, playlist.rs, album.rs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
2 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 1 of the 2 (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)
2 of 33 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with track.rs, spotify_api.rs. — One of this dimension's main actionable groups (2 warning-level).
D12 · Dependency Hygiene
5 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 593 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under BSD-2-Clause, which is its own choice and is not judged here.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: src/commands.rs (2×35=70)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with commands.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/ui/pagination.rs. Counted over 40 of the 54 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
9 deducted task-comment markers across 13365 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 8 TodoComment finding(s) in Explicit Debt — start with spotify.rs (3), pagination.rs (2), command.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with spotify.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 2 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
17 finding(s): 0 critical, 17 high, 0 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 10 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
15 finding(s): 1 critical, 1 high, 13 medium, 0 low.
What to do
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D34 · Knowledge Freshness
4 of 40 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/ui/tabbedview.rs. Counted over 40 of the 54 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 4 Orphaned file finding(s) in Knowledge Freshness — start with tabbedview.rs, main.rs, spotify_url.rs. — One of this dimension's main actionable groups (4 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
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
ES1 · Fold determinism
ES2 · Immutable events
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
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `xtask`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X21 · Side-effecting pattern guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 86% | Strong | Solid. |
| Architecture | 95% | Exemplary | Solid. |
| Maturity | 58% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 71% | Strong | Solid. |
| Security | 57% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
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 — 74 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: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~17 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- 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.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1756 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust 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. Aggregate roots were found in only one source directory (ui), which is a layered codebase, not two contexts. 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 .rs, 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
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 2 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- 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 — 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'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust 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 `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface: 54 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- 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
- X16 Unfloored truncation loop — 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X18 Disposal-pattern correctness — 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
- X19 Unrestored process-global state — 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
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- 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.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: 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. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — 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
- X3 Exception handling — 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
- 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 Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 20 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: ansi_colours
- REDACTED
- REDACTED
- REDACTED
Serious — 131 finding(s)
- TodoComment src/command.rs:566
- TodoComment src/spotify.rs:241
- TodoComment src/spotify.rs:243
- TodoComment src/spotify.rs:245
- TodoComment src/spotify_api.rs:455
- TodoComment src/ui/layout.rs:300
- TodoComment src/ui/pagination.rs:111
- TodoComment src/ui/pagination.rs:112
- MethodTooLong: ListView.on_command src/ui/listview.rs:505
- MethodTooLong: CommandManager.handle_default_commands src/commands.rs:147
- MethodTooLong: Worker.run_loop src/spotify_worker.rs:85
- MethodTooLong: CommandManager.default_keybindings src/commands.rs:501
- MethodTooLong: SearchResultsView.run_search src/ui/search_results.rs:389
- MethodTooLong: Application.new src/application.rs:83
- FileTooLong: src/command.rs src/command.rs
- FileTooLong: src/library.rs src/library.rs
- FileTooLong: src/commands.rs src/commands.rs
- FileTooLong: ui/listview.rs src/ui/listview.rs
- FileTooLong: src/spotify_api.rs src/spotify_api.rs
- ClassTooLong: Library src/library.rs:38
- ClassTooLong: ListView src/ui/listview.rs:40
- ClassTooLong: CommandManager src/commands.rs:54
- ClassTooLong: WebApi src/spotify_api.rs:32
- ClassTooLong: SearchResultsView src/ui/search_results.rs:25
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) src/model/show.rs:35
- Duplicated block (9 lines × 2) src/ui/listview.rs:666
- Duplicated block (9 lines × 2) src/model/album.rs:307
- Duplicated block (9 lines × 2) src/model/album.rs:213
- ListView::on_command (cyclomatic 58) src/ui/listview.rs:505
- ListView::handle_mouse_event (cyclomatic 17) src/ui/listview.rs:228
- ListView::draw (cyclomatic 17) src/ui/listview.rs:338
- ListView::on_command (cognitive 86) src/ui/listview.rs:505
- ListView::draw (cognitive 30) src/ui/listview.rs:338
- ListView::handle_mouse_event (cognitive 24) src/ui/listview.rs:228
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (15 corresponding lines) src/model/artist.rs:81
- Edited copy of a member (15 corresponding lines) src/model/track.rs:180
- Edited copy of a member (15 corresponding lines) src/authentication.rs:118
- Edited copy of a member (9 corresponding lines) src/sharing.rs:8
- Edited copy of a member (9 corresponding lines) src/model/playlist.rs:247
- Edited copy of a member (9 corresponding lines) src/model/album.rs:223
- Duplicated block (11 lines × 2) src/library.rs:702
- Duplicated block (11 lines × 2) src/model/playlist.rs:166
- Duplicated block (11 lines × 2) src/mpris.rs:398
- Duplicated block (8 lines × 2) src/library.rs:840
- Duplicated block (8 lines × 2) src/model/album.rs:168
- Duplicated block (8 lines × 2) src/model/album.rs:204
- Duplicated block (7 lines × 2) src/model/track.rs:71
- Duplicated block (7 lines × 2) src/ui/layout.rs:324
- Duplicated block (7 lines × 2) src/commands.rs:623
- Library::populate_artists (cognitive 25) src/library.rs:580
- Library::fetch_playlists (cognitive 18) src/library.rs:368
- StatusBar::on_event (cognitive 22) src/ui/statusbar.rs:222
- StatusBar::draw (cognitive 20) src/ui/statusbar.rs:91
- CommandManager::handle_default_commands (cognitive 20) src/commands.rs:147
- CommandManager::register_keybinding (cognitive 18) src/commands.rs:414
- TooManyMethods: WebApi src/spotify_api.rs:32
- TooManyMethods: Library src/library.rs:38
- Edited copy of a member (13 corresponding lines) src/ui/playlist.rs:66
- Edited copy of a member (13 corresponding lines) src/serialization.rs:56
- Edited copy of a member (11 corresponding lines) src/model/album.rs:201
- Edited copy of a member (11 corresponding lines) src/serialization.rs:44
- Edited copy of a member (4 corresponding lines) src/model/episode.rs:85
- Edited copy of a member (4 corresponding lines) src/model/episode.rs:70
- Low cohesion: Track (LCOM4 7) src/model/track.rs:20
- Low cohesion: WebApi (LCOM4 7) src/spotify_api.rs:32
- ncspot::command::parse (cyclomatic 99) src/command.rs:497
- Worker::run_loop (cyclomatic 42) src/spotify_worker.rs:85
- CommandManager::handle_default_commands (cyclomatic 35) src/commands.rs:147
- ContextMenu::new (cyclomatic 30) src/ui/contextmenu.rs:201
- Command::fmt (cyclomatic 28) src/command.rs:255
- MprisPlayer::open_uri (cyclomatic 18) src/mpris.rs:378
- Layout::on_event (cyclomatic 18) src/ui/layout.rs:404
- Application::run (cyclomatic 16) src/application.rs:251
- Hotspot: src/commands.rs src/commands.rs:147
- HackComment src/spotify.rs:499
- ncspot::command::parse (cognitive 92) src/command.rs:497
- Worker::run_loop (cognitive 75) src/spotify_worker.rs:85
- Application::run (cognitive 43) src/application.rs:251
- Layout::on_event (cognitive 28) src/ui/layout.rs:404
- ContextMenu::new (cognitive 26) src/ui/contextmenu.rs:201
- CoverView::on_command (cognitive 25) src/ui/cover.rs:308
- MprisPlayer::open_uri (cognitive 23) src/mpris.rs:378
- Album::load_all_tracks (cognitive 22) src/model/album.rs:34
- FunctionTooLong: ncspot::command::parse src/command.rs:497
- REDACTED
- REDACTED
- Near-duplicate member pair (31 shared lines) src/model/track.rs:41
- Members sharing a duplicated core (6 members, 50+ identical tokens) src/ui/search_results.rs:128
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/spotify_api.rs:401
- Edited copy of a member (40 corresponding lines) src/model/album.rs:257
- Edited copy of a member (39 corresponding lines) src/library.rs:491
- Edited copy of a member (25 corresponding lines) src/model/album.rs:84
- Edited copy of a member (36 corresponding lines) src/library.rs:675
- Edited copy of a member (21 corresponding lines) src/model/artist.rs:177
- Edited copies of one member (4 members, 25+ corresponding lines) src/library.rs:763
- Edited copy of a member (10 corresponding lines) src/library.rs:951
- Edited copy of a member (19 corresponding lines) src/model/artist.rs:101
- Edited copy of a member (6 corresponding lines) src/spotify_api.rs:692
- Edited copies of one member (8 members, 10+ corresponding lines) src/spotify_api.rs:562
- Edited copy of a member (12 corresponding lines) src/model/album.rs:188
- Duplicated block (14 lines × 3) src/command.rs:677
- Duplicated block (14 lines × 2) src/ui/cover.rs:335
- Duplicated block (12–13 lines × 2) src/model/album.rs:170
- Duplicated block (12 lines × 6) src/ui/search_results.rs:134
- Duplicated block (12 lines × 2) src/model/episode.rs:33
- Duplicated block (10–11 lines × 3) src/model/album.rs:286
- Duplicated block (9–10 lines × 4) src/spotify_api.rs:408
- Duplicated block (10 lines × 3) src/model/track.rs:42
- Duplicated block (10 lines × 2) src/command.rs:614
- Duplicated block (7–9 lines × 2) src/model/album.rs:87
- Duplicated block (7 lines × 3) src/model/album.rs:169
- Duplicated block (11 lines × 3) src/model/track.rs:56
- Duplicated block (2–7 lines × 3) src/model/track.rs:53
- Duplicated block (5 lines × 2) src/model/album.rs:141
- Duplicated block (6 lines × 3) src/commands.rs:599
- Off the main sequence: ncspot
Minor — 14 finding(s)
- Orphaned file src/ui/tabbedview.rs:1
- Orphaned file xtask/src/main.rs:1
- Orphaned file src/spotify_url.rs:1
- Orphaned file src/utils.rs:1
- Off-boarding risk: anonymized user #1
- No ADRs found src/main.rs:1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No release approval gate
Minor — 5 finding(s)
- Outdated: log
- Outdated: notify-rust
- Outdated: signal-hook
- Outdated: toml
- Outdated: zbus
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-3dbd96cbf3ab4044aa6f904ee5e64b9f/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-3dbd96cbf3ab4044aa6f904ee5e64b9f/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 . | 17 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 15 | artifacts/raw/osv-scanner.json |
| 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 | — |
| 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |