Executive summary
marciok/gust is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 49 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Security and Compliance, at 40, is the weakest lens and counts most in the score. The best first step is naming the access rules, worth about 6 points. Recording design decisions comes next, worth about 2 points. Raising Security and Compliance to 68 would lift the score to about 55.
Thirty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. Updating the vulnerable packages would fix the package with a known security hole. The three labels or groups of fields with no name need connecting to their fields or naming.
The product code is 11,518 lines, about €25,000 to rebuild.
If Security and Compliance rose from 40 to 68, the lowest score rated Strong, the score would rise from 49 to about 55.
New since the last survey: 19 findings
- Code Duplication · Edited copy of a member (11 corresponding lines) apps/gust/lib/gust/flows.ex
- Code Duplication · Edited copy of a member (12 corresponding lines) apps/gust/lib/gust/dag/runner/dag_worker.ex
- Code Duplication · Edited copy of a member (7 corresponding lines) apps/gust_web/lib/gust_web/live/dag_summary_component.ex
- Code Duplication · Edited copy of a member (3 corresponding lines) apps/gust/lib/gust/dag/parser/adapters/elixir.ex
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Keyboard semantics · Click handler on a non-interactive <td> apps/gust_web/lib/gust_web/components/core_components.ex
Fixed since the last survey: 16 findings
- God Classes · TooManyFunctions: Index apps/gust_web/lib/gust_web/live/run_live/index.ex
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · Medium: watchdog-mutable-service-container-image REDACTED
- Page structure · Document without a <title> apps/gust_web/lib/gust_web/components/layouts/root.html.heex
- ARIA correctness · Invalid value "{" for aria-current apps/gust_web/lib/gust_web/live/run_live/index.html.heex
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €25,000 · Estimate
| Cost to rebuild | €8,200 to €41,000, for 136 to 433 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 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,518 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 Gust | 3 Gust.DAG | 4 Gust.DAG.Run | 5 Gust.DAG.Runner | 6 Gust.DAG.Runtime | 7 Gust.Run | 8 GustPy | 9 GustWeb.MCP | 10 Gust.DAG.Loader | 11 Gust.DAG.Logger | 12 Gust.DAG.Parser | 13 Gust.DAG.Run.Trigger | 14 Gust.DAG.Runner.RunGateway | 15 Gust.DAG.RunnerSupervisor | 16 Gust.DAG.Runtime.Adapters | 17 Gust.DAG.StageCoordinator | 18 Gust.DAG.TaskDelayer | 19 Gust.DAG.TaskExpander | 20 Gust.DAG.TaskRunnerSupervisor | 21 Gust.DAG.TaskWaiter | 22 Gust.DAG.TaskWorker.Adapters | 23 Gust.DAG.Terminator | 24 Gust.DBLocker | 25 Gust.FileMonitor | 26 Gust.PGNotifier | 27 Gust.Run.Claim | 28 GustPy.Executor | 29 GustPy.Runtime | 30 GustPy.TaskMessenger | 31 GustPy.TaskWorker | 32 GustShell.Runtime | 33 GustShell.TaskWorker | 34 GustWeb | 35 GustWeb.DagLive | 36 GustWeb.MCP.Resources | 37 GustWeb.MCP.Tools | 38 Gust.DAG.Parser.Adapters | 39 GustPy.Parser | 40 GustShell.Parser |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 Gust | ||||||||||||||||||||||||||||||||||||||||
| 3 Gust.DAG | ||||||||||||||||||||||||||||||||||||||||
| 4 Gust.DAG.Run | ||||||||||||||||||||||||||||||||||||||||
| 5 Gust.DAG.Runner | ||||||||||||||||||||||||||||||||||||||||
| 6 Gust.DAG.Runtime | ||||||||||||||||||||||||||||||||||||||||
| 7 Gust.Run | ||||||||||||||||||||||||||||||||||||||||
| 8 GustPy | ||||||||||||||||||||||||||||||||||||||||
| 9 GustWeb.MCP | ||||||||||||||||||||||||||||||||||||||||
| 10 Gust.DAG.Loader | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Gust.DAG.Logger | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Gust.DAG.Parser | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Gust.DAG.Run.Trigger | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Gust.DAG.Runner.RunGateway | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Gust.DAG.RunnerSupervisor | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Gust.DAG.Runtime.Adapters | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Gust.DAG.StageCoordinator | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Gust.DAG.TaskDelayer | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Gust.DAG.TaskExpander | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Gust.DAG.TaskRunnerSupervisor | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Gust.DAG.TaskWaiter | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Gust.DAG.TaskWorker.Adapters | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Gust.DAG.Terminator | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Gust.DBLocker | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Gust.FileMonitor | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Gust.PGNotifier | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Gust.Run.Claim | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 GustPy.Executor | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 GustPy.Runtime | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 GustPy.TaskMessenger | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 GustPy.TaskWorker | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 GustShell.Runtime | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 GustShell.TaskWorker | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 GustWeb | 12 | |||||||||||||||||||||||||||||||||||||||
| 35 GustWeb.DagLive | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 GustWeb.MCP.Resources | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 GustWeb.MCP.Tools | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 Gust.DAG.Parser.Adapters | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 GustPy.Parser | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 GustShell.Parser | 1 |
10→3 Gust.DAG.Loader uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.Loader uses a type in Gust.DAG.
- The types involved
Gust.DAG.Loader.Worker→Gust.DAG.Loader
- Direction
- Gust.DAG.Loader uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.Loader, while a change to Gust.DAG.Loader can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.Loader uses a module listed above it, which is the healthy direction.
11→3 Gust.DAG.Logger uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.Logger uses a type in Gust.DAG.
- The types involved
Gust.DAG.Logger.Database→Gust.DAG.Logger
- Direction
- Gust.DAG.Logger uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.Logger, while a change to Gust.DAG.Logger can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.Logger uses a module listed above it, which is the healthy direction.
12→3 Gust.DAG.Parser uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.Parser uses a type in Gust.DAG.
- The types involved
Gust.DAG.Parser.File→Gust.DAG.Parser
- Direction
- Gust.DAG.Parser uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.Parser, while a change to Gust.DAG.Parser can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.Parser uses a module listed above it, which is the healthy direction.
13→4 Gust.DAG.Run.Trigger uses Gust.DAG.Run✕
- Connections
- 1 pair of types, where a type in Gust.DAG.Run.Trigger uses a type in Gust.DAG.Run.
- The types involved
Gust.DAG.Run.Trigger.Requeue→Gust.DAG.Run.Trigger
- Direction
- Gust.DAG.Run.Trigger uses Gust.DAG.Run, so a change to Gust.DAG.Run can break Gust.DAG.Run.Trigger, while a change to Gust.DAG.Run.Trigger can't break Gust.DAG.Run.
- Position
- Below the diagonal: Gust.DAG.Run.Trigger uses a module listed above it, which is the healthy direction.
14→5 Gust.DAG.Runner.RunGateway uses Gust.DAG.Runner✕
- Connections
- 1 pair of types, where a type in Gust.DAG.Runner.RunGateway uses a type in Gust.DAG.Runner.
- The types involved
Gust.DAG.Runner.RunGateway.Default→Gust.DAG.Runner.RunGateway
- Direction
- Gust.DAG.Runner.RunGateway uses Gust.DAG.Runner, so a change to Gust.DAG.Runner can break Gust.DAG.Runner.RunGateway, while a change to Gust.DAG.Runner.RunGateway can't break Gust.DAG.Runner.
- Position
- Below the diagonal: Gust.DAG.Runner.RunGateway uses a module listed above it, which is the healthy direction.
15→3 Gust.DAG.RunnerSupervisor uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.RunnerSupervisor uses a type in Gust.DAG.
- The types involved
Gust.DAG.RunnerSupervisor.DynamicSupervisor→Gust.DAG.RunnerSupervisor
- Direction
- Gust.DAG.RunnerSupervisor uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.RunnerSupervisor, while a change to Gust.DAG.RunnerSupervisor can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.RunnerSupervisor uses a module listed above it, which is the healthy direction.
16→6 Gust.DAG.Runtime.Adapters uses Gust.DAG.Runtime✕
- Connections
- 1 pair of types, where a type in Gust.DAG.Runtime.Adapters uses a type in Gust.DAG.Runtime.
- The types involved
Gust.DAG.Runtime.Adapters.Elixir→Gust.DAG.Runtime.Adapter
- Direction
- Gust.DAG.Runtime.Adapters uses Gust.DAG.Runtime, so a change to Gust.DAG.Runtime can break Gust.DAG.Runtime.Adapters, while a change to Gust.DAG.Runtime.Adapters can't break Gust.DAG.Runtime.
- Position
- Below the diagonal: Gust.DAG.Runtime.Adapters uses a module listed above it, which is the healthy direction.
17→3 Gust.DAG.StageCoordinator uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.StageCoordinator uses a type in Gust.DAG.
- The types involved
Gust.DAG.StageCoordinator.RetryingTask→Gust.DAG.StageCoordinator
- Direction
- Gust.DAG.StageCoordinator uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.StageCoordinator, while a change to Gust.DAG.StageCoordinator can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.StageCoordinator uses a module listed above it, which is the healthy direction.
18→3 Gust.DAG.TaskDelayer uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.TaskDelayer uses a type in Gust.DAG.
- The types involved
Gust.DAG.TaskDelayer.Calculator→Gust.DAG.TaskDelayer
- Direction
- Gust.DAG.TaskDelayer uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.TaskDelayer, while a change to Gust.DAG.TaskDelayer can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.TaskDelayer uses a module listed above it, which is the healthy direction.
19→3 Gust.DAG.TaskExpander uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.TaskExpander uses a type in Gust.DAG.
- The types involved
Gust.DAG.TaskExpander.MapOver→Gust.DAG.TaskExpander
- Direction
- Gust.DAG.TaskExpander uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.TaskExpander, while a change to Gust.DAG.TaskExpander can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.TaskExpander uses a module listed above it, which is the healthy direction.
20→3 Gust.DAG.TaskRunnerSupervisor uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.TaskRunnerSupervisor uses a type in Gust.DAG.
- The types involved
Gust.DAG.TaskRunnerSupervisor.DynamicSupervisor→Gust.DAG.TaskRunnerSupervisor
- Direction
- Gust.DAG.TaskRunnerSupervisor uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.TaskRunnerSupervisor, while a change to Gust.DAG.TaskRunnerSupervisor can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.TaskRunnerSupervisor uses a module listed above it, which is the healthy direction.
21→3 Gust.DAG.TaskWaiter uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.TaskWaiter uses a type in Gust.DAG.
- The types involved
Gust.DAG.TaskWaiter.Repo→Gust.DAG.TaskWaiter
- Direction
- Gust.DAG.TaskWaiter uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.TaskWaiter, while a change to Gust.DAG.TaskWaiter can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.TaskWaiter uses a module listed above it, which is the healthy direction.
22→3 Gust.DAG.TaskWorker.Adapters uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.TaskWorker.Adapters uses a type in Gust.DAG.
- The types involved
Gust.DAG.TaskWorker.Adapters.Elixir→Gust.DAG.TaskWorker
- Direction
- Gust.DAG.TaskWorker.Adapters uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.TaskWorker.Adapters, while a change to Gust.DAG.TaskWorker.Adapters can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.TaskWorker.Adapters uses a module listed above it, which is the healthy direction.
23→3 Gust.DAG.Terminator uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in Gust.DAG.Terminator uses a type in Gust.DAG.
- The types involved
Gust.DAG.Terminator.Gateway→Gust.DAG.Terminator
- Direction
- Gust.DAG.Terminator uses Gust.DAG, so a change to Gust.DAG can break Gust.DAG.Terminator, while a change to Gust.DAG.Terminator can't break Gust.DAG.
- Position
- Below the diagonal: Gust.DAG.Terminator uses a module listed above it, which is the healthy direction.
24→2 Gust.DBLocker uses Gust✕
- Connections
- 1 pair of types, where a type in Gust.DBLocker uses a type in Gust.
- The types involved
Gust.DBLocker.Postgres→Gust.DBLocker
- Direction
- Gust.DBLocker uses Gust, so a change to Gust can break Gust.DBLocker, while a change to Gust.DBLocker can't break Gust.
- Position
- Below the diagonal: Gust.DBLocker uses a module listed above it, which is the healthy direction.
25→2 Gust.FileMonitor uses Gust✕
- Connections
- 1 pair of types, where a type in Gust.FileMonitor uses a type in Gust.
- The types involved
Gust.FileMonitor.SystemFs→Gust.FileMonitor
- Direction
- Gust.FileMonitor uses Gust, so a change to Gust can break Gust.FileMonitor, while a change to Gust.FileMonitor can't break Gust.
- Position
- Below the diagonal: Gust.FileMonitor uses a module listed above it, which is the healthy direction.
26→2 Gust.PGNotifier uses Gust✕
- Connections
- 1 pair of types, where a type in Gust.PGNotifier uses a type in Gust.
- The types involved
Gust.PGNotifier.Postgrex→Gust.PGNotifier
- Direction
- Gust.PGNotifier uses Gust, so a change to Gust can break Gust.PGNotifier, while a change to Gust.PGNotifier can't break Gust.
- Position
- Below the diagonal: Gust.PGNotifier uses a module listed above it, which is the healthy direction.
26→7 Gust.PGNotifier uses Gust.Run✕
- Connections
- 1 pair of types, where a type in Gust.PGNotifier uses a type in Gust.Run.
- The types involved
Gust.PGNotifier.Worker→Gust.Run.Dispatcher
- Direction
- Gust.PGNotifier uses Gust.Run, so a change to Gust.Run can break Gust.PGNotifier, while a change to Gust.PGNotifier can't break Gust.Run.
- Position
- Below the diagonal: Gust.PGNotifier uses a module listed above it, which is the healthy direction.
27→7 Gust.Run.Claim uses Gust.Run✕
- Connections
- 1 pair of types, where a type in Gust.Run.Claim uses a type in Gust.Run.
- The types involved
Gust.Run.Claim.Repo→Gust.Run.Claim
- Direction
- Gust.Run.Claim uses Gust.Run, so a change to Gust.Run can break Gust.Run.Claim, while a change to Gust.Run.Claim can't break Gust.Run.
- Position
- Below the diagonal: Gust.Run.Claim uses a module listed above it, which is the healthy direction.
28→8 GustPy.Executor uses GustPy✕
- Connections
- 1 pair of types, where a type in GustPy.Executor uses a type in GustPy.
- The types involved
GustPy.Executor.UV→GustPy.Executor
- Direction
- GustPy.Executor uses GustPy, so a change to GustPy can break GustPy.Executor, while a change to GustPy.Executor can't break GustPy.
- Position
- Below the diagonal: GustPy.Executor uses a module listed above it, which is the healthy direction.
29→6 GustPy.Runtime uses Gust.DAG.Runtime✕
- Connections
- 1 pair of types, where a type in GustPy.Runtime uses a type in Gust.DAG.Runtime.
- The types involved
GustPy.Runtime.Adapter→Gust.DAG.Runtime.Adapter
- Direction
- GustPy.Runtime uses Gust.DAG.Runtime, so a change to Gust.DAG.Runtime can break GustPy.Runtime, while a change to GustPy.Runtime can't break Gust.DAG.Runtime.
- Position
- Below the diagonal: GustPy.Runtime uses a module listed above it, which is the healthy direction.
30→8 GustPy.TaskMessenger uses GustPy✕
- Connections
- 1 pair of types, where a type in GustPy.TaskMessenger uses a type in GustPy.
- The types involved
GustPy.TaskMessenger.JSON→GustPy.TaskMessenger
- Direction
- GustPy.TaskMessenger uses GustPy, so a change to GustPy can break GustPy.TaskMessenger, while a change to GustPy.TaskMessenger can't break GustPy.
- Position
- Below the diagonal: GustPy.TaskMessenger uses a module listed above it, which is the healthy direction.
31→3 GustPy.TaskWorker uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in GustPy.TaskWorker uses a type in Gust.DAG.
- The types involved
GustPy.TaskWorker.Adapter→Gust.DAG.TaskWorker
- Direction
- GustPy.TaskWorker uses Gust.DAG, so a change to Gust.DAG can break GustPy.TaskWorker, while a change to GustPy.TaskWorker can't break Gust.DAG.
- Position
- Below the diagonal: GustPy.TaskWorker uses a module listed above it, which is the healthy direction.
32→6 GustShell.Runtime uses Gust.DAG.Runtime✕
- Connections
- 1 pair of types, where a type in GustShell.Runtime uses a type in Gust.DAG.Runtime.
- The types involved
GustShell.Runtime.Adapter→Gust.DAG.Runtime.Adapter
- Direction
- GustShell.Runtime uses Gust.DAG.Runtime, so a change to Gust.DAG.Runtime can break GustShell.Runtime, while a change to GustShell.Runtime can't break Gust.DAG.Runtime.
- Position
- Below the diagonal: GustShell.Runtime uses a module listed above it, which is the healthy direction.
33→3 GustShell.TaskWorker uses Gust.DAG✕
- Connections
- 1 pair of types, where a type in GustShell.TaskWorker uses a type in Gust.DAG.
- The types involved
GustShell.TaskWorker.Adapter→Gust.DAG.TaskWorker
- Direction
- GustShell.TaskWorker uses Gust.DAG, so a change to Gust.DAG can break GustShell.TaskWorker, while a change to GustShell.TaskWorker can't break Gust.DAG.
- Position
- Below the diagonal: GustShell.TaskWorker uses a module listed above it, which is the healthy direction.
34→1 GustWeb uses (global)✕
- Connections
- 12 pairs of types, where a type in GustWeb uses a type in (global).
- The types involved
GustWeb.APIController→GustWebGustWeb.BreadcrumbsComponent→GustWebGustWeb.DagSummaryComponent→GustWebGustWeb.ErrorHTML→GustWebGustWeb.HealthCheckComponent→GustWebGustWeb.Layouts→GustWebGustWeb.MCPController→GustWebGustWeb.Pagination→GustWebGustWeb.Router→GustWebGustWeb.SelectedItemStatusComponent→GustWebGustWeb.SystemLive→GustWebGustWeb.WellKnownController→GustWeb
- Direction
- GustWeb uses (global), so a change to (global) can break GustWeb, while a change to GustWeb can't break (global).
- Position
- Below the diagonal: GustWeb uses a module listed above it, which is the healthy direction.
35→1 GustWeb.DagLive uses (global)✕
- Connections
- 2 pairs of types, where a type in GustWeb.DagLive uses a type in (global).
- The types involved
GustWeb.DagLive.Dashboard→GustWebGustWeb.DagLive.Index→GustWeb
- Direction
- GustWeb.DagLive uses (global), so a change to (global) can break GustWeb.DagLive, while a change to GustWeb.DagLive can't break (global).
- Position
- Below the diagonal: GustWeb.DagLive uses a module listed above it, which is the healthy direction.
36→9 GustWeb.MCP.Resources uses GustWeb.MCP✕
- Connections
- 1 pair of types, where a type in GustWeb.MCP.Resources uses a type in GustWeb.MCP.
- The types involved
GustWeb.MCP.Resources.List→GustWeb.MCP.Resources
- Direction
- GustWeb.MCP.Resources uses GustWeb.MCP, so a change to GustWeb.MCP can break GustWeb.MCP.Resources, while a change to GustWeb.MCP.Resources can't break GustWeb.MCP.
- Position
- Below the diagonal: GustWeb.MCP.Resources uses a module listed above it, which is the healthy direction.
37→9 GustWeb.MCP.Tools uses GustWeb.MCP✕
- Connections
- 1 pair of types, where a type in GustWeb.MCP.Tools uses a type in GustWeb.MCP.
- The types involved
GustWeb.MCP.Tools.List→GustWeb.MCP.Tools
- Direction
- GustWeb.MCP.Tools uses GustWeb.MCP, so a change to GustWeb.MCP can break GustWeb.MCP.Tools, while a change to GustWeb.MCP.Tools can't break GustWeb.MCP.
- Position
- Below the diagonal: GustWeb.MCP.Tools uses a module listed above it, which is the healthy direction.
38→12 Gust.DAG.Parser.Adapters uses Gust.DAG.Parser✕
- Connections
- 1 pair of types, where a type in Gust.DAG.Parser.Adapters uses a type in Gust.DAG.Parser.
- The types involved
Gust.DAG.Parser.Adapters.Elixir→Gust.DAG.Parser.Adapter
- Direction
- Gust.DAG.Parser.Adapters uses Gust.DAG.Parser, so a change to Gust.DAG.Parser can break Gust.DAG.Parser.Adapters, while a change to Gust.DAG.Parser.Adapters can't break Gust.DAG.Parser.
- Position
- Below the diagonal: Gust.DAG.Parser.Adapters uses a module listed above it, which is the healthy direction.
39→12 GustPy.Parser uses Gust.DAG.Parser✕
- Connections
- 1 pair of types, where a type in GustPy.Parser uses a type in Gust.DAG.Parser.
- The types involved
GustPy.Parser.Adapter→Gust.DAG.Parser.Adapter
- Direction
- GustPy.Parser uses Gust.DAG.Parser, so a change to Gust.DAG.Parser can break GustPy.Parser, while a change to GustPy.Parser can't break Gust.DAG.Parser.
- Position
- Below the diagonal: GustPy.Parser uses a module listed above it, which is the healthy direction.
40→12 GustShell.Parser uses Gust.DAG.Parser✕
- Connections
- 1 pair of types, where a type in GustShell.Parser uses a type in Gust.DAG.Parser.
- The types involved
GustShell.Parser.Adapter→Gust.DAG.Parser.Adapter
- Direction
- GustShell.Parser uses Gust.DAG.Parser, so a change to Gust.DAG.Parser can break GustShell.Parser, while a change to GustShell.Parser can't break Gust.DAG.Parser.
- Position
- Below the diagonal: GustShell.Parser uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 41 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 16 | High / Critical |
| A02:2025 — Security Misconfiguration | 7 | Medium |
Roadmap
Top priorities: Name the access rules — a Bodyguard.Policy or LetMe policy module, a Canada.Can implementation, or roles and permissions declared once — and consult them where access is checked (Bodyguard.permit!, a plug in the pipeline), so the rule set is reviewable and testable on its own; Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Name the access rules — a Bodyguard.Policy or LetMe policy module, a Canada.Can implementation, or roles and permissions declared once — and consult them where access is checked (Bodyguard.permit!, a plug in the pipeline), so the rule set is reviewable and testable on its own. | +6.4 pts | Medium | Access Controls |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with mix.exs. | +2.3 pts | Low | ADR Quality |
| Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. | +4.3 pts | Medium | Web-Security Posture |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +4.2 pts | Medium | Visual & motion safety |
| Resolve the 9 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). | +1.6 pts | Low | Dependency Vulnerabilities |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.3 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.6 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.5 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| apps/gust/lib/gust/flows.ex | 7.8 | Near-clean | God Classes: TooManyFunctions: Flows |
| apps/gust_web/lib/gust_web/live/dag_live/dashboard.ex | 8.5 | Near-clean | God Classes: TooManyFunctions: Dashboard |
| apps/gust/lib/gust/dag/runner/dag_worker.ex | 8.5 | Near-clean | Code Duplication: Edited copy of a member (12 corresponding lines) |
| apps/gust_web/lib/gust_web/live/dag_summary_component.ex | 8.5 | Near-clean | Code Duplication: Edited copy of a member (7 corresponding lines) |
| apps/gust/lib/gust/dag/parser/adapters/elixir.ex | 8.5 | Near-clean | Code Duplication: Edited copy of a member (3 corresponding lines) |
| mix.exs | 9.5 | Near-clean | ADR Quality: No ADRs found |
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 45 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 — 45 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, 74 of 91 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: 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 — a coverage step in CI (`mix coveralls`) shows coverage is measured in your own CI.
- 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 7 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 119 test source file(s) (.exs, .ex) 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, .ex, .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 an Elixir mix.exs/REDACTED (Hex), but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Mix dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (6 contributor(s) across 662 commit(s) sampled, automation and bot accounts excluded). One of them holds 92% of the history; the other 5 hold 1.6% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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 (apps/gust_web/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 — 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. 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.
- 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 DockerCompose (examples/docker/single-node/docker-compose.yml). compose up failed (exit 18 — an image could not be pulled) — 86cc7190d1c0 Pulling fs layer 5959c7ea857a Pulling fs layer 6bceb0db2fd1 Pulling fs layer b7106f8586ee Pulling fs layer f85a33377d83 Waiting 86cc7190d1c0 Waiting 5959c7ea857a Waiting 6bceb0db2fd1 Waiting b7106f8586ee Waiting 5788ee6f91dc Waiting f997efa53d88 Waiting a2d17f5b24d5 Waiting gust-web Error context canceled no matching manifest for linux/amd64 in the manifest list entries; the earlier `compose pull` step reported: gust-web Skipped - Image is already being pulled by gust-init db Pulling gust-init Pulling no matching manifest for linux/amd64 in the manifest list entries; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- 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.
- 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- 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.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 TooManyFunctions finding(s) in God Classes — start with flows.ex, dashboard.ex. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
0 duplicated block group(s) detected. 0.5 % of the production lines (56 of 11,518) are in a reported copy. A further 4 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 1 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with flows.ex. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with dag_worker.ex. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with dag_summary_component.ex. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
5 production modules (npm+OTP), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 4 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 8 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 7 tests. Measured on the JavaScript/TypeScript suite only — at least 119 test source file(s) (.exs, .ex) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
1 outdated, 0 retired direct Hex dependencies, 2 pinning defect(s). 4 of 36 direct dependencies were graded against hex.pm (0 not published there, 32 not resolved by a committed lockfile). 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.
What to do
- Resolve the 2 Unbounded dependency requirement finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 120 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 120 package(s) this repository's committed lockfile installs for a consumer — its 2 production, optional and peer dependency(ies), across 2 product package.json manifest(s), and everything those install in turn. Its 1 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under ISC, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares an Elixir mix.exs/REDACTED (Hex), 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.
D17 · Explicit Debt
0 deducted task-comment markers across 11518 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. 7 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with mix.exs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 6 build units (Mix, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
31 % of calls cross a namespace and 14 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
41 finding(s): 0 critical, 37 high, 4 medium, 0 low. 33 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `.github/scripts/check_release_versions.sh` (line 32, line 33) — 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 33 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 (33 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
11 finding(s): 1 critical, 0 high, 9 medium, 1 low.
What to do
- Resolve the 9 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D31 · IaC & Container Security
7 finding(s): 0 critical, 0 high, 6 medium, 1 low.
What to do
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 50 of the 179 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 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
AC2 · Forms & labels
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×3) — apps/gust_web/lib/gust_web/live/secret_live/index.html.heex:48, apps/gust_web/lib/gust_web/live/secret_live/index.html.heex:55, apps/gust_web/lib/gust_web/live/secret_live/index.html.heex:67
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
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — apps/gust_web/lib/gust_web/components/layouts/root.html.heex:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — apps/gust_web/lib/gust_web/components/core_components.ex:370
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.sidebar` moves (`transition: transform 150ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/gust_web/assets/css/app.css:691
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
- Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
What to do
- Name the access rules — a Bodyguard.Policy or LetMe policy module, a Canada.Can implementation, or roles and permissions declared once — and consult them where access is checked (Bodyguard.permit!, a plug in the pipeline), so the rule set is reviewable and testable on its own.
- Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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
- Most of the production code is in directories of its own, but 1 application file(s) sit at the repository root beside the build and tooling files (`mix.exs`).
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 3/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 3 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:5
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`:crypto.hash(:sha256, data)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — apps/gust_web/lib/gust_web/controllers/assets.ex:34
- 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: apps/gust_web/lib/gust_web/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: apps/gust_web/lib/gust_web/endpoint.ex:2 — `Phoenix.Endpoint`.
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
- 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.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 99% | Exemplary | Strongest area. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 66% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by D12, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 40% | Weak — gated by D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 44% | Weak — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
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
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- 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.
- 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 — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- 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 — compose up failed (exit 18 — an image could not be pulled) — 86cc7190d1c0 Pulling fs layer 5959c7ea857a Pulling fs layer 6bceb0db2fd1 Pulling fs layer b7106f8586ee Pulling fs layer f85a33377d83 Waiting 86cc7190d1c0 Waiting 5959c7ea857a Waiting 6bceb0db2fd1 Waiting b7106f8586ee Waiting 5788ee6f91dc Waiting f997efa53d88 Waiting a2d17f5b24d5 Waiting gust-web Error context canceled no matching manifest for linux/amd64 in the manifest list entries; the earlier `compose pull` step reported: gust-web Skipped - Image is already being pulled by gust-init db Pulling gust-init Pulling no matching manifest for linux/amd64 in the manifest list entries; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in 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
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 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"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .ex, .exs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 none of the 3 signals this lens looks for
- 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
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Elixir, JavaScript/TypeScript source (service entry point: apps/gust_web/lib/gust_web.ex:24 (use Phoenix.Router))
- 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 Benchee jobs (the entries of a `Benchee.run` job map) or Benchfella `bench "…"` blocks under `use Benchfella` in any `.ex`/`.exs` file, or benchee or benchfella in a mix.exs, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: Elixir has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 1% of this repository's production lines — elixir (11,518 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 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
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 1% of this repository's production lines — elixir (11,518 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
- X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Elixir's `nil` is an atom in a dynamically typed language: `@spec`s are checked by an external analysis that has no nullability operator, so there is no null-typed discipline in the language to adopt. Plain JavaScript carries no type annotations and commits no tsconfig, so it states no null-typed discipline for this check to grade: there is nothing here that switches null checking on or off, and TypeScript (or `// @ts-check`) is how a repository acquires one — advice, not a defect this card measures. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 42 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
- <label> that labels no control apps/gust_web/lib/gust_web/live/secret_live/index.html.heex:48
- <label> that labels no control apps/gust_web/lib/gust_web/live/secret_live/index.html.heex:55
- <label> that labels no control apps/gust_web/lib/gust_web/live/secret_live/index.html.heex:67
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <td> apps/gust_web/lib/gust_web/components/core_components.ex:370
- REDACTED
- REDACTED
Serious — 33 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unbounded dependency requirement: postgrex
- Unbounded dependency requirement: phoenix_live_view
- REDACTED
- REDACTED
- TooManyFunctions: Flows apps/gust/lib/gust/flows.ex:1
- TooManyFunctions: Dashboard apps/gust_web/lib/gust_web/live/dag_live/dashboard.ex:1
- Page without a main landmark apps/gust_web/lib/gust_web/components/layouts/root.html.heex:2
- Animation without a prefers-reduced-motion guard apps/gust_web/assets/css/app.css:691
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (11 corresponding lines) apps/gust/lib/gust/flows.ex:420
- Edited copy of a member (12 corresponding lines) apps/gust/lib/gust/dag/runner/dag_worker.ex:88
- Edited copy of a member (7 corresponding lines) apps/gust_web/lib/gust_web/live/dag_summary_component.ex:18
- Edited copy of a member (3 corresponding lines) apps/gust/lib/gust/dag/parser/adapters/elixir.ex:112
- Off the main sequence: gust
- Coverage collected but not gated
- Weak hash algorithm apps/gust_web/lib/gust_web/controllers/assets.ex:34
Minor — 15 finding(s)
- No named authorization policies
- Thin authorization enforcement
- No ADRs found mix.exs:11
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No src/ separation
- Logging is not universal
- No SAST REDACTED:5
- No app-layer HTTPS enforcement detected
- Security headers incomplete
Minor — 1 finding(s)
- Outdated: phoenix_live_view
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-4b531db9fa4d4910b64bcdc10126f93a/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-4b531db9fa4d4910b64bcdc10126f93a/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 . | 41 | 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/** . | 11 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 7 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 |