Executive summary
aome510/spotify-player falls short of our standard for a preview release, held back most by its Code Health lens, the quality of the code itself. It scores 63 out of 100 and is rated Adequate, and all 23 of its critical findings are security problems in the build pipeline and in its servers and containers.
Code Health, at 59, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is recording design decisions, worth about 3 points. Writing log messages as searchable templates would lift Code Health itself, also worth about 3.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four secrets can leak from the build pipeline, and three settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks.
The product code is 16,985 lines, about €19,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 8 findings
- Dependency Hygiene · Yanked release: clipboard-win
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €19,000 · Estimate
| Cost to rebuild | €6,300 to €32,000, for 106 to 336 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 63. 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: 16,985 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: which parts of the code depend on which
| uses → | 1 lyric_finder.search | 2 spotify_player.client.request | 3 spotify_player.state.ui.page | 4 spotify_player.state.ui.popup | 5 lyric_finder | 6 lyric_finder.parse | 7 spotify_player | 8 spotify_player.cli | 9 spotify_player.client.spotify | 10 spotify_player.config.theme | 11 spotify_player.media_control | 12 spotify_player.media_control.windows | 13 spotify_player.state.model | 14 spotify_player.ui | 15 spotify_player.ui.cover_image | 16 spotify_player.cli.commands | 17 spotify_player.client.middleware | 18 spotify_player.command | 19 spotify_player.event.clipboard | 20 spotify_player.key | 21 spotify_player.log_layer | 22 spotify_player.state.data | 23 spotify_player.state.queue | 24 spotify_player.ui.streaming | 25 spotify_player.config.keymap | 26 spotify_player.event | 27 spotify_player.event.page | 28 spotify_player.event.popup | 29 spotify_player.event.window | 30 spotify_player.state.player | 31 spotify_player.state.ui | 32 spotify_player.config | 33 spotify_player.state | 34 spotify_player.auth | 35 spotify_player.cli.handlers | 36 spotify_player.ui.playback | 37 spotify_player.client | 38 spotify_player.cli.client | 39 spotify_player.client.handlers | 40 spotify_player.streaming |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 lyric_finder.search | ||||||||||||||||||||||||||||||||||||||||
| 2 spotify_player.client.request | ||||||||||||||||||||||||||||||||||||||||
| 3 spotify_player.state.ui.page | ||||||||||||||||||||||||||||||||||||||||
| 4 spotify_player.state.ui.popup | ||||||||||||||||||||||||||||||||||||||||
| 5 lyric_finder | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 lyric_finder.parse | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 spotify_player | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 spotify_player.cli | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 spotify_player.client.spotify | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 spotify_player.config.theme | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 spotify_player.media_control | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 spotify_player.media_control.windows | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 spotify_player.state.model | 9 | |||||||||||||||||||||||||||||||||||||||
| 14 spotify_player.ui | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 spotify_player.ui.cover_image | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 spotify_player.cli.commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 spotify_player.client.middleware | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 spotify_player.command | 13 | |||||||||||||||||||||||||||||||||||||||
| 19 spotify_player.event.clipboard | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 spotify_player.key | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 spotify_player.log_layer | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 spotify_player.state.data | 1 | 11 | ||||||||||||||||||||||||||||||||||||||
| 23 spotify_player.state.queue | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 spotify_player.ui.streaming | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 spotify_player.config.keymap | 2 | 2 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 26 spotify_player.event | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 27 spotify_player.event.page | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 spotify_player.event.popup | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 spotify_player.event.window | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 spotify_player.state.player | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 spotify_player.state.ui | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 spotify_player.config | 5 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 spotify_player.state | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 spotify_player.auth | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 spotify_player.cli.handlers | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 spotify_player.ui.playback | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 spotify_player.client | 2 | 2 | 1 | 1 | 2 | 6 | 1 | |||||||||||||||||||||||||||||||||
| 38 spotify_player.cli.client | 2 | 6 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 spotify_player.client.handlers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 spotify_player.streaming | 2 | 1 | 1 |
5→1 lyric_finder uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in lyric_finder uses a type in lyric_finder.search.
- The types involved
lyric_finder.Client→lyric_finder.search.Result
- Direction
- lyric_finder uses lyric_finder.search, so a change to lyric_finder.search can break lyric_finder, while a change to lyric_finder can't break lyric_finder.search.
- Position
- Below the diagonal: lyric_finder uses a module listed above it, which is the healthy direction.
6→1 lyric_finder.parse uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in lyric_finder.parse uses a type in lyric_finder.search.
- The types involved
lyric_finder.parse.parse$module→lyric_finder.search.Result
- Direction
- lyric_finder.parse uses lyric_finder.search, so a change to lyric_finder.search can break lyric_finder.parse, while a change to lyric_finder.parse can't break lyric_finder.search.
- Position
- Below the diagonal: lyric_finder.parse uses a module listed above it, which is the healthy direction.
7→1 spotify_player uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player uses a type in lyric_finder.search.
- The types involved
spotify_player.spotify_player$module→lyric_finder.search.Result
- Direction
- spotify_player uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player, while a change to spotify_player can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player uses a module listed above it, which is the healthy direction.
8→1 spotify_player.cli uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.cli uses a type in lyric_finder.search.
- The types involved
spotify_player.cli.cli$module→lyric_finder.search.Result
- Direction
- spotify_player.cli uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.cli, while a change to spotify_player.cli can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.cli uses a module listed above it, which is the healthy direction.
9→1 spotify_player.client.spotify uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.client.spotify uses a type in lyric_finder.search.
- The types involved
spotify_player.client.spotify.Spotify→lyric_finder.search.Result
- Direction
- spotify_player.client.spotify uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.client.spotify, while a change to spotify_player.client.spotify can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.client.spotify uses a module listed above it, which is the healthy direction.
10→1 spotify_player.config.theme uses lyric_finder.search✕
- Connections
- 3 pairs of types, where a type in spotify_player.config.theme uses a type in lyric_finder.search.
- The types involved
spotify_player.config.theme.Color→lyric_finder.search.Resultspotify_player.config.theme.StyleColor→lyric_finder.search.Resultspotify_player.config.theme.ThemeConfig→lyric_finder.search.Result
- Direction
- spotify_player.config.theme uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.config.theme, while a change to spotify_player.config.theme can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.config.theme uses a module listed above it, which is the healthy direction.
11→1 spotify_player.media_control uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.media_control uses a type in lyric_finder.search.
- The types involved
spotify_player.media_control.media_control$module→lyric_finder.search.Result
- Direction
- spotify_player.media_control uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.media_control, while a change to spotify_player.media_control can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.media_control uses a module listed above it, which is the healthy direction.
12→1 spotify_player.media_control.windows uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.media_control.windows uses a type in lyric_finder.search.
- The types involved
spotify_player.media_control.windows.DummyWindow→lyric_finder.search.Result
- Direction
- spotify_player.media_control.windows uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.media_control.windows, while a change to spotify_player.media_control.windows can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.media_control.windows uses a module listed above it, which is the healthy direction.
13→1 spotify_player.state.model uses lyric_finder.search✕
- Connections
- 9 pairs of types, where a type in spotify_player.state.model uses a type in lyric_finder.search.
- The types involved
spotify_player.state.model.Album→lyric_finder.search.Resultspotify_player.state.model.Artist→lyric_finder.search.Resultspotify_player.state.model.Category→lyric_finder.search.Resultspotify_player.state.model.Episode→lyric_finder.search.Resultspotify_player.state.model.Playlist→lyric_finder.search.Resultspotify_player.state.model.PlaylistFolder→lyric_finder.search.Resultspotify_player.state.model.PlaylistFolderItem→lyric_finder.search.Resultspotify_player.state.model.Show→lyric_finder.search.Resultspotify_player.state.model.Track→lyric_finder.search.Result
- Direction
- spotify_player.state.model uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.state.model, while a change to spotify_player.state.model can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.state.model uses a module listed above it, which is the healthy direction.
14→1 spotify_player.ui uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.ui uses a type in lyric_finder.search.
- The types involved
spotify_player.ui.ui$module→lyric_finder.search.Result
- Direction
- spotify_player.ui uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.ui, while a change to spotify_player.ui can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.ui uses a module listed above it, which is the healthy direction.
15→1 spotify_player.ui.cover_image uses lyric_finder.search✕
- Connections
- 2 pairs of types, where a type in spotify_player.ui.cover_image uses a type in lyric_finder.search.
- The types involved
spotify_player.ui.cover_image.CoverImage→lyric_finder.search.Resultspotify_player.ui.cover_image.cover_image$module→lyric_finder.search.Result
- Direction
- spotify_player.ui.cover_image uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.ui.cover_image, while a change to spotify_player.ui.cover_image can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.ui.cover_image uses a module listed above it, which is the healthy direction.
16→8 spotify_player.cli.commands uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.cli.commands uses a type in spotify_player.cli.
- The types involved
spotify_player.cli.commands.commands$module→spotify_player.cli.Command
- Direction
- spotify_player.cli.commands uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.cli.commands, while a change to spotify_player.cli.commands can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.cli.commands uses a module listed above it, which is the healthy direction.
17→1 spotify_player.client.middleware uses lyric_finder.search✕
- Connections
- 5 pairs of types, where a type in spotify_player.client.middleware uses a type in lyric_finder.search.
- The types involved
spotify_player.client.middleware.CachedResponse→lyric_finder.search.Responsespotify_player.client.middleware.CachedResponse→lyric_finder.search.Resultspotify_player.client.middleware.SpotifyApiMiddleware→lyric_finder.search.Responsespotify_player.client.middleware.SpotifyApiMiddleware→lyric_finder.search.Resultspotify_player.client.middleware.SpotifyApiRequestManager→lyric_finder.search.Result
- Direction
- spotify_player.client.middleware uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.client.middleware, while a change to spotify_player.client.middleware can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.client.middleware uses a module listed above it, which is the healthy direction.
17→8 spotify_player.client.middleware uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.client.middleware uses a type in spotify_player.cli.
- The types involved
spotify_player.client.middleware.SpotifyApiMiddleware→spotify_player.cli.Request
- Direction
- spotify_player.client.middleware uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.client.middleware, while a change to spotify_player.client.middleware can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.client.middleware uses a module listed above it, which is the healthy direction.
18→13 spotify_player.command uses spotify_player.state.model✕
- Connections
- 13 pairs of types, where a type in spotify_player.command uses a type in spotify_player.state.model.
- The types involved
spotify_player.command.ActionContext→spotify_player.state.model.Albumspotify_player.command.ActionContext→spotify_player.state.model.Artistspotify_player.command.ActionContext→spotify_player.state.model.Episodespotify_player.command.ActionContext→spotify_player.state.model.Playlistspotify_player.command.ActionContext→spotify_player.state.model.PlaylistFolderItemspotify_player.command.ActionContext→spotify_player.state.model.Showspotify_player.command.ActionContext→spotify_player.state.model.Trackspotify_player.command.command$module→spotify_player.state.model.Albumspotify_player.command.command$module→spotify_player.state.model.Artistspotify_player.command.command$module→spotify_player.state.model.Episodespotify_player.command.command$module→spotify_player.state.model.Playlistspotify_player.command.command$module→spotify_player.state.model.Showspotify_player.command.command$module→spotify_player.state.model.Track
- Direction
- spotify_player.command uses spotify_player.state.model, so a change to spotify_player.state.model can break spotify_player.command, while a change to spotify_player.command can't break spotify_player.state.model.
- Position
- Below the diagonal: spotify_player.command uses a module listed above it, which is the healthy direction.
19→1 spotify_player.event.clipboard uses lyric_finder.search✕
- Connections
- 5 pairs of types, where a type in spotify_player.event.clipboard uses a type in lyric_finder.search.
- The types involved
spotify_player.event.clipboard.ClipboardProvider→lyric_finder.search.Resultspotify_player.event.clipboard.CommandProvider→lyric_finder.search.Resultspotify_player.event.clipboard.NopProvider→lyric_finder.search.Resultspotify_player.event.clipboard.WindowsProvider→lyric_finder.search.Resultspotify_player.event.clipboard.clipboard$module→lyric_finder.search.Result
- Direction
- spotify_player.event.clipboard uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.event.clipboard, while a change to spotify_player.event.clipboard can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.event.clipboard uses a module listed above it, which is the healthy direction.
19→8 spotify_player.event.clipboard uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.event.clipboard uses a type in spotify_player.cli.
- The types involved
spotify_player.event.clipboard.CommandProvider→spotify_player.cli.Command
- Direction
- spotify_player.event.clipboard uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.event.clipboard, while a change to spotify_player.event.clipboard can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.event.clipboard uses a module listed above it, which is the healthy direction.
20→1 spotify_player.key uses lyric_finder.search✕
- Connections
- 2 pairs of types, where a type in spotify_player.key uses a type in lyric_finder.search.
- The types involved
spotify_player.key.Key→lyric_finder.search.Resultspotify_player.key.KeySequence→lyric_finder.search.Result
- Direction
- spotify_player.key uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.key, while a change to spotify_player.key can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.key uses a module listed above it, which is the healthy direction.
20→8 spotify_player.key uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.key uses a type in spotify_player.cli.
- The types involved
spotify_player.key.KeySequence→spotify_player.cli.Key
- Direction
- spotify_player.key uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.key, while a change to spotify_player.key can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.key uses a module listed above it, which is the healthy direction.
21→13 spotify_player.log_layer uses spotify_player.state.model✕
- Connections
- 1 pair of types, where a type in spotify_player.log_layer uses a type in spotify_player.state.model.
- The types involved
spotify_player.log_layer.BufferLayer→spotify_player.state.model.Context
- Direction
- spotify_player.log_layer uses spotify_player.state.model, so a change to spotify_player.state.model can break spotify_player.log_layer, while a change to spotify_player.log_layer can't break spotify_player.state.model.
- Position
- Below the diagonal: spotify_player.log_layer uses a module listed above it, which is the healthy direction.
22→1 spotify_player.state.data uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.state.data uses a type in lyric_finder.search.
- The types involved
spotify_player.state.data.data$module→lyric_finder.search.Result
- Direction
- spotify_player.state.data uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.state.data, while a change to spotify_player.state.data can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.state.data uses a module listed above it, which is the healthy direction.
22→13 spotify_player.state.data uses spotify_player.state.model✕
- Connections
- 11 pairs of types, where a type in spotify_player.state.data uses a type in spotify_player.state.model.
- The types involved
spotify_player.state.data.AppData→spotify_player.state.model.ContextIdspotify_player.state.data.AppData→spotify_player.state.model.Trackspotify_player.state.data.BrowseData→spotify_player.state.model.Categoryspotify_player.state.data.MemoryCaches→spotify_player.state.model.SearchResultsspotify_player.state.data.UserData→spotify_player.state.model.Albumspotify_player.state.data.UserData→spotify_player.state.model.Artistspotify_player.state.data.UserData→spotify_player.state.model.Playlistspotify_player.state.data.UserData→spotify_player.state.model.PlaylistFolderItemspotify_player.state.data.UserData→spotify_player.state.model.PlaylistFolderNodespotify_player.state.data.UserData→spotify_player.state.model.Showspotify_player.state.data.UserData→spotify_player.state.model.Track
- Direction
- spotify_player.state.data uses spotify_player.state.model, so a change to spotify_player.state.model can break spotify_player.state.data, while a change to spotify_player.state.data can't break spotify_player.state.model.
- Position
- Below the diagonal: spotify_player.state.data uses a module listed above it, which is the healthy direction.
23→13 spotify_player.state.queue uses spotify_player.state.model✕
- Connections
- 1 pair of types, where a type in spotify_player.state.queue uses a type in spotify_player.state.model.
- The types involved
spotify_player.state.queue.CustomQueue→spotify_player.state.model.ContextId
- Direction
- spotify_player.state.queue uses spotify_player.state.model, so a change to spotify_player.state.model can break spotify_player.state.queue, while a change to spotify_player.state.queue can't break spotify_player.state.model.
- Position
- Below the diagonal: spotify_player.state.queue uses a module listed above it, which is the healthy direction.
24→10 spotify_player.ui.streaming uses spotify_player.config.theme✕
- Connections
- 2 pairs of types, where a type in spotify_player.ui.streaming uses a type in spotify_player.config.theme.
- The types involved
spotify_player.ui.streaming.streaming$module→spotify_player.config.theme.Colorspotify_player.ui.streaming.streaming$module→spotify_player.config.theme.Theme
- Direction
- spotify_player.ui.streaming uses spotify_player.config.theme, so a change to spotify_player.config.theme can break spotify_player.ui.streaming, while a change to spotify_player.ui.streaming can't break spotify_player.config.theme.
- Position
- Below the diagonal: spotify_player.ui.streaming uses a module listed above it, which is the healthy direction.
25→1 spotify_player.config.keymap uses lyric_finder.search✕
- Connections
- 2 pairs of types, where a type in spotify_player.config.keymap uses a type in lyric_finder.search.
- The types involved
spotify_player.config.keymap.Keymap→lyric_finder.search.Resultspotify_player.config.keymap.KeymapConfig→lyric_finder.search.Result
- Direction
- spotify_player.config.keymap uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.config.keymap, while a change to spotify_player.config.keymap can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.config.keymap uses a module listed above it, which is the healthy direction.
25→8 spotify_player.config.keymap uses spotify_player.cli✕
- Connections
- 2 pairs of types, where a type in spotify_player.config.keymap uses a type in spotify_player.cli.
- The types involved
spotify_player.config.keymap.Keymap→spotify_player.cli.Commandspotify_player.config.keymap.KeymapConfig→spotify_player.cli.Command
- Direction
- spotify_player.config.keymap uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.config.keymap, while a change to spotify_player.config.keymap can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.config.keymap uses a module listed above it, which is the healthy direction.
25→18 spotify_player.config.keymap uses spotify_player.command✕
- Connections
- 3 pairs of types, where a type in spotify_player.config.keymap uses a type in spotify_player.command.
- The types involved
spotify_player.config.keymap.ActionMap→spotify_player.command.Actionspotify_player.config.keymap.ActionMap→spotify_player.command.ActionTargetspotify_player.config.keymap.KeymapConfig→spotify_player.command.CommandOrAction
- Direction
- spotify_player.config.keymap uses spotify_player.command, so a change to spotify_player.command can break spotify_player.config.keymap, while a change to spotify_player.config.keymap can't break spotify_player.command.
- Position
- Below the diagonal: spotify_player.config.keymap uses a module listed above it, which is the healthy direction.
25→20 spotify_player.config.keymap uses spotify_player.key✕
- Connections
- 3 pairs of types, where a type in spotify_player.config.keymap uses a type in spotify_player.key.
- The types involved
spotify_player.config.keymap.ActionMap→spotify_player.key.KeySequencespotify_player.config.keymap.Keymap→spotify_player.key.KeySequencespotify_player.config.keymap.KeymapConfig→spotify_player.key.KeySequence
- Direction
- spotify_player.config.keymap uses spotify_player.key, so a change to spotify_player.key can break spotify_player.config.keymap, while a change to spotify_player.config.keymap can't break spotify_player.key.
- Position
- Below the diagonal: spotify_player.config.keymap uses a module listed above it, which is the healthy direction.
26→1 spotify_player.event uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.event uses a type in lyric_finder.search.
- The types involved
spotify_player.event.event$module→lyric_finder.search.Result
- Direction
- spotify_player.event uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.event, while a change to spotify_player.event can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.event uses a module listed above it, which is the healthy direction.
26→8 spotify_player.event uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.event uses a type in spotify_player.cli.
- The types involved
spotify_player.event.event$module→spotify_player.cli.Command
- Direction
- spotify_player.event uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.event, while a change to spotify_player.event can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.event uses a module listed above it, which is the healthy direction.
26→13 spotify_player.event uses spotify_player.state.model✕
- Connections
- 1 pair of types, where a type in spotify_player.event uses a type in spotify_player.state.model.
- The types involved
spotify_player.event.event$module→spotify_player.state.model.Artist
- Direction
- spotify_player.event uses spotify_player.state.model, so a change to spotify_player.state.model can break spotify_player.event, while a change to spotify_player.event can't break spotify_player.state.model.
- Position
- Below the diagonal: spotify_player.event uses a module listed above it, which is the healthy direction.
26→18 spotify_player.event uses spotify_player.command✕
- Connections
- 3 pairs of types, where a type in spotify_player.event uses a type in spotify_player.command.
- The types involved
spotify_player.event.event$module→spotify_player.command.Actionspotify_player.event.event$module→spotify_player.command.ActionContextspotify_player.event.event$module→spotify_player.command.ActionTarget
- Direction
- spotify_player.event uses spotify_player.command, so a change to spotify_player.command can break spotify_player.event, while a change to spotify_player.event can't break spotify_player.command.
- Position
- Below the diagonal: spotify_player.event uses a module listed above it, which is the healthy direction.
27→1 spotify_player.event.page uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.event.page uses a type in lyric_finder.search.
- The types involved
spotify_player.event.page.page$module→lyric_finder.search.Result
- Direction
- spotify_player.event.page uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.event.page, while a change to spotify_player.event.page can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.event.page uses a module listed above it, which is the healthy direction.
27→3 spotify_player.event.page uses spotify_player.state.ui.page✕
- Connections
- 1 pair of types, where a type in spotify_player.event.page uses a type in spotify_player.state.ui.page.
- The types involved
spotify_player.event.page.page$module→spotify_player.state.ui.page.PageState
- Direction
- spotify_player.event.page uses spotify_player.state.ui.page, so a change to spotify_player.state.ui.page can break spotify_player.event.page, while a change to spotify_player.event.page can't break spotify_player.state.ui.page.
- Position
- Below the diagonal: spotify_player.event.page uses a module listed above it, which is the healthy direction.
27→8 spotify_player.event.page uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.event.page uses a type in spotify_player.cli.
- The types involved
spotify_player.event.page.page$module→spotify_player.cli.Command
- Direction
- spotify_player.event.page uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.event.page, while a change to spotify_player.event.page can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.event.page uses a module listed above it, which is the healthy direction.
27→18 spotify_player.event.page uses spotify_player.command✕
- Connections
- 1 pair of types, where a type in spotify_player.event.page uses a type in spotify_player.command.
- The types involved
spotify_player.event.page.page$module→spotify_player.command.Action
- Direction
- spotify_player.event.page uses spotify_player.command, so a change to spotify_player.command can break spotify_player.event.page, while a change to spotify_player.event.page can't break spotify_player.command.
- Position
- Below the diagonal: spotify_player.event.page uses a module listed above it, which is the healthy direction.
27→20 spotify_player.event.page uses spotify_player.key✕
- Connections
- 1 pair of types, where a type in spotify_player.event.page uses a type in spotify_player.key.
- The types involved
spotify_player.event.page.page$module→spotify_player.key.KeySequence
- Direction
- spotify_player.event.page uses spotify_player.key, so a change to spotify_player.key can break spotify_player.event.page, while a change to spotify_player.event.page can't break spotify_player.key.
- Position
- Below the diagonal: spotify_player.event.page uses a module listed above it, which is the healthy direction.
28→1 spotify_player.event.popup uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.event.popup uses a type in lyric_finder.search.
- The types involved
spotify_player.event.popup.popup$module→lyric_finder.search.Result
- Direction
- spotify_player.event.popup uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.event.popup, while a change to spotify_player.event.popup can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.event.popup uses a module listed above it, which is the healthy direction.
28→4 spotify_player.event.popup uses spotify_player.state.ui.popup✕
- Connections
- 1 pair of types, where a type in spotify_player.event.popup uses a type in spotify_player.state.ui.popup.
- The types involved
spotify_player.event.popup.popup$module→spotify_player.state.ui.popup.ConfirmableAction
- Direction
- spotify_player.event.popup uses spotify_player.state.ui.popup, so a change to spotify_player.state.ui.popup can break spotify_player.event.popup, while a change to spotify_player.event.popup can't break spotify_player.state.ui.popup.
- Position
- Below the diagonal: spotify_player.event.popup uses a module listed above it, which is the healthy direction.
28→8 spotify_player.event.popup uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.event.popup uses a type in spotify_player.cli.
- The types involved
spotify_player.event.popup.popup$module→spotify_player.cli.Command
- Direction
- spotify_player.event.popup uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.event.popup, while a change to spotify_player.event.popup can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.event.popup uses a module listed above it, which is the healthy direction.
28→20 spotify_player.event.popup uses spotify_player.key✕
- Connections
- 1 pair of types, where a type in spotify_player.event.popup uses a type in spotify_player.key.
- The types involved
spotify_player.event.popup.popup$module→spotify_player.key.KeySequence
- Direction
- spotify_player.event.popup uses spotify_player.key, so a change to spotify_player.key can break spotify_player.event.popup, while a change to spotify_player.event.popup can't break spotify_player.key.
- Position
- Below the diagonal: spotify_player.event.popup uses a module listed above it, which is the healthy direction.
29→1 spotify_player.event.window uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.event.window uses a type in lyric_finder.search.
- The types involved
spotify_player.event.window.window$module→lyric_finder.search.Result
- Direction
- spotify_player.event.window uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.event.window, while a change to spotify_player.event.window can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.event.window uses a module listed above it, which is the healthy direction.
29→8 spotify_player.event.window uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.event.window uses a type in spotify_player.cli.
- The types involved
spotify_player.event.window.window$module→spotify_player.cli.Command
- Direction
- spotify_player.event.window uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.event.window, while a change to spotify_player.event.window can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.event.window uses a module listed above it, which is the healthy direction.
29→13 spotify_player.event.window uses spotify_player.state.model✕
- Connections
- 2 pairs of types, where a type in spotify_player.event.window uses a type in spotify_player.state.model.
- The types involved
spotify_player.event.window.PlaylistTrackSelection→spotify_player.state.model.Trackspotify_player.event.window.window$module→spotify_player.state.model.ContextId
- Direction
- spotify_player.event.window uses spotify_player.state.model, so a change to spotify_player.state.model can break spotify_player.event.window, while a change to spotify_player.event.window can't break spotify_player.state.model.
- Position
- Below the diagonal: spotify_player.event.window uses a module listed above it, which is the healthy direction.
29→18 spotify_player.event.window uses spotify_player.command✕
- Connections
- 1 pair of types, where a type in spotify_player.event.window uses a type in spotify_player.command.
- The types involved
spotify_player.event.window.window$module→spotify_player.command.Action
- Direction
- spotify_player.event.window uses spotify_player.command, so a change to spotify_player.command can break spotify_player.event.window, while a change to spotify_player.event.window can't break spotify_player.command.
- Position
- Below the diagonal: spotify_player.event.window uses a module listed above it, which is the healthy direction.
30→13 spotify_player.state.player uses spotify_player.state.model✕
- Connections
- 4 pairs of types, where a type in spotify_player.state.player uses a type in spotify_player.state.model.
- The types involved
spotify_player.state.player.PlayerState→spotify_player.state.model.ContextIdspotify_player.state.player.PlayerState→spotify_player.state.model.Devicespotify_player.state.player.PlayerState→spotify_player.state.model.PlaybackMetadataspotify_player.state.player.PlayerState→spotify_player.state.model.TracksId
- Direction
- spotify_player.state.player uses spotify_player.state.model, so a change to spotify_player.state.model can break spotify_player.state.player, while a change to spotify_player.state.player can't break spotify_player.state.model.
- Position
- Below the diagonal: spotify_player.state.player uses a module listed above it, which is the healthy direction.
30→23 spotify_player.state.player uses spotify_player.state.queue✕
- Connections
- 1 pair of types, where a type in spotify_player.state.player uses a type in spotify_player.state.queue.
- The types involved
spotify_player.state.player.PlayerState→spotify_player.state.queue.CustomQueue
- Direction
- spotify_player.state.player uses spotify_player.state.queue, so a change to spotify_player.state.queue can break spotify_player.state.player, while a change to spotify_player.state.player can't break spotify_player.state.queue.
- Position
- Below the diagonal: spotify_player.state.player uses a module listed above it, which is the healthy direction.
31→1 spotify_player.state.ui uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.state.ui uses a type in lyric_finder.search.
- The types involved
spotify_player.state.ui.ImageRenderInfo→lyric_finder.search.Result
- Direction
- spotify_player.state.ui uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.state.ui, while a change to spotify_player.state.ui can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.state.ui uses a module listed above it, which is the healthy direction.
31→3 spotify_player.state.ui uses spotify_player.state.ui.page✕
- Connections
- 1 pair of types, where a type in spotify_player.state.ui uses a type in spotify_player.state.ui.page.
- The types involved
spotify_player.state.ui.UIState→spotify_player.state.ui.page.PageState
- Direction
- spotify_player.state.ui uses spotify_player.state.ui.page, so a change to spotify_player.state.ui.page can break spotify_player.state.ui, while a change to spotify_player.state.ui can't break spotify_player.state.ui.page.
- Position
- Below the diagonal: spotify_player.state.ui uses a module listed above it, which is the healthy direction.
31→4 spotify_player.state.ui uses spotify_player.state.ui.popup✕
- Connections
- 1 pair of types, where a type in spotify_player.state.ui uses a type in spotify_player.state.ui.popup.
- The types involved
spotify_player.state.ui.UIState→spotify_player.state.ui.popup.PopupState
- Direction
- spotify_player.state.ui uses spotify_player.state.ui.popup, so a change to spotify_player.state.ui.popup can break spotify_player.state.ui, while a change to spotify_player.state.ui can't break spotify_player.state.ui.popup.
- Position
- Below the diagonal: spotify_player.state.ui uses a module listed above it, which is the healthy direction.
31→10 spotify_player.state.ui uses spotify_player.config.theme✕
- Connections
- 1 pair of types, where a type in spotify_player.state.ui uses a type in spotify_player.config.theme.
- The types involved
spotify_player.state.ui.UIState→spotify_player.config.theme.Theme
- Direction
- spotify_player.state.ui uses spotify_player.config.theme, so a change to spotify_player.config.theme can break spotify_player.state.ui, while a change to spotify_player.state.ui can't break spotify_player.config.theme.
- Position
- Below the diagonal: spotify_player.state.ui uses a module listed above it, which is the healthy direction.
31→14 spotify_player.state.ui uses spotify_player.ui✕
- Connections
- 1 pair of types, where a type in spotify_player.state.ui uses a type in spotify_player.ui.
- The types involved
spotify_player.state.ui.UIState→spotify_player.ui.Orientation
- Direction
- spotify_player.state.ui uses spotify_player.ui, so a change to spotify_player.ui can break spotify_player.state.ui, while a change to spotify_player.state.ui can't break spotify_player.ui.
- Position
- Below the diagonal: spotify_player.state.ui uses a module listed above it, which is the healthy direction.
31→15 spotify_player.state.ui uses spotify_player.ui.cover_image✕
- Connections
- 1 pair of types, where a type in spotify_player.state.ui uses a type in spotify_player.ui.cover_image.
- The types involved
spotify_player.state.ui.ImageRenderInfo→spotify_player.ui.cover_image.CoverImage
- Direction
- spotify_player.state.ui uses spotify_player.ui.cover_image, so a change to spotify_player.ui.cover_image can break spotify_player.state.ui, while a change to spotify_player.state.ui can't break spotify_player.ui.cover_image.
- Position
- Below the diagonal: spotify_player.state.ui uses a module listed above it, which is the healthy direction.
31→20 spotify_player.state.ui uses spotify_player.key✕
- Connections
- 1 pair of types, where a type in spotify_player.state.ui uses a type in spotify_player.key.
- The types involved
spotify_player.state.ui.UIState→spotify_player.key.KeySequence
- Direction
- spotify_player.state.ui uses spotify_player.key, so a change to spotify_player.key can break spotify_player.state.ui, while a change to spotify_player.state.ui can't break spotify_player.key.
- Position
- Below the diagonal: spotify_player.state.ui uses a module listed above it, which is the healthy direction.
32→1 spotify_player.config uses lyric_finder.search✕
- Connections
- 5 pairs of types, where a type in spotify_player.config uses a type in lyric_finder.search.
- The types involved
spotify_player.config.AppConfig→lyric_finder.search.Resultspotify_player.config.Command→lyric_finder.search.Resultspotify_player.config.Configs→lyric_finder.search.Resultspotify_player.config.LayoutConfig→lyric_finder.search.Resultspotify_player.config.config$module→lyric_finder.search.Result
- Direction
- spotify_player.config uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.config, while a change to spotify_player.config can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.config uses a module listed above it, which is the healthy direction.
32→8 spotify_player.config uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.config uses a type in spotify_player.cli.
- The types involved
spotify_player.config.AppConfig→spotify_player.cli.Command
- Direction
- spotify_player.config uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.config, while a change to spotify_player.config can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.config uses a module listed above it, which is the healthy direction.
32→10 spotify_player.config uses spotify_player.config.theme✕
- Connections
- 1 pair of types, where a type in spotify_player.config uses a type in spotify_player.config.theme.
- The types involved
spotify_player.config.Configs→spotify_player.config.theme.ThemeConfig
- Direction
- spotify_player.config uses spotify_player.config.theme, so a change to spotify_player.config.theme can break spotify_player.config, while a change to spotify_player.config can't break spotify_player.config.theme.
- Position
- Below the diagonal: spotify_player.config uses a module listed above it, which is the healthy direction.
32→25 spotify_player.config uses spotify_player.config.keymap✕
- Connections
- 1 pair of types, where a type in spotify_player.config uses a type in spotify_player.config.keymap.
- The types involved
spotify_player.config.Configs→spotify_player.config.keymap.KeymapConfig
- Direction
- spotify_player.config uses spotify_player.config.keymap, so a change to spotify_player.config.keymap can break spotify_player.config, while a change to spotify_player.config can't break spotify_player.config.keymap.
- Position
- Below the diagonal: spotify_player.config uses a module listed above it, which is the healthy direction.
33→22 spotify_player.state uses spotify_player.state.data✕
- Connections
- 1 pair of types, where a type in spotify_player.state uses a type in spotify_player.state.data.
- The types involved
spotify_player.state.State→spotify_player.state.data.AppData
- Direction
- spotify_player.state uses spotify_player.state.data, so a change to spotify_player.state.data can break spotify_player.state, while a change to spotify_player.state can't break spotify_player.state.data.
- Position
- Below the diagonal: spotify_player.state uses a module listed above it, which is the healthy direction.
33→24 spotify_player.state uses spotify_player.ui.streaming✕
- Connections
- 1 pair of types, where a type in spotify_player.state uses a type in spotify_player.ui.streaming.
- The types involved
spotify_player.state.State→spotify_player.ui.streaming.VisBands
- Direction
- spotify_player.state uses spotify_player.ui.streaming, so a change to spotify_player.ui.streaming can break spotify_player.state, while a change to spotify_player.state can't break spotify_player.ui.streaming.
- Position
- Below the diagonal: spotify_player.state uses a module listed above it, which is the healthy direction.
33→30 spotify_player.state uses spotify_player.state.player✕
- Connections
- 1 pair of types, where a type in spotify_player.state uses a type in spotify_player.state.player.
- The types involved
spotify_player.state.State→spotify_player.state.player.PlayerState
- Direction
- spotify_player.state uses spotify_player.state.player, so a change to spotify_player.state.player can break spotify_player.state, while a change to spotify_player.state can't break spotify_player.state.player.
- Position
- Below the diagonal: spotify_player.state uses a module listed above it, which is the healthy direction.
33→31 spotify_player.state uses spotify_player.state.ui✕
- Connections
- 1 pair of types, where a type in spotify_player.state uses a type in spotify_player.state.ui.
- The types involved
spotify_player.state.State→spotify_player.state.ui.UIState
- Direction
- spotify_player.state uses spotify_player.state.ui, so a change to spotify_player.state.ui can break spotify_player.state, while a change to spotify_player.state can't break spotify_player.state.ui.
- Position
- Below the diagonal: spotify_player.state uses a module listed above it, which is the healthy direction.
34→1 spotify_player.auth uses lyric_finder.search✕
- Connections
- 2 pairs of types, where a type in spotify_player.auth uses a type in lyric_finder.search.
- The types involved
spotify_player.auth.AuthConfig→lyric_finder.search.Resultspotify_player.auth.auth$module→lyric_finder.search.Result
- Direction
- spotify_player.auth uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.auth, while a change to spotify_player.auth can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.auth uses a module listed above it, which is the healthy direction.
34→9 spotify_player.auth uses spotify_player.client.spotify✕
- Connections
- 2 pairs of types, where a type in spotify_player.auth uses a type in spotify_player.client.spotify.
- The types involved
spotify_player.auth.auth$module→spotify_player.client.spotify.PkceWebApiClientspotify_player.auth.auth$module→spotify_player.client.spotify.WebApiClient
- Direction
- spotify_player.auth uses spotify_player.client.spotify, so a change to spotify_player.client.spotify can break spotify_player.auth, while a change to spotify_player.auth can't break spotify_player.client.spotify.
- Position
- Below the diagonal: spotify_player.auth uses a module listed above it, which is the healthy direction.
34→32 spotify_player.auth uses spotify_player.config✕
- Connections
- 1 pair of types, where a type in spotify_player.auth uses a type in spotify_player.config.
- The types involved
spotify_player.auth.AuthConfig→spotify_player.config.Configs
- Direction
- spotify_player.auth uses spotify_player.config, so a change to spotify_player.config can break spotify_player.auth, while a change to spotify_player.auth can't break spotify_player.config.
- Position
- Below the diagonal: spotify_player.auth uses a module listed above it, which is the healthy direction.
35→1 spotify_player.cli.handlers uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.cli.handlers uses a type in lyric_finder.search.
- The types involved
spotify_player.cli.handlers.handlers$module→lyric_finder.search.Result
- Direction
- spotify_player.cli.handlers uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.cli.handlers, while a change to spotify_player.cli.handlers can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.cli.handlers uses a module listed above it, which is the healthy direction.
35→8 spotify_player.cli.handlers uses spotify_player.cli✕
- Connections
- 2 pairs of types, where a type in spotify_player.cli.handlers uses a type in spotify_player.cli.
- The types involved
spotify_player.cli.handlers.handlers$module→spotify_player.cli.IdOrNamespotify_player.cli.handlers.handlers$module→spotify_player.cli.Request
- Direction
- spotify_player.cli.handlers uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.cli.handlers, while a change to spotify_player.cli.handlers can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.cli.handlers uses a module listed above it, which is the healthy direction.
35→32 spotify_player.cli.handlers uses spotify_player.config✕
- Connections
- 1 pair of types, where a type in spotify_player.cli.handlers uses a type in spotify_player.config.
- The types involved
spotify_player.cli.handlers.handlers$module→spotify_player.config.Configs
- Direction
- spotify_player.cli.handlers uses spotify_player.config, so a change to spotify_player.config can break spotify_player.cli.handlers, while a change to spotify_player.cli.handlers can't break spotify_player.config.
- Position
- Below the diagonal: spotify_player.cli.handlers uses a module listed above it, which is the healthy direction.
36→13 spotify_player.ui.playback uses spotify_player.state.model✕
- Connections
- 1 pair of types, where a type in spotify_player.ui.playback uses a type in spotify_player.state.model.
- The types involved
spotify_player.ui.playback.playback$module→spotify_player.state.model.PlaybackMetadata
- Direction
- spotify_player.ui.playback uses spotify_player.state.model, so a change to spotify_player.state.model can break spotify_player.ui.playback, while a change to spotify_player.ui.playback can't break spotify_player.state.model.
- Position
- Below the diagonal: spotify_player.ui.playback uses a module listed above it, which is the healthy direction.
36→32 spotify_player.ui.playback uses spotify_player.config✕
- Connections
- 1 pair of types, where a type in spotify_player.ui.playback uses a type in spotify_player.config.
- The types involved
spotify_player.ui.playback.playback$module→spotify_player.config.Configs
- Direction
- spotify_player.ui.playback uses spotify_player.config, so a change to spotify_player.config can break spotify_player.ui.playback, while a change to spotify_player.ui.playback can't break spotify_player.config.
- Position
- Below the diagonal: spotify_player.ui.playback uses a module listed above it, which is the healthy direction.
37→1 spotify_player.client uses lyric_finder.search✕
- Connections
- 2 pairs of types, where a type in spotify_player.client uses a type in lyric_finder.search.
- The types involved
spotify_player.client.AppClient→lyric_finder.search.Resultspotify_player.client.client$module→lyric_finder.search.Result
- Direction
- spotify_player.client uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.client, while a change to spotify_player.client can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.client uses a module listed above it, which is the healthy direction.
37→2 spotify_player.client uses spotify_player.client.request✕
- Connections
- 2 pairs of types, where a type in spotify_player.client uses a type in spotify_player.client.request.
- The types involved
spotify_player.client.AppClient→spotify_player.client.request.ClientRequestspotify_player.client.AppClient→spotify_player.client.request.PlayerRequest
- Direction
- spotify_player.client uses spotify_player.client.request, so a change to spotify_player.client.request can break spotify_player.client, while a change to spotify_player.client can't break spotify_player.client.request.
- Position
- Below the diagonal: spotify_player.client uses a module listed above it, which is the healthy direction.
37→5 spotify_player.client uses lyric_finder✕
- Connections
- 1 pair of types, where a type in spotify_player.client uses a type in lyric_finder.
- The types involved
spotify_player.client.AppClient→lyric_finder.Client
- Direction
- spotify_player.client uses lyric_finder, so a change to lyric_finder can break spotify_player.client, while a change to spotify_player.client can't break lyric_finder.
- Position
- Below the diagonal: spotify_player.client uses a module listed above it, which is the healthy direction.
37→8 spotify_player.client uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.client uses a type in spotify_player.cli.
- The types involved
spotify_player.client.AppClient→spotify_player.cli.ItemId
- Direction
- spotify_player.client uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.client, while a change to spotify_player.client can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.client uses a module listed above it, which is the healthy direction.
37→9 spotify_player.client uses spotify_player.client.spotify✕
- Connections
- 2 pairs of types, where a type in spotify_player.client uses a type in spotify_player.client.spotify.
- The types involved
spotify_player.client.AppClient→spotify_player.client.spotify.Spotifyspotify_player.client.AppClient→spotify_player.client.spotify.WebApiClient
- Direction
- spotify_player.client uses spotify_player.client.spotify, so a change to spotify_player.client.spotify can break spotify_player.client, while a change to spotify_player.client can't break spotify_player.client.spotify.
- Position
- Below the diagonal: spotify_player.client uses a module listed above it, which is the healthy direction.
37→13 spotify_player.client uses spotify_player.state.model✕
- Connections
- 6 pairs of types, where a type in spotify_player.client uses a type in spotify_player.state.model.
- The types involved
spotify_player.client.AppClient→spotify_player.state.model.Albumspotify_player.client.AppClient→spotify_player.state.model.Devicespotify_player.client.AppClient→spotify_player.state.model.Itemspotify_player.client.AppClient→spotify_player.state.model.Playbackspotify_player.client.AppClient→spotify_player.state.model.PlaybackMetadataspotify_player.client.client$module→spotify_player.state.model.Track
- Direction
- spotify_player.client uses spotify_player.state.model, so a change to spotify_player.state.model can break spotify_player.client, while a change to spotify_player.client can't break spotify_player.state.model.
- Position
- Below the diagonal: spotify_player.client uses a module listed above it, which is the healthy direction.
37→34 spotify_player.client uses spotify_player.auth✕
- Connections
- 1 pair of types, where a type in spotify_player.client uses a type in spotify_player.auth.
- The types involved
spotify_player.client.AppClient→spotify_player.auth.AuthConfig
- Direction
- spotify_player.client uses spotify_player.auth, so a change to spotify_player.auth can break spotify_player.client, while a change to spotify_player.client can't break spotify_player.auth.
- Position
- Below the diagonal: spotify_player.client uses a module listed above it, which is the healthy direction.
38→1 spotify_player.cli.client uses lyric_finder.search✕
- Connections
- 2 pairs of types, where a type in spotify_player.cli.client uses a type in lyric_finder.search.
- The types involved
spotify_player.cli.client.client$module→lyric_finder.search.Responsespotify_player.cli.client.client$module→lyric_finder.search.Result
- Direction
- spotify_player.cli.client uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.cli.client, while a change to spotify_player.cli.client can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.cli.client uses a module listed above it, which is the healthy direction.
38→8 spotify_player.cli.client uses spotify_player.cli✕
- Connections
- 6 pairs of types, where a type in spotify_player.cli.client uses a type in spotify_player.cli.
- The types involved
spotify_player.cli.client.client$module→spotify_player.cli.Commandspotify_player.cli.client.client$module→spotify_player.cli.IdOrNamespotify_player.cli.client.client$module→spotify_player.cli.ItemTypespotify_player.cli.client.client$module→spotify_player.cli.Keyspotify_player.cli.client.client$module→spotify_player.cli.PlaylistCommandspotify_player.cli.client.client$module→spotify_player.cli.Request
- Direction
- spotify_player.cli.client uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.cli.client, while a change to spotify_player.cli.client can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.cli.client uses a module listed above it, which is the healthy direction.
38→37 spotify_player.cli.client uses spotify_player.client✕
- Connections
- 1 pair of types, where a type in spotify_player.cli.client uses a type in spotify_player.client.
- The types involved
spotify_player.cli.client.client$module→spotify_player.client.AppClient
- Direction
- spotify_player.cli.client uses spotify_player.client, so a change to spotify_player.client can break spotify_player.cli.client, while a change to spotify_player.cli.client can't break spotify_player.client.
- Position
- Below the diagonal: spotify_player.cli.client uses a module listed above it, which is the healthy direction.
39→1 spotify_player.client.handlers uses lyric_finder.search✕
- Connections
- 1 pair of types, where a type in spotify_player.client.handlers uses a type in lyric_finder.search.
- The types involved
spotify_player.client.handlers.handlers$module→lyric_finder.search.Result
- Direction
- spotify_player.client.handlers uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.client.handlers, while a change to spotify_player.client.handlers can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.client.handlers uses a module listed above it, which is the healthy direction.
39→37 spotify_player.client.handlers uses spotify_player.client✕
- Connections
- 1 pair of types, where a type in spotify_player.client.handlers uses a type in spotify_player.client.
- The types involved
spotify_player.client.handlers.handlers$module→spotify_player.client.AppClient
- Direction
- spotify_player.client.handlers uses spotify_player.client, so a change to spotify_player.client can break spotify_player.client.handlers, while a change to spotify_player.client.handlers can't break spotify_player.client.
- Position
- Below the diagonal: spotify_player.client.handlers uses a module listed above it, which is the healthy direction.
40→1 spotify_player.streaming uses lyric_finder.search✕
- Connections
- 2 pairs of types, where a type in spotify_player.streaming uses a type in lyric_finder.search.
- The types involved
spotify_player.streaming.PlayerEvent→lyric_finder.search.Resultspotify_player.streaming.streaming$module→lyric_finder.search.Result
- Direction
- spotify_player.streaming uses lyric_finder.search, so a change to lyric_finder.search can break spotify_player.streaming, while a change to spotify_player.streaming can't break lyric_finder.search.
- Position
- Below the diagonal: spotify_player.streaming uses a module listed above it, which is the healthy direction.
40→8 spotify_player.streaming uses spotify_player.cli✕
- Connections
- 1 pair of types, where a type in spotify_player.streaming uses a type in spotify_player.cli.
- The types involved
spotify_player.streaming.streaming$module→spotify_player.cli.Command
- Direction
- spotify_player.streaming uses spotify_player.cli, so a change to spotify_player.cli can break spotify_player.streaming, while a change to spotify_player.streaming can't break spotify_player.cli.
- Position
- Below the diagonal: spotify_player.streaming uses a module listed above it, which is the healthy direction.
40→37 spotify_player.streaming uses spotify_player.client✕
- Connections
- 1 pair of types, where a type in spotify_player.streaming uses a type in spotify_player.client.
- The types involved
spotify_player.streaming.streaming$module→spotify_player.client.AppClient
- Direction
- spotify_player.streaming uses spotify_player.client, so a change to spotify_player.client can break spotify_player.streaming, while a change to spotify_player.streaming can't break spotify_player.client.
- Position
- Below the diagonal: spotify_player.streaming 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 |
|---|---|---|
| A05:2025 — Injection | 21 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 18 | Medium |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
First, replace interpolated log messages with structured logging to ensure data is machine-readable and searchable. Next, establish a dedicated ADR directory to document significant design decisions, capturing the context, choice, and consequences for each. Simultaneously, remove the blocking thread sleep from asynchronous code to prevent performance bottlenecks and update dependencies to eliminate any yanked releases.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.0 pts | Low | ADR Quality |
| Interpolated log message defeats structured logging | +3.1 pts | Medium | Structured logging |
| Resolve the 1 Yanked release finding(s) in Dependency Hygiene. | +1.3 pts | Low | Dependency Hygiene |
| 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. | +2.6 pts | Medium | Architecture documentation |
| Blocking `thread::sleep` inside an `async` body | +1.4 pts | Medium | Async correctness |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.3 pts | Medium | Documentation (README) |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.6 pts | Low | Bus Factor |
| Enable Dependabot/Renovate or a dependency-review gate. | +1.2 pts | Medium | Security & performance tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| spotify_player/src/event/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| spotify_player/src/client/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| spotify_player/src/ui/page.rs | 7.0 | Near-clean | Cyclomatic Complexity: spotify_player::ui::page::render_search_page (cyclomatic 27) |
| spotify_player/src/cli/client.rs | 7.0 | Near-clean | Cyclomatic Complexity: spotify_player::cli::client::handle_playback_request (cyclomatic 23) |
| spotify_player/src/config/mod.rs | 7.0 | Near-clean | God Classes: TooManyFields: AppConfig |
| spotify_player/src/event/window.rs | 7.0 | Near-clean | Cyclomatic Complexity: spotify_player::event::window::handle_command_for_focused_context_window (cyclomatic 19) |
| spotify_player/src/ui/playback.rs | 7.0 | Near-clean | Cyclomatic Complexity: spotify_player::ui::playback::construct_playback_text (cyclomatic 35) |
| spotify_player/src/event/popup.rs | 7.1 | Near-clean | Cyclomatic Complexity: spotify_player::event::popup::handle_key_sequence_for_popup (cyclomatic 26) |
| REDACTED | 7.2 | Near-clean | IaC & Container Security: High IaC: REDACTED |
| spotify_player/src/command.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| spotify_player/src/event/page.rs | 7.4 | Near-clean | Cyclomatic Complexity: spotify_player::event::page::handle_key_sequence_for_search_page (cyclomatic 32) |
| spotify_player/src/streaming.rs | 7.8 | Near-clean | Cyclomatic Complexity: spotify_player::streaming::new_connection (cyclomatic 20) |
| spotify_player/src/client/handlers.rs | 7.8 | Near-clean | Cyclomatic Complexity: spotify_player::client::handlers::handle_page_change_event (cyclomatic 17) |
| spotify_player/src/state/queue.rs | 7.8 | Near-clean | Cognitive Complexity: CustomQueue::set_shuffle_mode (cognitive 17) |
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
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 49 of 49 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 49 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, 195 of 219 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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 |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 6 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — [0m - FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 1) REDACTED:1 -------------------- 1 | >>> FROM rust as builder 2 | WORKDIR app 3 | COPY . . -------------------- ERROR: failed to solve: rust: failed to resolve source metadata for docker.io/library/rust:latest: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/latest": Forbidden; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- 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
18 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was spotify_player::event::handle_global_command at 61. A further 5 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::desc at 62 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: spotify_player/src/command.rs (Command::desc at 62), spotify_player/src/key.rs (Key::parse_key_code at 31), spotify_player/src/config/theme.rs (StyleColor::deserialize at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with spotify_player::event::handle_global_command (cyclomatic 61), spotify_player::event::handle_action_in_context (cyclomatic 48), AppClient::handle_request (cyclomatic 40). — 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 5 together lifts Cyclomatic Complexity from 6.6 to about 7.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
31 function(s) exceeded the cognitive complexity threshold of 15; the worst was spotify_player::ui::playback::construct_playback_text at 57.
What to do
- Bring the 9 bodies over 30 down to 30 or less in Cognitive Complexity — start with spotify_player::ui::playback::construct_playback_text (cognitive 57), spotify_player::ui::playback::render_playback_window (cognitive 49), spotify_player::event::page::handle_key_sequence_for_search_page (cognitive 47). — 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 9 together lifts Cognitive Complexity from 4.7 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
24 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 14 FunctionTooLong finding(s) in God Classes — start with page.rs (5), client.rs (3), mod.rs (2). — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 5 FileTooLong finding(s) in God Classes — start with mod.rs (2), page.rs, client.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with keymap.rs, mod.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
27 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with mod.rs (3), client.rs, model.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with page.rs (2), data.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with mod.rs, popup.rs, playback.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
1 of 30 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
45 test methods: 45 unit, 0 integration, 0 BDD, 0 e2e. The Rust suite contributes 45 `#[test]` function(s) across 6 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
12 outdated, 1 yanked direct Cargo dependencies. 51 of 53 direct crates were graded against crates.io (0 not published there, 2 not resolved by a committed REDACTED). 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.
What to do
- Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 756 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.
D15 · Churn × Complexity Hotspots
Top hotspots: spotify_player/src/client/mod.rs (13×40=520); spotify_player/src/event/page.rs (5×32=160); spotify_player/src/ui/page.rs (5×27=135)
What to do
- Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with page.rs (2), mod.rs, playback.rs. — One of this dimension's main actionable groups (5 warning-level).
D16 · Bus Factor
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is spotify_player/src/client/spotify.rs. Counted over 40 of the 45 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
6 deducted task-comment markers across 16985 LoC (0.0/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 6 TodoComment finding(s) in Explicit Debt — start with command.rs (2), mod.rs (2), main.rs. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 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. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
21 finding(s): 0 critical, 20 high, 1 medium, 0 low. 16 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 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 16 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 (16 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
9 finding(s): 0 critical, 0 high, 9 medium, 0 low.
What to do
- Resolve the 3 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 3 high, 2 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 40 of the 45 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 2 of 2 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- 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
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
- `start_app` is async and calls thread::sleep — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — spotify_player/src/main.rs:79
What to do
- Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
X1 · Async correctness
- This `async` body is polled on an executor's worker thread, and `std::thread::sleep` blocks that thread: for the whole delay no other task scheduled on it makes progress — the Rust form of blocking on a task. Use `tokio::time::sleep(…).await` (or the runtime's own timer), which suspends only this task. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the executor with `tokio::task::spawn_blocking(…).await`. — spotify_player/src/main.rs:223
What to do
- Blocking `thread::sleep` inside an `async` body
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn!` at line 188 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/auth.rs:188
- `info!` at line 248 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/auth.rs:248
- `warn!` at line 254 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/auth.rs:254
- `warn!` at line 261 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/auth.rs:261
- `debug!` at line 278 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/auth.rs:278
- `warn!` at line 301 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/auth.rs:301
- `error!` at line 200 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/main.rs:200
- `info!` at line 294 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/main.rs:294
- `info!` at line 102 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/media_control.rs:102
- `info!` at line 177 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/streaming.rs:177
- `info!` at line 195 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/streaming.rs:195
- `warn!` at line 267 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/streaming.rs:267
- `info!` at line 270 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/streaming.rs:270
- `warn!` at line 297 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/streaming.rs:297
- `info!` at line 43 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/token.rs:43
- `error!` at line 48 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/ui/cover_image.rs:48
- `error!` at line 70 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/ui/mod.rs:70
- `warn!` at line 99 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/ui/mod.rs:99
- `info!` at line 112 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/ui/mod.rs:112
- `error!` at line 92 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/ui/playback.rs:92
- `info!` at line 272 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/state/data.rs:272
- `info!` at line 276 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/state/data.rs:276
- `error!` at line 280 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/state/data.rs:280
- `warn!` at line 121 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/state/ui/mod.rs:121
- `error!` at line 59 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — spotify_player/src/event/mod.rs:59, spotify_player/src/client/handlers.rs:59
- `debug!` at line 70 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/event/mod.rs:70
- `debug!` at line 139 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/event/mod.rs:139
- `warn!` at line 811 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/event/mod.rs:811
- `warn!` at line 353 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/config/keymap.rs:353
- `warn!` at line 493 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/config/mod.rs:493
- `warn!` at line 170 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/config/theme.rs:170
- `error!` at line 37 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/client/handlers.rs:37
- `info!` at line 143 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/client/handlers.rs:143
- `info!` at line 190 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/client/handlers.rs:190
- `error!` at line 246 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/client/handlers.rs:246
- `error!` at line 204 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/client/mod.rs:204
- `error!` at line 218 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/client/mod.rs:218
- `warn!` at line 232 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/client/mod.rs:232
- `warn!` at line 239 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — spotify_player/src/client/mod.rs:239
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 59% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 60% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61% | Adequate | Acceptable, with room to improve. |
| Security | 70% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 85% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 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 — 70 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.
- AC7 A11y enforcement — 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — [0m - FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 1) REDACTED:1 -------------------- 1 | >>> FROM rust as builder 2 | WORKDIR app 3 | COPY . . -------------------- ERROR: failed to solve: rust: failed to resolve source metadata for docker.io/library/rust:latest: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/latest": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, 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 — ~25 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 — Naming consistency is measured on C# only; Rust not measured.
- 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+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic 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.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks. 29 claim(s) of kinds M4 does not check were not checked (environment variable 1, setting 28); M4 checks only links and versions.
- 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[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 applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- S1 Web-Security Posture — No web surface: 45 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.
- 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
- 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.
- 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
- 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.
- 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 — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 133 finding(s)
- spotify_player::ui::playback::construct_playback_text (cognitive 57) spotify_player/src/ui/playback.rs:224
- spotify_player::ui::playback::render_playback_window (cognitive 49) spotify_player/src/ui/playback.rs:19
- spotify_player::event::page::handle_key_sequence_for_search_page (cognitive 47) spotify_player/src/event/page.rs:197
- spotify_player::event::handle_global_command (cognitive 45) spotify_player/src/event/mod.rs:573
- spotify_player::cli::client::handle_playlist_request (cognitive 43) spotify_player/src/cli/client.rs:489
- spotify_player::streaming::new_connection (cognitive 42) spotify_player/src/streaming.rs:151
- spotify_player::cli::client::get_spotify_id (cognitive 41) spotify_player/src/cli/client.rs:243
- spotify_player::ui::page::render_search_page (cognitive 38) spotify_player/src/ui/page.rs:37
- spotify_player::event::handle_action_in_context (cognitive 32) spotify_player/src/event/mod.rs:198
- spotify_player::client::handlers::handle_page_change_event (cognitive 29) spotify_player/src/client/handlers.rs:123
- spotify_player::ui::page::render_track_table (cognitive 27) spotify_player/src/ui/page.rs:1065
- spotify_player::cli::client::playlist_import (cognitive 23) spotify_player/src/cli/client.rs:722
- spotify_player::event::popup::handle_key_sequence_for_playlist_search_popup (cognitive 22) spotify_player/src/event/popup.rs:575
- spotify_player::event::handle_mouse_event (cognitive 20) spotify_player/src/event/mod.rs:65
- spotify_player::cli::client::handle_playback_request (cognitive 19) spotify_player/src/cli/client.rs:347
- spotify_player::event::handle_key_event (cognitive 19) spotify_player/src/event/mod.rs:121
- spotify_player::event::popup::handle_key_sequence_for_popup (cognitive 19) spotify_player/src/event/popup.rs:7
- spotify_player::event::window::handle_command_for_focused_context_window (cognitive 19) spotify_player/src/event/window.rs:109
- spotify_player::ui::page::render_episode_table (cognitive 19) spotify_player/src/ui/page.rs:1231
- spotify_player::cli::client::handle_socket_request (cognitive 17) spotify_player/src/cli/client.rs:132
- spotify_player::cli::client::start_socket (cognitive 16) spotify_player/src/cli/client.rs:33
- spotify_player::event::window::handle_command_for_track_table_window (cognitive 16) spotify_player/src/event/window.rs:282
- spotify_player::event::handle_global_command (cyclomatic 61) spotify_player/src/event/mod.rs:573
- spotify_player::event::handle_action_in_context (cyclomatic 48) spotify_player/src/event/mod.rs:198
- spotify_player::ui::playback::construct_playback_text (cyclomatic 35) spotify_player/src/ui/playback.rs:224
- spotify_player::event::page::handle_key_sequence_for_search_page (cyclomatic 32) spotify_player/src/event/page.rs:197
- spotify_player::ui::page::render_search_page (cyclomatic 27) spotify_player/src/ui/page.rs:37
- spotify_player::event::popup::handle_key_sequence_for_popup (cyclomatic 26) spotify_player/src/event/popup.rs:7
- spotify_player::cli::client::handle_playback_request (cyclomatic 23) spotify_player/src/cli/client.rs:347
- spotify_player::cli::client::handle_playlist_request (cyclomatic 21) spotify_player/src/cli/client.rs:489
- spotify_player::streaming::new_connection (cyclomatic 20) spotify_player/src/streaming.rs:151
- spotify_player::event::window::handle_command_for_focused_context_window (cyclomatic 19) spotify_player/src/event/window.rs:109
- spotify_player::ui::playback::render_playback_window (cyclomatic 19) spotify_player/src/ui/playback.rs:19
- spotify_player::cli::client::get_spotify_id (cyclomatic 18) spotify_player/src/cli/client.rs:243
- spotify_player::media_control::start_event_watcher (cyclomatic 18) spotify_player/src/media_control.rs:78
- spotify_player::client::handlers::handle_page_change_event (cyclomatic 17) spotify_player/src/client/handlers.rs:123
- FunctionTooLong: spotify_player::event::handle_global_command spotify_player/src/event/mod.rs:573
- FunctionTooLong: spotify_player::event::popup::handle_key_sequence_for_popup spotify_player/src/event/popup.rs:7
- FunctionTooLong: spotify_player::event::handle_action_in_context spotify_player/src/event/mod.rs:198
- FunctionTooLong: spotify_player::ui::page::render_search_page spotify_player/src/ui/page.rs:37
- FunctionTooLong: spotify_player::cli::client::handle_playlist_request spotify_player/src/cli/client.rs:489
- FunctionTooLong: spotify_player::ui::popup::render_popup spotify_player/src/ui/popup.rs:18
- FunctionTooLong: spotify_player::ui::page::render_track_table spotify_player/src/ui/page.rs:1065
- FunctionTooLong: spotify_player::event::page::handle_key_sequence_for_search_page spotify_player/src/event/page.rs:197
- FunctionTooLong: spotify_player::ui::playback::construct_playback_text spotify_player/src/ui/playback.rs:224
- FunctionTooLong: spotify_player::ui::page::render_artist_context_page_windows spotify_player/src/ui/page.rs:907
- FunctionTooLong: spotify_player::ui::playback::render_playback_window spotify_player/src/ui/playback.rs:19
- FunctionTooLong: spotify_player::cli::client::playlist_import spotify_player/src/cli/client.rs:722
- FunctionTooLong: spotify_player::ui::page::render_library_page spotify_player/src/ui/page.rs:448
- FunctionTooLong: spotify_player::cli::client::handle_playback_request spotify_player/src/cli/client.rs:347
- TodoComment spotify_player/src/command.rs:125
- TodoComment spotify_player/src/command.rs:195
- TodoComment spotify_player/src/event/mod.rs:469
- TodoComment spotify_player/src/main.rs:229
- TodoComment spotify_player/src/client/mod.rs:786
- TodoComment spotify_player/src/client/spotify.rs:66
- Duplicated block (10 lines × 2) spotify_player/src/cli/client.rs:734
- Duplicated block (10 lines × 2) spotify_player/src/event/mod.rs:211
- Duplicated block (10 lines × 2) spotify_player/src/event/mod.rs:265
- Duplicated block (10 lines × 2) spotify_player/src/state/model.rs:364
- Duplicated block (10 lines × 2) spotify_player/src/event/mod.rs:227
- Duplicated block (10 lines × 2) spotify_player/src/ui/page.rs:137
- Hotspot: spotify_player/src/client/mod.rs spotify_player/src/client/mod.rs:470
- Hotspot: spotify_player/src/event/page.rs spotify_player/src/event/page.rs:197
- Hotspot: spotify_player/src/ui/page.rs spotify_player/src/ui/page.rs:37
- Hotspot: spotify_player/src/ui/playback.rs spotify_player/src/ui/playback.rs:19
- Hotspot: spotify_player/src/streaming.rs spotify_player/src/streaming.rs:151
- AppClient::handle_request (cognitive 26) spotify_player/src/client/mod.rs:470
- AppClient::initialize_playback (cognitive 22) spotify_player/src/client/mod.rs:189
- AppClient::handle_new_playback_event (cognitive 19) spotify_player/src/client/mod.rs:1730
- AppClient::handle_player_request (cognitive 17) spotify_player/src/client/mod.rs:361
- AppClient::notify_new_playback (cognitive 16) spotify_player/src/client/mod.rs:1892
- FileTooLong: client/mod.rs spotify_player/src/client/mod.rs
- FileTooLong: ui/page.rs spotify_player/src/ui/page.rs
- FileTooLong: event/mod.rs spotify_player/src/event/mod.rs
- FileTooLong: cli/client.rs spotify_player/src/cli/client.rs
- FileTooLong: event/window.rs spotify_player/src/event/window.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- AppClient::handle_request (cyclomatic 40) spotify_player/src/client/mod.rs:470
- AppClient::handle_player_request (cyclomatic 22) spotify_player/src/client/mod.rs:361
- AppClient::handle_new_playback_event (cyclomatic 17) spotify_player/src/client/mod.rs:1730
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) spotify_player/src/state/data.rs:134
- Duplicated block (12 lines × 2) spotify_player/src/ui/page.rs:767
- Duplicated block (12 lines × 2) spotify_player/src/ui/page.rs:147
- Duplicated block (11 lines × 2) spotify_player/src/client/mod.rs:1161
- Duplicated block (11 lines × 2) spotify_player/src/state/ui/popup.rs:89
- Duplicated block (11 lines × 2) spotify_player/src/ui/playback.rs:413
- MethodTooLong: KeymapConfig.default spotify_player/src/config/keymap.rs:34
- MethodTooLong: AppClient.handle_request spotify_player/src/client/mod.rs:470
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2) spotify_player/src/event/popup.rs:179
- Duplicated block (14 lines × 2) spotify_player/src/ui/page.rs:615
- PageState::focus_window_state_mut (cyclomatic 21) spotify_player/src/state/ui/page.rs:174
- Yanked release: clipboard-win
- VisualizationSink::write (cognitive 28) spotify_player/src/ui/streaming.rs:191
- LineInput::input (cognitive 20) spotify_player/src/ui/single_line_input.rs:37
- CustomQueue::set_shuffle_mode (cognitive 17) spotify_player/src/state/queue.rs:309
- lyric_finder::improve_query (cognitive 16) lyric_finder/src/lib.rs:152
- REDACTED
- ClassTooLong: AppClient spotify_player/src/client/mod.rs:72
- TooManyMethods: AppClient spotify_player/src/client/mod.rs:72
- TooManyFields: AppConfig spotify_player/src/config/mod.rs:53
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) spotify_player/src/event/window.rs:405
- Duplicated block (26–42 lines × 2) spotify_player/src/ui/page.rs:1167
- Duplicated block (18–24 lines × 2) spotify_player/src/event/window.rs:408
- Duplicated block (17 lines × 2) spotify_player/src/event/popup.rs:153
- Duplicated block (16 lines × 2) spotify_player/src/ui/page.rs:1098
- Duplicated block (15 lines × 2) spotify_player/src/cli/client.rs:637
- Duplicated block (12 lines × 3) spotify_player/src/event/window.rs:435
- Duplicated block (11 lines × 6) spotify_player/src/ui/page.rs:181
- Duplicated block (11 lines × 4) spotify_player/src/event/window.rs:406
- Duplicated block (11 lines × 3) spotify_player/src/event/window.rs:454
- Duplicated block (9 lines × 2) spotify_player/src/state/queue.rs:325
- Duplicated block (8 lines × 2) spotify_player/src/ui/utils.rs:95
- Duplicated block (6 lines × 2) spotify_player/src/event/mod.rs:616
- Duplicated block (5 lines × 2) spotify_player/src/client/mod.rs:1675
- Low cohesion: AppConfig (LCOM4 4) spotify_player/src/config/mod.rs:53
- Sync-over-async blocking spotify_player/src/main.rs:79
- Blocking `thread::sleep` inside an `async` body spotify_player/src/main.rs:223
Minor — 51 finding(s)
- Interpolated log message defeats structured logging spotify_player/src/auth.rs:188
- Interpolated log message defeats structured logging spotify_player/src/auth.rs:248
- Interpolated log message defeats structured logging spotify_player/src/auth.rs:254
- Interpolated log message defeats structured logging spotify_player/src/auth.rs:261
- Interpolated log message defeats structured logging spotify_player/src/auth.rs:278
- Interpolated log message defeats structured logging spotify_player/src/auth.rs:301
- Interpolated log message defeats structured logging spotify_player/src/main.rs:200
- Interpolated log message defeats structured logging spotify_player/src/main.rs:294
- Interpolated log message defeats structured logging spotify_player/src/media_control.rs:102
- Interpolated log message defeats structured logging spotify_player/src/streaming.rs:177
- Interpolated log message defeats structured logging spotify_player/src/streaming.rs:195
- Interpolated log message defeats structured logging spotify_player/src/streaming.rs:267
- Interpolated log message defeats structured logging spotify_player/src/streaming.rs:270
- Interpolated log message defeats structured logging spotify_player/src/streaming.rs:297
- Interpolated log message defeats structured logging spotify_player/src/token.rs:43
- Interpolated log message defeats structured logging spotify_player/src/ui/cover_image.rs:48
- Interpolated log message defeats structured logging spotify_player/src/ui/mod.rs:70
- Interpolated log message defeats structured logging spotify_player/src/ui/mod.rs:99
- Interpolated log message defeats structured logging spotify_player/src/ui/mod.rs:112
- Interpolated log message defeats structured logging spotify_player/src/ui/playback.rs:92
- Interpolated log message defeats structured logging spotify_player/src/state/data.rs:272
- Interpolated log message defeats structured logging spotify_player/src/state/data.rs:276
- Interpolated log message defeats structured logging spotify_player/src/state/data.rs:280
- Interpolated log message defeats structured logging spotify_player/src/state/ui/mod.rs:121
- Interpolated log message defeats structured logging spotify_player/src/event/mod.rs:59
- Off-boarding risk: anonymized user #1
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No release approval gate
- No changelog
- Duplicated predicate spotify_player/src/ui/page.rs:1098
Minor — 12 finding(s)
- Outdated: backtrace
- Outdated: clap
- Outdated: clap_complete
- Outdated: notify-rust
- Outdated: open
- Outdated: rand
- Outdated: ratatui-image
- Outdated: rustls
- Outdated: serde_json
- Outdated: sha2
- Outdated: tokio
- Outdated: toml
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ad0c3d89cf2e4037baa6f312ec92c832/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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ad0c3d89cf2e4037baa6f312ec92c832/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/watchdog-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 . | 21 | 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 . | 9 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 |