Executive summary
jeremehancock/Marquee falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 66.0 out of 100 and is rated Adequate, and 22 of its 28 critical findings are security problems in the build pipeline and in its servers and containers.
Production Readiness, at 63.7, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is recording design decisions, worth about 1.6 points. Adding automated security scanning would lift Production Readiness itself, worth about 1.9 points.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and four controls can't be used without a mouse. Making the controls work with a keyboard, pinning each tool to an exact version and limiting each secret to its own step would close these risks. The unsafe setting in infrastructure or container files needs changing to safe values. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 12,184 lines, about €44,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
Rebuild cost: about €44,000 · Estimate
| Cost to rebuild | €15,000 to €73,000, for 242 to 767 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,184 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 (global) | 2 App.Poster.Upload | 3 App.Support.Session | 4 App.Version | 5 public | 6 public.assets | 7 scripts | 8 src | 9 App.Poster.Search | 10 App.Poster | 11 App.Plex.Poster | 12 App.Support | 13 App.Plex | 14 App.Database | 15 App.Poster.Source | 16 App.Poster.Wall | 17 App.Plex.Connection | 18 App.Plex.Import | 19 App.Plex.Orphan | 20 App.Settings | 21 App.Config | 22 App.Auth | 23 App.Plex.Export | 24 App.Poster.Edit | 25 App.Controller |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | |||||||||||||||||||||||||
| 2 App.Poster.Upload | |||||||||||||||||||||||||
| 3 App.Support.Session | |||||||||||||||||||||||||
| 4 App.Version | |||||||||||||||||||||||||
| 5 public | |||||||||||||||||||||||||
| 6 public.assets | |||||||||||||||||||||||||
| 7 scripts | |||||||||||||||||||||||||
| 8 src | |||||||||||||||||||||||||
| 9 App.Poster.Search | 1 | ||||||||||||||||||||||||
| 10 App.Poster | 1 | 1 | 2 | ||||||||||||||||||||||
| 11 App.Plex.Poster | 1 | 1 | 1 | ||||||||||||||||||||||
| 12 App.Support | 3 | 5 | |||||||||||||||||||||||
| 13 App.Plex | 1 | 2 | 2 | ||||||||||||||||||||||
| 14 App.Database | 1 | ||||||||||||||||||||||||
| 15 App.Poster.Source | 1 | ||||||||||||||||||||||||
| 16 App.Poster.Wall | 2 | 3 | |||||||||||||||||||||||
| 17 App.Plex.Connection | 1 | 1 | 2 | 2 | 1 | ||||||||||||||||||||
| 18 App.Plex.Import | 3 | 4 | 4 | 1 | |||||||||||||||||||||
| 19 App.Plex.Orphan | 2 | 1 | 1 | ||||||||||||||||||||||
| 20 App.Settings | 1 | 1 | |||||||||||||||||||||||
| 21 App.Config | 1 | 1 | 1 | 6 | |||||||||||||||||||||
| 22 App.Auth | 3 | 2 | |||||||||||||||||||||||
| 23 App.Plex.Export | 2 | 1 | 2 | 1 | |||||||||||||||||||||
| 24 App.Poster.Edit | 2 | 1 | 1 | 2 | 1 | ||||||||||||||||||||
| 25 App.Controller | 5 | 1 | 8 | 2 | 7 | 11 | 3 | 4 | 4 | 3 | 1 | 1 | 4 | 3 | 2 | 1 |
9→10 App.Poster.Search uses App.Poster part of a loop✕
- Connections
- 1 pair of types, where a type in App.Poster.Search uses a type in App.Poster.
- The types involved
App.Poster.Search.PosterSearch→App.Poster.Poster
- Direction
- App.Poster.Search uses App.Poster, so a change to App.Poster can break App.Poster.Search, while a change to App.Poster.Search can't break App.Poster.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→9 App.Poster uses App.Poster.Search✕
- Connections
- 1 pair of types, where a type in App.Poster uses a type in App.Poster.Search.
- The types involved
App.Poster.PosterLibrary→App.Poster.Search.PosterSearch
- Direction
- App.Poster uses App.Poster.Search, so a change to App.Poster.Search can break App.Poster, while a change to App.Poster can't break App.Poster.Search.
- Position
- Below the diagonal: App.Poster uses a module listed above it, which is the healthy direction.
10→14 App.Poster uses App.Database part of a loop✕
- Connections
- 1 pair of types, where a type in App.Poster uses a type in App.Database.
- The types involved
App.Poster.PosterLibrary→App.Database.PlexItemRepository
- Direction
- App.Poster uses App.Database, so a change to App.Database can break App.Poster, while a change to App.Poster can't break App.Database.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→21 App.Poster uses App.Config part of a loop✕
- Connections
- 2 pairs of types, where a type in App.Poster uses a type in App.Config.
- The types involved
App.Poster.PosterLibrary→App.Config.PosterConfigApp.Poster.SortComparator→App.Config.PosterConfig
- Direction
- App.Poster uses App.Config, so a change to App.Config can break App.Poster, while a change to App.Poster can't break App.Config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→10 App.Plex.Poster uses App.Poster✕
- Connections
- 1 pair of types, where a type in App.Plex.Poster uses a type in App.Poster.
- The types involved
App.Plex.Poster.PlexPosterService→App.Poster.PosterCategory
- Direction
- App.Plex.Poster uses App.Poster, so a change to App.Poster can break App.Plex.Poster, while a change to App.Plex.Poster can't break App.Poster.
- Position
- Below the diagonal: App.Plex.Poster uses a module listed above it, which is the healthy direction.
11→13 App.Plex.Poster uses App.Plex part of a loop✕
- Connections
- 1 pair of types, where a type in App.Plex.Poster uses a type in App.Plex.
- The types involved
App.Plex.Poster.PlexPosterService→App.Plex.PlexClient
- Direction
- App.Plex.Poster uses App.Plex, so a change to App.Plex can break App.Plex.Poster, while a change to App.Plex.Poster can't break App.Plex.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→14 App.Plex.Poster uses App.Database part of a loop✕
- Connections
- 1 pair of types, where a type in App.Plex.Poster uses a type in App.Database.
- The types involved
App.Plex.Poster.PlexPosterService→App.Database.PlexItemRepository
- Direction
- App.Plex.Poster uses App.Database, so a change to App.Database can break App.Plex.Poster, while a change to App.Plex.Poster can't break App.Database.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→3 App.Support uses App.Support.Session✕
- Connections
- 3 pairs of types, where a type in App.Support uses a type in App.Support.Session.
- The types involved
App.Support.Flash→App.Support.Session.SessionInterfaceApp.Support.LastCategory→App.Support.Session.SessionInterfaceApp.Support.SortPreference→App.Support.Session.SessionInterface
- Direction
- App.Support uses App.Support.Session, so a change to App.Support.Session can break App.Support, while a change to App.Support can't break App.Support.Session.
- Position
- Below the diagonal: App.Support uses a module listed above it, which is the healthy direction.
12→10 App.Support uses App.Poster✕
- Connections
- 5 pairs of types, where a type in App.Support uses a type in App.Poster.
- The types involved
App.Support.LastCategory→App.Poster.GalleryViewApp.Support.SortButton→App.Poster.SortOrderApp.Support.SortPreference→App.Poster.SortFieldApp.Support.SortPreference→App.Poster.SortOrderApp.Support.SortState→App.Poster.SortOrder
- Direction
- App.Support uses App.Poster, so a change to App.Poster can break App.Support, while a change to App.Support can't break App.Poster.
- Position
- Below the diagonal: App.Support uses a module listed above it, which is the healthy direction.
13→10 App.Plex uses App.Poster✕
- Connections
- 1 pair of types, where a type in App.Plex uses a type in App.Poster.
- The types involved
App.Plex.PlexMediaType→App.Poster.PosterCategory
- Direction
- App.Plex uses App.Poster, so a change to App.Poster can break App.Plex, while a change to App.Plex can't break App.Poster.
- Position
- Below the diagonal: App.Plex uses a module listed above it, which is the healthy direction.
13→11 App.Plex uses App.Plex.Poster✕
- Connections
- 2 pairs of types, where a type in App.Plex uses a type in App.Plex.Poster.
- The types involved
App.Plex.HttpPlexClient→App.Plex.Poster.PlexPosterListApp.Plex.PlexClient→App.Plex.Poster.PlexPosterList
- Direction
- App.Plex uses App.Plex.Poster, so a change to App.Plex.Poster can break App.Plex, while a change to App.Plex can't break App.Plex.Poster.
- Position
- Below the diagonal: App.Plex uses a module listed above it, which is the healthy direction.
13→21 App.Plex uses App.Config part of a loop✕
- Connections
- 2 pairs of types, where a type in App.Plex uses a type in App.Config.
- The types involved
App.Plex.HttpPlexClient→App.Config.LibraryExclusionsApp.Plex.HttpPlexClient→App.Config.PlexConfig
- Direction
- App.Plex uses App.Config, so a change to App.Config can break App.Plex, while a change to App.Plex can't break App.Config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→13 App.Database uses App.Plex✕
- Connections
- 1 pair of types, where a type in App.Database uses a type in App.Plex.
- The types involved
App.Database.PlexLibraryRepository→App.Plex.PlexLibrary
- Direction
- App.Database uses App.Plex, so a change to App.Plex can break App.Database, while a change to App.Database can't break App.Plex.
- Position
- Below the diagonal: App.Database uses a module listed above it, which is the healthy direction.
15→13 App.Poster.Source uses App.Plex✕
- Connections
- 1 pair of types, where a type in App.Poster.Source uses a type in App.Plex.
- The types involved
App.Poster.Source.PosterQuery→App.Plex.PlexMediaType
- Direction
- App.Poster.Source uses App.Plex, so a change to App.Plex can break App.Poster.Source, while a change to App.Poster.Source can't break App.Plex.
- Position
- Below the diagonal: App.Poster.Source uses a module listed above it, which is the healthy direction.
16→10 App.Poster.Wall uses App.Poster✕
- Connections
- 2 pairs of types, where a type in App.Poster.Wall uses a type in App.Poster.
- The types involved
App.Poster.Wall.PosterWallService→App.Poster.PosterCategoryApp.Poster.Wall.PosterWallService→App.Poster.PosterStorage
- Direction
- App.Poster.Wall uses App.Poster, so a change to App.Poster can break App.Poster.Wall, while a change to App.Poster.Wall can't break App.Poster.
- Position
- Below the diagonal: App.Poster.Wall uses a module listed above it, which is the healthy direction.
16→13 App.Poster.Wall uses App.Plex✕
- Connections
- 3 pairs of types, where a type in App.Poster.Wall uses a type in App.Plex.
- The types involved
App.Poster.Wall.NowPlayingService→App.Plex.PlexClientApp.Poster.Wall.NowPlayingTile→App.Plex.PlexSessionApp.Poster.Wall.StreamToken→App.Plex.SignedImagePath
- Direction
- App.Poster.Wall uses App.Plex, so a change to App.Plex can break App.Poster.Wall, while a change to App.Poster.Wall can't break App.Plex.
- Position
- Below the diagonal: App.Poster.Wall uses a module listed above it, which is the healthy direction.
17→3 App.Plex.Connection uses App.Support.Session✕
- Connections
- 1 pair of types, where a type in App.Plex.Connection uses a type in App.Support.Session.
- The types involved
App.Plex.Connection.PlexSignInService→App.Support.Session.SessionInterface
- Direction
- App.Plex.Connection uses App.Support.Session, so a change to App.Support.Session can break App.Plex.Connection, while a change to App.Plex.Connection can't break App.Support.Session.
- Position
- Below the diagonal: App.Plex.Connection uses a module listed above it, which is the healthy direction.
17→13 App.Plex.Connection uses App.Plex✕
- Connections
- 1 pair of types, where a type in App.Plex.Connection uses a type in App.Plex.
- The types involved
App.Plex.Connection.PlexConnectionStatus→App.Plex.PlexClient
- Direction
- App.Plex.Connection uses App.Plex, so a change to App.Plex can break App.Plex.Connection, while a change to App.Plex.Connection can't break App.Plex.
- Position
- Below the diagonal: App.Plex.Connection uses a module listed above it, which is the healthy direction.
17→14 App.Plex.Connection uses App.Database✕
- Connections
- 2 pairs of types, where a type in App.Plex.Connection uses a type in App.Database.
- The types involved
App.Plex.Connection.PlexConnectionStatus→App.Database.PlexServerRepositoryApp.Plex.Connection.PlexSignInService→App.Database.PlexServerRepository
- Direction
- App.Plex.Connection uses App.Database, so a change to App.Database can break App.Plex.Connection, while a change to App.Plex.Connection can't break App.Database.
- Position
- Below the diagonal: App.Plex.Connection uses a module listed above it, which is the healthy direction.
17→21 App.Plex.Connection uses App.Config part of a loop✕
- Connections
- 2 pairs of types, where a type in App.Plex.Connection uses a type in App.Config.
- The types involved
App.Plex.Connection.PlexConnectionStatus→App.Config.PlexConfigApp.Plex.Connection.PlexServerOwner→App.Config.PlexConfig
- Direction
- App.Plex.Connection uses App.Config, so a change to App.Config can break App.Plex.Connection, while a change to App.Plex.Connection can't break App.Config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→22 App.Plex.Connection uses App.Auth part of a loop✕
- Connections
- 1 pair of types, where a type in App.Plex.Connection uses a type in App.Auth.
- The types involved
App.Plex.Connection.PlexSignInService→App.Auth.SessionAuthenticator
- Direction
- App.Plex.Connection uses App.Auth, so a change to App.Auth can break App.Plex.Connection, while a change to App.Plex.Connection can't break App.Auth.
- 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→10 App.Plex.Import uses App.Poster✕
- Connections
- 3 pairs of types, where a type in App.Plex.Import uses a type in App.Poster.
- The types involved
App.Plex.Import.ImportResult→App.Poster.PosterCategoryApp.Plex.Import.ImportService→App.Poster.PosterCategoryApp.Plex.Import.ImportService→App.Poster.PosterStorage
- Direction
- App.Plex.Import uses App.Poster, so a change to App.Poster can break App.Plex.Import, while a change to App.Plex.Import can't break App.Poster.
- Position
- Below the diagonal: App.Plex.Import uses a module listed above it, which is the healthy direction.
18→13 App.Plex.Import uses App.Plex✕
- Connections
- 4 pairs of types, where a type in App.Plex.Import uses a type in App.Plex.
- The types involved
App.Plex.Import.AutoImportService→App.Plex.PlexClientApp.Plex.Import.ImportService→App.Plex.PlexClientApp.Plex.Import.ImportService→App.Plex.PlexItemApp.Plex.Import.ImportService→App.Plex.PlexLibrary
- Direction
- App.Plex.Import uses App.Plex, so a change to App.Plex can break App.Plex.Import, while a change to App.Plex.Import can't break App.Plex.
- Position
- Below the diagonal: App.Plex.Import uses a module listed above it, which is the healthy direction.
18→14 App.Plex.Import uses App.Database✕
- Connections
- 4 pairs of types, where a type in App.Plex.Import uses a type in App.Database.
- The types involved
App.Plex.Import.AutoImportService→App.Database.AutoImportScheduleRepositoryApp.Plex.Import.ImportService→App.Database.PlexItemRecordApp.Plex.Import.ImportService→App.Database.PlexItemRepositoryApp.Plex.Import.ImportService→App.Database.PlexLibraryRepository
- Direction
- App.Plex.Import uses App.Database, so a change to App.Database can break App.Plex.Import, while a change to App.Plex.Import can't break App.Database.
- Position
- Below the diagonal: App.Plex.Import uses a module listed above it, which is the healthy direction.
18→21 App.Plex.Import uses App.Config part of a loop✕
- Connections
- 1 pair of types, where a type in App.Plex.Import uses a type in App.Config.
- The types involved
App.Plex.Import.AutoImportService→App.Config.AutoImportConfig
- Direction
- App.Plex.Import uses App.Config, so a change to App.Config can break App.Plex.Import, while a change to App.Plex.Import can't break App.Config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→10 App.Plex.Orphan uses App.Poster✕
- Connections
- 2 pairs of types, where a type in App.Plex.Orphan uses a type in App.Poster.
- The types involved
App.Plex.Orphan.OrphanService→App.Poster.PosterCategoryApp.Plex.Orphan.OrphanService→App.Poster.PosterStorage
- Direction
- App.Plex.Orphan uses App.Poster, so a change to App.Poster can break App.Plex.Orphan, while a change to App.Plex.Orphan can't break App.Poster.
- Position
- Below the diagonal: App.Plex.Orphan uses a module listed above it, which is the healthy direction.
19→13 App.Plex.Orphan uses App.Plex✕
- Connections
- 1 pair of types, where a type in App.Plex.Orphan uses a type in App.Plex.
- The types involved
App.Plex.Orphan.OrphanService→App.Plex.PlexClient
- Direction
- App.Plex.Orphan uses App.Plex, so a change to App.Plex can break App.Plex.Orphan, while a change to App.Plex.Orphan can't break App.Plex.
- Position
- Below the diagonal: App.Plex.Orphan uses a module listed above it, which is the healthy direction.
19→14 App.Plex.Orphan uses App.Database✕
- Connections
- 1 pair of types, where a type in App.Plex.Orphan uses a type in App.Database.
- The types involved
App.Plex.Orphan.OrphanService→App.Database.PlexItemRepository
- Direction
- App.Plex.Orphan uses App.Database, so a change to App.Database can break App.Plex.Orphan, while a change to App.Plex.Orphan can't break App.Database.
- Position
- Below the diagonal: App.Plex.Orphan uses a module listed above it, which is the healthy direction.
20→10 App.Settings uses App.Poster✕
- Connections
- 1 pair of types, where a type in App.Settings uses a type in App.Poster.
- The types involved
App.Settings.SettingsForm→App.Poster.SortOrder
- Direction
- App.Settings uses App.Poster, so a change to App.Poster can break App.Settings, while a change to App.Settings can't break App.Poster.
- Position
- Below the diagonal: App.Settings uses a module listed above it, which is the healthy direction.
20→18 App.Settings uses App.Plex.Import✕
- Connections
- 1 pair of types, where a type in App.Settings uses a type in App.Plex.Import.
- The types involved
App.Settings.SettingsForm→App.Plex.Import.AutoImportInterval
- Direction
- App.Settings uses App.Plex.Import, so a change to App.Plex.Import can break App.Settings, while a change to App.Settings can't break App.Plex.Import.
- Position
- Below the diagonal: App.Settings uses a module listed above it, which is the healthy direction.
21→10 App.Config uses App.Poster✕
- Connections
- 1 pair of types, where a type in App.Config uses a type in App.Poster.
- The types involved
App.Config.PosterConfig→App.Poster.SortOrder
- Direction
- App.Config uses App.Poster, so a change to App.Poster can break App.Config, while a change to App.Config can't break App.Poster.
- Position
- Below the diagonal: App.Config uses a module listed above it, which is the healthy direction.
21→17 App.Config uses App.Plex.Connection✕
- Connections
- 1 pair of types, where a type in App.Config uses a type in App.Plex.Connection.
- The types involved
App.Config.PlexConfig→App.Plex.Connection.PlexConnectionStore
- Direction
- App.Config uses App.Plex.Connection, so a change to App.Plex.Connection can break App.Config, while a change to App.Config can't break App.Plex.Connection.
- Position
- Below the diagonal: App.Config uses a module listed above it, which is the healthy direction.
21→18 App.Config uses App.Plex.Import✕
- Connections
- 1 pair of types, where a type in App.Config uses a type in App.Plex.Import.
- The types involved
App.Config.AutoImportConfig→App.Plex.Import.AutoImportInterval
- Direction
- App.Config uses App.Plex.Import, so a change to App.Plex.Import can break App.Config, while a change to App.Config can't break App.Plex.Import.
- Position
- Below the diagonal: App.Config uses a module listed above it, which is the healthy direction.
21→20 App.Config uses App.Settings✕
- Connections
- 6 pairs of types, where a type in App.Config uses a type in App.Settings.
- The types involved
App.Config.AppConfig→App.Settings.SettingsStoreApp.Config.AuthConfig→App.Settings.SettingsStoreApp.Config.AutoImportConfig→App.Settings.SettingsStoreApp.Config.LibraryExclusions→App.Settings.SettingsStoreApp.Config.PlexConfig→App.Settings.SettingsStoreApp.Config.PosterConfig→App.Settings.SettingsStore
- Direction
- App.Config uses App.Settings, so a change to App.Settings can break App.Config, while a change to App.Config can't break App.Settings.
- Position
- Below the diagonal: App.Config uses a module listed above it, which is the healthy direction.
22→3 App.Auth uses App.Support.Session✕
- Connections
- 3 pairs of types, where a type in App.Auth uses a type in App.Support.Session.
- The types involved
App.Auth.AuthMiddleware→App.Support.Session.SessionInterfaceApp.Auth.CsrfGuard→App.Support.Session.SessionInterfaceApp.Auth.SessionAuthenticator→App.Support.Session.SessionInterface
- Direction
- App.Auth uses App.Support.Session, so a change to App.Support.Session can break App.Auth, while a change to App.Auth can't break App.Support.Session.
- Position
- Below the diagonal: App.Auth uses a module listed above it, which is the healthy direction.
22→21 App.Auth uses App.Config✕
- Connections
- 2 pairs of types, where a type in App.Auth uses a type in App.Config.
- The types involved
App.Auth.PlexConnectionMiddleware→App.Config.PlexConfigApp.Auth.SessionAuthenticator→App.Config.AuthConfig
- Direction
- App.Auth uses App.Config, so a change to App.Config can break App.Auth, while a change to App.Auth can't break App.Config.
- Position
- Below the diagonal: App.Auth uses a module listed above it, which is the healthy direction.
23→10 App.Plex.Export uses App.Poster✕
- Connections
- 2 pairs of types, where a type in App.Plex.Export uses a type in App.Poster.
- The types involved
App.Plex.Export.PlexExportService→App.Poster.PosterCategoryApp.Plex.Export.PlexExportService→App.Poster.PosterStorage
- Direction
- App.Plex.Export uses App.Poster, so a change to App.Poster can break App.Plex.Export, while a change to App.Plex.Export can't break App.Poster.
- Position
- Below the diagonal: App.Plex.Export uses a module listed above it, which is the healthy direction.
23→13 App.Plex.Export uses App.Plex✕
- Connections
- 1 pair of types, where a type in App.Plex.Export uses a type in App.Plex.
- The types involved
App.Plex.Export.PlexExportService→App.Plex.PlexPosterWriter
- Direction
- App.Plex.Export uses App.Plex, so a change to App.Plex can break App.Plex.Export, while a change to App.Plex.Export can't break App.Plex.
- Position
- Below the diagonal: App.Plex.Export uses a module listed above it, which is the healthy direction.
23→14 App.Plex.Export uses App.Database✕
- Connections
- 2 pairs of types, where a type in App.Plex.Export uses a type in App.Database.
- The types involved
App.Plex.Export.PlexExportService→App.Database.PlexItemRecordApp.Plex.Export.PlexExportService→App.Database.PlexItemRepository
- Direction
- App.Plex.Export uses App.Database, so a change to App.Database can break App.Plex.Export, while a change to App.Plex.Export can't break App.Database.
- Position
- Below the diagonal: App.Plex.Export uses a module listed above it, which is the healthy direction.
23→21 App.Plex.Export uses App.Config✕
- Connections
- 1 pair of types, where a type in App.Plex.Export uses a type in App.Config.
- The types involved
App.Plex.Export.PlexExportService→App.Config.PlexConfig
- Direction
- App.Plex.Export uses App.Config, so a change to App.Config can break App.Plex.Export, while a change to App.Plex.Export can't break App.Config.
- Position
- Below the diagonal: App.Plex.Export uses a module listed above it, which is the healthy direction.
24→10 App.Poster.Edit uses App.Poster✕
- Connections
- 2 pairs of types, where a type in App.Poster.Edit uses a type in App.Poster.
- The types involved
App.Poster.Edit.ChangePosterService→App.Poster.PosterCategoryApp.Poster.Edit.ChangePosterService→App.Poster.PosterStorage
- Direction
- App.Poster.Edit uses App.Poster, so a change to App.Poster can break App.Poster.Edit, while a change to App.Poster.Edit can't break App.Poster.
- Position
- Below the diagonal: App.Poster.Edit uses a module listed above it, which is the healthy direction.
24→13 App.Poster.Edit uses App.Plex✕
- Connections
- 1 pair of types, where a type in App.Poster.Edit uses a type in App.Plex.
- The types involved
App.Poster.Edit.ChangePosterService→App.Plex.PlexClient
- Direction
- App.Poster.Edit uses App.Plex, so a change to App.Plex can break App.Poster.Edit, while a change to App.Poster.Edit can't break App.Plex.
- Position
- Below the diagonal: App.Poster.Edit uses a module listed above it, which is the healthy direction.
24→14 App.Poster.Edit uses App.Database✕
- Connections
- 1 pair of types, where a type in App.Poster.Edit uses a type in App.Database.
- The types involved
App.Poster.Edit.ChangePosterService→App.Database.PlexItemRepository
- Direction
- App.Poster.Edit uses App.Database, so a change to App.Database can break App.Poster.Edit, while a change to App.Poster.Edit can't break App.Database.
- Position
- Below the diagonal: App.Poster.Edit uses a module listed above it, which is the healthy direction.
24→21 App.Poster.Edit uses App.Config✕
- Connections
- 2 pairs of types, where a type in App.Poster.Edit uses a type in App.Config.
- The types involved
App.Poster.Edit.ChangePosterService→App.Config.PlexConfigApp.Poster.Edit.ChangePosterService→App.Config.PosterConfig
- Direction
- App.Poster.Edit uses App.Config, so a change to App.Config can break App.Poster.Edit, while a change to App.Poster.Edit can't break App.Config.
- Position
- Below the diagonal: App.Poster.Edit uses a module listed above it, which is the healthy direction.
24→23 App.Poster.Edit uses App.Plex.Export✕
- Connections
- 1 pair of types, where a type in App.Poster.Edit uses a type in App.Plex.Export.
- The types involved
App.Poster.Edit.ChangePosterService→App.Plex.Export.PlexExportService
- Direction
- App.Poster.Edit uses App.Plex.Export, so a change to App.Plex.Export can break App.Poster.Edit, while a change to App.Poster.Edit can't break App.Plex.Export.
- Position
- Below the diagonal: App.Poster.Edit uses a module listed above it, which is the healthy direction.
25→3 App.Controller uses App.Support.Session✕
- Connections
- 5 pairs of types, where a type in App.Controller uses a type in App.Support.Session.
- The types involved
App.Controller.GalleryController→App.Support.Session.SessionInterfaceApp.Controller.OrphanController→App.Support.Session.SessionInterfaceApp.Controller.PlexConnectionController→App.Support.Session.SessionInterfaceApp.Controller.PlexImportController→App.Support.Session.SessionInterfaceApp.Controller.SettingsController→App.Support.Session.SessionInterface
- Direction
- App.Controller uses App.Support.Session, so a change to App.Support.Session can break App.Controller, while a change to App.Controller can't break App.Support.Session.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→4 App.Controller uses App.Version✕
- Connections
- 1 pair of types, where a type in App.Controller uses a type in App.Version.
- The types involved
App.Controller.VersionController→App.Version.VersionService
- Direction
- App.Controller uses App.Version, so a change to App.Version can break App.Controller, while a change to App.Controller can't break App.Version.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→10 App.Controller uses App.Poster✕
- Connections
- 8 pairs of types, where a type in App.Controller uses a type in App.Poster.
- The types involved
App.Controller.ChangePosterController→App.Poster.PosterCategoryApp.Controller.GalleryController→App.Poster.GalleryViewApp.Controller.GalleryController→App.Poster.PosterApp.Controller.GalleryController→App.Poster.PosterFactsIndexApp.Controller.GalleryController→App.Poster.PosterLibraryApp.Controller.PosterController→App.Poster.PosterLibraryApp.Controller.PosterImageController→App.Poster.PosterCategoryApp.Controller.PosterImageController→App.Poster.PosterStorage
- Direction
- App.Controller uses App.Poster, so a change to App.Poster can break App.Controller, while a change to App.Controller can't break App.Poster.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→11 App.Controller uses App.Plex.Poster✕
- Connections
- 2 pairs of types, where a type in App.Controller uses a type in App.Plex.Poster.
- The types involved
App.Controller.ChangePosterController→App.Plex.Poster.PlexPosterOutcomeApp.Controller.ChangePosterController→App.Plex.Poster.PlexPosterService
- Direction
- App.Controller uses App.Plex.Poster, so a change to App.Plex.Poster can break App.Controller, while a change to App.Controller can't break App.Plex.Poster.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→12 App.Controller uses App.Support✕
- Connections
- 7 pairs of types, where a type in App.Controller uses a type in App.Support.
- The types involved
App.Controller.ChangePosterController→App.Support.FlashApp.Controller.GalleryController→App.Support.FlashApp.Controller.OrphanController→App.Support.FlashApp.Controller.PlexConnectionController→App.Support.FlashApp.Controller.PlexImportController→App.Support.FlashApp.Controller.PosterController→App.Support.FlashApp.Controller.SettingsController→App.Support.Flash
- Direction
- App.Controller uses App.Support, so a change to App.Support can break App.Controller, while a change to App.Controller can't break App.Support.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→13 App.Controller uses App.Plex✕
- Connections
- 11 pairs of types, where a type in App.Controller uses a type in App.Plex.
- The types involved
App.Controller.ChangePosterController→App.Plex.PlexFailureMessageApp.Controller.ChangePosterController→App.Plex.SignedImagePathApp.Controller.OrphanController→App.Plex.PlexClientApp.Controller.OrphanController→App.Plex.PlexFailureMessageApp.Controller.PlexImportController→App.Plex.PlexClientApp.Controller.PlexImportController→App.Plex.PlexFailureMessageApp.Controller.PlexPosterImageController→App.Plex.PlexClientApp.Controller.PlexPosterImageController→App.Plex.SignedImagePathApp.Controller.PosterWallController→App.Plex.PlexClientApp.Controller.SettingsController→App.Plex.PlexClientApp.Controller.SettingsController→App.Plex.PlexFailureMessage
- Direction
- App.Controller uses App.Plex, so a change to App.Plex can break App.Controller, while a change to App.Controller can't break App.Plex.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→14 App.Controller uses App.Database✕
- Connections
- 3 pairs of types, where a type in App.Controller uses a type in App.Database.
- The types involved
App.Controller.ChangePosterController→App.Database.PlexItemRecordApp.Controller.ChangePosterController→App.Database.PlexItemRepositoryApp.Controller.GalleryController→App.Database.PlexItemRepository
- Direction
- App.Controller uses App.Database, so a change to App.Database can break App.Controller, while a change to App.Controller can't break App.Database.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→15 App.Controller uses App.Poster.Source✕
- Connections
- 4 pairs of types, where a type in App.Controller uses a type in App.Poster.Source.
- The types involved
App.Controller.ChangePosterController→App.Poster.Source.PosterQueryApp.Controller.ChangePosterController→App.Poster.Source.PosterSearchOutcomeApp.Controller.ChangePosterController→App.Poster.Source.PosterSearchResultApp.Controller.ChangePosterController→App.Poster.Source.PosterSource
- Direction
- App.Controller uses App.Poster.Source, so a change to App.Poster.Source can break App.Controller, while a change to App.Controller can't break App.Poster.Source.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→16 App.Controller uses App.Poster.Wall✕
- Connections
- 4 pairs of types, where a type in App.Controller uses a type in App.Poster.Wall.
- The types involved
App.Controller.PosterImageController→App.Poster.Wall.PosterWallServiceApp.Controller.PosterWallController→App.Poster.Wall.NowPlayingServiceApp.Controller.PosterWallController→App.Poster.Wall.PosterWallServiceApp.Controller.PosterWallController→App.Poster.Wall.StreamToken
- Direction
- App.Controller uses App.Poster.Wall, so a change to App.Poster.Wall can break App.Controller, while a change to App.Controller can't break App.Poster.Wall.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→17 App.Controller uses App.Plex.Connection✕
- Connections
- 3 pairs of types, where a type in App.Controller uses a type in App.Plex.Connection.
- The types involved
App.Controller.PlexConnectionController→App.Plex.Connection.PlexConnectionStateApp.Controller.PlexConnectionController→App.Plex.Connection.PlexConnectionStatusApp.Controller.PlexConnectionController→App.Plex.Connection.PlexSignInService
- Direction
- App.Controller uses App.Plex.Connection, so a change to App.Plex.Connection can break App.Controller, while a change to App.Controller can't break App.Plex.Connection.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→18 App.Controller uses App.Plex.Import✕
- Connections
- 1 pair of types, where a type in App.Controller uses a type in App.Plex.Import.
- The types involved
App.Controller.PlexImportController→App.Plex.Import.ImportService
- Direction
- App.Controller uses App.Plex.Import, so a change to App.Plex.Import can break App.Controller, while a change to App.Controller can't break App.Plex.Import.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→19 App.Controller uses App.Plex.Orphan✕
- Connections
- 1 pair of types, where a type in App.Controller uses a type in App.Plex.Orphan.
- The types involved
App.Controller.OrphanController→App.Plex.Orphan.OrphanService
- Direction
- App.Controller uses App.Plex.Orphan, so a change to App.Plex.Orphan can break App.Controller, while a change to App.Controller can't break App.Plex.Orphan.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→20 App.Controller uses App.Settings✕
- Connections
- 4 pairs of types, where a type in App.Controller uses a type in App.Settings.
- The types involved
App.Controller.PlexConnectionController→App.Settings.SupersededEnvironmentApp.Controller.SettingsController→App.Settings.SettingsFormApp.Controller.SettingsController→App.Settings.SettingsStoreApp.Controller.SettingsController→App.Settings.SupersededEnvironment
- Direction
- App.Controller uses App.Settings, so a change to App.Settings can break App.Controller, while a change to App.Controller can't break App.Settings.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→21 App.Controller uses App.Config✕
- Connections
- 3 pairs of types, where a type in App.Controller uses a type in App.Config.
- The types involved
App.Controller.GalleryController→App.Config.PlexConfigApp.Controller.GalleryController→App.Config.PosterConfigApp.Controller.PlexImportController→App.Config.LibraryExclusions
- Direction
- App.Controller uses App.Config, so a change to App.Config can break App.Controller, while a change to App.Controller can't break App.Config.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→22 App.Controller uses App.Auth✕
- Connections
- 2 pairs of types, where a type in App.Controller uses a type in App.Auth.
- The types involved
App.Controller.AuthController→App.Auth.SessionAuthenticatorApp.Controller.PlexConnectionController→App.Auth.SessionAuthenticator
- Direction
- App.Controller uses App.Auth, so a change to App.Auth can break App.Controller, while a change to App.Controller can't break App.Auth.
- Position
- Below the diagonal: App.Controller uses a module listed above it, which is the healthy direction.
25→24 App.Controller uses App.Poster.Edit✕
- Connections
- 1 pair of types, where a type in App.Controller uses a type in App.Poster.Edit.
- The types involved
App.Controller.ChangePosterController→App.Poster.Edit.ChangePosterService
- Direction
- App.Controller uses App.Poster.Edit, so a change to App.Poster.Edit can break App.Controller, while a change to App.Controller can't break App.Poster.Edit.
- Position
- Below the diagonal: App.Controller 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 — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 42 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A02:2025 — Security Misconfiguration | 3 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate; Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. | +1.6 pts | Low | ADR Quality |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +2.4 pts | Medium | Keyboard semantics |
| Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate. | +1.9 pts | Medium | Security & performance tooling |
| Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail. | +1.9 pts | Medium | Outbound HTTP resilience |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +1.5 pts | Medium | Page structure |
| 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. | +1.5 pts | Medium | Architecture documentation |
| Resolve the 1 Small-team knowledge concentration finding(s) in Bus Factor. | +0.3 pts | Low | Bus Factor |
| Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands. | +0.7 pts | Medium | Web-Security Posture |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| public/assets/gallery.js | 7.0 | Mixed | Cyclomatic Complexity: (anonymous) (cyclomatic 201) |
| src/Plex/HttpPlexClient.php | 7.2 | Mixed | God Classes: TooManyMethods: HttpPlexClient |
| src/Plex/Connection/PlexConnectionStore.php | 7.2 | Mixed | Code Duplication: Edited copy of a member (30 corresponding lines) |
| src/Controller/ChangePosterController.php | 7.4 | Mixed | Code Duplication: Edited copy of a member (15 corresponding lines) |
| src/Controller/GalleryController.php | 7.8 | Mixed | Cyclomatic Complexity: GalleryController.show (cyclomatic 17) |
| src/Database/PlexItemRepository.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 59 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, 121 of 138 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — 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. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (15589 LoC, 134 module-visible types across 24 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Auth/AuthMiddleware.php`, `src/Auth/CsrfGuard.php`, `src/Auth/CsrfMiddleware.php`, `src/Auth/PlexConnectionMiddleware.php`, `src/Auth/SessionAuthenticator.php`, … (+82 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is PHP-DI, whose lifetimes are not modelled 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.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (src/Database/Database.php:34), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (src/Database/Database.php:34), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (src/Database/Database.php:34), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (src/Database/Database.php:34), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was (anonymous) at 201. A further 2 method(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 SettingKey.variable at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Settings/SettingKey.php (SettingKey.variable at 18). 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 4 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with (anonymous) (cyclomatic 201), gallery.document.addEventListener("DOMContentLoaded") (cyclomatic 196), (anonymous) (cyclomatic 121). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 6.7 to about 8.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was (anonymous) at 236.
What to do
- Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with (anonymous) (cognitive 236), gallery.document.addEventListener("DOMContentLoaded") (cognitive 214), (anonymous) (cognitive 123). — 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 10 together lifts Cognitive Complexity from 6.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with gallery.js (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with gallery.js. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with bootstrap.php. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
6 duplicated block group(s) detected. 2.8 % of the production lines (339 of 12,184) are in a reported copy. A further 12 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with ChangePosterController.php, HttpPlexClient.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with PlexItemRepository.php, PosterWallController.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with ChangePosterController.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
11 production modules (source-import), 1 dependency cycle(s), 2 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 2 module(s) off the main sequence, with abstractness counted on 10 of the 11 (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).
- Resolve the 1 Circular dependency finding(s) in Coupling — start with PlexConnectionMiddleware.php. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Unstable project src finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 60 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with SettingsForm.php. — One of this dimension's main actionable groups (1 warning-level).
D10 · Test Quality
1 skipped (1 with a documented reason), 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1190 tests.
What to do
- Resolve the 1 No assertions finding(s) in Test Quality — start with DesignTokenContractTest.php. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
3 outdated, 0 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 26 locked Composer package(s) use a banned license. Licences were read from this repository's composer.lock, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 57 package(s) under `packages-dev` are not installed for a consumer and are excluded.
D15 · Churn × Complexity Hotspots
Top hotspots: public/assets/gallery.js (15×196=2940); src/Controller/GalleryController.php (5×17=85)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with gallery.js, GalleryController.php. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
23 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Plex/Import/ImportService.php. Counted over 65 of the 130 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 12184 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 209 judged comments only repeat the code they sit on (0.0 %).
D27 · Navigability
45 % of calls cross a namespace and 10 % go through an interface, but 49 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
42 finding(s): 0 critical, 21 high, 21 medium, 0 low. 16 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 88 file(s) — `src/Auth/AuthMiddleware.php` (line 84, line 85), `src/Auth/CsrfGuard.php` (line 30), `src/Auth/CsrfMiddleware.php` (line 43), `src/Auth/PlexConnectionMiddleware.php` (line 76), `src/Auth/SessionAuthenticator.php` (line 25, line 26), … (+83 more) — 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 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 16 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (16 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
3 finding(s): 0 critical, 1 high, 2 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 65 of the 130 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 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).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 5 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
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — templates/wall.html.twig:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — REDACTED:390
- The repo's own CSS styles .card__image with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — REDACTED:21, REDACTED:204
- The repo's own CSS styles .btn with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — REDACTED:52
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — templates/partials/_overlays.html.twig:75
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AX10 · Code composition
AX3 · Project dependency cycles
- The projects src/Auth → src/Config → src/Plex → src/Auth (one cycle inside a mutually-dependent group of 7 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — src/Auth/PlexConnectionMiddleware.php:7
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
- `REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
What to do
- Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `new Client(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/bootstrap.php:122
What to do
- Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.
S1 · Web-Security Posture
- 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 configured — defense in depth, even when a reverse proxy could set them. This is reported because `marquee.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — docker/root/etc/nginx/http.d/marquee.conf:17
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X14 · Bypassable address classification
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
- `get` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — libxml's internal-error mode (changed at line 539, put back at line 541) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path. — src/Plex/HttpPlexClient.php:518
- `readOwner` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — libxml's internal-error mode (changed at line 95, put back at line 97) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path. — src/Plex/Connection/PlexServerOwner.php:93
What to do
- Each finding names the statement that changes the process-global value and the statement that puts it back. Confirm from the two that nothing between them is protected — then prefer removing the mutation over widening the restore: a working directory or an environment variable passed to the operation that needs it (the `cwd` and `env` options of `child_process`, or of `Deno.Command`) is scoped to that operation, which is what the save-and-restore was trying to approximate. Where the global genuinely must move, a `try`/`finally` is the least that makes the restore unconditional. In PHP the same holds for `chdir`, `putenv`, `setlocale`, `date_default_timezone_set`, `ini_set` and the error-handler stack: pass the value to the operation (`Process` with `cwd`/`env`, an explicit `DateTimeZone`) or restore in a `finally`.
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — src/Version/GitHubLatestReleaseProvider.php:41, src/Plex/Import/ImportService.php:320
- `.catch(function(){})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×9) — public/assets/app.js:8, public/assets/app.js:46, public/assets/gallery.js:2034, …
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — public/assets/gallery.js:1181
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 78.7 | Strong | Strongest area. |
| Architecture | 89.7 | Adequate — gated by D5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 67.8 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 63.7 | Adequate — gated by P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 69.6 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 63.9 | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'PDO' (src/Database/Database.php:34) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'PDO' (src/Database/Database.php:34) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'PDO' (src/Database/Database.php:34) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 check(s) not relevant to this codebase
- AX1 Captive dependencies — 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
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. PHP builds its object graph per request and shares none of it between requests. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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) — 10 | >>> --no-dev --no-scripts --no-interaction \ 11 | >>> --prefer-dist --optimize-autoloader \ 12 | >>> --ignore-platform-reqs 13 | -------------------- ERROR: failed to solve: process "/bin/sh -c composer install --no-dev --no-scripts --no-interaction --prefer-dist --optimize-autoloader --ignore-platform-reqs" did not complete successfully: exit code: 100; likely cause (the repository): a RUN step of the repository's REDACTED exited with code 100 (`/bin/sh -c composer install --no-dev --no-scripts --no-interaction --prefer-dist --optimize-autoloader --ign…`): the build's own command failed, for example a compile or test error; runtime evidence skipped The cause is in the repository, not in our sandbox: a RUN step of the repository's REDACTED exited with code 100 (`/bin/sh -c composer install --no-dev --no-scripts --no-interaction --prefer-dist --optimize-autoloader --ign…`): the build's own command failed, for example a compile or test error. Nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: this repository stores data through 'PDO' (src/Database/Database.php:34) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 87 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (48 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, 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
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 22% of this repository's production lines — php (12,184 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 22% of this repository's production lines — php (12,184 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — 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 — 28 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Clickable element isn't keyboard-operable REDACTED:21
- Clickable element isn't keyboard-operable REDACTED:52
- Clickable element isn't keyboard-operable REDACTED:204
- Click handler on a non-interactive <div> templates/partials/_overlays.html.twig:75
- Project dependency cycle src/Auth/PlexConnectionMiddleware.php:7
- REDACTED
- REDACTED
- Circular dependency src/Auth/PlexConnectionMiddleware.php:7
Serious — 92 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (empty catch) public/assets/app.js:8
- Swallowed exception (empty catch) public/assets/app.js:46
- Swallowed exception (empty catch) public/assets/gallery.js:1181
- Swallowed exception (empty catch) public/assets/gallery.js:2034
- Swallowed exception (empty catch) public/assets/gallery.js:2151
- Swallowed exception (empty catch) public/assets/gallery.js:2319
- Swallowed exception (empty catch) public/assets/gallery.js:2365
- Swallowed exception (empty catch) public/assets/gallery.js:2895
- Swallowed exception (empty catch) public/assets/wall.js:39
- Swallowed exception (empty catch) public/assets/wall.js:154
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: gallery.document.addEventListener("DOMContentLoaded") public/assets/gallery.js:1911
- FunctionTooLong: gallery.document.addEventListener("alpine:init") public/assets/gallery.js:978
- FunctionTooLong: gallery.document.addEventListener("alpine:init") public/assets/gallery.js:787
- gallery.document.addEventListener("alpine:init") (cyclomatic 109) public/assets/gallery.js:978
- gallery.document.addEventListener("alpine:init") (cyclomatic 26) public/assets/gallery.js:787
- Hotspot: public/assets/gallery.js public/assets/gallery.js:1911
- Hotspot: src/Controller/GalleryController.php src/Controller/GalleryController.php:50
- gallery.document.addEventListener("alpine:init") (cognitive 98) public/assets/gallery.js:978
- gallery.document.addEventListener("alpine:init") (cognitive 30) public/assets/gallery.js:787
- REDACTED
- REDACTED
- Edited copy of a member (11 corresponding lines) src/Controller/ChangePosterController.php:103
- Edited copy of a member (11 corresponding lines) src/Plex/HttpPlexClient.php:70
- Edited copy of a member (10 corresponding lines) src/Database/PlexItemRepository.php:283
- Edited copy of a member (10 corresponding lines) src/Controller/PosterWallController.php:66
- Off the main sequence: src/Version
- Off the main sequence: src/Support
- Process-global state is restored only on the happy path src/Plex/HttpPlexClient.php:518
- Process-global state is restored only on the happy path src/Plex/Connection/PlexServerOwner.php:93
- Swallowed exception (caught, then discarded) src/Version/GitHubLatestReleaseProvider.php:41
- Swallowed exception (caught, then discarded) src/Plex/Import/ImportService.php:320
- Page without a main landmark templates/wall.html.twig:2
- Modal dialog does not manage focus REDACTED:390
- (anonymous) (cyclomatic 201) public/assets/gallery.js:1911
- gallery.document.addEventListener("DOMContentLoaded") (cyclomatic 196) public/assets/gallery.js:1911
- (anonymous) (cyclomatic 121) public/assets/gallery.js:978
- (anonymous) (cyclomatic 29) public/assets/gallery.js:787
- GalleryController.show (cyclomatic 17) src/Controller/GalleryController.php:50
- No assertions: testEveryDurationComesFromTheScale tests/Unit/Asset/DesignTokenContractTest.php:262
- (anonymous) (cognitive 236) public/assets/gallery.js:1911
- gallery.document.addEventListener("DOMContentLoaded") (cognitive 214) public/assets/gallery.js:1911
- (anonymous) (cognitive 123) public/assets/gallery.js:978
- (anonymous) (cognitive 37) public/assets/gallery.js:787
- OrphanService.collectCurrentRatingKeys (cognitive 33) src/Plex/Orphan/OrphanService.php:133
- ImportService.importLibrary (cognitive 22) src/Plex/Import/ImportService.php:59
- Page.paginationWindow (cognitive 17) src/Poster/Page.php:73
- GalleryController.show (cognitive 16) src/Controller/GalleryController.php:50
- REDACTED
- FileTooLong: assets/gallery.js public/assets/gallery.js
- MethodTooLong: bootstrap.buildContainer src/bootstrap.php:77
- TooManyMethods: HttpPlexClient src/Plex/HttpPlexClient.php:19
- REDACTED
- Edited copy of a member (15 corresponding lines) src/Controller/ChangePosterController.php:81
- Edited copy of a member (30 corresponding lines) src/Plex/Connection/PlexConnectionStore.php:216
- Edited copy of a member (16 corresponding lines) src/Plex/Connection/PlexConnectionStore.php:259
- Edited copy of a member (13 corresponding lines) src/Settings/SettingsStore.php:95
- Edited copy of a member (9 corresponding lines) src/Plex/HttpPlexClient.php:215
- Edited copies of one member (3 members, 12+ corresponding lines) src/Controller/PlexImportController.php:105
- Edited copy of a member (12 corresponding lines) src/Database/PlexItemRepository.php:138
- Edited copy of a member (6 corresponding lines) src/Database/PlexItemRecord.php:57
- Duplicated block (24–25 lines × 2) src/Plex/Connection/PlexConnectionStore.php:216
- Duplicated block (10 lines × 2) src/Plex/HttpPlexClient.php:242
- Duplicated block (9 lines × 2) src/Poster/Edit/ChangePosterService.php:103
- Duplicated block (8 lines × 2) src/Controller/ChangePosterController.php:66
- Duplicated block (7 lines × 2) src/Plex/Connection/PlexConnectionStore.php:202
- Duplicated block (11 lines × 2) src/Auth/AuthMiddleware.php:150
- Unstable project src
- Unstable project src/Controller
- Low cohesion: SettingsForm (LCOM4 4) src/Settings/SettingsForm.php:33
- Test suite runs only after the merge
- SAST runs, but gates no merge
- Outbound HTTP without resilience src/bootstrap.php:122
Minor — 14 finding(s)
- Silent fallback default on parse failure src/Config/PlexConfig.php:100
- Silent fallback default on parse failure src/Plex/Connection/PlexConnectionStore.php:228
- Silent fallback default on parse failure src/Settings/SettingsStore.php:257
- Duplicated predicate src/Plex/Connection/PlexConnectionStore.php:272
- Duplicated predicate src/Controller/ChangePosterController.php:476
- Small-team knowledge concentration
- No ADRs found composer.json:4
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No security response headers detected docker/root/etc/nginx/http.d/marquee.conf:17
Minor — 4 finding(s)
- Outdated: monolog/monolog
- Outdated: slim/psr7
- Outdated: slim/slim
- Skipped (documented): testATrayInsideGlassChromeIsTeleportedOutOfIt tests/Unit/Asset/TrayDismissalTest.php:107
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-779429f95fdf497ba20e1a5acc5dc196/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=353" --report-format json --report-path /tmp/watchdog-gitleaks-779429f95fdf497ba20e1a5acc5dc196/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-779429f95fdf497ba20e1a5acc5dc196/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 42 | 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 . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | 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. semgrep could not parse 87 file(s) — `src/Auth/AuthMiddleware.php`, `src/Auth/CsrfGuard.php`, `src/Auth/CsrfMiddleware.php`, `src/Auth/PlexConnectionMiddleware.php`, `src/Auth/SessionAuthenticator.php`, … (+82 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |