Executive summary
jpochyla/psst falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. 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 the packages it uses.
Maturity, at 55, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Having someone learn and document the 53 files no active contributor knows is another step, worth about 5 points. Raising Maturity to 70 would lift the score to about 67.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five known security holes in the packages the code depends on can be used by attackers, and two pipeline steps install packages that can change without warning. Pinning each tool to an exact version, updating the vulnerable packages and pinning what the pipeline installs would close these risks.
The product code is 19,875 lines, about €23,000 to rebuild.
If Maturity rose from 55 to 70, the lowest score rated Strong, the score would rise from 63 to about 67.
New since the last survey: 34 findings
- Code Duplication · Edited copy of a member (60 corresponding lines) psst-gui/src/ui/library.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) psst-gui/src/ui/theme.rs
- Code Duplication · Edited copy of a member (24 corresponding lines) psst-gui/src/controller/playback.rs
- Code Duplication · Edited copy of a member (27 corresponding lines) psst-core/src/oauth.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) psst-gui/src/data/nav.rs
- Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) psst-gui/src/widget/promise.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) psst-gui/src/widget/remote_image.rs
- Code Duplication · Edited copies of one member (7 members, 16+ corresponding lines) psst-gui/src/ui/home.rs
- Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) psst-gui/src/ui/album.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) psst-core/src/player/mod.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) psst-gui/src/ui/home.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) psst-core/src/metadata.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) psst-core/src/session/audio_key.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) psst-gui/src/widget/maybe.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) psst-core/src/player/file.rs
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) psst-gui/src/webapi/client.rs
- Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) psst-gui/src/ui/home.rs
- Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) psst-gui/src/ui/mod.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) psst-gui/src/data/mod.rs
- Code Duplication · Edited copy of a member (6 corresponding lines) psst-gui/src/widget/maybe.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) psst-core/src/audio/decode.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) psst-gui/src/ui/artist.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) psst-gui/src/widget/maybe.rs
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) psst-gui/src/ui/episode.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) psst-gui/src/ui/playlist.rs
- Code Duplication · Duplicated block (12 lines × 2) psst-gui/src/webapi/client.rs
- Code Duplication · Duplicated block (10 lines × 2) psst-gui/src/ui/playback.rs
- Code Duplication · Duplicated block (8 lines × 2) psst-core/src/player/mod.rs
- Code Duplication · Duplicated block (6 lines × 2) psst-gui/src/ui/album.rs
- Code Duplication · Duplicated block (9 lines × 2) psst-core/src/oauth.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 5 findings
- Code Duplication · Duplicated block (6 lines × 2) psst-gui/src/ui/album.rs
- Code Duplication · Duplicated block (9 lines × 2) psst-core/src/oauth.rs
- Dependency Vulnerabilities · Medium CVE: RUSTSEC-2024-0336 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0346 REDACTED
Rebuild cost: about €23,000 · Estimate
| Cost to rebuild | €7,500 to €38,000, for 125 to 396 hours of work, about 0.2 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: 19,875 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 psst_core.actor | 2 psst_core.audio.decode | 3 psst_core.connection.shannon_codec | 4 psst_core.item_id | 5 psst_gui.data.find | 6 psst_gui.data.nav | 7 psst_gui.data.promise | 8 psst_gui.widget.icons | 9 psst_core.audio.output.cpal | 10 psst_core.connection | 11 psst_core.session.audio_key | 12 psst_core.audio.output.cubeb | 13 psst_core.session | 14 psst_core.session.login5 | 15 psst_core.cdn | 16 psst_core.player.file | 17 psst_core.metadata | 18 psst_core.player.item | 19 psst_core.player.worker | 20 psst_gui.data.track | 21 psst_core.player | 22 psst_core.session.mercury | 23 psst_gui.data.playback | 24 psst_gui.data.config | 25 psst_gui.ui.playable | 26 psst_gui.ui.playback | 27 psst_gui.data.recommend | 28 psst_gui.data.search | 29 psst_gui.data.utils | 30 psst_gui.data.album | 31 psst_gui.data.artist | 32 psst_gui.data.playlist | 33 psst_gui.data.show | 34 psst_gui.webapi.client | 35 psst_gui.data | 36 psst_gui.controller.playback | 37 psst_gui.ui | 38 psst_gui.ui.episode | 39 psst_gui.ui.preferences | 40 psst_gui.ui.track |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 psst_core.actor | ||||||||||||||||||||||||||||||||||||||||
| 2 psst_core.audio.decode | ||||||||||||||||||||||||||||||||||||||||
| 3 psst_core.connection.shannon_codec | ||||||||||||||||||||||||||||||||||||||||
| 4 psst_core.item_id | ||||||||||||||||||||||||||||||||||||||||
| 5 psst_gui.data.find | ||||||||||||||||||||||||||||||||||||||||
| 6 psst_gui.data.nav | ||||||||||||||||||||||||||||||||||||||||
| 7 psst_gui.data.promise | ||||||||||||||||||||||||||||||||||||||||
| 8 psst_gui.widget.icons | ||||||||||||||||||||||||||||||||||||||||
| 9 psst_core.audio.output.cpal | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 psst_core.connection | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 psst_core.session.audio_key | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 psst_core.audio.output.cubeb | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 psst_core.session | 3 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 14 psst_core.session.login5 | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 psst_core.cdn | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 psst_core.player.file | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 psst_core.metadata | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 psst_core.player.item | 1 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 19 psst_core.player.worker | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 psst_gui.data.track | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 psst_core.player | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 22 psst_core.session.mercury | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 psst_gui.data.playback | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 24 psst_gui.data.config | 1 | 2 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 psst_gui.ui.playable | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 psst_gui.ui.playback | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 27 psst_gui.data.recommend | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 psst_gui.data.search | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 psst_gui.data.utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 psst_gui.data.album | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 psst_gui.data.artist | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 psst_gui.data.playlist | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 psst_gui.data.show | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 34 psst_gui.webapi.client | 1 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 35 psst_gui.data | 1 | 1 | 2 | 3 | 1 | 2 | 7 | 2 | 1 | 1 | 1 | 2 | 1 | 3 | 2 | |||||||||||||||||||||||||
| 36 psst_gui.controller.playback | 1 | 1 | 3 | 3 | 2 | |||||||||||||||||||||||||||||||||||
| 37 psst_gui.ui | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 psst_gui.ui.episode | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 psst_gui.ui.preferences | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 psst_gui.ui.track | 1 | 1 | 2 | 1 |
9→1 psst_core.audio.output.cpal uses psst_core.actor✕
- Connections
- 2 pairs of types, where a type in psst_core.audio.output.cpal uses a type in psst_core.actor.
- The types involved
psst_core.audio.output.cpal.CpalOutput→psst_core.actor.ActorHandlepsst_core.audio.output.cpal.Stream→psst_core.actor.Actor
- Direction
- psst_core.audio.output.cpal uses psst_core.actor, so a change to psst_core.actor can break psst_core.audio.output.cpal, while a change to psst_core.audio.output.cpal can't break psst_core.actor.
- Position
- Below the diagonal: psst_core.audio.output.cpal uses a module listed above it, which is the healthy direction.
10→3 psst_core.connection uses psst_core.connection.shannon_codec✕
- Connections
- 3 pairs of types, where a type in psst_core.connection uses a type in psst_core.connection.shannon_codec.
- The types involved
psst_core.connection.Transport→psst_core.connection.shannon_codec.ShannonDecoderpsst_core.connection.Transport→psst_core.connection.shannon_codec.ShannonEncoderpsst_core.connection.connection$module→psst_core.connection.shannon_codec.ShannonMsg
- Direction
- psst_core.connection uses psst_core.connection.shannon_codec, so a change to psst_core.connection.shannon_codec can break psst_core.connection, while a change to psst_core.connection can't break psst_core.connection.shannon_codec.
- Position
- Below the diagonal: psst_core.connection uses a module listed above it, which is the healthy direction.
11→3 psst_core.session.audio_key uses psst_core.connection.shannon_codec✕
- Connections
- 1 pair of types, where a type in psst_core.session.audio_key uses a type in psst_core.connection.shannon_codec.
- The types involved
psst_core.session.audio_key.AudioKeyDispatcher→psst_core.connection.shannon_codec.ShannonMsg
- Direction
- psst_core.session.audio_key uses psst_core.connection.shannon_codec, so a change to psst_core.connection.shannon_codec can break psst_core.session.audio_key, while a change to psst_core.session.audio_key can't break psst_core.connection.shannon_codec.
- Position
- Below the diagonal: psst_core.session.audio_key uses a module listed above it, which is the healthy direction.
11→4 psst_core.session.audio_key uses psst_core.item_id✕
- Connections
- 2 pairs of types, where a type in psst_core.session.audio_key uses a type in psst_core.item_id.
- The types involved
psst_core.session.audio_key.AudioKeyDispatcher→psst_core.item_id.FileIdpsst_core.session.audio_key.AudioKeyDispatcher→psst_core.item_id.ItemId
- Direction
- psst_core.session.audio_key uses psst_core.item_id, so a change to psst_core.item_id can break psst_core.session.audio_key, while a change to psst_core.session.audio_key can't break psst_core.item_id.
- Position
- Below the diagonal: psst_core.session.audio_key uses a module listed above it, which is the healthy direction.
12→1 psst_core.audio.output.cubeb uses psst_core.actor✕
- Connections
- 2 pairs of types, where a type in psst_core.audio.output.cubeb uses a type in psst_core.actor.
- The types involved
psst_core.audio.output.cubeb.CubebOutput→psst_core.actor.ActorHandlepsst_core.audio.output.cubeb.Stream→psst_core.actor.Actor
- Direction
- psst_core.audio.output.cubeb uses psst_core.actor, so a change to psst_core.actor can break psst_core.audio.output.cubeb, while a change to psst_core.audio.output.cubeb can't break psst_core.actor.
- Position
- Below the diagonal: psst_core.audio.output.cubeb uses a module listed above it, which is the healthy direction.
12→9 psst_core.audio.output.cubeb uses psst_core.audio.output.cpal✕
- Connections
- 2 pairs of types, where a type in psst_core.audio.output.cubeb uses a type in psst_core.audio.output.cpal.
- The types involved
psst_core.audio.output.cubeb.Stream→psst_core.audio.output.cpal.Streampsst_core.audio.output.cubeb.StreamCallback→psst_core.audio.output.cpal.CallbackState
- Direction
- psst_core.audio.output.cubeb uses psst_core.audio.output.cpal, so a change to psst_core.audio.output.cpal can break psst_core.audio.output.cubeb, while a change to psst_core.audio.output.cubeb can't break psst_core.audio.output.cpal.
- Position
- Below the diagonal: psst_core.audio.output.cubeb uses a module listed above it, which is the healthy direction.
13→3 psst_core.session uses psst_core.connection.shannon_codec✕
- Connections
- 3 pairs of types, where a type in psst_core.session uses a type in psst_core.connection.shannon_codec.
- The types involved
psst_core.session.session$module→psst_core.connection.shannon_codec.ShannonDecoderpsst_core.session.session$module→psst_core.connection.shannon_codec.ShannonEncoderpsst_core.session.session$module→psst_core.connection.shannon_codec.ShannonMsg
- Direction
- psst_core.session uses psst_core.connection.shannon_codec, so a change to psst_core.connection.shannon_codec can break psst_core.session, while a change to psst_core.session can't break psst_core.connection.shannon_codec.
- Position
- Below the diagonal: psst_core.session uses a module listed above it, which is the healthy direction.
13→4 psst_core.session uses psst_core.item_id✕
- Connections
- 2 pairs of types, where a type in psst_core.session uses a type in psst_core.item_id.
- The types involved
psst_core.session.SessionHandle→psst_core.item_id.FileIdpsst_core.session.SessionHandle→psst_core.item_id.ItemId
- Direction
- psst_core.session uses psst_core.item_id, so a change to psst_core.item_id can break psst_core.session, while a change to psst_core.session can't break psst_core.item_id.
- Position
- Below the diagonal: psst_core.session uses a module listed above it, which is the healthy direction.
13→10 psst_core.session uses psst_core.connection✕
- Connections
- 4 pairs of types, where a type in psst_core.session uses a type in psst_core.connection.
- The types involved
psst_core.session.SessionConfig→psst_core.connection.Credentialspsst_core.session.SessionConnection→psst_core.connection.Credentialspsst_core.session.SessionConnection→psst_core.connection.Transportpsst_core.session.SessionWorker→psst_core.connection.Transport
- Direction
- psst_core.session uses psst_core.connection, so a change to psst_core.connection can break psst_core.session, while a change to psst_core.session can't break psst_core.connection.
- Position
- Below the diagonal: psst_core.session uses a module listed above it, which is the healthy direction.
14→13 psst_core.session.login5 uses psst_core.session✕
- Connections
- 1 pair of types, where a type in psst_core.session.login5 uses a type in psst_core.session.
- The types involved
psst_core.session.login5.Login5→psst_core.session.SessionService
- Direction
- psst_core.session.login5 uses psst_core.session, so a change to psst_core.session can break psst_core.session.login5, while a change to psst_core.session.login5 can't break psst_core.session.
- Position
- Below the diagonal: psst_core.session.login5 uses a module listed above it, which is the healthy direction.
15→4 psst_core.cdn uses psst_core.item_id✕
- Connections
- 1 pair of types, where a type in psst_core.cdn uses a type in psst_core.item_id.
- The types involved
psst_core.cdn.Cdn→psst_core.item_id.FileId
- Direction
- psst_core.cdn uses psst_core.item_id, so a change to psst_core.item_id can break psst_core.cdn, while a change to psst_core.cdn can't break psst_core.item_id.
- Position
- Below the diagonal: psst_core.cdn uses a module listed above it, which is the healthy direction.
15→13 psst_core.cdn uses psst_core.session✕
- Connections
- 1 pair of types, where a type in psst_core.cdn uses a type in psst_core.session.
- The types involved
psst_core.cdn.Cdn→psst_core.session.SessionService
- Direction
- psst_core.cdn uses psst_core.session, so a change to psst_core.session can break psst_core.cdn, while a change to psst_core.cdn can't break psst_core.session.
- Position
- Below the diagonal: psst_core.cdn uses a module listed above it, which is the healthy direction.
15→14 psst_core.cdn uses psst_core.session.login5✕
- Connections
- 1 pair of types, where a type in psst_core.cdn uses a type in psst_core.session.login5.
- The types involved
psst_core.cdn.Cdn→psst_core.session.login5.Login5
- Direction
- psst_core.cdn uses psst_core.session.login5, so a change to psst_core.session.login5 can break psst_core.cdn, while a change to psst_core.cdn can't break psst_core.session.login5.
- Position
- Below the diagonal: psst_core.cdn uses a module listed above it, which is the healthy direction.
16→2 psst_core.player.file uses psst_core.audio.decode✕
- Connections
- 1 pair of types, where a type in psst_core.player.file uses a type in psst_core.audio.decode.
- The types involved
psst_core.player.file.MediaFile→psst_core.audio.decode.AudioCodecFormat
- Direction
- psst_core.player.file uses psst_core.audio.decode, so a change to psst_core.audio.decode can break psst_core.player.file, while a change to psst_core.player.file can't break psst_core.audio.decode.
- Position
- Below the diagonal: psst_core.player.file uses a module listed above it, which is the healthy direction.
16→4 psst_core.player.file uses psst_core.item_id✕
- Connections
- 2 pairs of types, where a type in psst_core.player.file uses a type in psst_core.item_id.
- The types involved
psst_core.player.file.MediaPath→psst_core.item_id.FileIdpsst_core.player.file.MediaPath→psst_core.item_id.ItemId
- Direction
- psst_core.player.file uses psst_core.item_id, so a change to psst_core.item_id can break psst_core.player.file, while a change to psst_core.player.file can't break psst_core.item_id.
- Position
- Below the diagonal: psst_core.player.file uses a module listed above it, which is the healthy direction.
16→15 psst_core.player.file uses psst_core.cdn✕
- Connections
- 1 pair of types, where a type in psst_core.player.file uses a type in psst_core.cdn.
- The types involved
psst_core.player.file.StreamedFile→psst_core.cdn.CdnUrl
- Direction
- psst_core.player.file uses psst_core.cdn, so a change to psst_core.cdn can break psst_core.player.file, while a change to psst_core.player.file can't break psst_core.cdn.
- Position
- Below the diagonal: psst_core.player.file uses a module listed above it, which is the healthy direction.
17→4 psst_core.metadata uses psst_core.item_id✕
- Connections
- 2 pairs of types, where a type in psst_core.metadata uses a type in psst_core.item_id.
- The types involved
psst_core.metadata.Fetch→psst_core.item_id.ItemIdpsst_core.metadata.ToMediaPath→psst_core.item_id.ItemId
- Direction
- psst_core.metadata uses psst_core.item_id, so a change to psst_core.item_id can break psst_core.metadata, while a change to psst_core.metadata can't break psst_core.item_id.
- Position
- Below the diagonal: psst_core.metadata uses a module listed above it, which is the healthy direction.
17→13 psst_core.metadata uses psst_core.session✕
- Connections
- 1 pair of types, where a type in psst_core.metadata uses a type in psst_core.session.
- The types involved
psst_core.metadata.Fetch→psst_core.session.SessionService
- Direction
- psst_core.metadata uses psst_core.session, so a change to psst_core.session can break psst_core.metadata, while a change to psst_core.metadata can't break psst_core.session.
- Position
- Below the diagonal: psst_core.metadata uses a module listed above it, which is the healthy direction.
17→16 psst_core.metadata uses psst_core.player.file✕
- Connections
- 1 pair of types, where a type in psst_core.metadata uses a type in psst_core.player.file.
- The types involved
psst_core.metadata.ToMediaPath→psst_core.player.file.MediaPath
- Direction
- psst_core.metadata uses psst_core.player.file, so a change to psst_core.player.file can break psst_core.metadata, while a change to psst_core.metadata can't break psst_core.player.file.
- Position
- Below the diagonal: psst_core.metadata uses a module listed above it, which is the healthy direction.
18→2 psst_core.player.item uses psst_core.audio.decode✕
- Connections
- 1 pair of types, where a type in psst_core.player.item uses a type in psst_core.audio.decode.
- The types involved
psst_core.player.item.LoadedPlaybackItem→psst_core.audio.decode.AudioDecoder
- Direction
- psst_core.player.item uses psst_core.audio.decode, so a change to psst_core.audio.decode can break psst_core.player.item, while a change to psst_core.player.item can't break psst_core.audio.decode.
- Position
- Below the diagonal: psst_core.player.item uses a module listed above it, which is the healthy direction.
18→4 psst_core.player.item uses psst_core.item_id✕
- Connections
- 2 pairs of types, where a type in psst_core.player.item uses a type in psst_core.item_id.
- The types involved
psst_core.player.item.PlaybackItem→psst_core.item_id.ItemIdpsst_core.player.item.item$module→psst_core.item_id.ItemId
- Direction
- psst_core.player.item uses psst_core.item_id, so a change to psst_core.item_id can break psst_core.player.item, while a change to psst_core.player.item can't break psst_core.item_id.
- Position
- Below the diagonal: psst_core.player.item uses a module listed above it, which is the healthy direction.
18→13 psst_core.player.item uses psst_core.session✕
- Connections
- 2 pairs of types, where a type in psst_core.player.item uses a type in psst_core.session.
- The types involved
psst_core.player.item.PlaybackItem→psst_core.session.SessionServicepsst_core.player.item.item$module→psst_core.session.SessionService
- Direction
- psst_core.player.item uses psst_core.session, so a change to psst_core.session can break psst_core.player.item, while a change to psst_core.player.item can't break psst_core.session.
- Position
- Below the diagonal: psst_core.player.item uses a module listed above it, which is the healthy direction.
18→16 psst_core.player.item uses psst_core.player.file✕
- Connections
- 2 pairs of types, where a type in psst_core.player.item uses a type in psst_core.player.file.
- The types involved
psst_core.player.item.LoadedPlaybackItem→psst_core.player.file.MediaFilepsst_core.player.item.item$module→psst_core.player.file.MediaPath
- Direction
- psst_core.player.item uses psst_core.player.file, so a change to psst_core.player.file can break psst_core.player.item, while a change to psst_core.player.item can't break psst_core.player.file.
- Position
- Below the diagonal: psst_core.player.item uses a module listed above it, which is the healthy direction.
18→21 psst_core.player.item uses psst_core.player part of a loop✕
- Connections
- 2 pairs of types, where a type in psst_core.player.item uses a type in psst_core.player.
- The types involved
psst_core.player.item.PlaybackItem→psst_core.player.PlaybackConfigpsst_core.player.item.item$module→psst_core.player.PlaybackConfig
- Direction
- psst_core.player.item uses psst_core.player, so a change to psst_core.player can break psst_core.player.item, while a change to psst_core.player.item can't break psst_core.player.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→1 psst_core.player.worker uses psst_core.actor✕
- Connections
- 2 pairs of types, where a type in psst_core.player.worker uses a type in psst_core.actor.
- The types involved
psst_core.player.worker.DecoderSource→psst_core.actor.ActorHandlepsst_core.player.worker.Worker→psst_core.actor.Actor
- Direction
- psst_core.player.worker uses psst_core.actor, so a change to psst_core.actor can break psst_core.player.worker, while a change to psst_core.player.worker can't break psst_core.actor.
- Position
- Below the diagonal: psst_core.player.worker uses a module listed above it, which is the healthy direction.
19→2 psst_core.player.worker uses psst_core.audio.decode✕
- Connections
- 2 pairs of types, where a type in psst_core.player.worker uses a type in psst_core.audio.decode.
- The types involved
psst_core.player.worker.DecoderSource→psst_core.audio.decode.AudioDecoderpsst_core.player.worker.Worker→psst_core.audio.decode.AudioDecoder
- Direction
- psst_core.player.worker uses psst_core.audio.decode, so a change to psst_core.audio.decode can break psst_core.player.worker, while a change to psst_core.player.worker can't break psst_core.audio.decode.
- Position
- Below the diagonal: psst_core.player.worker uses a module listed above it, which is the healthy direction.
19→16 psst_core.player.worker uses psst_core.player.file✕
- Connections
- 1 pair of types, where a type in psst_core.player.worker uses a type in psst_core.player.file.
- The types involved
psst_core.player.worker.DecoderSource→psst_core.player.file.MediaFile
- Direction
- psst_core.player.worker uses psst_core.player.file, so a change to psst_core.player.file can break psst_core.player.worker, while a change to psst_core.player.worker can't break psst_core.player.file.
- Position
- Below the diagonal: psst_core.player.worker uses a module listed above it, which is the healthy direction.
19→18 psst_core.player.worker uses psst_core.player.item✕
- Connections
- 1 pair of types, where a type in psst_core.player.worker uses a type in psst_core.player.item.
- The types involved
psst_core.player.worker.PlaybackManager→psst_core.player.item.LoadedPlaybackItem
- Direction
- psst_core.player.worker uses psst_core.player.item, so a change to psst_core.player.item can break psst_core.player.worker, while a change to psst_core.player.worker can't break psst_core.player.item.
- Position
- Below the diagonal: psst_core.player.worker uses a module listed above it, which is the healthy direction.
20→4 psst_gui.data.track uses psst_core.item_id✕
- Connections
- 2 pairs of types, where a type in psst_gui.data.track uses a type in psst_core.item_id.
- The types involved
psst_gui.data.track.Track→psst_core.item_id.ItemIdpsst_gui.data.track.TrackId→psst_core.item_id.ItemId
- Direction
- psst_gui.data.track uses psst_core.item_id, so a change to psst_core.item_id can break psst_gui.data.track, while a change to psst_gui.data.track can't break psst_core.item_id.
- Position
- Below the diagonal: psst_gui.data.track uses a module listed above it, which is the healthy direction.
20→16 psst_gui.data.track uses psst_core.player.file✕
- Connections
- 1 pair of types, where a type in psst_gui.data.track uses a type in psst_core.player.file.
- The types involved
psst_gui.data.track.Track→psst_core.player.file.MediaPath
- Direction
- psst_gui.data.track uses psst_core.player.file, so a change to psst_core.player.file can break psst_gui.data.track, while a change to psst_gui.data.track can't break psst_core.player.file.
- Position
- Below the diagonal: psst_gui.data.track uses a module listed above it, which is the healthy direction.
20→17 psst_gui.data.track uses psst_core.metadata✕
- Connections
- 2 pairs of types, where a type in psst_gui.data.track uses a type in psst_core.metadata.
- The types involved
psst_gui.data.track.Track→psst_core.metadata.Fetchpsst_gui.data.track.Track→psst_core.metadata.ToMediaPath
- Direction
- psst_gui.data.track uses psst_core.metadata, so a change to psst_core.metadata can break psst_gui.data.track, while a change to psst_gui.data.track can't break psst_core.metadata.
- Position
- Below the diagonal: psst_gui.data.track uses a module listed above it, which is the healthy direction.
20→30 psst_gui.data.track uses psst_gui.data.album part of a loop✕
- Connections
- 1 pair of types, where a type in psst_gui.data.track uses a type in psst_gui.data.album.
- The types involved
psst_gui.data.track.Track→psst_gui.data.album.AlbumLink
- Direction
- psst_gui.data.track uses psst_gui.data.album, so a change to psst_gui.data.album can break psst_gui.data.track, while a change to psst_gui.data.track can't break psst_gui.data.album.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→13 psst_core.player uses psst_core.session✕
- Connections
- 1 pair of types, where a type in psst_core.player uses a type in psst_core.session.
- The types involved
psst_core.player.Player→psst_core.session.SessionService
- Direction
- psst_core.player uses psst_core.session, so a change to psst_core.session can break psst_core.player, while a change to psst_core.player can't break psst_core.session.
- Position
- Below the diagonal: psst_core.player uses a module listed above it, which is the healthy direction.
21→16 psst_core.player uses psst_core.player.file✕
- Connections
- 1 pair of types, where a type in psst_core.player uses a type in psst_core.player.file.
- The types involved
psst_core.player.Player→psst_core.player.file.MediaPath
- Direction
- psst_core.player uses psst_core.player.file, so a change to psst_core.player.file can break psst_core.player, while a change to psst_core.player can't break psst_core.player.file.
- Position
- Below the diagonal: psst_core.player uses a module listed above it, which is the healthy direction.
21→18 psst_core.player uses psst_core.player.item✕
- Connections
- 2 pairs of types, where a type in psst_core.player uses a type in psst_core.player.item.
- The types involved
psst_core.player.Player→psst_core.player.item.LoadedPlaybackItempsst_core.player.Player→psst_core.player.item.PlaybackItem
- Direction
- psst_core.player uses psst_core.player.item, so a change to psst_core.player.item can break psst_core.player, while a change to psst_core.player can't break psst_core.player.item.
- Position
- Below the diagonal: psst_core.player uses a module listed above it, which is the healthy direction.
21→19 psst_core.player uses psst_core.player.worker✕
- Connections
- 1 pair of types, where a type in psst_core.player uses a type in psst_core.player.worker.
- The types involved
psst_core.player.Player→psst_core.player.worker.PlaybackManager
- Direction
- psst_core.player uses psst_core.player.worker, so a change to psst_core.player.worker can break psst_core.player, while a change to psst_core.player can't break psst_core.player.worker.
- Position
- Below the diagonal: psst_core.player uses a module listed above it, which is the healthy direction.
22→3 psst_core.session.mercury uses psst_core.connection.shannon_codec✕
- Connections
- 1 pair of types, where a type in psst_core.session.mercury uses a type in psst_core.connection.shannon_codec.
- The types involved
psst_core.session.mercury.MercuryDispatcher→psst_core.connection.shannon_codec.ShannonMsg
- Direction
- psst_core.session.mercury uses psst_core.connection.shannon_codec, so a change to psst_core.connection.shannon_codec can break psst_core.session.mercury, while a change to psst_core.session.mercury can't break psst_core.connection.shannon_codec.
- Position
- Below the diagonal: psst_core.session.mercury uses a module listed above it, which is the healthy direction.
22→19 psst_core.session.mercury uses psst_core.player.worker✕
- Connections
- 1 pair of types, where a type in psst_core.session.mercury uses a type in psst_core.player.worker.
- The types involved
psst_core.session.mercury.Pending→psst_core.player.worker.Msg
- Direction
- psst_core.session.mercury uses psst_core.player.worker, so a change to psst_core.player.worker can break psst_core.session.mercury, while a change to psst_core.session.mercury can't break psst_core.player.worker.
- Position
- Below the diagonal: psst_core.session.mercury uses a module listed above it, which is the healthy direction.
23→4 psst_gui.data.playback uses psst_core.item_id✕
- Connections
- 1 pair of types, where a type in psst_gui.data.playback uses a type in psst_core.item_id.
- The types involved
psst_gui.data.playback.Playable→psst_core.item_id.ItemId
- Direction
- psst_gui.data.playback uses psst_core.item_id, so a change to psst_core.item_id can break psst_gui.data.playback, while a change to psst_gui.data.playback can't break psst_core.item_id.
- Position
- Below the diagonal: psst_gui.data.playback uses a module listed above it, which is the healthy direction.
23→6 psst_gui.data.playback uses psst_gui.data.nav✕
- Connections
- 1 pair of types, where a type in psst_gui.data.playback uses a type in psst_gui.data.nav.
- The types involved
psst_gui.data.playback.PlaybackOrigin→psst_gui.data.nav.Nav
- Direction
- psst_gui.data.playback uses psst_gui.data.nav, so a change to psst_gui.data.nav can break psst_gui.data.playback, while a change to psst_gui.data.playback can't break psst_gui.data.nav.
- Position
- Below the diagonal: psst_gui.data.playback uses a module listed above it, which is the healthy direction.
23→20 psst_gui.data.playback uses psst_gui.data.track✕
- Connections
- 1 pair of types, where a type in psst_gui.data.playback uses a type in psst_gui.data.track.
- The types involved
psst_gui.data.playback.Playable→psst_gui.data.track.Track
- Direction
- psst_gui.data.playback uses psst_gui.data.track, so a change to psst_gui.data.track can break psst_gui.data.playback, while a change to psst_gui.data.playback can't break psst_gui.data.track.
- Position
- Below the diagonal: psst_gui.data.playback uses a module listed above it, which is the healthy direction.
23→25 psst_gui.data.playback uses psst_gui.ui.playable part of a loop✕
- Connections
- 1 pair of types, where a type in psst_gui.data.playback uses a type in psst_gui.ui.playable.
- The types involved
psst_gui.data.playback.PlaybackOrigin→psst_gui.ui.playable.Display
- Direction
- psst_gui.data.playback uses psst_gui.ui.playable, so a change to psst_gui.ui.playable can break psst_gui.data.playback, while a change to psst_gui.data.playback can't break psst_gui.ui.playable.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→35 psst_gui.data.playback uses psst_gui.data part of a loop✕
- Connections
- 1 pair of types, where a type in psst_gui.data.playback uses a type in psst_gui.data.
- The types involved
psst_gui.data.playback.NowPlaying→psst_gui.data.Library
- Direction
- psst_gui.data.playback uses psst_gui.data, so a change to psst_gui.data can break psst_gui.data.playback, while a change to psst_gui.data.playback can't break psst_gui.data.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→6 psst_gui.data.config uses psst_gui.data.nav✕
- Connections
- 1 pair of types, where a type in psst_gui.data.config uses a type in psst_gui.data.nav.
- The types involved
psst_gui.data.config.Config→psst_gui.data.nav.Nav
- Direction
- psst_gui.data.config uses psst_gui.data.nav, so a change to psst_gui.data.nav can break psst_gui.data.config, while a change to psst_gui.data.config can't break psst_gui.data.nav.
- Position
- Below the diagonal: psst_gui.data.config uses a module listed above it, which is the healthy direction.
24→7 psst_gui.data.config uses psst_gui.data.promise✕
- Connections
- 2 pairs of types, where a type in psst_gui.data.config uses a type in psst_gui.data.promise.
- The types involved
psst_gui.data.config.Authentication→psst_gui.data.promise.Promisepsst_gui.data.config.Preferences→psst_gui.data.promise.Promise
- Direction
- psst_gui.data.config uses psst_gui.data.promise, so a change to psst_gui.data.promise can break psst_gui.data.config, while a change to psst_gui.data.config can't break psst_gui.data.promise.
- Position
- Below the diagonal: psst_gui.data.config uses a module listed above it, which is the healthy direction.
24→10 psst_gui.data.config uses psst_core.connection✕
- Connections
- 1 pair of types, where a type in psst_gui.data.config uses a type in psst_core.connection.
- The types involved
psst_gui.data.config.Config→psst_core.connection.Credentials
- Direction
- psst_gui.data.config uses psst_core.connection, so a change to psst_core.connection can break psst_gui.data.config, while a change to psst_gui.data.config can't break psst_core.connection.
- Position
- Below the diagonal: psst_gui.data.config uses a module listed above it, which is the healthy direction.
24→13 psst_gui.data.config uses psst_core.session✕
- Connections
- 2 pairs of types, where a type in psst_gui.data.config uses a type in psst_core.session.
- The types involved
psst_gui.data.config.Authentication→psst_core.session.SessionConfigpsst_gui.data.config.Config→psst_core.session.SessionConfig
- Direction
- psst_gui.data.config uses psst_core.session, so a change to psst_core.session can break psst_gui.data.config, while a change to psst_gui.data.config can't break psst_core.session.
- Position
- Below the diagonal: psst_gui.data.config uses a module listed above it, which is the healthy direction.
24→21 psst_gui.data.config uses psst_core.player✕
- Connections
- 1 pair of types, where a type in psst_gui.data.config uses a type in psst_core.player.
- The types involved
psst_gui.data.config.Config→psst_core.player.PlaybackConfig
- Direction
- psst_gui.data.config uses psst_core.player, so a change to psst_core.player can break psst_gui.data.config, while a change to psst_gui.data.config can't break psst_core.player.
- Position
- Below the diagonal: psst_gui.data.config uses a module listed above it, which is the healthy direction.
24→23 psst_gui.data.config uses psst_gui.data.playback✕
- Connections
- 1 pair of types, where a type in psst_gui.data.config uses a type in psst_gui.data.playback.
- The types involved
psst_gui.data.config.Config→psst_gui.data.playback.QueueBehavior
- Direction
- psst_gui.data.config uses psst_gui.data.playback, so a change to psst_gui.data.playback can break psst_gui.data.config, while a change to psst_gui.data.config can't break psst_gui.data.playback.
- Position
- Below the diagonal: psst_gui.data.config uses a module listed above it, which is the healthy direction.
25→5 psst_gui.ui.playable uses psst_gui.data.find✕
- Connections
- 2 pairs of types, where a type in psst_gui.ui.playable uses a type in psst_gui.data.find.
- The types involved
psst_gui.ui.playable.PlayRow→psst_gui.data.find.FindQuerypsst_gui.ui.playable.PlayRow→psst_gui.data.find.MatchFindQuery
- Direction
- psst_gui.ui.playable uses psst_gui.data.find, so a change to psst_gui.data.find can break psst_gui.ui.playable, while a change to psst_gui.ui.playable can't break psst_gui.data.find.
- Position
- Below the diagonal: psst_gui.ui.playable uses a module listed above it, which is the healthy direction.
25→23 psst_gui.ui.playable uses psst_gui.data.playback✕
- Connections
- 2 pairs of types, where a type in psst_gui.ui.playable uses a type in psst_gui.data.playback.
- The types involved
psst_gui.ui.playable.PlayRow→psst_gui.data.playback.PlaybackOriginpsst_gui.ui.playable.PlayableIter→psst_gui.data.playback.PlaybackOrigin
- Direction
- psst_gui.ui.playable uses psst_gui.data.playback, so a change to psst_gui.data.playback can break psst_gui.ui.playable, while a change to psst_gui.ui.playable can't break psst_gui.data.playback.
- Position
- Below the diagonal: psst_gui.ui.playable uses a module listed above it, which is the healthy direction.
25→35 psst_gui.ui.playable uses psst_gui.data part of a loop✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.playable uses a type in psst_gui.data.
- The types involved
psst_gui.ui.playable.PlayRow→psst_gui.data.CommonCtx
- Direction
- psst_gui.ui.playable uses psst_gui.data, so a change to psst_gui.data can break psst_gui.ui.playable, while a change to psst_gui.ui.playable can't break psst_gui.data.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→8 psst_gui.ui.playback uses psst_gui.widget.icons✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.playback uses a type in psst_gui.widget.icons.
- The types involved
psst_gui.ui.playback.playback$module→psst_gui.widget.icons.SvgIcon
- Direction
- psst_gui.ui.playback uses psst_gui.widget.icons, so a change to psst_gui.widget.icons can break psst_gui.ui.playback, while a change to psst_gui.ui.playback can't break psst_gui.widget.icons.
- Position
- Below the diagonal: psst_gui.ui.playback uses a module listed above it, which is the healthy direction.
26→20 psst_gui.ui.playback uses psst_gui.data.track✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.playback uses a type in psst_gui.data.track.
- The types involved
psst_gui.ui.playback.playback$module→psst_gui.data.track.AudioAnalysis
- Direction
- psst_gui.ui.playback uses psst_gui.data.track, so a change to psst_gui.data.track can break psst_gui.ui.playback, while a change to psst_gui.ui.playback can't break psst_gui.data.track.
- Position
- Below the diagonal: psst_gui.ui.playback uses a module listed above it, which is the healthy direction.
26→23 psst_gui.ui.playback uses psst_gui.data.playback✕
- Connections
- 4 pairs of types, where a type in psst_gui.ui.playback uses a type in psst_gui.data.playback.
- The types involved
psst_gui.ui.playback.SeekBar→psst_gui.data.playback.NowPlayingpsst_gui.ui.playback.playback$module→psst_gui.data.playback.NowPlayingpsst_gui.ui.playback.playback$module→psst_gui.data.playback.PlaybackOriginpsst_gui.ui.playback.playback$module→psst_gui.data.playback.QueueBehavior
- Direction
- psst_gui.ui.playback uses psst_gui.data.playback, so a change to psst_gui.data.playback can break psst_gui.ui.playback, while a change to psst_gui.ui.playback can't break psst_gui.data.playback.
- Position
- Below the diagonal: psst_gui.ui.playback uses a module listed above it, which is the healthy direction.
27→7 psst_gui.data.recommend uses psst_gui.data.promise✕
- Connections
- 1 pair of types, where a type in psst_gui.data.recommend uses a type in psst_gui.data.promise.
- The types involved
psst_gui.data.recommend.Recommend→psst_gui.data.promise.Promise
- Direction
- psst_gui.data.recommend uses psst_gui.data.promise, so a change to psst_gui.data.promise can break psst_gui.data.recommend, while a change to psst_gui.data.recommend can't break psst_gui.data.promise.
- Position
- Below the diagonal: psst_gui.data.recommend uses a module listed above it, which is the healthy direction.
27→20 psst_gui.data.recommend uses psst_gui.data.track✕
- Connections
- 1 pair of types, where a type in psst_gui.data.recommend uses a type in psst_gui.data.track.
- The types involved
psst_gui.data.recommend.RecommendationsRequest→psst_gui.data.track.TrackId
- Direction
- psst_gui.data.recommend uses psst_gui.data.track, so a change to psst_gui.data.track can break psst_gui.data.recommend, while a change to psst_gui.data.recommend can't break psst_gui.data.track.
- Position
- Below the diagonal: psst_gui.data.recommend uses a module listed above it, which is the healthy direction.
27→23 psst_gui.data.recommend uses psst_gui.data.playback✕
- Connections
- 1 pair of types, where a type in psst_gui.data.recommend uses a type in psst_gui.data.playback.
- The types involved
psst_gui.data.recommend.Recommendations→psst_gui.data.playback.PlaybackOrigin
- Direction
- psst_gui.data.recommend uses psst_gui.data.playback, so a change to psst_gui.data.playback can break psst_gui.data.recommend, while a change to psst_gui.data.recommend can't break psst_gui.data.playback.
- Position
- Below the diagonal: psst_gui.data.recommend uses a module listed above it, which is the healthy direction.
27→25 psst_gui.data.recommend uses psst_gui.ui.playable✕
- Connections
- 1 pair of types, where a type in psst_gui.data.recommend uses a type in psst_gui.ui.playable.
- The types involved
psst_gui.data.recommend.Recommendations→psst_gui.ui.playable.PlayableIter
- Direction
- psst_gui.data.recommend uses psst_gui.ui.playable, so a change to psst_gui.ui.playable can break psst_gui.data.recommend, while a change to psst_gui.data.recommend can't break psst_gui.ui.playable.
- Position
- Below the diagonal: psst_gui.data.recommend uses a module listed above it, which is the healthy direction.
28→7 psst_gui.data.search uses psst_gui.data.promise✕
- Connections
- 1 pair of types, where a type in psst_gui.data.search uses a type in psst_gui.data.promise.
- The types involved
psst_gui.data.search.Search→psst_gui.data.promise.Promise
- Direction
- psst_gui.data.search uses psst_gui.data.promise, so a change to psst_gui.data.promise can break psst_gui.data.search, while a change to psst_gui.data.search can't break psst_gui.data.promise.
- Position
- Below the diagonal: psst_gui.data.search uses a module listed above it, which is the healthy direction.
28→23 psst_gui.data.search uses psst_gui.data.playback✕
- Connections
- 1 pair of types, where a type in psst_gui.data.search uses a type in psst_gui.data.playback.
- The types involved
psst_gui.data.search.SearchResults→psst_gui.data.playback.PlaybackOrigin
- Direction
- psst_gui.data.search uses psst_gui.data.playback, so a change to psst_gui.data.playback can break psst_gui.data.search, while a change to psst_gui.data.search can't break psst_gui.data.playback.
- Position
- Below the diagonal: psst_gui.data.search uses a module listed above it, which is the healthy direction.
28→25 psst_gui.data.search uses psst_gui.ui.playable✕
- Connections
- 1 pair of types, where a type in psst_gui.data.search uses a type in psst_gui.ui.playable.
- The types involved
psst_gui.data.search.SearchResults→psst_gui.ui.playable.PlayableIter
- Direction
- psst_gui.data.search uses psst_gui.ui.playable, so a change to psst_gui.ui.playable can break psst_gui.data.search, while a change to psst_gui.data.search can't break psst_gui.ui.playable.
- Position
- Below the diagonal: psst_gui.data.search uses a module listed above it, which is the healthy direction.
29→25 psst_gui.data.utils uses psst_gui.ui.playable✕
- Connections
- 1 pair of types, where a type in psst_gui.data.utils uses a type in psst_gui.ui.playable.
- The types involved
psst_gui.data.utils.Float64→psst_gui.ui.playable.Display
- Direction
- psst_gui.data.utils uses psst_gui.ui.playable, so a change to psst_gui.ui.playable can break psst_gui.data.utils, while a change to psst_gui.data.utils can't break psst_gui.ui.playable.
- Position
- Below the diagonal: psst_gui.data.utils uses a module listed above it, which is the healthy direction.
30→7 psst_gui.data.album uses psst_gui.data.promise✕
- Connections
- 1 pair of types, where a type in psst_gui.data.album uses a type in psst_gui.data.promise.
- The types involved
psst_gui.data.album.AlbumDetail→psst_gui.data.promise.Promise
- Direction
- psst_gui.data.album uses psst_gui.data.promise, so a change to psst_gui.data.promise can break psst_gui.data.album, while a change to psst_gui.data.album can't break psst_gui.data.promise.
- Position
- Below the diagonal: psst_gui.data.album uses a module listed above it, which is the healthy direction.
30→29 psst_gui.data.album uses psst_gui.data.utils✕
- Connections
- 2 pairs of types, where a type in psst_gui.data.album uses a type in psst_gui.data.utils.
- The types involved
psst_gui.data.album.Album→psst_gui.data.utils.Imagepsst_gui.data.album.AlbumLink→psst_gui.data.utils.Image
- Direction
- psst_gui.data.album uses psst_gui.data.utils, so a change to psst_gui.data.utils can break psst_gui.data.album, while a change to psst_gui.data.album can't break psst_gui.data.utils.
- Position
- Below the diagonal: psst_gui.data.album uses a module listed above it, which is the healthy direction.
31→7 psst_gui.data.artist uses psst_gui.data.promise✕
- Connections
- 1 pair of types, where a type in psst_gui.data.artist uses a type in psst_gui.data.promise.
- The types involved
psst_gui.data.artist.ArtistDetail→psst_gui.data.promise.Promise
- Direction
- psst_gui.data.artist uses psst_gui.data.promise, so a change to psst_gui.data.promise can break psst_gui.data.artist, while a change to psst_gui.data.artist can't break psst_gui.data.promise.
- Position
- Below the diagonal: psst_gui.data.artist uses a module listed above it, which is the healthy direction.
31→29 psst_gui.data.artist uses psst_gui.data.utils✕
- Connections
- 1 pair of types, where a type in psst_gui.data.artist uses a type in psst_gui.data.utils.
- The types involved
psst_gui.data.artist.Artist→psst_gui.data.utils.Image
- Direction
- psst_gui.data.artist uses psst_gui.data.utils, so a change to psst_gui.data.utils can break psst_gui.data.artist, while a change to psst_gui.data.artist can't break psst_gui.data.utils.
- Position
- Below the diagonal: psst_gui.data.artist uses a module listed above it, which is the healthy direction.
32→7 psst_gui.data.playlist uses psst_gui.data.promise✕
- Connections
- 1 pair of types, where a type in psst_gui.data.playlist uses a type in psst_gui.data.promise.
- The types involved
psst_gui.data.playlist.PlaylistDetail→psst_gui.data.promise.Promise
- Direction
- psst_gui.data.playlist uses psst_gui.data.promise, so a change to psst_gui.data.promise can break psst_gui.data.playlist, while a change to psst_gui.data.playlist can't break psst_gui.data.promise.
- Position
- Below the diagonal: psst_gui.data.playlist uses a module listed above it, which is the healthy direction.
32→20 psst_gui.data.playlist uses psst_gui.data.track✕
- Connections
- 1 pair of types, where a type in psst_gui.data.playlist uses a type in psst_gui.data.track.
- The types involved
psst_gui.data.playlist.PlaylistAddTrack→psst_gui.data.track.TrackId
- Direction
- psst_gui.data.playlist uses psst_gui.data.track, so a change to psst_gui.data.track can break psst_gui.data.playlist, while a change to psst_gui.data.playlist can't break psst_gui.data.track.
- Position
- Below the diagonal: psst_gui.data.playlist uses a module listed above it, which is the healthy direction.
32→23 psst_gui.data.playlist uses psst_gui.data.playback✕
- Connections
- 1 pair of types, where a type in psst_gui.data.playlist uses a type in psst_gui.data.playback.
- The types involved
psst_gui.data.playlist.PlaylistTracks→psst_gui.data.playback.PlaybackOrigin
- Direction
- psst_gui.data.playlist uses psst_gui.data.playback, so a change to psst_gui.data.playback can break psst_gui.data.playlist, while a change to psst_gui.data.playlist can't break psst_gui.data.playback.
- Position
- Below the diagonal: psst_gui.data.playlist uses a module listed above it, which is the healthy direction.
32→25 psst_gui.data.playlist uses psst_gui.ui.playable✕
- Connections
- 1 pair of types, where a type in psst_gui.data.playlist uses a type in psst_gui.ui.playable.
- The types involved
psst_gui.data.playlist.PlaylistTracks→psst_gui.ui.playable.PlayableIter
- Direction
- psst_gui.data.playlist uses psst_gui.ui.playable, so a change to psst_gui.ui.playable can break psst_gui.data.playlist, while a change to psst_gui.data.playlist can't break psst_gui.ui.playable.
- Position
- Below the diagonal: psst_gui.data.playlist uses a module listed above it, which is the healthy direction.
32→29 psst_gui.data.playlist uses psst_gui.data.utils✕
- Connections
- 1 pair of types, where a type in psst_gui.data.playlist uses a type in psst_gui.data.utils.
- The types involved
psst_gui.data.playlist.Playlist→psst_gui.data.utils.Image
- Direction
- psst_gui.data.playlist uses psst_gui.data.utils, so a change to psst_gui.data.utils can break psst_gui.data.playlist, while a change to psst_gui.data.playlist can't break psst_gui.data.utils.
- Position
- Below the diagonal: psst_gui.data.playlist uses a module listed above it, which is the healthy direction.
33→4 psst_gui.data.show uses psst_core.item_id✕
- Connections
- 2 pairs of types, where a type in psst_gui.data.show uses a type in psst_core.item_id.
- The types involved
psst_gui.data.show.Episode→psst_core.item_id.ItemIdpsst_gui.data.show.EpisodeId→psst_core.item_id.ItemId
- Direction
- psst_gui.data.show uses psst_core.item_id, so a change to psst_core.item_id can break psst_gui.data.show, while a change to psst_gui.data.show can't break psst_core.item_id.
- Position
- Below the diagonal: psst_gui.data.show uses a module listed above it, which is the healthy direction.
33→7 psst_gui.data.show uses psst_gui.data.promise✕
- Connections
- 1 pair of types, where a type in psst_gui.data.show uses a type in psst_gui.data.promise.
- The types involved
psst_gui.data.show.ShowDetail→psst_gui.data.promise.Promise
- Direction
- psst_gui.data.show uses psst_gui.data.promise, so a change to psst_gui.data.promise can break psst_gui.data.show, while a change to psst_gui.data.show can't break psst_gui.data.promise.
- Position
- Below the diagonal: psst_gui.data.show uses a module listed above it, which is the healthy direction.
33→16 psst_gui.data.show uses psst_core.player.file✕
- Connections
- 1 pair of types, where a type in psst_gui.data.show uses a type in psst_core.player.file.
- The types involved
psst_gui.data.show.Episode→psst_core.player.file.MediaPath
- Direction
- psst_gui.data.show uses psst_core.player.file, so a change to psst_core.player.file can break psst_gui.data.show, while a change to psst_gui.data.show can't break psst_core.player.file.
- Position
- Below the diagonal: psst_gui.data.show uses a module listed above it, which is the healthy direction.
33→17 psst_gui.data.show uses psst_core.metadata✕
- Connections
- 2 pairs of types, where a type in psst_gui.data.show uses a type in psst_core.metadata.
- The types involved
psst_gui.data.show.Episode→psst_core.metadata.Fetchpsst_gui.data.show.Episode→psst_core.metadata.ToMediaPath
- Direction
- psst_gui.data.show uses psst_core.metadata, so a change to psst_core.metadata can break psst_gui.data.show, while a change to psst_gui.data.show can't break psst_core.metadata.
- Position
- Below the diagonal: psst_gui.data.show uses a module listed above it, which is the healthy direction.
33→23 psst_gui.data.show uses psst_gui.data.playback✕
- Connections
- 1 pair of types, where a type in psst_gui.data.show uses a type in psst_gui.data.playback.
- The types involved
psst_gui.data.show.ShowEpisodes→psst_gui.data.playback.PlaybackOrigin
- Direction
- psst_gui.data.show uses psst_gui.data.playback, so a change to psst_gui.data.playback can break psst_gui.data.show, while a change to psst_gui.data.show can't break psst_gui.data.playback.
- Position
- Below the diagonal: psst_gui.data.show uses a module listed above it, which is the healthy direction.
33→25 psst_gui.data.show uses psst_gui.ui.playable✕
- Connections
- 1 pair of types, where a type in psst_gui.data.show uses a type in psst_gui.ui.playable.
- The types involved
psst_gui.data.show.ShowEpisodes→psst_gui.ui.playable.PlayableIter
- Direction
- psst_gui.data.show uses psst_gui.ui.playable, so a change to psst_gui.ui.playable can break psst_gui.data.show, while a change to psst_gui.data.show can't break psst_gui.ui.playable.
- Position
- Below the diagonal: psst_gui.data.show uses a module listed above it, which is the healthy direction.
33→29 psst_gui.data.show uses psst_gui.data.utils✕
- Connections
- 2 pairs of types, where a type in psst_gui.data.show uses a type in psst_gui.data.utils.
- The types involved
psst_gui.data.show.Episode→psst_gui.data.utils.Imagepsst_gui.data.show.Show→psst_gui.data.utils.Image
- Direction
- psst_gui.data.show uses psst_gui.data.utils, so a change to psst_gui.data.utils can break psst_gui.data.show, while a change to psst_gui.data.show can't break psst_gui.data.utils.
- Position
- Below the diagonal: psst_gui.data.show uses a module listed above it, which is the healthy direction.
33→30 psst_gui.data.show uses psst_gui.data.album✕
- Connections
- 1 pair of types, where a type in psst_gui.data.show uses a type in psst_gui.data.album.
- The types involved
psst_gui.data.show.Episode→psst_gui.data.album.DatePrecision
- Direction
- psst_gui.data.show uses psst_gui.data.album, so a change to psst_gui.data.album can break psst_gui.data.show, while a change to psst_gui.data.show can't break psst_gui.data.album.
- Position
- Below the diagonal: psst_gui.data.show uses a module listed above it, which is the healthy direction.
34→6 psst_gui.webapi.client uses psst_gui.data.nav✕
- Connections
- 1 pair of types, where a type in psst_gui.webapi.client uses a type in psst_gui.data.nav.
- The types involved
psst_gui.webapi.client.WebApi→psst_gui.data.nav.SpotifyUrl
- Direction
- psst_gui.webapi.client uses psst_gui.data.nav, so a change to psst_gui.data.nav can break psst_gui.webapi.client, while a change to psst_gui.webapi.client can't break psst_gui.data.nav.
- Position
- Below the diagonal: psst_gui.webapi.client uses a module listed above it, which is the healthy direction.
34→13 psst_gui.webapi.client uses psst_core.session✕
- Connections
- 1 pair of types, where a type in psst_gui.webapi.client uses a type in psst_core.session.
- The types involved
psst_gui.webapi.client.WebApi→psst_core.session.SessionService
- Direction
- psst_gui.webapi.client uses psst_core.session, so a change to psst_core.session can break psst_gui.webapi.client, while a change to psst_gui.webapi.client can't break psst_core.session.
- Position
- Below the diagonal: psst_gui.webapi.client uses a module listed above it, which is the healthy direction.
34→14 psst_gui.webapi.client uses psst_core.session.login5✕
- Connections
- 1 pair of types, where a type in psst_gui.webapi.client uses a type in psst_core.session.login5.
- The types involved
psst_gui.webapi.client.WebApi→psst_core.session.login5.Login5
- Direction
- psst_gui.webapi.client uses psst_core.session.login5, so a change to psst_core.session.login5 can break psst_gui.webapi.client, while a change to psst_gui.webapi.client can't break psst_core.session.login5.
- Position
- Below the diagonal: psst_gui.webapi.client uses a module listed above it, which is the healthy direction.
34→27 psst_gui.webapi.client uses psst_gui.data.recommend✕
- Connections
- 1 pair of types, where a type in psst_gui.webapi.client uses a type in psst_gui.data.recommend.
- The types involved
psst_gui.webapi.client.WebApi→psst_gui.data.recommend.RecommendationsRequest
- Direction
- psst_gui.webapi.client uses psst_gui.data.recommend, so a change to psst_gui.data.recommend can break psst_gui.webapi.client, while a change to psst_gui.webapi.client can't break psst_gui.data.recommend.
- Position
- Below the diagonal: psst_gui.webapi.client uses a module listed above it, which is the healthy direction.
34→30 psst_gui.webapi.client uses psst_gui.data.album✕
- Connections
- 3 pairs of types, where a type in psst_gui.webapi.client uses a type in psst_gui.data.album.
- The types involved
psst_gui.webapi.client.Release→psst_gui.data.album.Albumpsst_gui.webapi.client.Release→psst_gui.data.album.AlbumTypepsst_gui.webapi.client.WebApi→psst_gui.data.album.AlbumType
- Direction
- psst_gui.webapi.client uses psst_gui.data.album, so a change to psst_gui.data.album can break psst_gui.webapi.client, while a change to psst_gui.webapi.client can't break psst_gui.data.album.
- Position
- Below the diagonal: psst_gui.webapi.client uses a module listed above it, which is the healthy direction.
35→4 psst_gui.data uses psst_core.item_id✕
- Connections
- 1 pair of types, where a type in psst_gui.data uses a type in psst_core.item_id.
- The types involved
psst_gui.data.AppState→psst_core.item_id.ItemId
- Direction
- psst_gui.data uses psst_core.item_id, so a change to psst_core.item_id can break psst_gui.data, while a change to psst_gui.data can't break psst_core.item_id.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→5 psst_gui.data uses psst_gui.data.find✕
- Connections
- 1 pair of types, where a type in psst_gui.data uses a type in psst_gui.data.find.
- The types involved
psst_gui.data.AppState→psst_gui.data.find.Finder
- Direction
- psst_gui.data uses psst_gui.data.find, so a change to psst_gui.data.find can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.find.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→6 psst_gui.data uses psst_gui.data.nav✕
- Connections
- 2 pairs of types, where a type in psst_gui.data uses a type in psst_gui.data.nav.
- The types involved
psst_gui.data.AppState→psst_gui.data.nav.Navpsst_gui.data.CommonCtx→psst_gui.data.nav.Nav
- Direction
- psst_gui.data uses psst_gui.data.nav, so a change to psst_gui.data.nav can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.nav.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→7 psst_gui.data uses psst_gui.data.promise✕
- Connections
- 3 pairs of types, where a type in psst_gui.data uses a type in psst_gui.data.promise.
- The types involved
psst_gui.data.AppState→psst_gui.data.promise.Promisepsst_gui.data.HomeDetail→psst_gui.data.promise.Promisepsst_gui.data.Library→psst_gui.data.promise.Promise
- Direction
- psst_gui.data uses psst_gui.data.promise, so a change to psst_gui.data.promise can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.promise.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→13 psst_gui.data uses psst_core.session✕
- Connections
- 1 pair of types, where a type in psst_gui.data uses a type in psst_core.session.
- The types involved
psst_gui.data.AppState→psst_core.session.SessionService
- Direction
- psst_gui.data uses psst_core.session, so a change to psst_core.session can break psst_gui.data, while a change to psst_gui.data can't break psst_core.session.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→20 psst_gui.data uses psst_gui.data.track✕
- Connections
- 2 pairs of types, where a type in psst_gui.data uses a type in psst_gui.data.track.
- The types involved
psst_gui.data.Library→psst_gui.data.track.Trackpsst_gui.data.Library→psst_gui.data.track.TrackId
- Direction
- psst_gui.data uses psst_gui.data.track, so a change to psst_gui.data.track can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.track.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→23 psst_gui.data uses psst_gui.data.playback✕
- Connections
- 7 pairs of types, where a type in psst_gui.data uses a type in psst_gui.data.playback.
- The types involved
psst_gui.data.AppState→psst_gui.data.playback.Playablepsst_gui.data.AppState→psst_gui.data.playback.Playbackpsst_gui.data.AppState→psst_gui.data.playback.PlaybackOriginpsst_gui.data.AppState→psst_gui.data.playback.QueueBehaviorpsst_gui.data.AppState→psst_gui.data.playback.QueueEntrypsst_gui.data.CommonCtx→psst_gui.data.playback.Playablepsst_gui.data.SavedTracks→psst_gui.data.playback.PlaybackOrigin
- Direction
- psst_gui.data uses psst_gui.data.playback, so a change to psst_gui.data.playback can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.playback.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→24 psst_gui.data uses psst_gui.data.config✕
- Connections
- 2 pairs of types, where a type in psst_gui.data uses a type in psst_gui.data.config.
- The types involved
psst_gui.data.AppState→psst_gui.data.config.Configpsst_gui.data.AppState→psst_gui.data.config.Preferences
- Direction
- psst_gui.data uses psst_gui.data.config, so a change to psst_gui.data.config can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.config.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→25 psst_gui.data uses psst_gui.ui.playable✕
- Connections
- 1 pair of types, where a type in psst_gui.data uses a type in psst_gui.ui.playable.
- The types involved
psst_gui.data.SavedTracks→psst_gui.ui.playable.PlayableIter
- Direction
- psst_gui.data uses psst_gui.ui.playable, so a change to psst_gui.ui.playable can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.ui.playable.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→27 psst_gui.data uses psst_gui.data.recommend✕
- Connections
- 1 pair of types, where a type in psst_gui.data uses a type in psst_gui.data.recommend.
- The types involved
psst_gui.data.AppState→psst_gui.data.recommend.Recommend
- Direction
- psst_gui.data uses psst_gui.data.recommend, so a change to psst_gui.data.recommend can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.recommend.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→28 psst_gui.data uses psst_gui.data.search✕
- Connections
- 1 pair of types, where a type in psst_gui.data uses a type in psst_gui.data.search.
- The types involved
psst_gui.data.AppState→psst_gui.data.search.Search
- Direction
- psst_gui.data uses psst_gui.data.search, so a change to psst_gui.data.search can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.search.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→30 psst_gui.data uses psst_gui.data.album✕
- Connections
- 2 pairs of types, where a type in psst_gui.data uses a type in psst_gui.data.album.
- The types involved
psst_gui.data.AppState→psst_gui.data.album.AlbumDetailpsst_gui.data.Library→psst_gui.data.album.Album
- Direction
- psst_gui.data uses psst_gui.data.album, so a change to psst_gui.data.album can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.album.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→31 psst_gui.data uses psst_gui.data.artist✕
- Connections
- 1 pair of types, where a type in psst_gui.data uses a type in psst_gui.data.artist.
- The types involved
psst_gui.data.AppState→psst_gui.data.artist.ArtistDetail
- Direction
- psst_gui.data uses psst_gui.data.artist, so a change to psst_gui.data.artist can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.artist.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→32 psst_gui.data uses psst_gui.data.playlist✕
- Connections
- 3 pairs of types, where a type in psst_gui.data uses a type in psst_gui.data.playlist.
- The types involved
psst_gui.data.AppState→psst_gui.data.playlist.PlaylistDetailpsst_gui.data.Library→psst_gui.data.playlist.Playlistpsst_gui.data.Library→psst_gui.data.playlist.PlaylistLink
- Direction
- psst_gui.data uses psst_gui.data.playlist, so a change to psst_gui.data.playlist can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.playlist.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
35→33 psst_gui.data uses psst_gui.data.show✕
- Connections
- 2 pairs of types, where a type in psst_gui.data uses a type in psst_gui.data.show.
- The types involved
psst_gui.data.AppState→psst_gui.data.show.ShowDetailpsst_gui.data.Library→psst_gui.data.show.Show
- Direction
- psst_gui.data uses psst_gui.data.show, so a change to psst_gui.data.show can break psst_gui.data, while a change to psst_gui.data can't break psst_gui.data.show.
- Position
- Below the diagonal: psst_gui.data uses a module listed above it, which is the healthy direction.
36→13 psst_gui.controller.playback uses psst_core.session✕
- Connections
- 1 pair of types, where a type in psst_gui.controller.playback uses a type in psst_core.session.
- The types involved
psst_gui.controller.playback.PlaybackController→psst_core.session.SessionService
- Direction
- psst_gui.controller.playback uses psst_core.session, so a change to psst_core.session can break psst_gui.controller.playback, while a change to psst_gui.controller.playback can't break psst_core.session.
- Position
- Below the diagonal: psst_gui.controller.playback uses a module listed above it, which is the healthy direction.
36→18 psst_gui.controller.playback uses psst_core.player.item✕
- Connections
- 1 pair of types, where a type in psst_gui.controller.playback uses a type in psst_core.player.item.
- The types involved
psst_gui.controller.playback.PlaybackController→psst_core.player.item.PlaybackItem
- Direction
- psst_gui.controller.playback uses psst_core.player.item, so a change to psst_core.player.item can break psst_gui.controller.playback, while a change to psst_gui.controller.playback can't break psst_core.player.item.
- Position
- Below the diagonal: psst_gui.controller.playback uses a module listed above it, which is the healthy direction.
36→21 psst_gui.controller.playback uses psst_core.player✕
- Connections
- 3 pairs of types, where a type in psst_gui.controller.playback uses a type in psst_core.player.
- The types involved
psst_gui.controller.playback.PlaybackController→psst_core.player.PlaybackConfigpsst_gui.controller.playback.PlaybackController→psst_core.player.Playerpsst_gui.controller.playback.PlaybackController→psst_core.player.PlayerEvent
- Direction
- psst_gui.controller.playback uses psst_core.player, so a change to psst_core.player can break psst_gui.controller.playback, while a change to psst_gui.controller.playback can't break psst_core.player.
- Position
- Below the diagonal: psst_gui.controller.playback uses a module listed above it, which is the healthy direction.
36→23 psst_gui.controller.playback uses psst_gui.data.playback✕
- Connections
- 3 pairs of types, where a type in psst_gui.controller.playback uses a type in psst_gui.data.playback.
- The types involved
psst_gui.controller.playback.PlaybackController→psst_gui.data.playback.NowPlayingpsst_gui.controller.playback.PlaybackController→psst_gui.data.playback.Playbackpsst_gui.controller.playback.PlaybackController→psst_gui.data.playback.QueueBehavior
- Direction
- psst_gui.controller.playback uses psst_gui.data.playback, so a change to psst_gui.data.playback can break psst_gui.controller.playback, while a change to psst_gui.controller.playback can't break psst_gui.data.playback.
- Position
- Below the diagonal: psst_gui.controller.playback uses a module listed above it, which is the healthy direction.
36→35 psst_gui.controller.playback uses psst_gui.data✕
- Connections
- 2 pairs of types, where a type in psst_gui.controller.playback uses a type in psst_gui.data.
- The types involved
psst_gui.controller.playback.PlaybackController→psst_gui.data.AppStatepsst_gui.controller.playback.playback$module→psst_gui.data.AppState
- Direction
- psst_gui.controller.playback uses psst_gui.data, so a change to psst_gui.data can break psst_gui.controller.playback, while a change to psst_gui.controller.playback can't break psst_gui.data.
- Position
- Below the diagonal: psst_gui.controller.playback uses a module listed above it, which is the healthy direction.
37→6 psst_gui.ui uses psst_gui.data.nav✕
- Connections
- 1 pair of types, where a type in psst_gui.ui uses a type in psst_gui.data.nav.
- The types involved
psst_gui.ui.ui$module→psst_gui.data.nav.Nav
- Direction
- psst_gui.ui uses psst_gui.data.nav, so a change to psst_gui.data.nav can break psst_gui.ui, while a change to psst_gui.ui can't break psst_gui.data.nav.
- Position
- Below the diagonal: psst_gui.ui uses a module listed above it, which is the healthy direction.
37→8 psst_gui.ui uses psst_gui.widget.icons✕
- Connections
- 1 pair of types, where a type in psst_gui.ui uses a type in psst_gui.widget.icons.
- The types involved
psst_gui.ui.ui$module→psst_gui.widget.icons.SvgIcon
- Direction
- psst_gui.ui uses psst_gui.widget.icons, so a change to psst_gui.widget.icons can break psst_gui.ui, while a change to psst_gui.ui can't break psst_gui.widget.icons.
- Position
- Below the diagonal: psst_gui.ui uses a module listed above it, which is the healthy direction.
37→24 psst_gui.ui uses psst_gui.data.config✕
- Connections
- 1 pair of types, where a type in psst_gui.ui uses a type in psst_gui.data.config.
- The types involved
psst_gui.ui.ui$module→psst_gui.data.config.Config
- Direction
- psst_gui.ui uses psst_gui.data.config, so a change to psst_gui.data.config can break psst_gui.ui, while a change to psst_gui.ui can't break psst_gui.data.config.
- Position
- Below the diagonal: psst_gui.ui uses a module listed above it, which is the healthy direction.
37→35 psst_gui.ui uses psst_gui.data✕
- Connections
- 2 pairs of types, where a type in psst_gui.ui uses a type in psst_gui.data.
- The types involved
psst_gui.ui.ArtworkController→psst_gui.data.AppStatepsst_gui.ui.ui$module→psst_gui.data.AppState
- Direction
- psst_gui.ui uses psst_gui.data, so a change to psst_gui.data can break psst_gui.ui, while a change to psst_gui.ui can't break psst_gui.data.
- Position
- Below the diagonal: psst_gui.ui uses a module listed above it, which is the healthy direction.
38→25 psst_gui.ui.episode uses psst_gui.ui.playable✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.episode uses a type in psst_gui.ui.playable.
- The types involved
psst_gui.ui.episode.episode$module→psst_gui.ui.playable.PlayRow
- Direction
- psst_gui.ui.episode uses psst_gui.ui.playable, so a change to psst_gui.ui.playable can break psst_gui.ui.episode, while a change to psst_gui.ui.episode can't break psst_gui.ui.playable.
- Position
- Below the diagonal: psst_gui.ui.episode uses a module listed above it, which is the healthy direction.
38→33 psst_gui.ui.episode uses psst_gui.data.show✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.episode uses a type in psst_gui.data.show.
- The types involved
psst_gui.ui.episode.episode$module→psst_gui.data.show.Episode
- Direction
- psst_gui.ui.episode uses psst_gui.data.show, so a change to psst_gui.data.show can break psst_gui.ui.episode, while a change to psst_gui.ui.episode can't break psst_gui.data.show.
- Position
- Below the diagonal: psst_gui.ui.episode uses a module listed above it, which is the healthy direction.
38→35 psst_gui.ui.episode uses psst_gui.data✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.episode uses a type in psst_gui.data.
- The types involved
psst_gui.ui.episode.episode$module→psst_gui.data.Library
- Direction
- psst_gui.ui.episode uses psst_gui.data, so a change to psst_gui.data can break psst_gui.ui.episode, while a change to psst_gui.ui.episode can't break psst_gui.data.
- Position
- Below the diagonal: psst_gui.ui.episode uses a module listed above it, which is the healthy direction.
39→8 psst_gui.ui.preferences uses psst_gui.widget.icons✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.preferences uses a type in psst_gui.widget.icons.
- The types involved
psst_gui.ui.preferences.preferences$module→psst_gui.widget.icons.SvgIcon
- Direction
- psst_gui.ui.preferences uses psst_gui.widget.icons, so a change to psst_gui.widget.icons can break psst_gui.ui.preferences, while a change to psst_gui.ui.preferences can't break psst_gui.widget.icons.
- Position
- Below the diagonal: psst_gui.ui.preferences uses a module listed above it, which is the healthy direction.
39→24 psst_gui.ui.preferences uses psst_gui.data.config✕
- Connections
- 2 pairs of types, where a type in psst_gui.ui.preferences uses a type in psst_gui.data.config.
- The types involved
psst_gui.ui.preferences.CacheController→psst_gui.data.config.Preferencespsst_gui.ui.preferences.preferences$module→psst_gui.data.config.PreferencesTab
- Direction
- psst_gui.ui.preferences uses psst_gui.data.config, so a change to psst_gui.data.config can break psst_gui.ui.preferences, while a change to psst_gui.ui.preferences can't break psst_gui.data.config.
- Position
- Below the diagonal: psst_gui.ui.preferences uses a module listed above it, which is the healthy direction.
39→35 psst_gui.ui.preferences uses psst_gui.data✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.preferences uses a type in psst_gui.data.
- The types involved
psst_gui.ui.preferences.Authenticate→psst_gui.data.AppState
- Direction
- psst_gui.ui.preferences uses psst_gui.data, so a change to psst_gui.data can break psst_gui.ui.preferences, while a change to psst_gui.ui.preferences can't break psst_gui.data.
- Position
- Below the diagonal: psst_gui.ui.preferences uses a module listed above it, which is the healthy direction.
40→20 psst_gui.ui.track uses psst_gui.data.track✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.track uses a type in psst_gui.data.track.
- The types involved
psst_gui.ui.track.track$module→psst_gui.data.track.Track
- Direction
- psst_gui.ui.track uses psst_gui.data.track, so a change to psst_gui.data.track can break psst_gui.ui.track, while a change to psst_gui.ui.track can't break psst_gui.data.track.
- Position
- Below the diagonal: psst_gui.ui.track uses a module listed above it, which is the healthy direction.
40→23 psst_gui.ui.track uses psst_gui.data.playback✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.track uses a type in psst_gui.data.playback.
- The types involved
psst_gui.ui.track.track$module→psst_gui.data.playback.PlaybackOrigin
- Direction
- psst_gui.ui.track uses psst_gui.data.playback, so a change to psst_gui.data.playback can break psst_gui.ui.track, while a change to psst_gui.ui.track can't break psst_gui.data.playback.
- Position
- Below the diagonal: psst_gui.ui.track uses a module listed above it, which is the healthy direction.
40→25 psst_gui.ui.track uses psst_gui.ui.playable✕
- Connections
- 2 pairs of types, where a type in psst_gui.ui.track uses a type in psst_gui.ui.playable.
- The types involved
psst_gui.ui.track.track$module→psst_gui.ui.playable.Displaypsst_gui.ui.track.track$module→psst_gui.ui.playable.PlayRow
- Direction
- psst_gui.ui.track uses psst_gui.ui.playable, so a change to psst_gui.ui.playable can break psst_gui.ui.track, while a change to psst_gui.ui.track can't break psst_gui.ui.playable.
- Position
- Below the diagonal: psst_gui.ui.track uses a module listed above it, which is the healthy direction.
40→35 psst_gui.ui.track uses psst_gui.data✕
- Connections
- 1 pair of types, where a type in psst_gui.ui.track uses a type in psst_gui.data.
- The types involved
psst_gui.ui.track.track$module→psst_gui.data.Library
- Direction
- psst_gui.ui.track uses psst_gui.data, so a change to psst_gui.data can break psst_gui.ui.track, while a change to psst_gui.ui.track can't break psst_gui.data.
- Position
- Below the diagonal: psst_gui.ui.track 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 62 | High / Critical |
| A05:2025 — Injection | 18 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 53 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (3), utils.rs (2), show.rs (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +7.7 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.4 pts | Medium | Architecture documentation |
| Resolve the 53 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (3), utils.rs (2), show.rs (2). | +5.5 pts | Medium | Knowledge Freshness |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.7 pts | Medium | Documentation (README) |
| Enable Dependabot/Renovate or a dependency-review gate. | +2.0 pts | Medium | Security & performance tooling |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.8 pts | Low | Static Analysis (SAST) |
| 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. | +1.5 pts | Medium | Deployment & Rollback |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.6 pts | Low | Project Cohesion |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| psst-gui/src/webapi/client.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| psst-core/src/player/file.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| psst-gui/src/data/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| psst-gui/src/ui/playlist.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| psst-gui/src/ui/playback.rs | 6.3 | Mixed | Code Duplication: Duplicated block (10 lines × 2) |
| psst-gui/src/webapi/local.rs | 6.6 | Mixed | Explicit Debt: TodoComment |
| psst-gui/src/ui/episode.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| psst-gui/src/controller/playback.rs | 7.1 | Mixed | Cyclomatic Complexity: PlaybackController::event (cyclomatic 30) |
| psst-gui/src/ui/track.rs | 7.2 | Mixed | Cyclomatic Complexity: psst_gui::ui::track::playable_widget (cyclomatic 17) |
| psst-core/src/session/client_token.rs | 7.4 | Mixed | Cyclomatic Complexity: ClientTokenProvider::request_new_token (cyclomatic 16) |
| psst-gui/src/ui/preferences.rs | 7.4 | Mixed | Cognitive Complexity: Authenticate::event (cognitive 19) |
| psst-gui/src/ui/mod.rs | 7.4 | Mixed | Cognitive Complexity: ArtworkController::event (cognitive 16) |
| psst-gui/src/ui/theme.rs | 7.4 | Mixed | Code Duplication: Edited copy of a member (18 corresponding lines) |
| psst-gui/src/ui/home.rs | 7.4 | Mixed | Code Duplication: Edited copies of one member (7 members, 16+ corresponding lines) |
| psst-gui/src/ui/album.rs | 7.4 | Mixed | Code Duplication: Edited copies of one member (4 members, 16+ corresponding lines) |
| psst-gui/src/widget/maybe.rs | 7.4 | Mixed | Code Duplication: Edited copy of a member (11 corresponding lines) |
| psst-gui/src/delegate.rs | 7.8 | Mixed | Cyclomatic Complexity: Delegate::command (cyclomatic 24) |
| psst-gui/src/controller/nav.rs | 7.8 | Mixed | Cyclomatic Complexity: NavController::load_route_data (cyclomatic 21) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 41 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 41 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, 218 of 247 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.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.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
5 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was PlaybackController::event at 30. A further 1 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 Error::fmt at 26 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: psst-core/src/error.rs (Error::fmt at 26). 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 15 down to 15 or less in Cyclomatic Complexity — start with PlaybackController::event (cyclomatic 30), Delegate::command (cyclomatic 24), NavController::load_route_data (cyclomatic 21). — 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 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
9 function(s) exceeded the cognitive complexity threshold of 15; the worst was Delegate::command at 36.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with Delegate::command (cognitive 36). — Refactoring it lifts Cognitive Complexity from 8.4 to about 8.6/10.
D3 · God Classes
10 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 MethodTooLong finding(s) in God Classes — start with client.rs (2), client_token.rs, playback.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with client.rs, playback.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with client.rs, preferences.rs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
15 duplicated block group(s) detected. 5.4 % of the production lines (1,073 of 19,875) are in a reported copy. A further 25 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with nav.rs, remote_image.rs, mod.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with file.rs, mod.rs, artist.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with playback.rs, preferences.rs, playlist.rs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
3 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
3 of 88 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with client.rs, mod.rs, playback.rs. — One of this dimension's main actionable groups (3 warning-level).
D12 · Dependency Hygiene
14 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 651 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. A further 7 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is psst-gui/src/ui/search.rs. Counted over 81 of the 113 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
19 deducted task-comment markers across 19875 LoC (0.1/KLoC) → score 9.8. 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 19 TodoComment finding(s) in Explicit Debt — start with local.rs (4), mod.rs (2), file.rs (2). — One of this dimension's main actionable groups (19 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 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)
18 finding(s): 0 critical, 18 high, 0 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. semgrep hit a parse error in 1 file(s) — `psst-gui/build-icons.sh` (line 6, line 10, line 14, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-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
55 finding(s): 0 critical, 5 high, 50 medium, 0 low.
What to do
- Resolve the 22 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (22). — One of this dimension's main actionable groups (22 warning-level).
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
55 of 81 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is psst-gui/src/widget/icons.rs. Counted over 81 of the 113 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 53 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (3), utils.rs (2), show.rs (2). — One of this dimension's main actionable groups (53 recommendation-level).
- Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with icons.rs, playback.rs. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 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 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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`cargo test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
P2 · Observability
What to do
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- 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
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — psst-core/src/util.rs:41, psst-core/src/util.rs:51
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `psst-core/src/util.rs:41` (`Sha1::digest`), `psst-core/src/util.rs:51` (`Sha1::new`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X15 · Unvalidated length from an untrusted reader
- `size` is read from the bytes being parsed at line 338 (`read_u32`), then used to size a `vec![…; n]` at line 339 — and nowhere in its scope is `size` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `size` against the bytes actually remaining and a maximum the format allows before allocating. — psst-core/src/connection/mod.rs:339
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 91% | Exemplary | Solid. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 55% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate | Acceptable, with room to improve. |
| Security | 67% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
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 — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~78 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 — no .rs test runner
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (3549 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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): 3 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 — Not assessed, and this one is on us: 3 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 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 — 142 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment psst-gui/src/webapi/client.rs:285
- TodoComment psst-gui/src/webapi/local.rs:152
- TodoComment psst-gui/src/webapi/local.rs:161
- TodoComment psst-gui/src/webapi/local.rs:171
- TodoComment psst-gui/src/webapi/local.rs:184
- TodoComment psst-gui/src/ui/episode.rs:88
- TodoComment psst-gui/src/ui/playlist.rs:395
- TodoComment psst-gui/src/ui/show.rs:200
- TodoComment psst-gui/src/ui/menu.rs:25
- TodoComment psst-gui/src/ui/playable.rs:57
- TodoComment psst-gui/src/ui/user.rs:19
- TodoComment psst-gui/src/data/mod.rs:280
- TodoComment psst-core/src/item_id.rs:122
- TodoComment psst-core/src/player/file.rs:250
- TodoComment psst-core/src/player/file.rs:263
- TodoComment psst-core/src/player/item.rs:102
- TodoComment psst-core/src/connection/mod.rs:239
- TodoComment psst-core/src/audio/resample.rs:68
- TodoComment psst-core/src/audio/output/cpal.rs:38
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: WebApi.load_and_return_home_section psst-gui/src/webapi/client.rs:396
- MethodTooLong: ClientTokenProvider.request_new_token psst-core/src/session/client_token.rs:49
- MethodTooLong: WebApi.get_artist_overview psst-gui/src/webapi/client.rs:1094
- MethodTooLong: PlaybackController.event psst-gui/src/controller/playback.rs:417
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (15 corresponding lines) psst-gui/src/data/nav.rs:60
- Edited copy of a member (15 corresponding lines) psst-gui/src/widget/remote_image.rs:58
- Edited copy of a member (15 corresponding lines) psst-core/src/player/mod.rs:302
- Edited copy of a member (7 corresponding lines) psst-core/src/player/file.rs:163
- Edited copy of a member (7 corresponding lines) psst-gui/src/data/mod.rs:476
- Edited copy of a member (7 corresponding lines) psst-gui/src/ui/artist.rs:216
- Duplicated block (10 lines × 2) psst-gui/src/ui/playback.rs:135
- Duplicated block (10 lines × 2) psst-gui/src/ui/preferences.rs:216
- Duplicated block (10 lines × 2) psst-gui/src/ui/playlist.rs:168
- Duplicated block (9 lines × 2) psst-gui/src/ui/mod.rs:72
- Duplicated block (9 lines × 2) psst-gui/src/ui/theme.rs:140
- Duplicated block (9 lines × 2) psst-core/src/oauth.rs:276
- Duplicated block (6 lines × 2) psst-gui/src/webapi/client.rs:289
- Duplicated block (6 lines × 2) psst-gui/src/ui/album.rs:93
- Duplicated block (6 lines × 2) psst-gui/src/data/nav.rs:61
- Low cohesion: RequestBuilder (LCOM4 5) psst-gui/src/webapi/client.rs:1902
- Low cohesion: Library (LCOM4 4) psst-gui/src/data/mod.rs:345
- Low cohesion: SeekBar (LCOM4 4) psst-gui/src/ui/playback.rs:397
- psst_gui::ui::track::playable_widget (cognitive 22) psst-gui/src/ui/track.rs:53
- psst_gui::ui::track::track_menu (cognitive 19) psst-gui/src/ui/track.rs:238
- PlaybackController::report_scrobble (cognitive 18) psst-gui/src/controller/playback.rs:290
- PlaybackController::event (cognitive 18) psst-gui/src/controller/playback.rs:417
- ClassTooLong: WebApi psst-gui/src/webapi/client.rs:53
- ClassTooLong: PlaybackController psst-gui/src/controller/playback.rs:36
- FileTooLong: webapi/client.rs psst-gui/src/webapi/client.rs
- FileTooLong: ui/preferences.rs psst-gui/src/ui/preferences.rs
- Edited copy of a member (11 corresponding lines) psst-gui/src/widget/maybe.rs:89
- Edited copy of a member (11 corresponding lines) psst-gui/src/ui/playlist.rs:527
- Duplicated block (5 lines × 2) psst-gui/src/ui/playback.rs:552
- Duplicated block (5 lines × 2) psst-gui/src/ui/theme.rs:132
- Weak hash algorithm psst-core/src/util.rs:41
- Weak hash algorithm psst-core/src/util.rs:51
- PlaybackController::event (cyclomatic 30) psst-gui/src/controller/playback.rs:417
- Delegate::command (cyclomatic 24) psst-gui/src/delegate.rs:134
- NavController::load_route_data (cyclomatic 21) psst-gui/src/controller/nav.rs:12
- psst_gui::ui::track::playable_widget (cyclomatic 17) psst-gui/src/ui/track.rs:53
- ClientTokenProvider::request_new_token (cyclomatic 16) psst-core/src/session/client_token.rs:49
- Delegate::command (cognitive 36) psst-gui/src/delegate.rs:134
- ClientTokenProvider::request_new_token (cognitive 24) psst-core/src/session/client_token.rs:49
- NavController::load_route_data (cognitive 20) psst-gui/src/controller/nav.rs:12
- Authenticate::event (cognitive 19) psst-gui/src/ui/preferences.rs:740
- ArtworkController::event (cognitive 16) psst-gui/src/ui/mod.rs:164
- TooManyMethods: WebApi psst-gui/src/webapi/client.rs:53
- FunctionTooLong: psst_gui::ui::track::playable_widget psst-gui/src/ui/track.rs:53
- REDACTED
- REDACTED
- Edited copy of a member (60 corresponding lines) psst-gui/src/ui/library.rs:34
- Edited copy of a member (18 corresponding lines) psst-gui/src/ui/theme.rs:131
- Edited copy of a member (24 corresponding lines) psst-gui/src/controller/playback.rs:265
- Edited copy of a member (27 corresponding lines) psst-core/src/oauth.rs:270
- Edited copies of one member (3 members, 16+ corresponding lines) psst-gui/src/widget/promise.rs:50
- Edited copies of one member (7 members, 16+ corresponding lines) psst-gui/src/ui/home.rs:49
- Edited copies of one member (4 members, 16+ corresponding lines) psst-gui/src/ui/album.rs:23
- Edited copy of a member (17 corresponding lines) psst-gui/src/ui/home.rs:83
- Edited copy of a member (9 corresponding lines) psst-core/src/metadata.rs:53
- Edited copy of a member (13 corresponding lines) psst-core/src/session/audio_key.rs:50
- Edited copies of one member (3 members, 13+ corresponding lines) psst-gui/src/webapi/client.rs:1377
- Edited copies of one member (3 members, 10+ corresponding lines) psst-gui/src/ui/home.rs:311
- Edited copies of one member (4 members, 13+ corresponding lines) psst-gui/src/ui/mod.rs:57
- Edited copy of a member (6 corresponding lines) psst-gui/src/widget/maybe.rs:74
- Edited copy of a member (12 corresponding lines) psst-core/src/audio/decode.rs:30
- Edited copy of a member (8 corresponding lines) psst-gui/src/widget/maybe.rs:49
- Edited copies of one member (3 members, 7+ corresponding lines) psst-gui/src/ui/episode.rs:79
- Duplicated block (15 lines × 2) psst-gui/src/ui/album.rs:193
- Duplicated block (12 lines × 2) psst-gui/src/webapi/client.rs:673
- Duplicated block (8 lines × 2) psst-core/src/player/mod.rs:243
- Duplicated block (7 lines × 2) psst-gui/src/controller/ex_click.rs:55
- Off the main sequence: psst-core
- Length read from the parsed input is spent without ever being bounded psst-core/src/connection/mod.rs:339
Minor — 68 finding(s)
- Orphaned file psst-core/src/player/mod.rs:1
- Orphaned file psst-core/src/session/mod.rs:1
- Orphaned file psst-gui/src/ui/home.rs:1
- Orphaned file psst-gui/src/webapi/local.rs:1
- Orphaned file psst-core/src/player/worker.rs:1
- Orphaned file psst-core/src/player/file.rs:1
- Orphaned file psst-core/src/session/client_token.rs:1
- Orphaned file psst-core/src/session/login5.rs:1
- Orphaned file psst-core/src/player/storage.rs:1
- Orphaned file psst-core/src/audio/output/cpal.rs:1
- Orphaned file psst-gui/src/ui/album.rs:1
- Orphaned file psst-gui/src/widget/utils.rs:1
- Orphaned file psst-gui/src/ui/show.rs:1
- Orphaned file psst-core/src/player/item.rs:1
- Orphaned file psst-core/src/audio/output/cubeb.rs:1
- Orphaned file psst-gui/src/widget/promise.rs:1
- Orphaned file psst-gui/src/ui/find.rs:1
- Orphaned file psst-gui/src/ui/theme.rs:1
- Orphaned file psst-core/src/item_id.rs:1
- Orphaned file psst-core/src/session/mercury.rs:1
- Orphaned file psst-gui/src/widget/maybe.rs:1
- Orphaned file psst-core/src/audio/decode.rs:1
- Orphaned file psst-gui/src/ui/recommend.rs:1
- Orphaned file psst-gui/src/ui/library.rs:1
- Orphaned file psst-gui/src/data/ctx.rs:1
- Most significant orphaned file psst-gui/src/widget/icons.rs:1
- Most significant orphaned file psst-gui/src/controller/playback.rs:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found psst-gui/src/main.rs:1
- Projects may be oversized for their cohesion
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No release approval gate
Minor — 14 finding(s)
- Outdated: crossbeam-channel
- Outdated: data-encoding
- Outdated: env_logger
- Outdated: image
- Outdated: log
- Outdated: open
- Outdated: rangemap
- Outdated: regex
- Outdated: serde
- Outdated: serde_json
- Outdated: tempfile
- Outdated: time
- Outdated: ureq
- Outdated: url
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c8869c31f0b045ef858442a1100ee1aa/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c8869c31f0b045ef858442a1100ee1aa/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 18 | 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 . | 55 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |