Executive summary
librespot-org/librespot falls short of our standard for a preview release, in part because we found no access checks on the code's endpoints or handlers. It scores 51 out of 100 and is rated Adequate, and all 44 of its critical findings are security problems.
Security and Compliance, at 28, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 9 points. Adding access checks would lift Security and Compliance itself, worth about 13 points. Raising Security and Compliance to 68 would lift the score to about 66.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seventeen settings leave the servers or containers unsafe, and three known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, correcting the unsafe settings and updating the vulnerable packages would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the password or key in the code's history needs replacing, with the old one switched off.
The product code is 25,552 lines, about €25,000 to rebuild.
If Security and Compliance rose from 28 to 68, the lowest score rated Strong, the score would rise from 51 to about 66.
New since the last survey: 20 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Documentation (README) · README may be stale
- Web-Security Posture · Weak hash algorithm core/src/authentication.rs
- Web-Security Posture · Weak hash algorithm core/src/connection/handshake.rs
- Web-Security Posture · Weak hash algorithm core/src/util.rs
- Web-Security Posture · Weak hash algorithm core/src/util.rs
- Web-Security Posture · Weak hash algorithm discovery/src/server.rs
- Web-Security Posture · Weak hash algorithm src/main.rs
Fixed since the last survey: 5 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0190 REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €25,000 · Estimate
| Cost to rebuild | €8,200 to €41,000, for 137 to 435 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.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 25,552 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 librespot_connect.state.metadata | 2 librespot_core.authentication | 3 librespot_core.config | 4 librespot_core.date | 5 librespot_core.dealer.protocol | 6 librespot_core.dealer.protocol.request | 7 librespot_metadata.audio.file | 8 librespot_metadata.restriction | 9 librespot_playback.config | 10 librespot_playback.convert | 11 librespot_connect.state.context | 12 librespot_core.dealer | 13 librespot_core.spotify_id | 14 librespot_metadata.availability | 15 librespot_metadata.playlist.attribute | 16 librespot_playback.decoder | 17 librespot_audio.fetch | 18 librespot_discovery.server | 19 librespot_metadata.episode | 20 librespot_metadata.playlist.item | 21 librespot_metadata.track | 22 librespot_playback.audio_backend | 23 librespot_discovery | 24 librespot_metadata.artist | 25 librespot_metadata.playlist.list | 26 librespot_metadata.show | 27 librespot_metadata.album | 28 librespot_core.spotify_uri | 29 librespot_metadata.image | 30 librespot_core.file_id | 31 librespot_core.cache | 32 librespot_core.session | 33 librespot_metadata.audio.item | 34 librespot_metadata.playlist.annotation | 35 librespot_playback.player | 36 librespot_connect.state | 37 librespot.main | 38 librespot_connect.context_resolver | 39 librespot_connect.spirc | 40 librespot_core.error |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 librespot_connect.state.metadata | ||||||||||||||||||||||||||||||||||||||||
| 2 librespot_core.authentication | ||||||||||||||||||||||||||||||||||||||||
| 3 librespot_core.config | ||||||||||||||||||||||||||||||||||||||||
| 4 librespot_core.date | ||||||||||||||||||||||||||||||||||||||||
| 5 librespot_core.dealer.protocol | ||||||||||||||||||||||||||||||||||||||||
| 6 librespot_core.dealer.protocol.request | ||||||||||||||||||||||||||||||||||||||||
| 7 librespot_metadata.audio.file | ||||||||||||||||||||||||||||||||||||||||
| 8 librespot_metadata.restriction | ||||||||||||||||||||||||||||||||||||||||
| 9 librespot_playback.config | ||||||||||||||||||||||||||||||||||||||||
| 10 librespot_playback.convert | ||||||||||||||||||||||||||||||||||||||||
| 11 librespot_connect.state.context | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 librespot_core.dealer | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 librespot_core.spotify_id | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 librespot_metadata.availability | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 librespot_metadata.playlist.attribute | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 librespot_playback.decoder | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 librespot_audio.fetch | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 librespot_discovery.server | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 librespot_metadata.episode | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||
| 20 librespot_metadata.playlist.item | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 21 librespot_metadata.track | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||
| 22 librespot_playback.audio_backend | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 librespot_discovery | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 librespot_metadata.artist | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||
| 25 librespot_metadata.playlist.list | 1 | 2 | 2 | 1 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 26 librespot_metadata.show | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 27 librespot_metadata.album | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||
| 28 librespot_core.spotify_uri | 1 | 1 | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 29 librespot_metadata.image | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 librespot_core.file_id | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 librespot_core.cache | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 librespot_core.session | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 33 librespot_metadata.audio.item | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 34 librespot_metadata.playlist.annotation | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 librespot_playback.player | 1 | 4 | 1 | 1 | 3 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 36 librespot_connect.state | 1 | 2 | 1 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 37 librespot.main | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 librespot_connect.context_resolver | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 librespot_connect.spirc | 1 | 1 | 1 | 2 | 2 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 40 librespot_core.error | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
11→1 librespot_connect.state.context uses librespot_connect.state.metadata✕
- Connections
- 1 pair of types, where a type in librespot_connect.state.context uses a type in librespot_connect.state.metadata.
- The types involved
librespot_connect.state.context.StateContext→librespot_connect.state.metadata.Metadata
- Direction
- librespot_connect.state.context uses librespot_connect.state.metadata, so a change to librespot_connect.state.metadata can break librespot_connect.state.context, while a change to librespot_connect.state.context can't break librespot_connect.state.metadata.
- Position
- Below the diagonal: librespot_connect.state.context uses a module listed above it, which is the healthy direction.
11→8 librespot_connect.state.context uses librespot_metadata.restriction✕
- Connections
- 1 pair of types, where a type in librespot_connect.state.context uses a type in librespot_metadata.restriction.
- The types involved
librespot_connect.state.context.StateContext→librespot_metadata.restriction.Restrictions
- Direction
- librespot_connect.state.context uses librespot_metadata.restriction, so a change to librespot_metadata.restriction can break librespot_connect.state.context, while a change to librespot_connect.state.context can't break librespot_metadata.restriction.
- Position
- Below the diagonal: librespot_connect.state.context uses a module listed above it, which is the healthy direction.
12→5 librespot_core.dealer uses librespot_core.dealer.protocol✕
- Connections
- 3 pairs of types, where a type in librespot_core.dealer uses a type in librespot_core.dealer.protocol.
- The types involved
librespot_core.dealer.DealerShared→librespot_core.dealer.protocol.MessageOrRequestlibrespot_core.dealer.DealerShared→librespot_core.dealer.protocol.WebsocketMessagelibrespot_core.dealer.DealerShared→librespot_core.dealer.protocol.WebsocketRequest
- Direction
- librespot_core.dealer uses librespot_core.dealer.protocol, so a change to librespot_core.dealer.protocol can break librespot_core.dealer, while a change to librespot_core.dealer can't break librespot_core.dealer.protocol.
- Position
- Below the diagonal: librespot_core.dealer uses a module listed above it, which is the healthy direction.
12→6 librespot_core.dealer uses librespot_core.dealer.protocol.request✕
- Connections
- 1 pair of types, where a type in librespot_core.dealer uses a type in librespot_core.dealer.protocol.request.
- The types involved
librespot_core.dealer.RequestHandler→librespot_core.dealer.protocol.request.Request
- Direction
- librespot_core.dealer uses librespot_core.dealer.protocol.request, so a change to librespot_core.dealer.protocol.request can break librespot_core.dealer, while a change to librespot_core.dealer can't break librespot_core.dealer.protocol.request.
- Position
- Below the diagonal: librespot_core.dealer uses a module listed above it, which is the healthy direction.
13→28 librespot_core.spotify_id uses librespot_core.spotify_uri part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_core.spotify_id uses a type in librespot_core.spotify_uri.
- The types involved
librespot_core.spotify_id.SpotifyId→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_core.spotify_id uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_core.spotify_id, while a change to librespot_core.spotify_id can't break librespot_core.spotify_uri.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→4 librespot_metadata.availability uses librespot_core.date✕
- Connections
- 1 pair of types, where a type in librespot_metadata.availability uses a type in librespot_core.date.
- The types involved
librespot_metadata.availability.Availability→librespot_core.date.Date
- Direction
- librespot_metadata.availability uses librespot_core.date, so a change to librespot_core.date can break librespot_metadata.availability, while a change to librespot_metadata.availability can't break librespot_core.date.
- Position
- Below the diagonal: librespot_metadata.availability uses a module listed above it, which is the healthy direction.
15→4 librespot_metadata.playlist.attribute uses librespot_core.date✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.attribute uses a type in librespot_core.date.
- The types involved
librespot_metadata.playlist.attribute.PlaylistItemAttributes→librespot_core.date.Date
- Direction
- librespot_metadata.playlist.attribute uses librespot_core.date, so a change to librespot_core.date can break librespot_metadata.playlist.attribute, while a change to librespot_metadata.playlist.attribute can't break librespot_core.date.
- Position
- Below the diagonal: librespot_metadata.playlist.attribute uses a module listed above it, which is the healthy direction.
15→29 librespot_metadata.playlist.attribute uses librespot_metadata.image part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.attribute uses a type in librespot_metadata.image.
- The types involved
librespot_metadata.playlist.attribute.PlaylistAttributes→librespot_metadata.image.PictureSizes
- Direction
- librespot_metadata.playlist.attribute uses librespot_metadata.image, so a change to librespot_metadata.image can break librespot_metadata.playlist.attribute, while a change to librespot_metadata.playlist.attribute can't break librespot_metadata.image.
- 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.
16→40 librespot_playback.decoder uses librespot_core.error part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_playback.decoder uses a type in librespot_core.error.
- The types involved
librespot_playback.decoder.DecoderError→librespot_core.error.Error
- Direction
- librespot_playback.decoder uses librespot_core.error, so a change to librespot_core.error can break librespot_playback.decoder, while a change to librespot_playback.decoder can't break librespot_core.error.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→12 librespot_audio.fetch uses librespot_core.dealer✕
- Connections
- 1 pair of types, where a type in librespot_audio.fetch uses a type in librespot_core.dealer.
- The types involved
librespot_audio.fetch.StreamingRequest→librespot_core.dealer.Response
- Direction
- librespot_audio.fetch uses librespot_core.dealer, so a change to librespot_core.dealer can break librespot_audio.fetch, while a change to librespot_audio.fetch can't break librespot_core.dealer.
- Position
- Below the diagonal: librespot_audio.fetch uses a module listed above it, which is the healthy direction.
17→30 librespot_audio.fetch uses librespot_core.file_id part of a loop✕
- Connections
- 2 pairs of types, where a type in librespot_audio.fetch uses a type in librespot_core.file_id.
- The types involved
librespot_audio.fetch.AudioFile→librespot_core.file_id.FileIdlibrespot_audio.fetch.AudioFileStreaming→librespot_core.file_id.FileId
- Direction
- librespot_audio.fetch uses librespot_core.file_id, so a change to librespot_core.file_id can break librespot_audio.fetch, while a change to librespot_audio.fetch can't break librespot_core.file_id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→32 librespot_audio.fetch uses librespot_core.session part of a loop✕
- Connections
- 2 pairs of types, where a type in librespot_audio.fetch uses a type in librespot_core.session.
- The types involved
librespot_audio.fetch.AudioFile→librespot_core.session.Sessionlibrespot_audio.fetch.AudioFileStreaming→librespot_core.session.Session
- Direction
- librespot_audio.fetch uses librespot_core.session, so a change to librespot_core.session can break librespot_audio.fetch, while a change to librespot_audio.fetch can't break librespot_core.session.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→3 librespot_discovery.server uses librespot_core.config✕
- Connections
- 1 pair of types, where a type in librespot_discovery.server uses a type in librespot_core.config.
- The types involved
librespot_discovery.server.Config→librespot_core.config.DeviceType
- Direction
- librespot_discovery.server uses librespot_core.config, so a change to librespot_core.config can break librespot_discovery.server, while a change to librespot_discovery.server can't break librespot_core.config.
- Position
- Below the diagonal: librespot_discovery.server uses a module listed above it, which is the healthy direction.
18→6 librespot_discovery.server uses librespot_core.dealer.protocol.request✕
- Connections
- 1 pair of types, where a type in librespot_discovery.server uses a type in librespot_core.dealer.protocol.request.
- The types involved
librespot_discovery.server.RequestHandler→librespot_core.dealer.protocol.request.Request
- Direction
- librespot_discovery.server uses librespot_core.dealer.protocol.request, so a change to librespot_core.dealer.protocol.request can break librespot_discovery.server, while a change to librespot_discovery.server can't break librespot_core.dealer.protocol.request.
- Position
- Below the diagonal: librespot_discovery.server uses a module listed above it, which is the healthy direction.
18→12 librespot_discovery.server uses librespot_core.dealer✕
- Connections
- 1 pair of types, where a type in librespot_discovery.server uses a type in librespot_core.dealer.
- The types involved
librespot_discovery.server.RequestHandler→librespot_core.dealer.Response
- Direction
- librespot_discovery.server uses librespot_core.dealer, so a change to librespot_core.dealer can break librespot_discovery.server, while a change to librespot_discovery.server can't break librespot_core.dealer.
- Position
- Below the diagonal: librespot_discovery.server uses a module listed above it, which is the healthy direction.
18→40 librespot_discovery.server uses librespot_core.error part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_discovery.server uses a type in librespot_core.error.
- The types involved
librespot_discovery.server.RequestHandler→librespot_core.error.Error
- Direction
- librespot_discovery.server uses librespot_core.error, so a change to librespot_core.error can break librespot_discovery.server, while a change to librespot_discovery.server can't break librespot_core.error.
- 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 librespot_metadata.episode uses librespot_connect.state.metadata✕
- Connections
- 1 pair of types, where a type in librespot_metadata.episode uses a type in librespot_connect.state.metadata.
- The types involved
librespot_metadata.episode.Episode→librespot_connect.state.metadata.Metadata
- Direction
- librespot_metadata.episode uses librespot_connect.state.metadata, so a change to librespot_connect.state.metadata can break librespot_metadata.episode, while a change to librespot_metadata.episode can't break librespot_connect.state.metadata.
- Position
- Below the diagonal: librespot_metadata.episode uses a module listed above it, which is the healthy direction.
19→4 librespot_metadata.episode uses librespot_core.date✕
- Connections
- 1 pair of types, where a type in librespot_metadata.episode uses a type in librespot_core.date.
- The types involved
librespot_metadata.episode.Episode→librespot_core.date.Date
- Direction
- librespot_metadata.episode uses librespot_core.date, so a change to librespot_core.date can break librespot_metadata.episode, while a change to librespot_metadata.episode can't break librespot_core.date.
- Position
- Below the diagonal: librespot_metadata.episode uses a module listed above it, which is the healthy direction.
19→5 librespot_metadata.episode uses librespot_core.dealer.protocol✕
- Connections
- 1 pair of types, where a type in librespot_metadata.episode uses a type in librespot_core.dealer.protocol.
- The types involved
librespot_metadata.episode.Episode→librespot_core.dealer.protocol.Message
- Direction
- librespot_metadata.episode uses librespot_core.dealer.protocol, so a change to librespot_core.dealer.protocol can break librespot_metadata.episode, while a change to librespot_metadata.episode can't break librespot_core.dealer.protocol.
- Position
- Below the diagonal: librespot_metadata.episode uses a module listed above it, which is the healthy direction.
19→7 librespot_metadata.episode uses librespot_metadata.audio.file✕
- Connections
- 1 pair of types, where a type in librespot_metadata.episode uses a type in librespot_metadata.audio.file.
- The types involved
librespot_metadata.episode.Episode→librespot_metadata.audio.file.AudioFiles
- Direction
- librespot_metadata.episode uses librespot_metadata.audio.file, so a change to librespot_metadata.audio.file can break librespot_metadata.episode, while a change to librespot_metadata.episode can't break librespot_metadata.audio.file.
- Position
- Below the diagonal: librespot_metadata.episode uses a module listed above it, which is the healthy direction.
19→8 librespot_metadata.episode uses librespot_metadata.restriction✕
- Connections
- 1 pair of types, where a type in librespot_metadata.episode uses a type in librespot_metadata.restriction.
- The types involved
librespot_metadata.episode.Episode→librespot_metadata.restriction.Restrictions
- Direction
- librespot_metadata.episode uses librespot_metadata.restriction, so a change to librespot_metadata.restriction can break librespot_metadata.episode, while a change to librespot_metadata.episode can't break librespot_metadata.restriction.
- Position
- Below the diagonal: librespot_metadata.episode uses a module listed above it, which is the healthy direction.
19→14 librespot_metadata.episode uses librespot_metadata.availability✕
- Connections
- 1 pair of types, where a type in librespot_metadata.episode uses a type in librespot_metadata.availability.
- The types involved
librespot_metadata.episode.Episode→librespot_metadata.availability.Availabilities
- Direction
- librespot_metadata.episode uses librespot_metadata.availability, so a change to librespot_metadata.availability can break librespot_metadata.episode, while a change to librespot_metadata.episode can't break librespot_metadata.availability.
- Position
- Below the diagonal: librespot_metadata.episode uses a module listed above it, which is the healthy direction.
19→28 librespot_metadata.episode uses librespot_core.spotify_uri part of a loop✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.episode uses a type in librespot_core.spotify_uri.
- The types involved
librespot_metadata.episode.Episode→librespot_core.spotify_uri.SpotifyUrilibrespot_metadata.episode.Episodes→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_metadata.episode uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_metadata.episode, while a change to librespot_metadata.episode can't break librespot_core.spotify_uri.
- 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→29 librespot_metadata.episode uses librespot_metadata.image part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.episode uses a type in librespot_metadata.image.
- The types involved
librespot_metadata.episode.Episode→librespot_metadata.image.Images
- Direction
- librespot_metadata.episode uses librespot_metadata.image, so a change to librespot_metadata.image can break librespot_metadata.episode, while a change to librespot_metadata.episode can't break librespot_metadata.image.
- 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→32 librespot_metadata.episode uses librespot_core.session part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.episode uses a type in librespot_core.session.
- The types involved
librespot_metadata.episode.Episode→librespot_core.session.Session
- Direction
- librespot_metadata.episode uses librespot_core.session, so a change to librespot_core.session can break librespot_metadata.episode, while a change to librespot_metadata.episode can't break librespot_core.session.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→4 librespot_metadata.playlist.item uses librespot_core.date✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.item uses a type in librespot_core.date.
- The types involved
librespot_metadata.playlist.item.PlaylistMetaItem→librespot_core.date.Date
- Direction
- librespot_metadata.playlist.item uses librespot_core.date, so a change to librespot_core.date can break librespot_metadata.playlist.item, while a change to librespot_metadata.playlist.item can't break librespot_core.date.
- Position
- Below the diagonal: librespot_metadata.playlist.item uses a module listed above it, which is the healthy direction.
20→15 librespot_metadata.playlist.item uses librespot_metadata.playlist.attribute✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.playlist.item uses a type in librespot_metadata.playlist.attribute.
- The types involved
librespot_metadata.playlist.item.PlaylistItem→librespot_metadata.playlist.attribute.PlaylistItemAttributeslibrespot_metadata.playlist.item.PlaylistMetaItem→librespot_metadata.playlist.attribute.PlaylistAttributes
- Direction
- librespot_metadata.playlist.item uses librespot_metadata.playlist.attribute, so a change to librespot_metadata.playlist.attribute can break librespot_metadata.playlist.item, while a change to librespot_metadata.playlist.item can't break librespot_metadata.playlist.attribute.
- Position
- Below the diagonal: librespot_metadata.playlist.item uses a module listed above it, which is the healthy direction.
20→28 librespot_metadata.playlist.item uses librespot_core.spotify_uri part of a loop✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.playlist.item uses a type in librespot_core.spotify_uri.
- The types involved
librespot_metadata.playlist.item.PlaylistItem→librespot_core.spotify_uri.SpotifyUrilibrespot_metadata.playlist.item.PlaylistMetaItem→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_metadata.playlist.item uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_metadata.playlist.item, while a change to librespot_metadata.playlist.item can't break librespot_core.spotify_uri.
- 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→1 librespot_metadata.track uses librespot_connect.state.metadata✕
- Connections
- 1 pair of types, where a type in librespot_metadata.track uses a type in librespot_connect.state.metadata.
- The types involved
librespot_metadata.track.Track→librespot_connect.state.metadata.Metadata
- Direction
- librespot_metadata.track uses librespot_connect.state.metadata, so a change to librespot_connect.state.metadata can break librespot_metadata.track, while a change to librespot_metadata.track can't break librespot_connect.state.metadata.
- Position
- Below the diagonal: librespot_metadata.track uses a module listed above it, which is the healthy direction.
21→4 librespot_metadata.track uses librespot_core.date✕
- Connections
- 1 pair of types, where a type in librespot_metadata.track uses a type in librespot_core.date.
- The types involved
librespot_metadata.track.Track→librespot_core.date.Date
- Direction
- librespot_metadata.track uses librespot_core.date, so a change to librespot_core.date can break librespot_metadata.track, while a change to librespot_metadata.track can't break librespot_core.date.
- Position
- Below the diagonal: librespot_metadata.track uses a module listed above it, which is the healthy direction.
21→5 librespot_metadata.track uses librespot_core.dealer.protocol✕
- Connections
- 1 pair of types, where a type in librespot_metadata.track uses a type in librespot_core.dealer.protocol.
- The types involved
librespot_metadata.track.Track→librespot_core.dealer.protocol.Message
- Direction
- librespot_metadata.track uses librespot_core.dealer.protocol, so a change to librespot_core.dealer.protocol can break librespot_metadata.track, while a change to librespot_metadata.track can't break librespot_core.dealer.protocol.
- Position
- Below the diagonal: librespot_metadata.track uses a module listed above it, which is the healthy direction.
21→7 librespot_metadata.track uses librespot_metadata.audio.file✕
- Connections
- 1 pair of types, where a type in librespot_metadata.track uses a type in librespot_metadata.audio.file.
- The types involved
librespot_metadata.track.Track→librespot_metadata.audio.file.AudioFiles
- Direction
- librespot_metadata.track uses librespot_metadata.audio.file, so a change to librespot_metadata.audio.file can break librespot_metadata.track, while a change to librespot_metadata.track can't break librespot_metadata.audio.file.
- Position
- Below the diagonal: librespot_metadata.track uses a module listed above it, which is the healthy direction.
21→8 librespot_metadata.track uses librespot_metadata.restriction✕
- Connections
- 1 pair of types, where a type in librespot_metadata.track uses a type in librespot_metadata.restriction.
- The types involved
librespot_metadata.track.Track→librespot_metadata.restriction.Restrictions
- Direction
- librespot_metadata.track uses librespot_metadata.restriction, so a change to librespot_metadata.restriction can break librespot_metadata.track, while a change to librespot_metadata.track can't break librespot_metadata.restriction.
- Position
- Below the diagonal: librespot_metadata.track uses a module listed above it, which is the healthy direction.
21→14 librespot_metadata.track uses librespot_metadata.availability✕
- Connections
- 1 pair of types, where a type in librespot_metadata.track uses a type in librespot_metadata.availability.
- The types involved
librespot_metadata.track.Track→librespot_metadata.availability.Availabilities
- Direction
- librespot_metadata.track uses librespot_metadata.availability, so a change to librespot_metadata.availability can break librespot_metadata.track, while a change to librespot_metadata.track can't break librespot_metadata.availability.
- Position
- Below the diagonal: librespot_metadata.track uses a module listed above it, which is the healthy direction.
21→24 librespot_metadata.track uses librespot_metadata.artist part of a loop✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.track uses a type in librespot_metadata.artist.
- The types involved
librespot_metadata.track.Track→librespot_metadata.artist.Artistslibrespot_metadata.track.Track→librespot_metadata.artist.ArtistsWithRole
- Direction
- librespot_metadata.track uses librespot_metadata.artist, so a change to librespot_metadata.artist can break librespot_metadata.track, while a change to librespot_metadata.track can't break librespot_metadata.artist.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→27 librespot_metadata.track uses librespot_metadata.album part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.track uses a type in librespot_metadata.album.
- The types involved
librespot_metadata.track.Track→librespot_metadata.album.Album
- Direction
- librespot_metadata.track uses librespot_metadata.album, so a change to librespot_metadata.album can break librespot_metadata.track, while a change to librespot_metadata.track can't break librespot_metadata.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→28 librespot_metadata.track uses librespot_core.spotify_uri part of a loop✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.track uses a type in librespot_core.spotify_uri.
- The types involved
librespot_metadata.track.Track→librespot_core.spotify_uri.SpotifyUrilibrespot_metadata.track.Tracks→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_metadata.track uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_metadata.track, while a change to librespot_metadata.track can't break librespot_core.spotify_uri.
- 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→32 librespot_metadata.track uses librespot_core.session part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.track uses a type in librespot_core.session.
- The types involved
librespot_metadata.track.Track→librespot_core.session.Session
- Direction
- librespot_metadata.track uses librespot_core.session, so a change to librespot_core.session can break librespot_metadata.track, while a change to librespot_metadata.track can't break librespot_core.session.
- 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.
22→9 librespot_playback.audio_backend uses librespot_playback.config✕
- Connections
- 2 pairs of types, where a type in librespot_playback.audio_backend uses a type in librespot_playback.config.
- The types involved
librespot_playback.audio_backend.Open→librespot_playback.config.AudioFormatlibrespot_playback.audio_backend.audio_backend$module→librespot_playback.config.AudioFormat
- Direction
- librespot_playback.audio_backend uses librespot_playback.config, so a change to librespot_playback.config can break librespot_playback.audio_backend, while a change to librespot_playback.audio_backend can't break librespot_playback.config.
- Position
- Below the diagonal: librespot_playback.audio_backend uses a module listed above it, which is the healthy direction.
22→10 librespot_playback.audio_backend uses librespot_playback.convert✕
- Connections
- 1 pair of types, where a type in librespot_playback.audio_backend uses a type in librespot_playback.convert.
- The types involved
librespot_playback.audio_backend.Sink→librespot_playback.convert.Converter
- Direction
- librespot_playback.audio_backend uses librespot_playback.convert, so a change to librespot_playback.convert can break librespot_playback.audio_backend, while a change to librespot_playback.audio_backend can't break librespot_playback.convert.
- Position
- Below the diagonal: librespot_playback.audio_backend uses a module listed above it, which is the healthy direction.
22→16 librespot_playback.audio_backend uses librespot_playback.decoder✕
- Connections
- 1 pair of types, where a type in librespot_playback.audio_backend uses a type in librespot_playback.decoder.
- The types involved
librespot_playback.audio_backend.Sink→librespot_playback.decoder.AudioPacket
- Direction
- librespot_playback.audio_backend uses librespot_playback.decoder, so a change to librespot_playback.decoder can break librespot_playback.audio_backend, while a change to librespot_playback.audio_backend can't break librespot_playback.decoder.
- Position
- Below the diagonal: librespot_playback.audio_backend uses a module listed above it, which is the healthy direction.
23→3 librespot_discovery uses librespot_core.config✕
- Connections
- 1 pair of types, where a type in librespot_discovery uses a type in librespot_core.config.
- The types involved
librespot_discovery.Builder→librespot_core.config.DeviceType
- Direction
- librespot_discovery uses librespot_core.config, so a change to librespot_core.config can break librespot_discovery, while a change to librespot_discovery can't break librespot_core.config.
- Position
- Below the diagonal: librespot_discovery uses a module listed above it, which is the healthy direction.
23→12 librespot_discovery uses librespot_core.dealer✕
- Connections
- 1 pair of types, where a type in librespot_discovery uses a type in librespot_core.dealer.
- The types involved
librespot_discovery.Discovery→librespot_core.dealer.Builder
- Direction
- librespot_discovery uses librespot_core.dealer, so a change to librespot_core.dealer can break librespot_discovery, while a change to librespot_discovery can't break librespot_core.dealer.
- Position
- Below the diagonal: librespot_discovery uses a module listed above it, which is the healthy direction.
23→18 librespot_discovery uses librespot_discovery.server✕
- Connections
- 2 pairs of types, where a type in librespot_discovery uses a type in librespot_discovery.server.
- The types involved
librespot_discovery.Builder→librespot_discovery.server.Configlibrespot_discovery.Discovery→librespot_discovery.server.DiscoveryServer
- Direction
- librespot_discovery uses librespot_discovery.server, so a change to librespot_discovery.server can break librespot_discovery, while a change to librespot_discovery can't break librespot_discovery.server.
- Position
- Below the diagonal: librespot_discovery uses a module listed above it, which is the healthy direction.
23→40 librespot_discovery uses librespot_core.error part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_discovery uses a type in librespot_core.error.
- The types involved
librespot_discovery.DiscoveryError→librespot_core.error.Error
- Direction
- librespot_discovery uses librespot_core.error, so a change to librespot_core.error can break librespot_discovery, while a change to librespot_discovery can't break librespot_core.error.
- 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→1 librespot_metadata.artist uses librespot_connect.state.metadata✕
- Connections
- 1 pair of types, where a type in librespot_metadata.artist uses a type in librespot_connect.state.metadata.
- The types involved
librespot_metadata.artist.Artist→librespot_connect.state.metadata.Metadata
- Direction
- librespot_metadata.artist uses librespot_connect.state.metadata, so a change to librespot_connect.state.metadata can break librespot_metadata.artist, while a change to librespot_metadata.artist can't break librespot_connect.state.metadata.
- Position
- Below the diagonal: librespot_metadata.artist uses a module listed above it, which is the healthy direction.
24→5 librespot_metadata.artist uses librespot_core.dealer.protocol✕
- Connections
- 1 pair of types, where a type in librespot_metadata.artist uses a type in librespot_core.dealer.protocol.
- The types involved
librespot_metadata.artist.Artist→librespot_core.dealer.protocol.Message
- Direction
- librespot_metadata.artist uses librespot_core.dealer.protocol, so a change to librespot_core.dealer.protocol can break librespot_metadata.artist, while a change to librespot_metadata.artist can't break librespot_core.dealer.protocol.
- Position
- Below the diagonal: librespot_metadata.artist uses a module listed above it, which is the healthy direction.
24→8 librespot_metadata.artist uses librespot_metadata.restriction✕
- Connections
- 1 pair of types, where a type in librespot_metadata.artist uses a type in librespot_metadata.restriction.
- The types involved
librespot_metadata.artist.Artist→librespot_metadata.restriction.Restrictions
- Direction
- librespot_metadata.artist uses librespot_metadata.restriction, so a change to librespot_metadata.restriction can break librespot_metadata.artist, while a change to librespot_metadata.artist can't break librespot_metadata.restriction.
- Position
- Below the diagonal: librespot_metadata.artist uses a module listed above it, which is the healthy direction.
24→14 librespot_metadata.artist uses librespot_metadata.availability✕
- Connections
- 1 pair of types, where a type in librespot_metadata.artist uses a type in librespot_metadata.availability.
- The types involved
librespot_metadata.artist.Artist→librespot_metadata.availability.Availabilities
- Direction
- librespot_metadata.artist uses librespot_metadata.availability, so a change to librespot_metadata.availability can break librespot_metadata.artist, while a change to librespot_metadata.artist can't break librespot_metadata.availability.
- Position
- Below the diagonal: librespot_metadata.artist uses a module listed above it, which is the healthy direction.
24→21 librespot_metadata.artist uses librespot_metadata.track✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.artist uses a type in librespot_metadata.track.
- The types involved
librespot_metadata.artist.CountryTopTracks→librespot_metadata.track.Trackslibrespot_metadata.artist.TopTracks→librespot_metadata.track.Tracks
- Direction
- librespot_metadata.artist uses librespot_metadata.track, so a change to librespot_metadata.track can break librespot_metadata.artist, while a change to librespot_metadata.artist can't break librespot_metadata.track.
- Position
- Below the diagonal: librespot_metadata.artist uses a module listed above it, which is the healthy direction.
24→27 librespot_metadata.artist uses librespot_metadata.album part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.artist uses a type in librespot_metadata.album.
- The types involved
librespot_metadata.artist.AlbumGroup→librespot_metadata.album.Albums
- Direction
- librespot_metadata.artist uses librespot_metadata.album, so a change to librespot_metadata.album can break librespot_metadata.artist, while a change to librespot_metadata.artist can't break librespot_metadata.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.
24→28 librespot_metadata.artist uses librespot_core.spotify_uri part of a loop✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.artist uses a type in librespot_core.spotify_uri.
- The types involved
librespot_metadata.artist.Artist→librespot_core.spotify_uri.SpotifyUrilibrespot_metadata.artist.ArtistWithRole→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_metadata.artist uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_metadata.artist, while a change to librespot_metadata.artist can't break librespot_core.spotify_uri.
- 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→29 librespot_metadata.artist uses librespot_metadata.image part of a loop✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.artist uses a type in librespot_metadata.image.
- The types involved
librespot_metadata.artist.Artist→librespot_metadata.image.Imageslibrespot_metadata.artist.Biography→librespot_metadata.image.Images
- Direction
- librespot_metadata.artist uses librespot_metadata.image, so a change to librespot_metadata.image can break librespot_metadata.artist, while a change to librespot_metadata.artist can't break librespot_metadata.image.
- 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→32 librespot_metadata.artist uses librespot_core.session part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.artist uses a type in librespot_core.session.
- The types involved
librespot_metadata.artist.Artist→librespot_core.session.Session
- Direction
- librespot_metadata.artist uses librespot_core.session, so a change to librespot_core.session can break librespot_metadata.artist, while a change to librespot_metadata.artist can't break librespot_core.session.
- 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.
25→1 librespot_metadata.playlist.list uses librespot_connect.state.metadata✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.list uses a type in librespot_connect.state.metadata.
- The types involved
librespot_metadata.playlist.list.Playlist→librespot_connect.state.metadata.Metadata
- Direction
- librespot_metadata.playlist.list uses librespot_connect.state.metadata, so a change to librespot_connect.state.metadata can break librespot_metadata.playlist.list, while a change to librespot_metadata.playlist.list can't break librespot_connect.state.metadata.
- Position
- Below the diagonal: librespot_metadata.playlist.list uses a module listed above it, which is the healthy direction.
25→4 librespot_metadata.playlist.list uses librespot_core.date✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.playlist.list uses a type in librespot_core.date.
- The types involved
librespot_metadata.playlist.list.Playlist→librespot_core.date.Datelibrespot_metadata.playlist.list.SelectedListContent→librespot_core.date.Date
- Direction
- librespot_metadata.playlist.list uses librespot_core.date, so a change to librespot_core.date can break librespot_metadata.playlist.list, while a change to librespot_metadata.playlist.list can't break librespot_core.date.
- Position
- Below the diagonal: librespot_metadata.playlist.list uses a module listed above it, which is the healthy direction.
25→5 librespot_metadata.playlist.list uses librespot_core.dealer.protocol✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.playlist.list uses a type in librespot_core.dealer.protocol.
- The types involved
librespot_metadata.playlist.list.Playlist→librespot_core.dealer.protocol.Messagelibrespot_metadata.playlist.list.SelectedListContent→librespot_core.dealer.protocol.Message
- Direction
- librespot_metadata.playlist.list uses librespot_core.dealer.protocol, so a change to librespot_core.dealer.protocol can break librespot_metadata.playlist.list, while a change to librespot_metadata.playlist.list can't break librespot_core.dealer.protocol.
- Position
- Below the diagonal: librespot_metadata.playlist.list uses a module listed above it, which is the healthy direction.
25→13 librespot_metadata.playlist.list uses librespot_core.spotify_id✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.list uses a type in librespot_core.spotify_id.
- The types involved
librespot_metadata.playlist.list.Playlists→librespot_core.spotify_id.SpotifyId
- Direction
- librespot_metadata.playlist.list uses librespot_core.spotify_id, so a change to librespot_core.spotify_id can break librespot_metadata.playlist.list, while a change to librespot_metadata.playlist.list can't break librespot_core.spotify_id.
- Position
- Below the diagonal: librespot_metadata.playlist.list uses a module listed above it, which is the healthy direction.
25→15 librespot_metadata.playlist.list uses librespot_metadata.playlist.attribute✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.playlist.list uses a type in librespot_metadata.playlist.attribute.
- The types involved
librespot_metadata.playlist.list.Playlist→librespot_metadata.playlist.attribute.PlaylistAttributeslibrespot_metadata.playlist.list.SelectedListContent→librespot_metadata.playlist.attribute.PlaylistAttributes
- Direction
- librespot_metadata.playlist.list uses librespot_metadata.playlist.attribute, so a change to librespot_metadata.playlist.attribute can break librespot_metadata.playlist.list, while a change to librespot_metadata.playlist.list can't break librespot_metadata.playlist.attribute.
- Position
- Below the diagonal: librespot_metadata.playlist.list uses a module listed above it, which is the healthy direction.
25→20 librespot_metadata.playlist.list uses librespot_metadata.playlist.item✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.playlist.list uses a type in librespot_metadata.playlist.item.
- The types involved
librespot_metadata.playlist.list.Playlist→librespot_metadata.playlist.item.PlaylistItemListlibrespot_metadata.playlist.list.SelectedListContent→librespot_metadata.playlist.item.PlaylistItemList
- Direction
- librespot_metadata.playlist.list uses librespot_metadata.playlist.item, so a change to librespot_metadata.playlist.item can break librespot_metadata.playlist.list, while a change to librespot_metadata.playlist.list can't break librespot_metadata.playlist.item.
- Position
- Below the diagonal: librespot_metadata.playlist.list uses a module listed above it, which is the healthy direction.
25→28 librespot_metadata.playlist.list uses librespot_core.spotify_uri part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.list uses a type in librespot_core.spotify_uri.
- The types involved
librespot_metadata.playlist.list.Playlist→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_metadata.playlist.list uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_metadata.playlist.list, while a change to librespot_metadata.playlist.list can't break librespot_core.spotify_uri.
- 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.
25→32 librespot_metadata.playlist.list uses librespot_core.session part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.list uses a type in librespot_core.session.
- The types involved
librespot_metadata.playlist.list.Playlist→librespot_core.session.Session
- Direction
- librespot_metadata.playlist.list uses librespot_core.session, so a change to librespot_core.session can break librespot_metadata.playlist.list, while a change to librespot_metadata.playlist.list can't break librespot_core.session.
- 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→1 librespot_metadata.show uses librespot_connect.state.metadata✕
- Connections
- 1 pair of types, where a type in librespot_metadata.show uses a type in librespot_connect.state.metadata.
- The types involved
librespot_metadata.show.Show→librespot_connect.state.metadata.Metadata
- Direction
- librespot_metadata.show uses librespot_connect.state.metadata, so a change to librespot_connect.state.metadata can break librespot_metadata.show, while a change to librespot_metadata.show can't break librespot_connect.state.metadata.
- Position
- Below the diagonal: librespot_metadata.show uses a module listed above it, which is the healthy direction.
26→5 librespot_metadata.show uses librespot_core.dealer.protocol✕
- Connections
- 1 pair of types, where a type in librespot_metadata.show uses a type in librespot_core.dealer.protocol.
- The types involved
librespot_metadata.show.Show→librespot_core.dealer.protocol.Message
- Direction
- librespot_metadata.show uses librespot_core.dealer.protocol, so a change to librespot_core.dealer.protocol can break librespot_metadata.show, while a change to librespot_metadata.show can't break librespot_core.dealer.protocol.
- Position
- Below the diagonal: librespot_metadata.show uses a module listed above it, which is the healthy direction.
26→8 librespot_metadata.show uses librespot_metadata.restriction✕
- Connections
- 1 pair of types, where a type in librespot_metadata.show uses a type in librespot_metadata.restriction.
- The types involved
librespot_metadata.show.Show→librespot_metadata.restriction.Restrictions
- Direction
- librespot_metadata.show uses librespot_metadata.restriction, so a change to librespot_metadata.restriction can break librespot_metadata.show, while a change to librespot_metadata.show can't break librespot_metadata.restriction.
- Position
- Below the diagonal: librespot_metadata.show uses a module listed above it, which is the healthy direction.
26→14 librespot_metadata.show uses librespot_metadata.availability✕
- Connections
- 1 pair of types, where a type in librespot_metadata.show uses a type in librespot_metadata.availability.
- The types involved
librespot_metadata.show.Show→librespot_metadata.availability.Availabilities
- Direction
- librespot_metadata.show uses librespot_metadata.availability, so a change to librespot_metadata.availability can break librespot_metadata.show, while a change to librespot_metadata.show can't break librespot_metadata.availability.
- Position
- Below the diagonal: librespot_metadata.show uses a module listed above it, which is the healthy direction.
26→19 librespot_metadata.show uses librespot_metadata.episode✕
- Connections
- 1 pair of types, where a type in librespot_metadata.show uses a type in librespot_metadata.episode.
- The types involved
librespot_metadata.show.Show→librespot_metadata.episode.Episodes
- Direction
- librespot_metadata.show uses librespot_metadata.episode, so a change to librespot_metadata.episode can break librespot_metadata.show, while a change to librespot_metadata.show can't break librespot_metadata.episode.
- Position
- Below the diagonal: librespot_metadata.show uses a module listed above it, which is the healthy direction.
26→28 librespot_metadata.show uses librespot_core.spotify_uri part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.show uses a type in librespot_core.spotify_uri.
- The types involved
librespot_metadata.show.Show→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_metadata.show uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_metadata.show, while a change to librespot_metadata.show can't break librespot_core.spotify_uri.
- 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→29 librespot_metadata.show uses librespot_metadata.image part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.show uses a type in librespot_metadata.image.
- The types involved
librespot_metadata.show.Show→librespot_metadata.image.Images
- Direction
- librespot_metadata.show uses librespot_metadata.image, so a change to librespot_metadata.image can break librespot_metadata.show, while a change to librespot_metadata.show can't break librespot_metadata.image.
- 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→32 librespot_metadata.show uses librespot_core.session part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.show uses a type in librespot_core.session.
- The types involved
librespot_metadata.show.Show→librespot_core.session.Session
- Direction
- librespot_metadata.show uses librespot_core.session, so a change to librespot_core.session can break librespot_metadata.show, while a change to librespot_metadata.show can't break librespot_core.session.
- 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.
27→1 librespot_metadata.album uses librespot_connect.state.metadata✕
- Connections
- 1 pair of types, where a type in librespot_metadata.album uses a type in librespot_connect.state.metadata.
- The types involved
librespot_metadata.album.Album→librespot_connect.state.metadata.Metadata
- Direction
- librespot_metadata.album uses librespot_connect.state.metadata, so a change to librespot_connect.state.metadata can break librespot_metadata.album, while a change to librespot_metadata.album can't break librespot_connect.state.metadata.
- Position
- Below the diagonal: librespot_metadata.album uses a module listed above it, which is the healthy direction.
27→4 librespot_metadata.album uses librespot_core.date✕
- Connections
- 1 pair of types, where a type in librespot_metadata.album uses a type in librespot_core.date.
- The types involved
librespot_metadata.album.Album→librespot_core.date.Date
- Direction
- librespot_metadata.album uses librespot_core.date, so a change to librespot_core.date can break librespot_metadata.album, while a change to librespot_metadata.album can't break librespot_core.date.
- Position
- Below the diagonal: librespot_metadata.album uses a module listed above it, which is the healthy direction.
27→5 librespot_metadata.album uses librespot_core.dealer.protocol✕
- Connections
- 1 pair of types, where a type in librespot_metadata.album uses a type in librespot_core.dealer.protocol.
- The types involved
librespot_metadata.album.Album→librespot_core.dealer.protocol.Message
- Direction
- librespot_metadata.album uses librespot_core.dealer.protocol, so a change to librespot_core.dealer.protocol can break librespot_metadata.album, while a change to librespot_metadata.album can't break librespot_core.dealer.protocol.
- Position
- Below the diagonal: librespot_metadata.album uses a module listed above it, which is the healthy direction.
27→8 librespot_metadata.album uses librespot_metadata.restriction✕
- Connections
- 1 pair of types, where a type in librespot_metadata.album uses a type in librespot_metadata.restriction.
- The types involved
librespot_metadata.album.Album→librespot_metadata.restriction.Restrictions
- Direction
- librespot_metadata.album uses librespot_metadata.restriction, so a change to librespot_metadata.restriction can break librespot_metadata.album, while a change to librespot_metadata.album can't break librespot_metadata.restriction.
- Position
- Below the diagonal: librespot_metadata.album uses a module listed above it, which is the healthy direction.
27→14 librespot_metadata.album uses librespot_metadata.availability✕
- Connections
- 1 pair of types, where a type in librespot_metadata.album uses a type in librespot_metadata.availability.
- The types involved
librespot_metadata.album.Album→librespot_metadata.availability.Availabilities
- Direction
- librespot_metadata.album uses librespot_metadata.availability, so a change to librespot_metadata.availability can break librespot_metadata.album, while a change to librespot_metadata.album can't break librespot_metadata.availability.
- Position
- Below the diagonal: librespot_metadata.album uses a module listed above it, which is the healthy direction.
27→21 librespot_metadata.album uses librespot_metadata.track✕
- Connections
- 1 pair of types, where a type in librespot_metadata.album uses a type in librespot_metadata.track.
- The types involved
librespot_metadata.album.Disc→librespot_metadata.track.Tracks
- Direction
- librespot_metadata.album uses librespot_metadata.track, so a change to librespot_metadata.track can break librespot_metadata.album, while a change to librespot_metadata.album can't break librespot_metadata.track.
- Position
- Below the diagonal: librespot_metadata.album uses a module listed above it, which is the healthy direction.
27→24 librespot_metadata.album uses librespot_metadata.artist✕
- Connections
- 1 pair of types, where a type in librespot_metadata.album uses a type in librespot_metadata.artist.
- The types involved
librespot_metadata.album.Album→librespot_metadata.artist.Artists
- Direction
- librespot_metadata.album uses librespot_metadata.artist, so a change to librespot_metadata.artist can break librespot_metadata.album, while a change to librespot_metadata.album can't break librespot_metadata.artist.
- Position
- Below the diagonal: librespot_metadata.album uses a module listed above it, which is the healthy direction.
27→28 librespot_metadata.album uses librespot_core.spotify_uri part of a loop✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.album uses a type in librespot_core.spotify_uri.
- The types involved
librespot_metadata.album.Album→librespot_core.spotify_uri.SpotifyUrilibrespot_metadata.album.Albums→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_metadata.album uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_metadata.album, while a change to librespot_metadata.album can't break librespot_core.spotify_uri.
- 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.
27→29 librespot_metadata.album uses librespot_metadata.image part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.album uses a type in librespot_metadata.image.
- The types involved
librespot_metadata.album.Album→librespot_metadata.image.Images
- Direction
- librespot_metadata.album uses librespot_metadata.image, so a change to librespot_metadata.image can break librespot_metadata.album, while a change to librespot_metadata.album can't break librespot_metadata.image.
- 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.
27→32 librespot_metadata.album uses librespot_core.session part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.album uses a type in librespot_core.session.
- The types involved
librespot_metadata.album.Album→librespot_core.session.Session
- Direction
- librespot_metadata.album uses librespot_core.session, so a change to librespot_core.session can break librespot_metadata.album, while a change to librespot_metadata.album can't break librespot_core.session.
- 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.
28→19 librespot_core.spotify_uri uses librespot_metadata.episode✕
- Connections
- 1 pair of types, where a type in librespot_core.spotify_uri uses a type in librespot_metadata.episode.
- The types involved
librespot_core.spotify_uri.SpotifyUri→librespot_metadata.episode.Episode
- Direction
- librespot_core.spotify_uri uses librespot_metadata.episode, so a change to librespot_metadata.episode can break librespot_core.spotify_uri, while a change to librespot_core.spotify_uri can't break librespot_metadata.episode.
- Position
- Below the diagonal: librespot_core.spotify_uri uses a module listed above it, which is the healthy direction.
28→21 librespot_core.spotify_uri uses librespot_metadata.track✕
- Connections
- 1 pair of types, where a type in librespot_core.spotify_uri uses a type in librespot_metadata.track.
- The types involved
librespot_core.spotify_uri.SpotifyUri→librespot_metadata.track.Track
- Direction
- librespot_core.spotify_uri uses librespot_metadata.track, so a change to librespot_metadata.track can break librespot_core.spotify_uri, while a change to librespot_core.spotify_uri can't break librespot_metadata.track.
- Position
- Below the diagonal: librespot_core.spotify_uri uses a module listed above it, which is the healthy direction.
28→24 librespot_core.spotify_uri uses librespot_metadata.artist✕
- Connections
- 2 pairs of types, where a type in librespot_core.spotify_uri uses a type in librespot_metadata.artist.
- The types involved
librespot_core.spotify_uri.SpotifyUri→librespot_metadata.artist.Artistlibrespot_core.spotify_uri.SpotifyUri→librespot_metadata.artist.ArtistWithRole
- Direction
- librespot_core.spotify_uri uses librespot_metadata.artist, so a change to librespot_metadata.artist can break librespot_core.spotify_uri, while a change to librespot_core.spotify_uri can't break librespot_metadata.artist.
- Position
- Below the diagonal: librespot_core.spotify_uri uses a module listed above it, which is the healthy direction.
28→25 librespot_core.spotify_uri uses librespot_metadata.playlist.list✕
- Connections
- 1 pair of types, where a type in librespot_core.spotify_uri uses a type in librespot_metadata.playlist.list.
- The types involved
librespot_core.spotify_uri.SpotifyUri→librespot_metadata.playlist.list.SelectedListContent
- Direction
- librespot_core.spotify_uri uses librespot_metadata.playlist.list, so a change to librespot_metadata.playlist.list can break librespot_core.spotify_uri, while a change to librespot_core.spotify_uri can't break librespot_metadata.playlist.list.
- Position
- Below the diagonal: librespot_core.spotify_uri uses a module listed above it, which is the healthy direction.
28→26 librespot_core.spotify_uri uses librespot_metadata.show✕
- Connections
- 1 pair of types, where a type in librespot_core.spotify_uri uses a type in librespot_metadata.show.
- The types involved
librespot_core.spotify_uri.SpotifyUri→librespot_metadata.show.Show
- Direction
- librespot_core.spotify_uri uses librespot_metadata.show, so a change to librespot_metadata.show can break librespot_core.spotify_uri, while a change to librespot_core.spotify_uri can't break librespot_metadata.show.
- Position
- Below the diagonal: librespot_core.spotify_uri uses a module listed above it, which is the healthy direction.
28→27 librespot_core.spotify_uri uses librespot_metadata.album✕
- Connections
- 1 pair of types, where a type in librespot_core.spotify_uri uses a type in librespot_metadata.album.
- The types involved
librespot_core.spotify_uri.SpotifyUri→librespot_metadata.album.Album
- Direction
- librespot_core.spotify_uri uses librespot_metadata.album, so a change to librespot_metadata.album can break librespot_core.spotify_uri, while a change to librespot_core.spotify_uri can't break librespot_metadata.album.
- Position
- Below the diagonal: librespot_core.spotify_uri uses a module listed above it, which is the healthy direction.
28→29 librespot_core.spotify_uri uses librespot_metadata.image part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_core.spotify_uri uses a type in librespot_metadata.image.
- The types involved
librespot_core.spotify_uri.SpotifyUri→librespot_metadata.image.TranscodedPicture
- Direction
- librespot_core.spotify_uri uses librespot_metadata.image, so a change to librespot_metadata.image can break librespot_core.spotify_uri, while a change to librespot_core.spotify_uri can't break librespot_metadata.image.
- 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.
29→28 librespot_metadata.image uses librespot_core.spotify_uri✕
- Connections
- 1 pair of types, where a type in librespot_metadata.image uses a type in librespot_core.spotify_uri.
- The types involved
librespot_metadata.image.TranscodedPicture→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_metadata.image uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_metadata.image, while a change to librespot_metadata.image can't break librespot_core.spotify_uri.
- Position
- Below the diagonal: librespot_metadata.image uses a module listed above it, which is the healthy direction.
29→30 librespot_metadata.image uses librespot_core.file_id part of a loop✕
- Connections
- 1 pair of types, where a type in librespot_metadata.image uses a type in librespot_core.file_id.
- The types involved
librespot_metadata.image.Image→librespot_core.file_id.FileId
- Direction
- librespot_metadata.image uses librespot_core.file_id, so a change to librespot_core.file_id can break librespot_metadata.image, while a change to librespot_metadata.image can't break librespot_core.file_id.
- 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.
30→17 librespot_core.file_id uses librespot_audio.fetch✕
- Connections
- 1 pair of types, where a type in librespot_core.file_id uses a type in librespot_audio.fetch.
- The types involved
librespot_core.file_id.FileId→librespot_audio.fetch.AudioFile
- Direction
- librespot_core.file_id uses librespot_audio.fetch, so a change to librespot_audio.fetch can break librespot_core.file_id, while a change to librespot_core.file_id can't break librespot_audio.fetch.
- Position
- Below the diagonal: librespot_core.file_id uses a module listed above it, which is the healthy direction.
30→29 librespot_core.file_id uses librespot_metadata.image✕
- Connections
- 1 pair of types, where a type in librespot_core.file_id uses a type in librespot_metadata.image.
- The types involved
librespot_core.file_id.FileId→librespot_metadata.image.Image
- Direction
- librespot_core.file_id uses librespot_metadata.image, so a change to librespot_metadata.image can break librespot_core.file_id, while a change to librespot_core.file_id can't break librespot_metadata.image.
- Position
- Below the diagonal: librespot_core.file_id uses a module listed above it, which is the healthy direction.
31→2 librespot_core.cache uses librespot_core.authentication✕
- Connections
- 1 pair of types, where a type in librespot_core.cache uses a type in librespot_core.authentication.
- The types involved
librespot_core.cache.Cache→librespot_core.authentication.Credentials
- Direction
- librespot_core.cache uses librespot_core.authentication, so a change to librespot_core.authentication can break librespot_core.cache, while a change to librespot_core.cache can't break librespot_core.authentication.
- Position
- Below the diagonal: librespot_core.cache uses a module listed above it, which is the healthy direction.
31→30 librespot_core.cache uses librespot_core.file_id✕
- Connections
- 1 pair of types, where a type in librespot_core.cache uses a type in librespot_core.file_id.
- The types involved
librespot_core.cache.Cache→librespot_core.file_id.FileId
- Direction
- librespot_core.cache uses librespot_core.file_id, so a change to librespot_core.file_id can break librespot_core.cache, while a change to librespot_core.cache can't break librespot_core.file_id.
- Position
- Below the diagonal: librespot_core.cache uses a module listed above it, which is the healthy direction.
32→2 librespot_core.session uses librespot_core.authentication✕
- Connections
- 1 pair of types, where a type in librespot_core.session uses a type in librespot_core.authentication.
- The types involved
librespot_core.session.Session→librespot_core.authentication.Credentials
- Direction
- librespot_core.session uses librespot_core.authentication, so a change to librespot_core.authentication can break librespot_core.session, while a change to librespot_core.session can't break librespot_core.authentication.
- Position
- Below the diagonal: librespot_core.session uses a module listed above it, which is the healthy direction.
32→3 librespot_core.session uses librespot_core.config✕
- Connections
- 2 pairs of types, where a type in librespot_core.session uses a type in librespot_core.config.
- The types involved
librespot_core.session.Session→librespot_core.config.SessionConfiglibrespot_core.session.SessionInternal→librespot_core.config.SessionConfig
- Direction
- librespot_core.session uses librespot_core.config, so a change to librespot_core.config can break librespot_core.session, while a change to librespot_core.session can't break librespot_core.config.
- Position
- Below the diagonal: librespot_core.session uses a module listed above it, which is the healthy direction.
32→31 librespot_core.session uses librespot_core.cache✕
- Connections
- 2 pairs of types, where a type in librespot_core.session uses a type in librespot_core.cache.
- The types involved
librespot_core.session.Session→librespot_core.cache.Cachelibrespot_core.session.SessionInternal→librespot_core.cache.Cache
- Direction
- librespot_core.session uses librespot_core.cache, so a change to librespot_core.cache can break librespot_core.session, while a change to librespot_core.session can't break librespot_core.cache.
- Position
- Below the diagonal: librespot_core.session uses a module listed above it, which is the healthy direction.
33→7 librespot_metadata.audio.item uses librespot_metadata.audio.file✕
- Connections
- 1 pair of types, where a type in librespot_metadata.audio.item uses a type in librespot_metadata.audio.file.
- The types involved
librespot_metadata.audio.item.AudioItem→librespot_metadata.audio.file.AudioFiles
- Direction
- librespot_metadata.audio.item uses librespot_metadata.audio.file, so a change to librespot_metadata.audio.file can break librespot_metadata.audio.item, while a change to librespot_metadata.audio.item can't break librespot_metadata.audio.file.
- Position
- Below the diagonal: librespot_metadata.audio.item uses a module listed above it, which is the healthy direction.
33→8 librespot_metadata.audio.item uses librespot_metadata.restriction✕
- Connections
- 1 pair of types, where a type in librespot_metadata.audio.item uses a type in librespot_metadata.restriction.
- The types involved
librespot_metadata.audio.item.item$module→librespot_metadata.restriction.Restrictions
- Direction
- librespot_metadata.audio.item uses librespot_metadata.restriction, so a change to librespot_metadata.restriction can break librespot_metadata.audio.item, while a change to librespot_metadata.audio.item can't break librespot_metadata.restriction.
- Position
- Below the diagonal: librespot_metadata.audio.item uses a module listed above it, which is the healthy direction.
33→14 librespot_metadata.audio.item uses librespot_metadata.availability✕
- Connections
- 1 pair of types, where a type in librespot_metadata.audio.item uses a type in librespot_metadata.availability.
- The types involved
librespot_metadata.audio.item.item$module→librespot_metadata.availability.Availabilities
- Direction
- librespot_metadata.audio.item uses librespot_metadata.availability, so a change to librespot_metadata.availability can break librespot_metadata.audio.item, while a change to librespot_metadata.audio.item can't break librespot_metadata.availability.
- Position
- Below the diagonal: librespot_metadata.audio.item uses a module listed above it, which is the healthy direction.
33→21 librespot_metadata.audio.item uses librespot_metadata.track✕
- Connections
- 1 pair of types, where a type in librespot_metadata.audio.item uses a type in librespot_metadata.track.
- The types involved
librespot_metadata.audio.item.AudioItem→librespot_metadata.track.Tracks
- Direction
- librespot_metadata.audio.item uses librespot_metadata.track, so a change to librespot_metadata.track can break librespot_metadata.audio.item, while a change to librespot_metadata.audio.item can't break librespot_metadata.track.
- Position
- Below the diagonal: librespot_metadata.audio.item uses a module listed above it, which is the healthy direction.
33→28 librespot_metadata.audio.item uses librespot_core.spotify_uri✕
- Connections
- 1 pair of types, where a type in librespot_metadata.audio.item uses a type in librespot_core.spotify_uri.
- The types involved
librespot_metadata.audio.item.AudioItem→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_metadata.audio.item uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_metadata.audio.item, while a change to librespot_metadata.audio.item can't break librespot_core.spotify_uri.
- Position
- Below the diagonal: librespot_metadata.audio.item uses a module listed above it, which is the healthy direction.
33→29 librespot_metadata.audio.item uses librespot_metadata.image✕
- Connections
- 1 pair of types, where a type in librespot_metadata.audio.item uses a type in librespot_metadata.image.
- The types involved
librespot_metadata.audio.item.item$module→librespot_metadata.image.Images
- Direction
- librespot_metadata.audio.item uses librespot_metadata.image, so a change to librespot_metadata.image can break librespot_metadata.audio.item, while a change to librespot_metadata.audio.item can't break librespot_metadata.image.
- Position
- Below the diagonal: librespot_metadata.audio.item uses a module listed above it, which is the healthy direction.
33→32 librespot_metadata.audio.item uses librespot_core.session✕
- Connections
- 2 pairs of types, where a type in librespot_metadata.audio.item uses a type in librespot_core.session.
- The types involved
librespot_metadata.audio.item.AudioItem→librespot_core.session.Sessionlibrespot_metadata.audio.item.item$module→librespot_core.session.UserData
- Direction
- librespot_metadata.audio.item uses librespot_core.session, so a change to librespot_core.session can break librespot_metadata.audio.item, while a change to librespot_metadata.audio.item can't break librespot_core.session.
- Position
- Below the diagonal: librespot_metadata.audio.item uses a module listed above it, which is the healthy direction.
34→1 librespot_metadata.playlist.annotation uses librespot_connect.state.metadata✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.annotation uses a type in librespot_connect.state.metadata.
- The types involved
librespot_metadata.playlist.annotation.PlaylistAnnotation→librespot_connect.state.metadata.Metadata
- Direction
- librespot_metadata.playlist.annotation uses librespot_connect.state.metadata, so a change to librespot_connect.state.metadata can break librespot_metadata.playlist.annotation, while a change to librespot_metadata.playlist.annotation can't break librespot_connect.state.metadata.
- Position
- Below the diagonal: librespot_metadata.playlist.annotation uses a module listed above it, which is the healthy direction.
34→5 librespot_metadata.playlist.annotation uses librespot_core.dealer.protocol✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.annotation uses a type in librespot_core.dealer.protocol.
- The types involved
librespot_metadata.playlist.annotation.PlaylistAnnotation→librespot_core.dealer.protocol.Message
- Direction
- librespot_metadata.playlist.annotation uses librespot_core.dealer.protocol, so a change to librespot_core.dealer.protocol can break librespot_metadata.playlist.annotation, while a change to librespot_metadata.playlist.annotation can't break librespot_core.dealer.protocol.
- Position
- Below the diagonal: librespot_metadata.playlist.annotation uses a module listed above it, which is the healthy direction.
34→13 librespot_metadata.playlist.annotation uses librespot_core.spotify_id✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.annotation uses a type in librespot_core.spotify_id.
- The types involved
librespot_metadata.playlist.annotation.PlaylistAnnotation→librespot_core.spotify_id.SpotifyId
- Direction
- librespot_metadata.playlist.annotation uses librespot_core.spotify_id, so a change to librespot_core.spotify_id can break librespot_metadata.playlist.annotation, while a change to librespot_metadata.playlist.annotation can't break librespot_core.spotify_id.
- Position
- Below the diagonal: librespot_metadata.playlist.annotation uses a module listed above it, which is the healthy direction.
34→28 librespot_metadata.playlist.annotation uses librespot_core.spotify_uri✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.annotation uses a type in librespot_core.spotify_uri.
- The types involved
librespot_metadata.playlist.annotation.PlaylistAnnotation→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_metadata.playlist.annotation uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_metadata.playlist.annotation, while a change to librespot_metadata.playlist.annotation can't break librespot_core.spotify_uri.
- Position
- Below the diagonal: librespot_metadata.playlist.annotation uses a module listed above it, which is the healthy direction.
34→29 librespot_metadata.playlist.annotation uses librespot_metadata.image✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.annotation uses a type in librespot_metadata.image.
- The types involved
librespot_metadata.playlist.annotation.PlaylistAnnotation→librespot_metadata.image.TranscodedPictures
- Direction
- librespot_metadata.playlist.annotation uses librespot_metadata.image, so a change to librespot_metadata.image can break librespot_metadata.playlist.annotation, while a change to librespot_metadata.playlist.annotation can't break librespot_metadata.image.
- Position
- Below the diagonal: librespot_metadata.playlist.annotation uses a module listed above it, which is the healthy direction.
34→32 librespot_metadata.playlist.annotation uses librespot_core.session✕
- Connections
- 1 pair of types, where a type in librespot_metadata.playlist.annotation uses a type in librespot_core.session.
- The types involved
librespot_metadata.playlist.annotation.PlaylistAnnotation→librespot_core.session.Session
- Direction
- librespot_metadata.playlist.annotation uses librespot_core.session, so a change to librespot_core.session can break librespot_metadata.playlist.annotation, while a change to librespot_metadata.playlist.annotation can't break librespot_core.session.
- Position
- Below the diagonal: librespot_metadata.playlist.annotation uses a module listed above it, which is the healthy direction.
35→7 librespot_playback.player uses librespot_metadata.audio.file✕
- Connections
- 1 pair of types, where a type in librespot_playback.player uses a type in librespot_metadata.audio.file.
- The types involved
librespot_playback.player.PlayerTrackLoader→librespot_metadata.audio.file.AudioFileFormat
- Direction
- librespot_playback.player uses librespot_metadata.audio.file, so a change to librespot_metadata.audio.file can break librespot_playback.player, while a change to librespot_playback.player can't break librespot_metadata.audio.file.
- Position
- Below the diagonal: librespot_playback.player uses a module listed above it, which is the healthy direction.
35→9 librespot_playback.player uses librespot_playback.config✕
- Connections
- 4 pairs of types, where a type in librespot_playback.player uses a type in librespot_playback.config.
- The types involved
librespot_playback.player.NormalisationData→librespot_playback.config.PlayerConfiglibrespot_playback.player.Player→librespot_playback.config.PlayerConfiglibrespot_playback.player.PlayerInternal→librespot_playback.config.PlayerConfiglibrespot_playback.player.PlayerTrackLoader→librespot_playback.config.PlayerConfig
- Direction
- librespot_playback.player uses librespot_playback.config, so a change to librespot_playback.config can break librespot_playback.player, while a change to librespot_playback.player can't break librespot_playback.config.
- Position
- Below the diagonal: librespot_playback.player uses a module listed above it, which is the healthy direction.
35→10 librespot_playback.player uses librespot_playback.convert✕
- Connections
- 1 pair of types, where a type in librespot_playback.player uses a type in librespot_playback.convert.
- The types involved
librespot_playback.player.PlayerInternal→librespot_playback.convert.Converter
- Direction
- librespot_playback.player uses librespot_playback.convert, so a change to librespot_playback.convert can break librespot_playback.player, while a change to librespot_playback.player can't break librespot_playback.convert.
- Position
- Below the diagonal: librespot_playback.player uses a module listed above it, which is the healthy direction.
35→17 librespot_playback.player uses librespot_audio.fetch✕
- Connections
- 1 pair of types, where a type in librespot_playback.player uses a type in librespot_audio.fetch.
- The types involved
librespot_playback.player.PlayerLoadedTrackData→librespot_audio.fetch.StreamLoaderController
- Direction
- librespot_playback.player uses librespot_audio.fetch, so a change to librespot_audio.fetch can break librespot_playback.player, while a change to librespot_playback.player can't break librespot_audio.fetch.
- Position
- Below the diagonal: librespot_playback.player uses a module listed above it, which is the healthy direction.
35→28 librespot_playback.player uses librespot_core.spotify_uri✕
- Connections
- 3 pairs of types, where a type in librespot_playback.player uses a type in librespot_core.spotify_uri.
- The types involved
librespot_playback.player.Player→librespot_core.spotify_uri.SpotifyUrilibrespot_playback.player.PlayerInternal→librespot_core.spotify_uri.SpotifyUrilibrespot_playback.player.PlayerTrackLoader→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_playback.player uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_playback.player, while a change to librespot_playback.player can't break librespot_core.spotify_uri.
- Position
- Below the diagonal: librespot_playback.player uses a module listed above it, which is the healthy direction.
35→32 librespot_playback.player uses librespot_core.session✕
- Connections
- 3 pairs of types, where a type in librespot_playback.player uses a type in librespot_core.session.
- The types involved
librespot_playback.player.Player→librespot_core.session.Sessionlibrespot_playback.player.PlayerInternal→librespot_core.session.Sessionlibrespot_playback.player.PlayerTrackLoader→librespot_core.session.Session
- Direction
- librespot_playback.player uses librespot_core.session, so a change to librespot_core.session can break librespot_playback.player, while a change to librespot_playback.player can't break librespot_core.session.
- Position
- Below the diagonal: librespot_playback.player uses a module listed above it, which is the healthy direction.
35→33 librespot_playback.player uses librespot_metadata.audio.item✕
- Connections
- 2 pairs of types, where a type in librespot_playback.player uses a type in librespot_metadata.audio.item.
- The types involved
librespot_playback.player.PlayerLoadedTrackData→librespot_metadata.audio.item.AudioItemlibrespot_playback.player.PlayerTrackLoader→librespot_metadata.audio.item.AudioItem
- Direction
- librespot_playback.player uses librespot_metadata.audio.item, so a change to librespot_metadata.audio.item can break librespot_playback.player, while a change to librespot_playback.player can't break librespot_metadata.audio.item.
- Position
- Below the diagonal: librespot_playback.player uses a module listed above it, which is the healthy direction.
36→3 librespot_connect.state uses librespot_core.config✕
- Connections
- 1 pair of types, where a type in librespot_connect.state uses a type in librespot_core.config.
- The types involved
librespot_connect.state.ConnectConfig→librespot_core.config.DeviceType
- Direction
- librespot_connect.state uses librespot_core.config, so a change to librespot_core.config can break librespot_connect.state, while a change to librespot_connect.state can't break librespot_core.config.
- Position
- Below the diagonal: librespot_connect.state uses a module listed above it, which is the healthy direction.
36→6 librespot_connect.state uses librespot_core.dealer.protocol.request✕
- Connections
- 2 pairs of types, where a type in librespot_connect.state uses a type in librespot_core.dealer.protocol.request.
- The types involved
librespot_connect.state.ConnectState→librespot_core.dealer.protocol.request.Requestlibrespot_connect.state.ConnectState→librespot_core.dealer.protocol.request.SetQueueCommand
- Direction
- librespot_connect.state uses librespot_core.dealer.protocol.request, so a change to librespot_core.dealer.protocol.request can break librespot_connect.state, while a change to librespot_connect.state can't break librespot_core.dealer.protocol.request.
- Position
- Below the diagonal: librespot_connect.state uses a module listed above it, which is the healthy direction.
36→8 librespot_connect.state uses librespot_metadata.restriction✕
- Connections
- 1 pair of types, where a type in librespot_connect.state uses a type in librespot_metadata.restriction.
- The types involved
librespot_connect.state.ConnectState→librespot_metadata.restriction.Restrictions
- Direction
- librespot_connect.state uses librespot_metadata.restriction, so a change to librespot_metadata.restriction can break librespot_connect.state, while a change to librespot_connect.state can't break librespot_metadata.restriction.
- Position
- Below the diagonal: librespot_connect.state uses a module listed above it, which is the healthy direction.
36→11 librespot_connect.state uses librespot_connect.state.context✕
- Connections
- 3 pairs of types, where a type in librespot_connect.state uses a type in librespot_connect.state.context.
- The types involved
librespot_connect.state.ConnectState→librespot_connect.state.context.ContextTypelibrespot_connect.state.ConnectState→librespot_connect.state.context.ResetContextlibrespot_connect.state.ConnectState→librespot_connect.state.context.StateContext
- Direction
- librespot_connect.state uses librespot_connect.state.context, so a change to librespot_connect.state.context can break librespot_connect.state, while a change to librespot_connect.state can't break librespot_connect.state.context.
- Position
- Below the diagonal: librespot_connect.state uses a module listed above it, which is the healthy direction.
36→28 librespot_connect.state uses librespot_core.spotify_uri✕
- Connections
- 1 pair of types, where a type in librespot_connect.state uses a type in librespot_core.spotify_uri.
- The types involved
librespot_connect.state.ConnectState→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_connect.state uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_connect.state, while a change to librespot_connect.state can't break librespot_core.spotify_uri.
- Position
- Below the diagonal: librespot_connect.state uses a module listed above it, which is the healthy direction.
36→32 librespot_connect.state uses librespot_core.session✕
- Connections
- 1 pair of types, where a type in librespot_connect.state uses a type in librespot_core.session.
- The types involved
librespot_connect.state.ConnectState→librespot_core.session.Session
- Direction
- librespot_connect.state uses librespot_core.session, so a change to librespot_core.session can break librespot_connect.state, while a change to librespot_connect.state can't break librespot_core.session.
- Position
- Below the diagonal: librespot_connect.state uses a module listed above it, which is the healthy direction.
36→35 librespot_connect.state uses librespot_playback.player✕
- Connections
- 1 pair of types, where a type in librespot_connect.state uses a type in librespot_playback.player.
- The types involved
librespot_connect.state.ConnectState→librespot_playback.player.PlayerState
- Direction
- librespot_connect.state uses librespot_playback.player, so a change to librespot_playback.player can break librespot_connect.state, while a change to librespot_connect.state can't break librespot_playback.player.
- Position
- Below the diagonal: librespot_connect.state uses a module listed above it, which is the healthy direction.
37→2 librespot.main uses librespot_core.authentication✕
- Connections
- 1 pair of types, where a type in librespot.main uses a type in librespot_core.authentication.
- The types involved
librespot.main.Setup→librespot_core.authentication.Credentials
- Direction
- librespot.main uses librespot_core.authentication, so a change to librespot_core.authentication can break librespot.main, while a change to librespot.main can't break librespot_core.authentication.
- Position
- Below the diagonal: librespot.main uses a module listed above it, which is the healthy direction.
37→3 librespot.main uses librespot_core.config✕
- Connections
- 1 pair of types, where a type in librespot.main uses a type in librespot_core.config.
- The types involved
librespot.main.Setup→librespot_core.config.SessionConfig
- Direction
- librespot.main uses librespot_core.config, so a change to librespot_core.config can break librespot.main, while a change to librespot.main can't break librespot_core.config.
- Position
- Below the diagonal: librespot.main uses a module listed above it, which is the healthy direction.
37→9 librespot.main uses librespot_playback.config✕
- Connections
- 2 pairs of types, where a type in librespot.main uses a type in librespot_playback.config.
- The types involved
librespot.main.Setup→librespot_playback.config.AudioFormatlibrespot.main.Setup→librespot_playback.config.PlayerConfig
- Direction
- librespot.main uses librespot_playback.config, so a change to librespot_playback.config can break librespot.main, while a change to librespot.main can't break librespot_playback.config.
- Position
- Below the diagonal: librespot.main uses a module listed above it, which is the healthy direction.
37→31 librespot.main uses librespot_core.cache✕
- Connections
- 1 pair of types, where a type in librespot.main uses a type in librespot_core.cache.
- The types involved
librespot.main.Setup→librespot_core.cache.Cache
- Direction
- librespot.main uses librespot_core.cache, so a change to librespot_core.cache can break librespot.main, while a change to librespot.main can't break librespot_core.cache.
- Position
- Below the diagonal: librespot.main uses a module listed above it, which is the healthy direction.
37→36 librespot.main uses librespot_connect.state✕
- Connections
- 1 pair of types, where a type in librespot.main uses a type in librespot_connect.state.
- The types involved
librespot.main.Setup→librespot_connect.state.ConnectConfig
- Direction
- librespot.main uses librespot_connect.state, so a change to librespot_connect.state can break librespot.main, while a change to librespot.main can't break librespot_connect.state.
- Position
- Below the diagonal: librespot.main uses a module listed above it, which is the healthy direction.
38→11 librespot_connect.context_resolver uses librespot_connect.state.context✕
- Connections
- 1 pair of types, where a type in librespot_connect.context_resolver uses a type in librespot_connect.state.context.
- The types involved
librespot_connect.context_resolver.ResolveContext→librespot_connect.state.context.ContextType
- Direction
- librespot_connect.context_resolver uses librespot_connect.state.context, so a change to librespot_connect.state.context can break librespot_connect.context_resolver, while a change to librespot_connect.context_resolver can't break librespot_connect.state.context.
- Position
- Below the diagonal: librespot_connect.context_resolver uses a module listed above it, which is the healthy direction.
38→32 librespot_connect.context_resolver uses librespot_core.session✕
- Connections
- 1 pair of types, where a type in librespot_connect.context_resolver uses a type in librespot_core.session.
- The types involved
librespot_connect.context_resolver.ContextResolver→librespot_core.session.Session
- Direction
- librespot_connect.context_resolver uses librespot_core.session, so a change to librespot_core.session can break librespot_connect.context_resolver, while a change to librespot_connect.context_resolver can't break librespot_core.session.
- Position
- Below the diagonal: librespot_connect.context_resolver uses a module listed above it, which is the healthy direction.
38→36 librespot_connect.context_resolver uses librespot_connect.state✕
- Connections
- 1 pair of types, where a type in librespot_connect.context_resolver uses a type in librespot_connect.state.
- The types involved
librespot_connect.context_resolver.ContextResolver→librespot_connect.state.ConnectState
- Direction
- librespot_connect.context_resolver uses librespot_connect.state, so a change to librespot_connect.state can break librespot_connect.context_resolver, while a change to librespot_connect.context_resolver can't break librespot_connect.state.
- Position
- Below the diagonal: librespot_connect.context_resolver uses a module listed above it, which is the healthy direction.
39→2 librespot_connect.spirc uses librespot_core.authentication✕
- Connections
- 1 pair of types, where a type in librespot_connect.spirc uses a type in librespot_core.authentication.
- The types involved
librespot_connect.spirc.Spirc→librespot_core.authentication.Credentials
- Direction
- librespot_connect.spirc uses librespot_core.authentication, so a change to librespot_core.authentication can break librespot_connect.spirc, while a change to librespot_connect.spirc can't break librespot_core.authentication.
- Position
- Below the diagonal: librespot_connect.spirc uses a module listed above it, which is the healthy direction.
39→5 librespot_connect.spirc uses librespot_core.dealer.protocol✕
- Connections
- 1 pair of types, where a type in librespot_connect.spirc uses a type in librespot_core.dealer.protocol.
- The types involved
librespot_connect.spirc.SpircTask→librespot_core.dealer.protocol.FallbackWrapper
- Direction
- librespot_connect.spirc uses librespot_core.dealer.protocol, so a change to librespot_core.dealer.protocol can break librespot_connect.spirc, while a change to librespot_connect.spirc can't break librespot_core.dealer.protocol.
- Position
- Below the diagonal: librespot_connect.spirc uses a module listed above it, which is the healthy direction.
39→6 librespot_connect.spirc uses librespot_core.dealer.protocol.request✕
- Connections
- 1 pair of types, where a type in librespot_connect.spirc uses a type in librespot_core.dealer.protocol.request.
- The types involved
librespot_connect.spirc.SpircTask→librespot_core.dealer.protocol.request.Request
- Direction
- librespot_connect.spirc uses librespot_core.dealer.protocol.request, so a change to librespot_core.dealer.protocol.request can break librespot_connect.spirc, while a change to librespot_connect.spirc can't break librespot_core.dealer.protocol.request.
- Position
- Below the diagonal: librespot_connect.spirc uses a module listed above it, which is the healthy direction.
39→28 librespot_connect.spirc uses librespot_core.spotify_uri✕
- Connections
- 2 pairs of types, where a type in librespot_connect.spirc uses a type in librespot_core.spotify_uri.
- The types involved
librespot_connect.spirc.Spirc→librespot_core.spotify_uri.SpotifyUrilibrespot_connect.spirc.SpircTask→librespot_core.spotify_uri.SpotifyUri
- Direction
- librespot_connect.spirc uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_connect.spirc, while a change to librespot_connect.spirc can't break librespot_core.spotify_uri.
- Position
- Below the diagonal: librespot_connect.spirc uses a module listed above it, which is the healthy direction.
39→32 librespot_connect.spirc uses librespot_core.session✕
- Connections
- 2 pairs of types, where a type in librespot_connect.spirc uses a type in librespot_core.session.
- The types involved
librespot_connect.spirc.Spirc→librespot_core.session.Sessionlibrespot_connect.spirc.SpircTask→librespot_core.session.Session
- Direction
- librespot_connect.spirc uses librespot_core.session, so a change to librespot_core.session can break librespot_connect.spirc, while a change to librespot_connect.spirc can't break librespot_core.session.
- Position
- Below the diagonal: librespot_connect.spirc uses a module listed above it, which is the healthy direction.
39→35 librespot_connect.spirc uses librespot_playback.player✕
- Connections
- 3 pairs of types, where a type in librespot_connect.spirc uses a type in librespot_playback.player.
- The types involved
librespot_connect.spirc.Spirc→librespot_playback.player.Playerlibrespot_connect.spirc.SpircTask→librespot_playback.player.Playerlibrespot_connect.spirc.SpircTask→librespot_playback.player.PlayerEvent
- Direction
- librespot_connect.spirc uses librespot_playback.player, so a change to librespot_playback.player can break librespot_connect.spirc, while a change to librespot_connect.spirc can't break librespot_playback.player.
- Position
- Below the diagonal: librespot_connect.spirc uses a module listed above it, which is the healthy direction.
39→36 librespot_connect.spirc uses librespot_connect.state✕
- Connections
- 2 pairs of types, where a type in librespot_connect.spirc uses a type in librespot_connect.state.
- The types involved
librespot_connect.spirc.Spirc→librespot_connect.state.ConnectConfiglibrespot_connect.spirc.SpircTask→librespot_connect.state.ConnectState
- Direction
- librespot_connect.spirc uses librespot_connect.state, so a change to librespot_connect.state can break librespot_connect.spirc, while a change to librespot_connect.spirc can't break librespot_connect.state.
- Position
- Below the diagonal: librespot_connect.spirc uses a module listed above it, which is the healthy direction.
39→38 librespot_connect.spirc uses librespot_connect.context_resolver✕
- Connections
- 1 pair of types, where a type in librespot_connect.spirc uses a type in librespot_connect.context_resolver.
- The types involved
librespot_connect.spirc.SpircTask→librespot_connect.context_resolver.ContextResolver
- Direction
- librespot_connect.spirc uses librespot_connect.context_resolver, so a change to librespot_connect.context_resolver can break librespot_connect.spirc, while a change to librespot_connect.spirc can't break librespot_connect.context_resolver.
- Position
- Below the diagonal: librespot_connect.spirc uses a module listed above it, which is the healthy direction.
40→2 librespot_core.error uses librespot_core.authentication✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_core.authentication.
- The types involved
librespot_core.error.Error→librespot_core.authentication.AuthenticationError
- Direction
- librespot_core.error uses librespot_core.authentication, so a change to librespot_core.authentication can break librespot_core.error, while a change to librespot_core.error can't break librespot_core.authentication.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→5 librespot_core.error uses librespot_core.dealer.protocol✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_core.dealer.protocol.
- The types involved
librespot_core.error.Error→librespot_core.dealer.protocol.ProtocolError
- Direction
- librespot_core.error uses librespot_core.dealer.protocol, so a change to librespot_core.dealer.protocol can break librespot_core.error, while a change to librespot_core.error can't break librespot_core.dealer.protocol.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→12 librespot_core.error uses librespot_core.dealer✕
- Connections
- 2 pairs of types, where a type in librespot_core.error uses a type in librespot_core.dealer.
- The types involved
librespot_core.error.Error→librespot_core.dealer.AddHandlerErrorlibrespot_core.error.Error→librespot_core.dealer.SubscriptionError
- Direction
- librespot_core.error uses librespot_core.dealer, so a change to librespot_core.dealer can break librespot_core.error, while a change to librespot_core.error can't break librespot_core.dealer.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→13 librespot_core.error uses librespot_core.spotify_id✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_core.spotify_id.
- The types involved
librespot_core.error.Error→librespot_core.spotify_id.SpotifyIdError
- Direction
- librespot_core.error uses librespot_core.spotify_id, so a change to librespot_core.spotify_id can break librespot_core.error, while a change to librespot_core.error can't break librespot_core.spotify_id.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→16 librespot_core.error uses librespot_playback.decoder✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_playback.decoder.
- The types involved
librespot_core.error.Error→librespot_playback.decoder.DecoderError
- Direction
- librespot_core.error uses librespot_playback.decoder, so a change to librespot_playback.decoder can break librespot_core.error, while a change to librespot_core.error can't break librespot_playback.decoder.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→17 librespot_core.error uses librespot_audio.fetch✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_audio.fetch.
- The types involved
librespot_core.error.Error→librespot_audio.fetch.AudioFileError
- Direction
- librespot_core.error uses librespot_audio.fetch, so a change to librespot_audio.fetch can break librespot_core.error, while a change to librespot_core.error can't break librespot_audio.fetch.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→23 librespot_core.error uses librespot_discovery✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_discovery.
- The types involved
librespot_core.error.Error→librespot_discovery.DiscoveryError
- Direction
- librespot_core.error uses librespot_discovery, so a change to librespot_discovery can break librespot_core.error, while a change to librespot_core.error can't break librespot_discovery.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→28 librespot_core.error uses librespot_core.spotify_uri✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_core.spotify_uri.
- The types involved
librespot_core.error.Error→librespot_core.spotify_uri.SpotifyUriError
- Direction
- librespot_core.error uses librespot_core.spotify_uri, so a change to librespot_core.spotify_uri can break librespot_core.error, while a change to librespot_core.error can't break librespot_core.spotify_uri.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→31 librespot_core.error uses librespot_core.cache✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_core.cache.
- The types involved
librespot_core.error.Error→librespot_core.cache.CacheError
- Direction
- librespot_core.error uses librespot_core.cache, so a change to librespot_core.cache can break librespot_core.error, while a change to librespot_core.error can't break librespot_core.cache.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→32 librespot_core.error uses librespot_core.session✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_core.session.
- The types involved
librespot_core.error.Error→librespot_core.session.SessionError
- Direction
- librespot_core.error uses librespot_core.session, so a change to librespot_core.session can break librespot_core.error, while a change to librespot_core.error can't break librespot_core.session.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→36 librespot_core.error uses librespot_connect.state✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_connect.state.
- The types involved
librespot_core.error.Error→librespot_connect.state.StateError
- Direction
- librespot_core.error uses librespot_connect.state, so a change to librespot_connect.state can break librespot_core.error, while a change to librespot_core.error can't break librespot_connect.state.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→38 librespot_core.error uses librespot_connect.context_resolver✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_connect.context_resolver.
- The types involved
librespot_core.error.Error→librespot_connect.context_resolver.ContextResolverError
- Direction
- librespot_core.error uses librespot_connect.context_resolver, so a change to librespot_connect.context_resolver can break librespot_core.error, while a change to librespot_core.error can't break librespot_connect.context_resolver.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
40→39 librespot_core.error uses librespot_connect.spirc✕
- Connections
- 1 pair of types, where a type in librespot_core.error uses a type in librespot_connect.spirc.
- The types involved
librespot_core.error.Error→librespot_connect.spirc.SpircError
- Direction
- librespot_core.error uses librespot_connect.spirc, so a change to librespot_connect.spirc can break librespot_core.error, while a change to librespot_core.error can't break librespot_connect.spirc.
- Position
- Below the diagonal: librespot_core.error uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 33 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 29 | High / Critical |
| A05:2025 — Injection | 23 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
First, secure the application by implementing a global authentication guard with explicit public opt-outs and named role permissions. Next, address critical web-security risks by replacing weak MD5 and SHA1 hashes with SHA-256 or non-cryptographic alternatives where appropriate. Simultaneously, resolve the lack of architectural documentation by creating a dedicated folder for decision records and clean up technical debt by removing 42 orphaned files, starting with config.rs, lib.rs, and receive.rs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +9.1 pts | Low | ADR Quality |
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +13.3 pts | Medium | Access Controls |
| 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 7 sites, not one: `core/src/authentication.rs:100` (`Sha1::digest`), `core/src/authentication.rs:110` (`Sha1::digest`), `core/src/connection/handshake.rs:92` (`Sha1::digest`), `core/src/util.rs:139` (`Sha1::digest`), `core/src/util.rs:153` (`Sha1::new`), `discovery/src/server.rs:165` (`Sha1::digest`), `src/main.rs:45` (`Sha1::digest`). Each is a separate decision — fixing only the line this row cites leaves the others in place. | +7.5 pts | Medium | Web-Security Posture |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.9 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy. | +3.4 pts | Low | Vulnerability-disclosure Policy |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +2.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 42 Orphaned file finding(s) in Knowledge Freshness — start with config.rs (2), lib.rs, receive.rs. | +4.3 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.5 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| connect/src/spirc.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| playback/src/player.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/dealer/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/session.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| playback/src/decoder/symphonia_decoder.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| audio/src/fetch/receive.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| connect/src/state/tracks.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| discovery/src/lib.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| connect/src/state.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| core/src/spclient.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| metadata/src/playlist/annotation.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 63 of 63 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 63 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, 235 of 285 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 9 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 15 | 16 | >>> FROM debian:trixie 17 | 18 | RUN dpkg --add-architecture arm64 && \ -------------------- ERROR: failed to solve: debian:trixie: failed to resolve source metadata for docker.io/library/debian:trixie: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/trixie": Forbidden; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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
20 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was librespot::get_setup at 115. A further 5 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SpircTask::handle_command at 23 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: core/src/connection/mod.rs (librespot_core::connection::authenticate at 19), core/src/config.rs (DeviceType::from_str at 16). 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 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with librespot::get_setup (cyclomatic 115). — Refactoring it lifts Cyclomatic Complexity from 6.3 to about 6.9/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
30 function(s) exceeded the cognitive complexity threshold of 15; the worst was librespot::get_setup at 200.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with librespot::get_setup (cognitive 200), PlayerInternal::poll (cognitive 139), librespot::main (cognitive 73). — 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 3 together lifts Cognitive Complexity from 4.8 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
17 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 5 FileTooLong finding(s) in God Classes — start with player.rs, main.rs, spirc.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 MethodTooLong finding(s) in God Classes — start with player.rs (3), player_event_handler.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with main.rs (2), alsa.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
7 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with item.rs, portaudio.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (11–14 lines × 2) finding(s) in Code Duplication — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (12–13 lines × 2) finding(s) in Code Duplication — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
9 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 8 of the 9 (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 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 61 classes have LCOM4 above 3.
D9 · Test Distribution
31 test methods: 30 unit, 1 integration, 0 BDD, 0 e2e. The Rust suite contributes 31 `#[test]` function(s) across 9 file(s) declaring at least one; its unit/integration split is Cargo's own — 1 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
32 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.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 474 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/main.rs (4×115=460)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is connect/src/state/transfer.rs. Counted over 80 of the 121 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
28 deducted task-comment markers across 25552 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 27 TodoComment finding(s) in Explicit Debt — start with tracks.rs (4), session.rs (3), mod.rs (3). — One of this dimension's main actionable groups (27 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with spirc.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 7 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 9 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
23 finding(s): 0 critical, 23 high, 0 medium, 0 low. 22 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 2 file(s) — `REDACTED` (line 60, line 61, line 62), `REDACTED` (line 40) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 22 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 (22 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
21 finding(s): 0 critical, 3 high, 18 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 6 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D31 · IaC & Container Security
32 finding(s): 0 critical, 17 high, 6 medium, 9 low.
What to do
- Resolve the 17 High IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED (8). — One of this dimension's main actionable groups (17 issue-level).
- Resolve the 9 Low IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 warning-level).
D34 · Knowledge Freshness
44 of 80 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/src/session.rs. Counted over 80 of the 121 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 42 Orphaned file finding(s) in Knowledge Freshness — start with config.rs (2), lib.rs, receive.rs. — One of this dimension's main actionable groups (42 recommendation-level).
- Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with session.rs, spotify_uri.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 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is present but only routes reports to a public channel (no private reporting contact).
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
C2 · Access Controls
- This repository serves requests — a server (.serve_connection) (discovery/src/server.rs:354) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — discovery/src/server.rs:354
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
- 30 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 7 of 8 project(s) that lack one — worth up to 1.8 pts.
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `cargo` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency 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. (×7) — core/src/authentication.rs:100, core/src/authentication.rs:110, core/src/connection/handshake.rs:92, …
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `.serve_connection(` (discovery/src/server.rs:354).
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection(` (discovery/src/server.rs:354).
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 7 sites, not one: `core/src/authentication.rs:100` (`Sha1::digest`), `core/src/authentication.rs:110` (`Sha1::digest`), `core/src/connection/handshake.rs:92` (`Sha1::digest`), `core/src/util.rs:139` (`Sha1::digest`), `core/src/util.rs:153` (`Sha1::new`), `discovery/src/server.rs:165` (`Sha1::digest`), `src/main.rs:45` (`Sha1::digest`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 90% | Exemplary | Solid. |
| Architecture | 98% | Exemplary | Solid. |
| Maturity | 52% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 79% | Strong | Solid. |
| Security | 28% | Weak — gated by D31, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 15 | 16 | >>> FROM debian:trixie 17 | 18 | RUN dpkg --add-architecture arm64 && \ -------------------- ERROR: failed to solve: debian:trixie: failed to resolve source metadata for docker.io/library/debian:trixie: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/trixie": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- 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 — ~526 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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): 46 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; 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.
- 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 — 44 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
- 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)
- TodoComment protocol/build.rs:58
- TodoComment playback/src/player.rs:500
- TodoComment playback/src/decoder/passthrough_decoder.rs:7
- TodoComment playback/src/decoder/symphonia_decoder.rs:67
- TodoComment metadata/src/lyrics.rs:50
- TodoComment metadata/src/lyrics.rs:75
- TodoComment metadata/src/playlist/annotation.rs:44
- TodoComment discovery/src/lib.rs:292
- TodoComment discovery/src/server.rs:114
- TodoComment core/src/packet.rs:38
- TodoComment core/src/session.rs:370
- TodoComment core/src/session.rs:932
- TodoComment core/src/session.rs:943
- TodoComment core/src/spclient.rs:770
- TodoComment core/src/spotify_uri.rs:330
- TodoComment core/src/mercury/mod.rs:250
- TodoComment core/src/mercury/mod.rs:270
- TodoComment core/src/dealer/mod.rs:154
- TodoComment core/src/dealer/protocol/request.rs:17
- TodoComment connect/src/spirc.rs:526
- TodoComment connect/src/spirc.rs:707
- TodoComment connect/src/state.rs:165
- TodoComment connect/src/state/tracks.rs:35
- TodoComment connect/src/state/tracks.rs:45
- TodoComment connect/src/state/tracks.rs:175
- Weak hash algorithm core/src/authentication.rs:100
- Weak hash algorithm core/src/authentication.rs:110
- Weak hash algorithm core/src/connection/handshake.rs:92
- Weak hash algorithm core/src/util.rs:139
- Weak hash algorithm core/src/util.rs:153
- Weak hash algorithm discovery/src/server.rs:165
- Weak hash algorithm src/main.rs:45
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- SpircTask::run (cognitive 44) connect/src/spirc.rs:458
- SpircTask::handle_transfer (cognitive 20) connect/src/spirc.rs:1188
- SpircTask::handle_player_event (cognitive 18) connect/src/spirc.rs:776
- SpircTask::handle_user_attributes_mutation (cognitive 18) connect/src/spirc.rs:971
- SpircTask::handle_load (cognitive 17) connect/src/spirc.rs:1365
- FileTooLong: src/player.rs playback/src/player.rs
- FileTooLong: src/main.rs src/main.rs
- FileTooLong: src/spirc.rs connect/src/spirc.rs
- FileTooLong: src/session.rs core/src/session.rs
- FileTooLong: src/spclient.rs core/src/spclient.rs
- SpircTask::run (cyclomatic 35) connect/src/spirc.rs:458
- SpircTask::handle_request (cyclomatic 24) connect/src/spirc.rs:1061
- SpircTask::handle_player_event (cyclomatic 21) connect/src/spirc.rs:776
- SpircTask::handle_transfer (cyclomatic 16) connect/src/spirc.rs:1188
- PlayerInternal::poll (cyclomatic 34) playback/src/player.rs:1361
- PlayerInternal::handle_command (cyclomatic 22) playback/src/player.rs:2307
- PlayerInternal::handle_command_load (cyclomatic 21) playback/src/player.rs:1979
- PlayerInternal::handle_packet (cyclomatic 16) playback/src/player.rs:1777
- MethodTooLong: EventHandler.new src/player_event_handler.rs:15
- MethodTooLong: PlayerInternal.poll playback/src/player.rs:1361
- MethodTooLong: PlayerTrackLoader.load_remote_track playback/src/player.rs:1009
- MethodTooLong: PlayerInternal.handle_command_load playback/src/player.rs:1979
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- PlayerInternal::poll (cognitive 139) playback/src/player.rs:1361
- PlayerInternal::handle_packet (cognitive 52) playback/src/player.rs:1777
- PlayerInternal::handle_command_load (cognitive 49) playback/src/player.rs:1979
- ConnectState::update_context (cognitive 30) connect/src/state/context.rs:188
- ConnectState::finish_transfer (cognitive 20) connect/src/state/transfer.rs:121
- ConnectState::next_track (cognitive 16) connect/src/state/tracks.rs:105
- FunctionTooLong: librespot::get_setup src/main.rs:227
- FunctionTooLong: librespot::main src/main.rs:1911
- FunctionTooLong: librespot_playback::audio_backend::alsa::open_device playback/src/audio_backend/alsa.rs:165
- TooManyMethods: ConnectState connect/src/state.rs:112
- TooManyMethods: Session core/src/session.rs:130
- TooManyMethods: SpircTask connect/src/spirc.rs:72
- REDACTED
- REDACTED
- REDACTED
- librespot::get_setup (cyclomatic 115) src/main.rs:227
- librespot::main (cyclomatic 39) src/main.rs:1911
- librespot_core::dealer::connect (cyclomatic 24) core/src/dealer/mod.rs:499
- librespot_core::connection::handshake::platform_for (cyclomatic 16) core/src/connection/handshake.rs:113
- librespot::get_setup (cognitive 200) src/main.rs:227
- librespot::main (cognitive 73) src/main.rs:1911
- librespot_playback::audio_backend::alsa::list_compatible_devices (cognitive 44) playback/src/audio_backend/alsa.rs:105
- librespot_playback::audio_backend::alsa::open_device (cognitive 32) playback/src/audio_backend/alsa.rs:165
- librespot_core::dealer::connect (cognitive 34) core/src/dealer/mod.rs:499
- librespot_core::dealer::run (cognitive 22) core/src/dealer/mod.rs:663
- librespot_audio::fetch::receive::receive_data (cognitive 32) audio/src/fetch/receive.rs:38
- librespot_audio::fetch::receive::audio_file_fetch (cognitive 23) audio/src/fetch/receive.rs:422
- ClassTooLong: SpircTask connect/src/spirc.rs:72
- ClassTooLong: PlayerInternal playback/src/player.rs:71
- Duplicated block (11 lines × 2) metadata/src/audio/item.rs:96
- Duplicated block (11 lines × 2) playback/src/audio_backend/portaudio.rs:84
- Off the main sequence: librespot-oauth
- Off the main sequence: librespot-core
- No authorization discovery/src/server.rs:354
- EventHandler::new (cyclomatic 28) src/player_event_handler.rs:15
- PlayerTrackLoader::load_remote_track (cyclomatic 22) playback/src/player.rs:1009
- DispatchTask::dispatch (cyclomatic 19) core/src/session.rs:736
- SymphoniaDecoder::local_file_metadata (cyclomatic 18) playback/src/decoder/symphonia_decoder.rs:120
- librespot_audio::fetch::receive::receive_data (cyclomatic 17) audio/src/fetch/receive.rs:38
- ConnectState::update_context (cyclomatic 17) connect/src/state/context.rs:188
- librespot_playback::audio_backend::alsa::open_device (cyclomatic 17) playback/src/audio_backend/alsa.rs:165
- MaybeExpiringUrls::try_from (cyclomatic 16) core/src/cdn_url.rs:131
- Hotspot: src/main.rs src/main.rs:227
- FixmeComment connect/src/spirc.rs:1027
- MaybeExpiringUrls::try_from (cognitive 40) core/src/cdn_url.rs:131
- PlayerTrackLoader::load_remote_track (cognitive 38) playback/src/player.rs:1009
- Session::connect (cognitive 23) core/src/session.rs:206
- librespot_discovery::avahi_task (cognitive 23) discovery/src/lib.rs:181
- HttpClient::get_retry_after (cognitive 22) core/src/http_client.rs:259
- AlsaMixer::open (cognitive 22) playback/src/mixer/alsamixer.rs:58
- AudioFileFetch::handle_file_data (cognitive 20) audio/src/fetch/receive.rs:276
- AudioItem::get_file (cognitive 17) metadata/src/audio/item.rs:87
- SymphoniaDecoder::local_file_metadata (cognitive 17) playback/src/decoder/symphonia_decoder.rs:120
- EventHandler::new (cognitive 17) src/player_event_handler.rs:15
- RangeSet::subtract_range (cognitive 16) audio/src/range_set.rs:149
- REDACTED
- Duplicated block (11–14 lines × 2) audio/src/fetch/mod.rs:575
- Duplicated block (12–13 lines × 2) oauth/src/lib.rs:353
- Duplicated block (8 lines × 2) metadata/src/playlist/annotation.rs:42
- Duplicated block (5 lines × 2) playback/src/mixer/alsamixer.rs:197
- Duplicated block (6 lines × 2) core/src/cache.rs:282
- README may be stale
Minor — 67 finding(s)
- Orphaned file discovery/src/lib.rs:1
- Orphaned file audio/src/fetch/receive.rs:1
- Orphaned file src/player_event_handler.rs:1
- Orphaned file playback/src/audio_backend/alsa.rs:1
- Orphaned file core/src/error.rs:1
- Orphaned file playback/src/mixer/alsamixer.rs:1
- Orphaned file core/src/http_client.rs:1
- Orphaned file core/src/spotify_id.rs:1
- Orphaned file playback/src/decoder/symphonia_decoder.rs:1
- Orphaned file metadata/src/artist.rs:1
- Orphaned file core/src/cdn_url.rs:1
- Orphaned file playback/src/audio_backend/rodio.rs:1
- Orphaned file audio/src/range_set.rs:1
- Orphaned file playback/src/decoder/passthrough_decoder.rs:1
- Orphaned file core/src/channel.rs:1
- Orphaned file playback/src/audio_backend/gstreamer.rs:1
- Orphaned file metadata/src/playlist/attribute.rs:1
- Orphaned file playback/src/audio_backend/subprocess.rs:1
- Orphaned file metadata/src/playlist/list.rs:1
- Orphaned file playback/src/audio_backend/portaudio.rs:1
- Orphaned file playback/src/mixer/mappings.rs:1
- Orphaned file core/src/config.rs:1
- Orphaned file playback/src/config.rs:1
- Orphaned file core/src/apresolve.rs:1
- Orphaned file playback/src/local_file.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Most significant orphaned file core/src/session.rs:1
- Most significant orphaned file core/src/spotify_uri.rs:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No app-layer HTTPS enforcement detected
- No security response headers detected
Minor — 32 finding(s)
- Outdated: bytes
- Outdated: data-encoding
- Outdated: env_logger
- Outdated: flate2
- Outdated: futures-core
- Outdated: futures-util
- Outdated: governor
- Outdated: http
- Outdated: http-body-util
- Outdated: hyper
- Outdated: hyper-rustls
- Outdated: hyper-util
- Outdated: jack
- Outdated: log
- Outdated: num-integer
- Outdated: open
- Outdated: pin-project-lite
- Outdated: portable-atomic
- Outdated: rsa
- Outdated: serde
- Outdated: serde_json
- Outdated: serde_repr
- Outdated: shell-words
- Outdated: tempfile
- Outdated: thiserror
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b24dcca03f08472c9b6edc523d66a97f/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b24dcca03f08472c9b6edc523d66a97f/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 23 | 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 . | 21 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 32 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 |