Executive summary
software-mansion/live-debugger is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no access checks on the code's endpoints or handlers and 31 of the dependencies have a known vulnerability. It scores 38 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 15, is the weakest lens and counts most in the score. The best first steps are adding access checks and moving the keys out of the code, each worth about 13 points. Raising Security and Compliance to 70 would lift the score to about 57.
Thirty-three known security holes in the packages the code depends on can be used by attackers. Twenty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and eight controls can't be used without a mouse. Updating the vulnerable packages, pinning each tool to an exact version and making the controls work with a keyboard would close these risks. Limiting each secret to its own step would fix the four secrets exposed to more of the pipeline than needed. The button or link with no name needs a name, even when it only shows an icon.
The product code is 21,531 lines, about €27,000 to rebuild.
If Security and Compliance rose from 15 to 70, the lowest score rated Strong, the score would rise from 38 to about 57.
New since the last survey: 25 findings
- Code Duplication · Edited copy of a member (37 corresponding lines) lib/live_debugger/app/debugger/callback_tracing/web/global_traces_live.ex
- Code Duplication · Edited copy of a member (16 corresponding lines) lib/live_debugger/app/debugger/callback_tracing/web/hook_components/load_more_button.ex
- Code Duplication · Edited copy of a member (7 corresponding lines) lib/live_debugger/app/web/live_components/live_dropdown.ex
- Code Duplication · Edited copy of a member (12 corresponding lines) lib/live_debugger/services/garbage_collector/actions/garbage_collecting.ex
- Code Duplication · Edited copy of a member (11 corresponding lines) lib/live_debugger/app/debugger/components_tree/web/components_tree_live.ex
- Code Duplication · Edited copy of a member (6 corresponding lines) lib/live_debugger/app/debugger/callback_tracing/web/hook_components/load_more_button.ex
- Code Duplication · Edited copy of a member (6 corresponding lines) lib/live_debugger/app/debugger/queries/lv_process.ex
- Code Duplication · Edited copy of a member (4 corresponding lines) lib/live_debugger/app/debugger/callback_tracing/web/global_traces_live.ex
- Code Duplication · Edited copy of a member (8 corresponding lines) lib/live_debugger/app/debugger/associated_live_views/web/associated_live_views_live.ex
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Hygiene · Unused dependency 'phoenix_live_view'
- Dependency Hygiene · Unused dependency 'embla-carousel'
- Web-Security Posture · Third-party script without Subresource Integrity dev/layout.ex
- Exception handling · Swallowed exception (empty catch) landing/src/components/TopBarBanner/TopBarBannerClient.tsx
- Exception handling · Swallowed exception (empty catch) landing/src/components/TopBarBanner/TopBarBannerClient.tsx
- Exception handling · Swallowed exception (empty catch) landing/src/components/TopBarBanner/TopBarBannerClient.tsx
- Text alternatives · <canvas> without a text alternative lib/live_debugger/app/debugger/resources/components/chart.ex
- Forms & labels · <input> without a programmatic label lib/live_debugger/app/debugger/components.ex
- Forms & labels · Custom control with no accessible name on <div> lib/live_debugger/app/web/components.ex
- Page structure · More than one main landmark dev/layout.ex
- Page structure · Viewport restricts zoom lib/live_debugger/app/web/layout.ex
- Keyboard semantics · Click handler on a non-interactive <div> lib/live_debugger/app/web/components.ex
- Keyboard semantics · Click handler on a non-interactive <div> lib/live_debugger/app/web/live_components/live_dropdown.ex
Fixed since the last survey: 9 findings
- Secret Scanning · Leaked secret: high-entropy-secret dev/runner.ex
- Secret Scanning · Leaked secret: signing-key dev/runner.ex
- Dependency Vulnerabilities · High CVE: [CVE redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [CVE redacted] REDACTED
- Platform End-of-Life · End-of-life runtime: Node.js 20 .tool-versions
- Exception handling · Swallowed exception (empty catch) landing/src/components/TopBarBanner/TopBarBannerClient.tsx
- Exception handling · Swallowed exception (empty catch) landing/src/components/TopBarBanner/TopBarBannerClient.tsx
- Exception handling · Swallowed exception (empty catch) landing/src/components/TopBarBanner/TopBarBannerClient.tsx
- A11y enforcement · Accessibility enforcement below the top rung landing/package.json
Rebuild cost: about €27,000 · Estimate
| Cost to rebuild | €9,100 to €46,000, for 151 to 480 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 38. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 21,531 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 LiveDebugger | 3 LiveDebugger.API | 4 LiveDebugger.API.System | 5 landing.src.components.TopBarBanner.TopBarBannerClient | 6 landing.src.components.ui | 7 LiveDebugger.API.LiveViewDebug | 8 LiveDebugger.API.LiveViewDiscovery | 9 LiveDebugger.API.SettingsStorage | 10 LiveDebugger.API.StatesStorage | 11 LiveDebugger.API.System.Dbg | 12 LiveDebugger.API.System.FileSystem | 13 LiveDebugger.API.System.Module | 14 LiveDebugger.API.System.ProcessInfo | 15 LiveDebugger.API.TracesStorage | 16 LiveDebugger.API.UserEvents | 17 LiveDebugger.App | 18 LiveDebugger.App.Debugger | 19 LiveDebugger.App.Debugger.AssociatedLiveViews.Web | 20 LiveDebugger.App.Debugger.AsyncJobs | 21 LiveDebugger.App.Debugger.AsyncJobs.Web | 22 LiveDebugger.App.Debugger.CallbackTracing.Web | 23 LiveDebugger.App.Debugger.CallbackTracing.Web.Components | 24 LiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents | 25 LiveDebugger.App.Debugger.CallbackTracing.Web.Hooks | 26 LiveDebugger.App.Debugger.CallbackTracing.Web.LiveComponents | 27 LiveDebugger.App.Debugger.ComponentsTree.Web | 28 LiveDebugger.App.Debugger.NodeState.Web | 29 LiveDebugger.App.Debugger.NodeState.Web.HookComponents | 30 LiveDebugger.App.Debugger.NodeState.Web.Hooks | 31 LiveDebugger.App.Debugger.Resources | 32 LiveDebugger.App.Debugger.Resources.Components | 33 LiveDebugger.App.Debugger.Resources.Web | 34 LiveDebugger.App.Debugger.Streams.Web | 35 LiveDebugger.App.Debugger.Streams.Web.Hooks | 36 LiveDebugger.App.Debugger.Web | 37 LiveDebugger.App.Debugger.Web.Components | 38 LiveDebugger.App.Debugger.Web.HookComponents | 39 LiveDebugger.App.Debugger.Web.Hooks | 40 LiveDebugger.App.Debugger.Web.LiveComponents |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 LiveDebugger | ||||||||||||||||||||||||||||||||||||||||
| 3 LiveDebugger.API | ||||||||||||||||||||||||||||||||||||||||
| 4 LiveDebugger.API.System | ||||||||||||||||||||||||||||||||||||||||
| 5 landing.src.components.TopBarBanner.TopBarBannerClient | ||||||||||||||||||||||||||||||||||||||||
| 6 landing.src.components.ui | ||||||||||||||||||||||||||||||||||||||||
| 7 LiveDebugger.API.LiveViewDebug | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 LiveDebugger.API.LiveViewDiscovery | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 LiveDebugger.API.SettingsStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 LiveDebugger.API.StatesStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 LiveDebugger.API.System.Dbg | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 LiveDebugger.API.System.FileSystem | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 LiveDebugger.API.System.Module | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 LiveDebugger.API.System.ProcessInfo | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 LiveDebugger.API.TracesStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 LiveDebugger.API.UserEvents | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 LiveDebugger.App | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 LiveDebugger.App.Debugger | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 LiveDebugger.App.Debugger.AssociatedLiveViews.Web | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 LiveDebugger.App.Debugger.AsyncJobs | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 LiveDebugger.App.Debugger.AsyncJobs.Web | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 LiveDebugger.App.Debugger.CallbackTracing.Web | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 LiveDebugger.App.Debugger.CallbackTracing.Web.Components | 3 | |||||||||||||||||||||||||||||||||||||||
| 24 LiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents | 9 | |||||||||||||||||||||||||||||||||||||||
| 25 LiveDebugger.App.Debugger.CallbackTracing.Web.Hooks | 4 | |||||||||||||||||||||||||||||||||||||||
| 26 LiveDebugger.App.Debugger.CallbackTracing.Web.LiveComponents | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 LiveDebugger.App.Debugger.ComponentsTree.Web | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 LiveDebugger.App.Debugger.NodeState.Web | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 LiveDebugger.App.Debugger.NodeState.Web.HookComponents | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 LiveDebugger.App.Debugger.NodeState.Web.Hooks | 3 | |||||||||||||||||||||||||||||||||||||||
| 31 LiveDebugger.App.Debugger.Resources | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 LiveDebugger.App.Debugger.Resources.Components | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 LiveDebugger.App.Debugger.Resources.Web | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 LiveDebugger.App.Debugger.Streams.Web | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 LiveDebugger.App.Debugger.Streams.Web.Hooks | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 LiveDebugger.App.Debugger.Web | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 LiveDebugger.App.Debugger.Web.Components | 3 | |||||||||||||||||||||||||||||||||||||||
| 38 LiveDebugger.App.Debugger.Web.HookComponents | 2 | |||||||||||||||||||||||||||||||||||||||
| 39 LiveDebugger.App.Debugger.Web.Hooks | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 LiveDebugger.App.Debugger.Web.LiveComponents | 3 |
7→3 LiveDebugger.API.LiveViewDebug uses LiveDebugger.API✕
- Connections
- 1 pair of types, where a type in LiveDebugger.API.LiveViewDebug uses a type in LiveDebugger.API.
- The types involved
LiveDebugger.API.LiveViewDebug.Impl→LiveDebugger.API.LiveViewDebug
- Direction
- LiveDebugger.API.LiveViewDebug uses LiveDebugger.API, so a change to LiveDebugger.API can break LiveDebugger.API.LiveViewDebug, while a change to LiveDebugger.API.LiveViewDebug can't break LiveDebugger.API.
- Position
- Below the diagonal: LiveDebugger.API.LiveViewDebug uses a module listed above it, which is the healthy direction.
8→3 LiveDebugger.API.LiveViewDiscovery uses LiveDebugger.API✕
- Connections
- 1 pair of types, where a type in LiveDebugger.API.LiveViewDiscovery uses a type in LiveDebugger.API.
- The types involved
LiveDebugger.API.LiveViewDiscovery.Impl→LiveDebugger.API.LiveViewDiscovery
- Direction
- LiveDebugger.API.LiveViewDiscovery uses LiveDebugger.API, so a change to LiveDebugger.API can break LiveDebugger.API.LiveViewDiscovery, while a change to LiveDebugger.API.LiveViewDiscovery can't break LiveDebugger.API.
- Position
- Below the diagonal: LiveDebugger.API.LiveViewDiscovery uses a module listed above it, which is the healthy direction.
9→3 LiveDebugger.API.SettingsStorage uses LiveDebugger.API✕
- Connections
- 1 pair of types, where a type in LiveDebugger.API.SettingsStorage uses a type in LiveDebugger.API.
- The types involved
LiveDebugger.API.SettingsStorage.Impl→LiveDebugger.API.SettingsStorage
- Direction
- LiveDebugger.API.SettingsStorage uses LiveDebugger.API, so a change to LiveDebugger.API can break LiveDebugger.API.SettingsStorage, while a change to LiveDebugger.API.SettingsStorage can't break LiveDebugger.API.
- Position
- Below the diagonal: LiveDebugger.API.SettingsStorage uses a module listed above it, which is the healthy direction.
10→3 LiveDebugger.API.StatesStorage uses LiveDebugger.API✕
- Connections
- 1 pair of types, where a type in LiveDebugger.API.StatesStorage uses a type in LiveDebugger.API.
- The types involved
LiveDebugger.API.StatesStorage.Impl→LiveDebugger.API.StatesStorage
- Direction
- LiveDebugger.API.StatesStorage uses LiveDebugger.API, so a change to LiveDebugger.API can break LiveDebugger.API.StatesStorage, while a change to LiveDebugger.API.StatesStorage can't break LiveDebugger.API.
- Position
- Below the diagonal: LiveDebugger.API.StatesStorage uses a module listed above it, which is the healthy direction.
11→4 LiveDebugger.API.System.Dbg uses LiveDebugger.API.System✕
- Connections
- 1 pair of types, where a type in LiveDebugger.API.System.Dbg uses a type in LiveDebugger.API.System.
- The types involved
LiveDebugger.API.System.Dbg.Impl→LiveDebugger.API.System.Dbg
- Direction
- LiveDebugger.API.System.Dbg uses LiveDebugger.API.System, so a change to LiveDebugger.API.System can break LiveDebugger.API.System.Dbg, while a change to LiveDebugger.API.System.Dbg can't break LiveDebugger.API.System.
- Position
- Below the diagonal: LiveDebugger.API.System.Dbg uses a module listed above it, which is the healthy direction.
12→4 LiveDebugger.API.System.FileSystem uses LiveDebugger.API.System✕
- Connections
- 1 pair of types, where a type in LiveDebugger.API.System.FileSystem uses a type in LiveDebugger.API.System.
- The types involved
LiveDebugger.API.System.FileSystem.Impl→LiveDebugger.API.System.FileSystem
- Direction
- LiveDebugger.API.System.FileSystem uses LiveDebugger.API.System, so a change to LiveDebugger.API.System can break LiveDebugger.API.System.FileSystem, while a change to LiveDebugger.API.System.FileSystem can't break LiveDebugger.API.System.
- Position
- Below the diagonal: LiveDebugger.API.System.FileSystem uses a module listed above it, which is the healthy direction.
13→4 LiveDebugger.API.System.Module uses LiveDebugger.API.System✕
- Connections
- 1 pair of types, where a type in LiveDebugger.API.System.Module uses a type in LiveDebugger.API.System.
- The types involved
LiveDebugger.API.System.Module.Impl→LiveDebugger.API.System.Module
- Direction
- LiveDebugger.API.System.Module uses LiveDebugger.API.System, so a change to LiveDebugger.API.System can break LiveDebugger.API.System.Module, while a change to LiveDebugger.API.System.Module can't break LiveDebugger.API.System.
- Position
- Below the diagonal: LiveDebugger.API.System.Module uses a module listed above it, which is the healthy direction.
14→4 LiveDebugger.API.System.ProcessInfo uses LiveDebugger.API.System✕
- Connections
- 1 pair of types, where a type in LiveDebugger.API.System.ProcessInfo uses a type in LiveDebugger.API.System.
- The types involved
LiveDebugger.API.System.ProcessInfo.Impl→LiveDebugger.API.System.ProcessInfo
- Direction
- LiveDebugger.API.System.ProcessInfo uses LiveDebugger.API.System, so a change to LiveDebugger.API.System can break LiveDebugger.API.System.ProcessInfo, while a change to LiveDebugger.API.System.ProcessInfo can't break LiveDebugger.API.System.
- Position
- Below the diagonal: LiveDebugger.API.System.ProcessInfo uses a module listed above it, which is the healthy direction.
15→3 LiveDebugger.API.TracesStorage uses LiveDebugger.API✕
- Connections
- 1 pair of types, where a type in LiveDebugger.API.TracesStorage uses a type in LiveDebugger.API.
- The types involved
LiveDebugger.API.TracesStorage.Impl→LiveDebugger.API.TracesStorage
- Direction
- LiveDebugger.API.TracesStorage uses LiveDebugger.API, so a change to LiveDebugger.API can break LiveDebugger.API.TracesStorage, while a change to LiveDebugger.API.TracesStorage can't break LiveDebugger.API.
- Position
- Below the diagonal: LiveDebugger.API.TracesStorage uses a module listed above it, which is the healthy direction.
16→3 LiveDebugger.API.UserEvents uses LiveDebugger.API✕
- Connections
- 1 pair of types, where a type in LiveDebugger.API.UserEvents uses a type in LiveDebugger.API.
- The types involved
LiveDebugger.API.UserEvents.Impl→LiveDebugger.API.UserEvents
- Direction
- LiveDebugger.API.UserEvents uses LiveDebugger.API, so a change to LiveDebugger.API can break LiveDebugger.API.UserEvents, while a change to LiveDebugger.API.UserEvents can't break LiveDebugger.API.
- Position
- Below the diagonal: LiveDebugger.API.UserEvents uses a module listed above it, which is the healthy direction.
17→2 LiveDebugger.App uses LiveDebugger✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App uses a type in LiveDebugger.
- The types involved
LiveDebugger.App.Events→LiveDebugger.Event
- Direction
- LiveDebugger.App uses LiveDebugger, so a change to LiveDebugger can break LiveDebugger.App, while a change to LiveDebugger.App can't break LiveDebugger.
- Position
- Below the diagonal: LiveDebugger.App uses a module listed above it, which is the healthy direction.
18→2 LiveDebugger.App.Debugger uses LiveDebugger✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger uses a type in LiveDebugger.
- The types involved
LiveDebugger.App.Debugger.Events→LiveDebugger.Event
- Direction
- LiveDebugger.App.Debugger uses LiveDebugger, so a change to LiveDebugger can break LiveDebugger.App.Debugger, while a change to LiveDebugger.App.Debugger can't break LiveDebugger.
- Position
- Below the diagonal: LiveDebugger.App.Debugger uses a module listed above it, which is the healthy direction.
18→17 LiveDebugger.App.Debugger uses LiveDebugger.App✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Components→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger, while a change to LiveDebugger.App.Debugger can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger uses a module listed above it, which is the healthy direction.
19→17 LiveDebugger.App.Debugger.AssociatedLiveViews.Web uses LiveDebugger.App✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger.AssociatedLiveViews.Web uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.AssociatedLiveViews.Web.AssociatedLiveViewsLive→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.AssociatedLiveViews.Web uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.AssociatedLiveViews.Web, while a change to LiveDebugger.App.Debugger.AssociatedLiveViews.Web can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.AssociatedLiveViews.Web uses a module listed above it, which is the healthy direction.
20→17 LiveDebugger.App.Debugger.AsyncJobs uses LiveDebugger.App✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger.AsyncJobs uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.AsyncJobs.Components→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.AsyncJobs uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.AsyncJobs, while a change to LiveDebugger.App.Debugger.AsyncJobs can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.AsyncJobs uses a module listed above it, which is the healthy direction.
21→17 LiveDebugger.App.Debugger.AsyncJobs.Web uses LiveDebugger.App✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger.AsyncJobs.Web uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.AsyncJobs.Web.AsyncJobsLive→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.AsyncJobs.Web uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.AsyncJobs.Web, while a change to LiveDebugger.App.Debugger.AsyncJobs.Web can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.AsyncJobs.Web uses a module listed above it, which is the healthy direction.
22→17 LiveDebugger.App.Debugger.CallbackTracing.Web uses LiveDebugger.App✕
- Connections
- 2 pairs of types, where a type in LiveDebugger.App.Debugger.CallbackTracing.Web uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.CallbackTracing.Web.GlobalTracesLive→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.NodeTracesLive→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.CallbackTracing.Web uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.CallbackTracing.Web, while a change to LiveDebugger.App.Debugger.CallbackTracing.Web can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.CallbackTracing.Web uses a module listed above it, which is the healthy direction.
23→17 LiveDebugger.App.Debugger.CallbackTracing.Web.Components uses LiveDebugger.App✕
- Connections
- 3 pairs of types, where a type in LiveDebugger.App.Debugger.CallbackTracing.Web.Components uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.CallbackTracing.Web.Components.Filters→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.Components.Trace→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.Components.TraceSettings→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.CallbackTracing.Web.Components uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.CallbackTracing.Web.Components, while a change to LiveDebugger.App.Debugger.CallbackTracing.Web.Components can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.CallbackTracing.Web.Components uses a module listed above it, which is the healthy direction.
24→17 LiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents uses LiveDebugger.App✕
- Connections
- 9 pairs of types, where a type in LiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents.ClearButton→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents.FiltersFullscreen→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents.FiltersSidebar→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents.LoadMoreButton→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents.RefreshButton→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents.SearchInput→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents.Stream→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents.ToggleTracingButton→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents.TraceWrapper→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents, while a change to LiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.CallbackTracing.Web.HookComponents uses a module listed above it, which is the healthy direction.
25→17 LiveDebugger.App.Debugger.CallbackTracing.Web.Hooks uses LiveDebugger.App✕
- Connections
- 4 pairs of types, where a type in LiveDebugger.App.Debugger.CallbackTracing.Web.Hooks uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.CallbackTracing.Web.Hooks.DisplayNewTraces→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.Hooks.ExistingTraces→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.Hooks.FilterNewTraces→LiveDebugger.App.WebLiveDebugger.App.Debugger.CallbackTracing.Web.Hooks.TracingFuse→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.CallbackTracing.Web.Hooks uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.CallbackTracing.Web.Hooks, while a change to LiveDebugger.App.Debugger.CallbackTracing.Web.Hooks can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.CallbackTracing.Web.Hooks uses a module listed above it, which is the healthy direction.
26→17 LiveDebugger.App.Debugger.CallbackTracing.Web.LiveComponents uses LiveDebugger.App✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger.CallbackTracing.Web.LiveComponents uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.CallbackTracing.Web.LiveComponents.FiltersForm→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.CallbackTracing.Web.LiveComponents uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.CallbackTracing.Web.LiveComponents, while a change to LiveDebugger.App.Debugger.CallbackTracing.Web.LiveComponents can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.CallbackTracing.Web.LiveComponents uses a module listed above it, which is the healthy direction.
27→17 LiveDebugger.App.Debugger.ComponentsTree.Web uses LiveDebugger.App✕
- Connections
- 2 pairs of types, where a type in LiveDebugger.App.Debugger.ComponentsTree.Web uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.ComponentsTree.Web.Components→LiveDebugger.App.WebLiveDebugger.App.Debugger.ComponentsTree.Web.ComponentsTreeLive→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.ComponentsTree.Web uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.ComponentsTree.Web, while a change to LiveDebugger.App.Debugger.ComponentsTree.Web can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.ComponentsTree.Web uses a module listed above it, which is the healthy direction.
28→17 LiveDebugger.App.Debugger.NodeState.Web uses LiveDebugger.App✕
- Connections
- 2 pairs of types, where a type in LiveDebugger.App.Debugger.NodeState.Web uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.NodeState.Web.Components→LiveDebugger.App.WebLiveDebugger.App.Debugger.NodeState.Web.NodeStateLive→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.NodeState.Web uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.NodeState.Web, while a change to LiveDebugger.App.Debugger.NodeState.Web can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.NodeState.Web uses a module listed above it, which is the healthy direction.
29→17 LiveDebugger.App.Debugger.NodeState.Web.HookComponents uses LiveDebugger.App✕
- Connections
- 2 pairs of types, where a type in LiveDebugger.App.Debugger.NodeState.Web.HookComponents uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.NodeState.Web.HookComponents.AssignsHistory→LiveDebugger.App.WebLiveDebugger.App.Debugger.NodeState.Web.HookComponents.AssignsSearch→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.NodeState.Web.HookComponents uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.NodeState.Web.HookComponents, while a change to LiveDebugger.App.Debugger.NodeState.Web.HookComponents can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.NodeState.Web.HookComponents uses a module listed above it, which is the healthy direction.
30→17 LiveDebugger.App.Debugger.NodeState.Web.Hooks uses LiveDebugger.App✕
- Connections
- 3 pairs of types, where a type in LiveDebugger.App.Debugger.NodeState.Web.Hooks uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.NodeState.Web.Hooks.NodeAssigns→LiveDebugger.App.WebLiveDebugger.App.Debugger.NodeState.Web.Hooks.TemporaryAssigns→LiveDebugger.App.WebLiveDebugger.App.Debugger.NodeState.Web.Hooks.TermNodeToggle→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.NodeState.Web.Hooks uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.NodeState.Web.Hooks, while a change to LiveDebugger.App.Debugger.NodeState.Web.Hooks can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.NodeState.Web.Hooks uses a module listed above it, which is the healthy direction.
31→17 LiveDebugger.App.Debugger.Resources uses LiveDebugger.App✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger.Resources uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Resources.Components→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.Resources uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.Resources, while a change to LiveDebugger.App.Debugger.Resources can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.Resources uses a module listed above it, which is the healthy direction.
32→17 LiveDebugger.App.Debugger.Resources.Components uses LiveDebugger.App✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger.Resources.Components uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Resources.Components.Chart→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.Resources.Components uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.Resources.Components, while a change to LiveDebugger.App.Debugger.Resources.Components can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.Resources.Components uses a module listed above it, which is the healthy direction.
33→17 LiveDebugger.App.Debugger.Resources.Web uses LiveDebugger.App✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger.Resources.Web uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Resources.Web.ResourcesLive→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.Resources.Web uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.Resources.Web, while a change to LiveDebugger.App.Debugger.Resources.Web can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.Resources.Web uses a module listed above it, which is the healthy direction.
34→17 LiveDebugger.App.Debugger.Streams.Web uses LiveDebugger.App✕
- Connections
- 2 pairs of types, where a type in LiveDebugger.App.Debugger.Streams.Web uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Streams.Web.Components→LiveDebugger.App.WebLiveDebugger.App.Debugger.Streams.Web.StreamsLive→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.Streams.Web uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.Streams.Web, while a change to LiveDebugger.App.Debugger.Streams.Web can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.Streams.Web uses a module listed above it, which is the healthy direction.
35→17 LiveDebugger.App.Debugger.Streams.Web.Hooks uses LiveDebugger.App✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger.Streams.Web.Hooks uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Streams.Web.Hooks.Streams→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.Streams.Web.Hooks uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.Streams.Web.Hooks, while a change to LiveDebugger.App.Debugger.Streams.Web.Hooks can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.Streams.Web.Hooks uses a module listed above it, which is the healthy direction.
36→17 LiveDebugger.App.Debugger.Web uses LiveDebugger.App✕
- Connections
- 2 pairs of types, where a type in LiveDebugger.App.Debugger.Web uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Web.Components→LiveDebugger.App.WebLiveDebugger.App.Debugger.Web.DebuggerLive→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.Web uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.Web, while a change to LiveDebugger.App.Debugger.Web can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.Web uses a module listed above it, which is the healthy direction.
37→17 LiveDebugger.App.Debugger.Web.Components uses LiveDebugger.App✕
- Connections
- 3 pairs of types, where a type in LiveDebugger.App.Debugger.Web.Components uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Web.Components.ElixirDisplay→LiveDebugger.App.WebLiveDebugger.App.Debugger.Web.Components.NavigationMenu→LiveDebugger.App.WebLiveDebugger.App.Debugger.Web.Components.Pages→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.Web.Components uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.Web.Components, while a change to LiveDebugger.App.Debugger.Web.Components can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.Web.Components uses a module listed above it, which is the healthy direction.
38→17 LiveDebugger.App.Debugger.Web.HookComponents uses LiveDebugger.App✕
- Connections
- 2 pairs of types, where a type in LiveDebugger.App.Debugger.Web.HookComponents uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Web.HookComponents.DeadViewMode→LiveDebugger.App.WebLiveDebugger.App.Debugger.Web.HookComponents.InspectButton→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.Web.HookComponents uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.Web.HookComponents, while a change to LiveDebugger.App.Debugger.Web.HookComponents can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.Web.HookComponents uses a module listed above it, which is the healthy direction.
39→17 LiveDebugger.App.Debugger.Web.Hooks uses LiveDebugger.App✕
- Connections
- 1 pair of types, where a type in LiveDebugger.App.Debugger.Web.Hooks uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Web.Hooks.AsyncLvProcess→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.Web.Hooks uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.Web.Hooks, while a change to LiveDebugger.App.Debugger.Web.Hooks can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.Web.Hooks uses a module listed above it, which is the healthy direction.
40→17 LiveDebugger.App.Debugger.Web.LiveComponents uses LiveDebugger.App✕
- Connections
- 3 pairs of types, where a type in LiveDebugger.App.Debugger.Web.LiveComponents uses a type in LiveDebugger.App.
- The types involved
LiveDebugger.App.Debugger.Web.LiveComponents.NodeBasicInfo→LiveDebugger.App.WebLiveDebugger.App.Debugger.Web.LiveComponents.NodeInspectorSidebar→LiveDebugger.App.WebLiveDebugger.App.Debugger.Web.LiveComponents.SendEventFullscreen→LiveDebugger.App.Web
- Direction
- LiveDebugger.App.Debugger.Web.LiveComponents uses LiveDebugger.App, so a change to LiveDebugger.App can break LiveDebugger.App.Debugger.Web.LiveComponents, while a change to LiveDebugger.App.Debugger.Web.LiveComponents can't break LiveDebugger.App.
- Position
- Below the diagonal: LiveDebugger.App.Debugger.Web.LiveComponents 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
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 60 | High / Critical |
| A05:2025 — Injection | 31 | High / Critical |
Roadmap
Top priorities: Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations; Resolve the 31 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15), REDACTED (11), REDACTED (5).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +13.4 pts | Medium | Access Controls |
| Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations. | +13.4 pts | Medium | Web-Security Posture |
| Resolve the 31 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15), REDACTED (11), REDACTED (5). | +4.8 pts | Medium | Dependency Vulnerabilities |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). | +2.1 pts | Low | Static Analysis (SAST) |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.5 pts | Medium | Keyboard semantics |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 2 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. | +1.5 pts | Low | Dependency Vulnerabilities |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.4 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Dependency Vulnerabilities: Critical vulnerability: REDACTED |
| REDACTED | 0.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 1.3 | Slop | Dependency Vulnerabilities: Critical vulnerability: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.3 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| dev/live_components/async_demo_component.ex | 7.1 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| landing/src/components/TopBarBanner/TopBarBannerClient.tsx | 7.2 | Mixed | Cyclomatic Complexity: TopBarBannerClient.TopBarBanner (cyclomatic 27) |
| lib/live_debugger/app/debugger/callback_tracing/web/global_traces_live.ex | 7.4 | Mixed | Code Duplication: Edited copy of a member (37 corresponding lines) |
| landing/src/components/ui/Header.tsx | 7.8 | Mixed | Cyclomatic Complexity: Header.Header (cyclomatic 17) |
| lib/live_debugger/app/debugger/callback_tracing/web/hook_components/load_more_button.ex | 7.8 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
| lib/live_debugger/app/debugger/associated_live_views/web/associated_live_views_live.ex | 7.8 | Mixed | Code Duplication: Edited copy of a member (8 corresponding lines) |
| dev/components.ex | 7.8 | Mixed | Change Coupling: Change coupling: components.ex ↔ router.ex |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: 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 57 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 — 57 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, 183 of 213 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — e2e/ (@playwright/test) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 54 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 59 test source file(s) (.exs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 (.exs, .ts) 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.
- D14 License Compliance — 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 repository declares package.json, but the licence verdict published here was taken over its Hex package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (mix.exs), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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.
- 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. `landing/src/components/TopBarBanner/config.ts`, `priv/static/app.js` 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.
- AC6 Visual & motion safety — 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. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: Destination is too short. (Parameter 'destination').
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — 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. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Elixir 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 and Scala source only, and this repository's Elixir 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.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- 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.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X2 Cancellation propagation — 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.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Elixir 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.
- X29 Per-element action decided by a fixed element — 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.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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.
- X7 Silent fallback defaults — 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. X7 measured the part of this repository it reads (C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart), and its Elixir source is outside the check's reach, so the card covers only part of the product. That is a gap in this analyzer's language reach — not a finding that the unread source is free of silent defaults.
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.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TopBarBannerClient.TopBarBanner at 27.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TopBarBannerClient.TopBarBanner (cyclomatic 27), Header.Header (cyclomatic 17), block.Block (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was TopBarBannerClient.TopBarBanner at 30.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with TopBarBannerClient.TopBarBanner (cognitive 30), Header.Header (cognitive 22), TopBarBannerClient.BannerZoneSlot (cognitive 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with TopBarBannerClient.tsx, inspect.js. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with components.ex. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with traces_storage.ex. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
13 duplicated block group(s) detected. 1.9 % of the production lines (404 of 21,531) are in a reported copy. A further 9 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with associated_live_views_live.ex, filters_form.ex, async_demo_component.ex. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with global_traces_live.ex, async_demo_component.ex, node_traces_live.ex. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with load_more_button.ex, lv_process.ex. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
2 production modules (npm+OTP), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 6 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 54 tests. Measured on the JavaScript/TypeScript suite only — at least 59 test source file(s) (.exs) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
7 outdated, 0 retired direct Hex dependencies, 0 pinning defect(s). Whether any of these packages is UNMAINTAINED is not graded — hex.pm publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: a Hex app name does not determine the modules it provides (`ecto_sql` provides Ecto.Adapters.SQL), and a large idiomatic class of BEAM dependencies — runtime adapters, codec plugins, protocol implementations and OTP applications the release starts — is correctly declared and never referenced in source, so absence of a reference is not evidence of an unused dependency. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets. 2 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D14 · License Compliance
0 of 27 shipped Hex package(s) use a banned license. Licences were resolved from hex.pm over the packages a consumer installs — this repository's REDACTED closed over the declarations its mix.exs files do not gate behind `only:`. Packages it asks for ONLY under `only: [:dev, :test]` (or any other non-prod environment, such as `:docs`) are excluded: they are not installed by anything that depends on this repository. Each licence is the one hex.pm publishes for the package's current release. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's Hex package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/live_debugger/app/debugger/node_state/web/hook_components/assigns_history.ex. Counted over 106 of the 236 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 21531 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. 21 document(s) read across 2 unit(s).
D24 · Comment Value
1 of 65 judged comments only repeat the code they sit on (1.5 %). 2 comment(s) in another language or script were not judged.
What to do
- Resolve the 1 redundant comment finding(s) in Comment Value — start with debug_options.js. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 4 build units (Mix, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
13 % of calls cross a namespace and 33 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection 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)
31 finding(s): 0 critical, 29 high, 2 medium, 0 low. 25 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `landing/src/components/TopBarBanner/config.ts` (line 22), `priv/static/app.js` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 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 25 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 (25 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
49 finding(s): 2 critical, 31 high, 12 medium, 4 low.
What to do
- Resolve the 31 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15), REDACTED (11), REDACTED (5). — One of this dimension's main actionable groups (31 issue-level).
- Resolve the 12 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 2 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
29 of 106 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is landing/src/components/TopBarBanner/TopBarBannerClient.tsx. Counted over 106 of the 236 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with user_events.ex (2), TopBarBannerClient.tsx, Logo.tsx. — One of this dimension's main actionable groups (29 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: components.ex↔router.ex 67%; tracing.ex↔trace_handler.ex 60%; components.ex↔main.ex 54%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with components.ex (2), tracing.ex, url.js. — One of this dimension's main actionable groups (4 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-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 4 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. — lib/live_debugger/app/debugger/resources/components/chart.ex:22
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — lib/live_debugger/app/debugger/components.ex:31
- This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — lib/live_debugger/app/web/components.ex:1279
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- A document must expose only one main landmark. Multiple visible <main> (or role="main") elements confuse the landmark map and the "skip to content" target. Keep one; remove or hide the rest. — dev/layout.ex:13
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — devtools/common/panel.html:1
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — devtools/common/panel.html:1
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — devtools/common/panel.html:1, landing/src/layouts/Layout.astro:27
- user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — lib/live_debugger/app/web/layout.ex:25
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
- The repo's own CSS styles .live-debugger-tooltip-option with `cursor: pointer`, so this <div> 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. (×6) — assets/client/components/debug_options/debug_options.html:2, assets/client/components/debug_options/debug_options.html:24, assets/client/components/debug_options/debug_options.html:55, …
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — lib/live_debugger/app/web/components.ex:1279, lib/live_debugger/app/web/live_components/live_dropdown.ex:60
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
C2 · Access Controls
- This repository serves requests — a server (use Phoenix.Endpoint) (lib/live_debugger/app/web/endpoint.ex:6) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — lib/live_debugger/app/web/endpoint.ex:6
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
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
P10 · Library API & versioning
P2 · Observability
What to do
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add sobelow (Elixir/Phoenix) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 8 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:13
- `assets/app/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — assets/app/package.json:2
What to do
- Add a SAST step to CI running what this repository's stack ships: sobelow (Elixir/Phoenix) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- 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
PF3 · Async & latency hygiene
R1 · Type Safety
- 42 typed · 42 plain JS — the untyped files are assets/app/app.js, assets/app/hooks/assigns_body_search_highlight.js, assets/app/hooks/auto_clear_flash.js, assets/app/hooks/chart_hook.js, assets/app/hooks/close_sidebar_on_resize.js, assets/app/hooks/code_mirror_textarea.js (+36 more).
R10 · Code Duplication
- devtools/chrome/devtools.js:5 · devtools/firefox/devtools.js:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — devtools/chrome/devtools.js:5
- assets/client/components/tooltip/tooltip.js:13 · assets/client/components/tooltip/tooltip.js:40 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — assets/client/components/tooltip/tooltip.js:13
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- Block has cyclomatic complexity 17 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — landing/src/components/ui/block.tsx:56
- we has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/static/client.js:163
- setTooltipPosition has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — assets/app/hooks/tooltip.js:3
R3 · Large Files
- landing/src/components/TopBarBanner/TopBarBannerClient.tsx has 500 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — landing/src/components/TopBarBanner/TopBarBannerClient.tsx:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- 27 file(s) (~2428 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — landing
- Unreachable from the 56 application, 3 tooling and 18 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (56 application, 3 tooling, 18 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — devtools/chrome/devtools.js, devtools/firefox/devtools.js
- Nothing imports this binding — it is safe to review for removal. — landing/swm-geo.mjs:19
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — e2e/tests/global-traces.spec.ts:38
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in assets/app/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×4)
- Declared in landing/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- `secret_key_base` is the secret key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — dev/runner.ex:35
- `https://cdn.tailwindcss.com` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — dev/layout.ex:19
- This repository runs an HTTP server and nothing in its Elixir source or production configuration secures the transport: no HTTPS served (an endpoint's `https: [...]`, `scheme: :https`, `Plug.Cowboy.https`, SiteEncrypt), no `force_ssl:` or `plug Plug.SSL` redirecting to HTTPS and sending HSTS, no `strict-transport-security` header, no `rewrite_on: [:x_forwarded_proto]` or `x-forwarded-proto` read for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: dev/endpoint.ex:2 — `Phoenix.Endpoint`.
- Set: Content-Security-Policy, Referrer-Policy, X-Content-Type-Options, X-Permitted-Cross-Domain-Policies. Missing: Strict-Transport-Security, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.0 on this card.) The server: dev/endpoint.ex:2 — `Phoenix.Endpoint`.
- No handler of this repository's Elixir server answers 400, 413 or 422 (`put_status(conn, :bad_request)`, `:unprocessable_entity`, `send_resp(conn, 400, …)`), and nothing declares validation — no Ecto changeset `validate_required`/`validate_length`/`validate_format`, no OpenApiSpex `CastAndValidate`, ExJsonSchema or other schema validator, no `Plug.Parsers` `length:` cap — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: dev/endpoint.ex:2 — `Phoenix.Endpoint`.
What to do
- Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Secure the server's transport: set `force_ssl: [rewrite_on: [:x_forwarded_proto], hsts: true]` on the endpoint in `config/prod.exs` (Plug.SSL redirects to HTTPS and sends `Strict-Transport-Security`; `rewrite_on` trusts the TLS-terminating proxy in front of it), or serve TLS itself with the endpoint's `https: [port: 443, cipher_suite: :strong, keyfile: …, certfile: …]`.
- Add Strict-Transport-Security, X-Frame-Options beside the headers the Elixir server already sets.
- Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body, 422 for an invalid changeset) before a handler acts on it: cast params through an Ecto changeset with `validate_*` and render its errors with `put_status(:unprocessable_entity)`, or declare the request schema with OpenApiSpex's `CastAndValidate` plug.
X5 · Nullable reference types
- 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~0.4 `!` null assertions per 1k TypeScript source lines — 1 assertion(s) across the 2264 source line(s) of the 25 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: landing/src/components/ui/Header.tsx (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
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 |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 81% | Strong | Solid. |
| Maturity | 70% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 58% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 15% | Critical — gated by D36, C2, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 49% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
- AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- AX1 Captive dependencies — Not applicable: the BEAM has no dependency-injection container — state lives in processes, and no process is handed an instance whose lifetime another one scopes; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: Elixir processes share no mutable memory — state lives in a process's own mailbox — so there is no shared object to race on. 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
- AX6 Interface segregation — AX6 reached only 18% of this repository's production lines — elixir (19,482 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (an Ecto repo, Postgrex, MyXQL, Exqlite, Mongo, Mnesia, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (Ecto, Postgrex, MyXQL, Mongo, EventStore, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (an Ecto repo, Postgrex, MyXQL, Exqlite, Mongo, Mnesia, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (an Ecto repo, Postgrex, MyXQL, Exqlite, Mongo, Mnesia, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — no .exs 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- 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
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 2 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 measured — JavaScript/TypeScript suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 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 and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Elixir, JavaScript/TypeScript source (service entry point: lib/live_debugger/app/web/endpoint.ex:6 (use Phoenix.Endpoint))
- 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — 18 test file(s) reach none of 65 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — X1 reached only 18% of this repository's production lines — elixir (19,482 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 18% of this repository's production lines — elixir (19,482 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
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 18% of this repository's production lines — elixir (19,482 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — 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 — X2 reached only 18% of this repository's production lines — elixir (19,482 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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.
- X21 Side-effecting pattern guard — X21 reached only 18% of this repository's production lines — elixir (19,482 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X23 Unguarded diagnostic materialisation — 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 18% of this repository's production lines — elixir (19,482 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. Elixir processes share no heap: a value sent to another process arrives as a copy, so no collection is reachable from two processes 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.
- X27 Collection changed while being enumerated — 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — X29 reached only 18% of this repository's production lines — elixir (19,482 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X3 Exception handling — X3 reached only 18% of this repository's production lines — elixir (19,482 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 76 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Clickable element isn't keyboard-operable assets/client/components/debug_options/debug_options.html:2
- Clickable element isn't keyboard-operable assets/client/components/debug_options/debug_options.html:24
- Clickable element isn't keyboard-operable assets/client/components/debug_options/debug_options.html:55
- Clickable element isn't keyboard-operable priv/static/client.js:80
- Clickable element isn't keyboard-operable priv/static/client.js:102
- Clickable element isn't keyboard-operable priv/static/client.js:133
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <div> lib/live_debugger/app/web/components.ex:1279
- Click handler on a non-interactive <div> lib/live_debugger/app/web/live_components/live_dropdown.ex:60
- REDACTED
- REDACTED
- <input> without a programmatic label lib/live_debugger/app/debugger/components.ex:31
- Custom control with no accessible name on <div> lib/live_debugger/app/web/components.ex:1279
- <html> without a lang devtools/common/panel.html:1
- Document without a <title> devtools/common/panel.html:1
- Viewport restricts zoom lib/live_debugger/app/web/layout.ex:25
- REDACTED
- Cryptographic key material is a compile-time constant dev/runner.ex:35
Serious — 78 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change coupling: components.ex ↔ router.ex dev/components.ex:1
- Change coupling: tracing.ex ↔ trace_handler.ex lib/live_debugger/services/callback_tracer/actions/tracing.ex:1
- Change coupling: components.ex ↔ main.ex dev/components.ex:1
- Change coupling: url.js ↔ live_debugger.ex devtools/common/url.js:1
- Duplicated block (14 lines × 2) lib/live_debugger/app/debugger/associated_live_views/web/associated_live_views_live.ex:141
- Duplicated block (14 lines × 2) lib/live_debugger/app/debugger/callback_tracing/web/live_components/filters_form.ex:425
- Duplicated block (14 lines × 2) dev/live_components/async_demo_component.ex:157
- Duplicated block (10 lines × 2) lib/live_debugger/app/debugger/callback_tracing/web/global_traces_live.ex:102
- Duplicated block (10 lines × 2) dev/live_components/async_demo_component.ex:174
- Duplicated block (10 lines × 2) lib/live_debugger/app/debugger/callback_tracing/web/node_traces_live.ex:32
- Page without a main landmark devtools/common/panel.html:1
- Page without a main landmark landing/src/layouts/Layout.astro:27
- REDACTED
- REDACTED
- FunctionTooLong: TopBarBannerClient.TopBarBanner landing/src/components/TopBarBanner/TopBarBannerClient.tsx:329
- FunctionTooLong: inspect.initElementInspection assets/client/services/inspect.js:3
- REDACTED
- REDACTED
- Edited copy of a member (6 corresponding lines) lib/live_debugger/app/debugger/callback_tracing/web/hook_components/load_more_button.ex:93
- Edited copy of a member (6 corresponding lines) lib/live_debugger/app/debugger/queries/lv_process.ex:33
- Duplicated block (7 lines × 2) lib/live_debugger/services/callback_tracer/actions/diff_trace.ex:27
- Duplicated block (7 lines × 2) dev/live_components/async_demo_component.ex:202
- Dead file (~21 LoC) devtools/chrome/devtools.js
- Dead file (~21 LoC) devtools/firefox/devtools.js
- <canvas> without a text alternative lib/live_debugger/app/debugger/resources/components/chart.ex:22
- More than one main landmark dev/layout.ex:13
- No authorization lib/live_debugger/app/web/endpoint.ex:6
- TopBarBannerClient.TopBarBanner (cyclomatic 27) landing/src/components/TopBarBanner/TopBarBannerClient.tsx:329
- Header.Header (cyclomatic 17) landing/src/components/ui/Header.tsx:44
- block.Block (cyclomatic 17) landing/src/components/ui/block.tsx:56
- TopBarBannerClient.TopBarBanner (cognitive 30) landing/src/components/TopBarBanner/TopBarBannerClient.tsx:329
- Header.Header (cognitive 22) landing/src/components/ui/Header.tsx:44
- TopBarBannerClient.BannerZoneSlot (cognitive 17) landing/src/components/TopBarBanner/TopBarBannerClient.tsx:141
- FileTooLong: web/components.ex lib/live_debugger/app/web/components.ex
- TooManyFunctions: Impl lib/live_debugger/api/traces_storage.ex:169
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (37 corresponding lines) lib/live_debugger/app/debugger/callback_tracing/web/global_traces_live.ex:81
- Edited copy of a member (16 corresponding lines) lib/live_debugger/app/debugger/callback_tracing/web/hook_components/load_more_button.ex:74
- Edited copy of a member (7 corresponding lines) lib/live_debugger/app/web/live_components/live_dropdown.ex:22
- Edited copy of a member (12 corresponding lines) lib/live_debugger/services/garbage_collector/actions/garbage_collecting.ex:26
- Edited copy of a member (11 corresponding lines) lib/live_debugger/app/debugger/components_tree/web/components_tree_live.ex:178
- Edited copy of a member (4 corresponding lines) lib/live_debugger/app/debugger/callback_tracing/web/global_traces_live.ex:257
- Edited copy of a member (8 corresponding lines) lib/live_debugger/app/debugger/associated_live_views/web/associated_live_views_live.ex:34
- Duplicated block (9 lines × 3) lib/live_debugger/app/debugger/async_jobs/web/async_jobs_live.ex:36
- Duplicated block (6 lines × 2) lib/live_debugger/app/debugger/callback_tracing/web/hook_components/filters_fullscreen.ex:20
- Duplicated block (5 lines × 2) lib/live_debugger/services/callback_tracer/actions/state.ex:48
- Duplicated block (11 lines × 2) dev/live_components/async_demo_component.ex:143
- Duplicated block (12 lines × 2) dev/live_components/async_demo_component.ex:187
- Type Safety
- Duplicated block (16 lines × 2 locations) devtools/chrome/devtools.js:5
- Duplicated block with local edits (13 matched lines × 2 locations) assets/client/components/tooltip/tooltip.js:13
- Complex function Block (cyclomatic 17, cognitive 12) landing/src/components/ui/block.tsx:56
- Complex function we (cyclomatic 13, cognitive 12) priv/static/client.js:163
- Complex function setTooltipPosition (cyclomatic 13, cognitive 11) assets/app/hooks/tooltip.js:3
- landing/src/components/TopBarBanner/TopBarBannerClient.tsx: 500 lines of code landing/src/components/TopBarBanner/TopBarBannerClient.tsx:1
- No typecheck script
- Unused dependency '@codemirror/theme-one-dark'
- Unused dependency 'phoenix'
- Unused dependency 'phoenix_html'
- Unused dependency 'phoenix_live_view'
- Unused dependency 'embla-carousel'
- Third-party script without Subresource Integrity dev/layout.ex:19
Minor — 52 finding(s)
- Orphaned file landing/src/components/TopBarBanner/TopBarBannerClient.tsx:1
- Orphaned file landing/src/components/ui/Logo.tsx:1
- Orphaned file dev/live_components/async_demo_component.ex:1
- Orphaned file dev/live_views/async_demo.ex:1
- Orphaned file dev/live_views/memory_explosion.ex:1
- Orphaned file landing/src/components/ui/block.tsx:1
- Orphaned file lib/live_debugger/app/debugger/resources/web/resources_live.ex:1
- Orphaned file lib/live_debugger/services/successor_discoverer/gen_servers/successor_discoverer.ex:1
- Orphaned file lib/live_debugger/app/web/live_components/tracer_status.ex:1
- Orphaned file lib/mix/tasks/live_debugger.install.ex:1
- Orphaned file lib/live_debugger/app/debugger/web/live_components/send_event_fullscreen.ex:1
- Orphaned file lib/live_debugger/app/debugger/associated_live_views/web/associated_live_views_live.ex:1
- Orphaned file lib/live_debugger/api/user_events.ex:1
- Orphaned file landing/src/components/ui/card.tsx:1
- Orphaned file lib/live_debugger/app/debugger/actions/user_events.ex:1
- Orphaned file lib/live_debugger/app/discovery/web/live_components/active_live_views.ex:1
- Orphaned file lib/live_debugger/app/debugger/resources/components.ex:1
- Orphaned file lib/live_debugger/services/garbage_collector/gen_servers/table_watcher.ex:1
- Orphaned file lib/live_debugger/app/debugger/components_tree/utils.ex:1
- Orphaned file lib/live_debugger/app/debugger/resources/structs/process_info.ex:1
- Orphaned file lib/live_debugger/app/debugger/web/components/handler_info.ex:1
- Orphaned file lib/live_debugger/services/callback_tracer/queries/callbacks.ex:1
- Orphaned file lib/live_debugger/app/debugger/node_state/web/hooks/temporary_assigns.ex:1
- Orphaned file landing/src/components/ui/blockWrapper.tsx:1
- Orphaned file lib/live_debugger/app/web/live_components/live_dropdown.ex:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- redundant comment assets/client/components/debug_options/debug_options.js:16
- Projects may be oversized for their cohesion
- High interface indirection
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:13
- No dependency-update automation assets/app/package.json:2
- Unused export 'structuredData' landing/swm-geo.mjs:19
- Unused module-local declaration 'componentCheckbox' e2e/tests/global-traces.spec.ts:38
- No app-layer HTTPS enforcement detected
- Security headers incomplete
- No inbound request validation detected
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
Minor — 7 finding(s)
- Outdated: bandit
- Outdated: esbuild
- Outdated: igniter
- Outdated: phoenix
- Outdated: phoenix_live_view
- Outdated: phx_new
- Outdated: tailwind
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e623c6eb011c416ea86c7fd34dcdf808/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e623c6eb011c416ea86c7fd34dcdf808/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 . | 31 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 49 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `landing/src/components/TopBarBanner/config.ts`, `priv/static/app.js` — 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |