Executive summary
exposedev/expose is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because it has form fields without a label. It scores 46.3 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 38.2, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 5.6 points. Labelling the form fields and buttons comes next, worth about 3.9 points. Raising Accessibility to 70 would lift the score to about 53.5.
Fourteen known security holes in the packages the code depends on can be used by attackers. Seven form fields can't be read by a screen reader, and five settings leave the servers or containers unsafe. Labelling the form fields, updating the vulnerable packages and correcting the unsafe settings would close these risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed. The four loops of files that import each other need breaking.
The product code is 206,806 lines, about €190,000 to rebuild.
If Accessibility rose from 38.2 to 70, the lowest score rated Strong, the score would rise from 46.3 to about 53.5.
New since the last survey: 9 findings
- Code Duplication · Edited copy of a member (41 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (21 corresponding lines) app/Commands/ServerAwareCommand.php
- Code Duplication · Edited copy of a member (13 corresponding lines) app/Http/Controllers/ReplayLogController.php
- Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) REDACTED
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) app/Logger/Plugins/GitHubPlugin.php
- Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) app/Support/ClearServerNodeVisitor.php
- Code Duplication · Duplicated block (20 lines × 2 locations) resources/js/internal-dashboard/src/components/ui/ResponseBadge.vue
- Dependency Hygiene · Unused dependency '@iconify-json/radix-icons' resources/js/internal-dashboard/package.json
- Dependency Hygiene · Unused dependency 'clipboard' resources/js/internal-dashboard/package.json
Fixed since the last survey: 5 findings
- Code Duplication · Duplicated block (20 lines × 2) REDACTED
- Code Duplication · Duplicated block (13 lines × 2) app/Support/InsertDefaultDomainNodeVisitor.php
- Dependency Hygiene · Unused dependency '@iconify-json/radix-icons'
- Dependency Hygiene · Unused dependency 'clipboard'
- A11y enforcement · Accessibility enforcement below the top rung resources/js/internal-dashboard/package.json
Rebuild cost: about €190,000 · Estimate
| Cost to rebuild | €62,000 to €310,000, for 1,031 to 3,270 hours of work, about 1.3 person-years for 1 to 3 engineers |
|---|---|
| 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 46. 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 | Large: 206,806 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 Database.Seeders | 3 Expose.Client.Commands.Concerns | 4 Expose.Client.Commands.Support | 5 Expose.Client.Exceptions | 6 Expose.Client.Providers | 7 Expose.Client.Support | 8 Expose.Client.WebSockets | 9 resources.js.internal-dashboard.src.lib | 10 resources.js.internal-dashboard.src.lib.composables | 11 Expose.Client.Connections | 12 Expose.Client.Contracts | 13 Expose.Client.Logger.Plugins | 14 Expose.Client.Traits | 15 Expose.Client.Commands | 16 Expose.Client.Logger | 17 Expose.Client.Http | 18 Expose.Client | 19 Expose.Client.Http.Controllers | 20 Expose.Client.Http.Modifiers | 21 Expose.Client.Http.Resources |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | |||||||||||||||||||||
| 2 Database.Seeders | |||||||||||||||||||||
| 3 Expose.Client.Commands.Concerns | |||||||||||||||||||||
| 4 Expose.Client.Commands.Support | |||||||||||||||||||||
| 5 Expose.Client.Exceptions | |||||||||||||||||||||
| 6 Expose.Client.Providers | |||||||||||||||||||||
| 7 Expose.Client.Support | |||||||||||||||||||||
| 8 Expose.Client.WebSockets | |||||||||||||||||||||
| 9 resources.js.internal-dashboard.src.lib | |||||||||||||||||||||
| 10 resources.js.internal-dashboard.src.lib.composables | |||||||||||||||||||||
| 11 Expose.Client.Connections | 1 | ||||||||||||||||||||
| 12 Expose.Client.Contracts | 3 | ||||||||||||||||||||
| 13 Expose.Client.Logger.Plugins | 2 | ||||||||||||||||||||
| 14 Expose.Client.Traits | 1 | ||||||||||||||||||||
| 15 Expose.Client.Commands | 5 | 3 | |||||||||||||||||||
| 16 Expose.Client.Logger | 1 | 5 | 1 | 1 | |||||||||||||||||
| 17 Expose.Client.Http | 1 | 1 | |||||||||||||||||||
| 18 Expose.Client | 1 | 1 | 1 | ||||||||||||||||||
| 19 Expose.Client.Http.Controllers | 2 | 4 | 3 | 1 | |||||||||||||||||
| 20 Expose.Client.Http.Modifiers | 2 | 2 | |||||||||||||||||||
| 21 Expose.Client.Http.Resources | 2 | 1 |
11→18 Expose.Client.Connections uses Expose.Client part of a loop✕
- Connections
- 1 pair of types, where a type in Expose.Client.Connections uses a type in Expose.Client.
- The types involved
Expose.Client.Connections.ControlConnection→Expose.Client.ProxyManager
- Direction
- Expose.Client.Connections uses Expose.Client, so a change to Expose.Client can break Expose.Client.Connections, while a change to Expose.Client.Connections can't break Expose.Client.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→16 Expose.Client.Contracts uses Expose.Client.Logger part of a loop✕
- Connections
- 3 pairs of types, where a type in Expose.Client.Contracts uses a type in Expose.Client.Logger.
- The types involved
Expose.Client.Contracts.LogStorageContract→Expose.Client.Logger.LoggedRequestExpose.Client.Contracts.LoggerContract→Expose.Client.Logger.LoggedRequestExpose.Client.Contracts.LoggerContract→Expose.Client.Logger.LoggedResponse
- Direction
- Expose.Client.Contracts uses Expose.Client.Logger, so a change to Expose.Client.Logger can break Expose.Client.Contracts, while a change to Expose.Client.Contracts can't break Expose.Client.Logger.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→16 Expose.Client.Logger.Plugins uses Expose.Client.Logger part of a loop✕
- Connections
- 2 pairs of types, where a type in Expose.Client.Logger.Plugins uses a type in Expose.Client.Logger.
- The types involved
Expose.Client.Logger.Plugins.BasePlugin→Expose.Client.Logger.LoggedRequestExpose.Client.Logger.Plugins.PluginManager→Expose.Client.Logger.LoggedRequest
- Direction
- Expose.Client.Logger.Plugins uses Expose.Client.Logger, so a change to Expose.Client.Logger can break Expose.Client.Logger.Plugins, while a change to Expose.Client.Logger.Plugins can't break Expose.Client.Logger.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→4 Expose.Client.Traits uses Expose.Client.Commands.Support✕
- Connections
- 1 pair of types, where a type in Expose.Client.Traits uses a type in Expose.Client.Commands.Support.
- The types involved
Expose.Client.Traits.FetchesPlatformData→Expose.Client.Commands.Support.ExposeToken
- Direction
- Expose.Client.Traits uses Expose.Client.Commands.Support, so a change to Expose.Client.Commands.Support can break Expose.Client.Traits, while a change to Expose.Client.Traits can't break Expose.Client.Commands.Support.
- Position
- Below the diagonal: Expose.Client.Traits uses a module listed above it, which is the healthy direction.
15→12 Expose.Client.Commands uses Expose.Client.Contracts✕
- Connections
- 5 pairs of types, where a type in Expose.Client.Commands uses a type in Expose.Client.Contracts.
- The types involved
Expose.Client.Commands.InfoCommand→Expose.Client.Contracts.FetchesPlatformDataContractExpose.Client.Commands.SetUpExposeDefaultDomain→Expose.Client.Contracts.FetchesPlatformDataContractExpose.Client.Commands.SetUpExposeDefaultServer→Expose.Client.Contracts.FetchesPlatformDataContractExpose.Client.Commands.SetUpExposeProToken→Expose.Client.Contracts.FetchesPlatformDataContractExpose.Client.Commands.StoreAuthenticationTokenCommand→Expose.Client.Contracts.FetchesPlatformDataContract
- Direction
- Expose.Client.Commands uses Expose.Client.Contracts, so a change to Expose.Client.Contracts can break Expose.Client.Commands, while a change to Expose.Client.Commands can't break Expose.Client.Contracts.
- Position
- Below the diagonal: Expose.Client.Commands uses a module listed above it, which is the healthy direction.
15→13 Expose.Client.Commands uses Expose.Client.Logger.Plugins✕
- Connections
- 3 pairs of types, where a type in Expose.Client.Commands uses a type in Expose.Client.Logger.Plugins.
- The types involved
Expose.Client.Commands.CreateCustomPluginCommand→Expose.Client.Logger.Plugins.PluginManagerExpose.Client.Commands.ListPluginsCommand→Expose.Client.Logger.Plugins.PluginManagerExpose.Client.Commands.ManagePluginsCommand→Expose.Client.Logger.Plugins.PluginManager
- Direction
- Expose.Client.Commands uses Expose.Client.Logger.Plugins, so a change to Expose.Client.Logger.Plugins can break Expose.Client.Commands, while a change to Expose.Client.Commands can't break Expose.Client.Logger.Plugins.
- Position
- Below the diagonal: Expose.Client.Commands uses a module listed above it, which is the healthy direction.
16→7 Expose.Client.Logger uses Expose.Client.Support✕
- Connections
- 1 pair of types, where a type in Expose.Client.Logger uses a type in Expose.Client.Support.
- The types involved
Expose.Client.Logger.CliLogger→Expose.Client.Support.ConsoleSectionOutput
- Direction
- Expose.Client.Logger uses Expose.Client.Support, so a change to Expose.Client.Support can break Expose.Client.Logger, while a change to Expose.Client.Logger can't break Expose.Client.Support.
- Position
- Below the diagonal: Expose.Client.Logger uses a module listed above it, which is the healthy direction.
16→12 Expose.Client.Logger uses Expose.Client.Contracts✕
- Connections
- 5 pairs of types, where a type in Expose.Client.Logger uses a type in Expose.Client.Contracts.
- The types involved
Expose.Client.Logger.CliLogger→Expose.Client.Contracts.LoggerContractExpose.Client.Logger.DatabaseLogger→Expose.Client.Contracts.LogStorageContractExpose.Client.Logger.DatabaseLogger→Expose.Client.Contracts.LoggerContractExpose.Client.Logger.FrontendLogger→Expose.Client.Contracts.LoggerContractExpose.Client.Logger.RequestLogger→Expose.Client.Contracts.LogStorageContract
- Direction
- Expose.Client.Logger uses Expose.Client.Contracts, so a change to Expose.Client.Contracts can break Expose.Client.Logger, while a change to Expose.Client.Logger can't break Expose.Client.Contracts.
- Position
- Below the diagonal: Expose.Client.Logger uses a module listed above it, which is the healthy direction.
16→13 Expose.Client.Logger uses Expose.Client.Logger.Plugins✕
- Connections
- 1 pair of types, where a type in Expose.Client.Logger uses a type in Expose.Client.Logger.Plugins.
- The types involved
Expose.Client.Logger.LoggedRequest→Expose.Client.Logger.Plugins.PluginData
- Direction
- Expose.Client.Logger uses Expose.Client.Logger.Plugins, so a change to Expose.Client.Logger.Plugins can break Expose.Client.Logger, while a change to Expose.Client.Logger can't break Expose.Client.Logger.Plugins.
- Position
- Below the diagonal: Expose.Client.Logger uses a module listed above it, which is the healthy direction.
16→18 Expose.Client.Logger uses Expose.Client part of a loop✕
- Connections
- 1 pair of types, where a type in Expose.Client.Logger uses a type in Expose.Client.
- The types involved
Expose.Client.Logger.LoggedRequest→Expose.Client.RequestLog
- Direction
- Expose.Client.Logger uses Expose.Client, so a change to Expose.Client can break Expose.Client.Logger, while a change to Expose.Client.Logger can't break Expose.Client.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→16 Expose.Client.Http uses Expose.Client.Logger✕
- Connections
- 1 pair of types, where a type in Expose.Client.Http uses a type in Expose.Client.Logger.
- The types involved
Expose.Client.Http.HttpClient→Expose.Client.Logger.RequestLogger
- Direction
- Expose.Client.Http uses Expose.Client.Logger, so a change to Expose.Client.Logger can break Expose.Client.Http, while a change to Expose.Client.Http can't break Expose.Client.Logger.
- Position
- Below the diagonal: Expose.Client.Http uses a module listed above it, which is the healthy direction.
17→18 Expose.Client.Http uses Expose.Client part of a loop✕
- Connections
- 1 pair of types, where a type in Expose.Client.Http uses a type in Expose.Client.
- The types involved
Expose.Client.Http.HttpClient→Expose.Client.Configuration
- Direction
- Expose.Client.Http uses Expose.Client, so a change to Expose.Client can break Expose.Client.Http, while a change to Expose.Client.Http can't break Expose.Client.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→11 Expose.Client uses Expose.Client.Connections✕
- Connections
- 1 pair of types, where a type in Expose.Client uses a type in Expose.Client.Connections.
- The types involved
Expose.Client.Client→Expose.Client.Connections.ControlConnection
- Direction
- Expose.Client uses Expose.Client.Connections, so a change to Expose.Client.Connections can break Expose.Client, while a change to Expose.Client can't break Expose.Client.Connections.
- Position
- Below the diagonal: Expose.Client uses a module listed above it, which is the healthy direction.
18→16 Expose.Client uses Expose.Client.Logger✕
- Connections
- 1 pair of types, where a type in Expose.Client uses a type in Expose.Client.Logger.
- The types involved
Expose.Client.Client→Expose.Client.Logger.CliLogger
- Direction
- Expose.Client uses Expose.Client.Logger, so a change to Expose.Client.Logger can break Expose.Client, while a change to Expose.Client can't break Expose.Client.Logger.
- Position
- Below the diagonal: Expose.Client uses a module listed above it, which is the healthy direction.
18→17 Expose.Client uses Expose.Client.Http✕
- Connections
- 1 pair of types, where a type in Expose.Client uses a type in Expose.Client.Http.
- The types involved
Expose.Client.Factory→Expose.Client.Http.App
- Direction
- Expose.Client uses Expose.Client.Http, so a change to Expose.Client.Http can break Expose.Client, while a change to Expose.Client can't break Expose.Client.Http.
- Position
- Below the diagonal: Expose.Client uses a module listed above it, which is the healthy direction.
19→12 Expose.Client.Http.Controllers uses Expose.Client.Contracts✕
- Connections
- 2 pairs of types, where a type in Expose.Client.Http.Controllers uses a type in Expose.Client.Contracts.
- The types involved
Expose.Client.Http.Controllers.GetLogsController→Expose.Client.Contracts.LogStorageContractExpose.Client.Http.Controllers.SearchLogsController→Expose.Client.Contracts.LogStorageContract
- Direction
- Expose.Client.Http.Controllers uses Expose.Client.Contracts, so a change to Expose.Client.Contracts can break Expose.Client.Http.Controllers, while a change to Expose.Client.Http.Controllers can't break Expose.Client.Contracts.
- Position
- Below the diagonal: Expose.Client.Http.Controllers uses a module listed above it, which is the healthy direction.
19→16 Expose.Client.Http.Controllers uses Expose.Client.Logger✕
- Connections
- 4 pairs of types, where a type in Expose.Client.Http.Controllers uses a type in Expose.Client.Logger.
- The types involved
Expose.Client.Http.Controllers.ClearLogsController→Expose.Client.Logger.RequestLoggerExpose.Client.Http.Controllers.GetLogController→Expose.Client.Logger.RequestLoggerExpose.Client.Http.Controllers.ReplayLogController→Expose.Client.Logger.RequestLoggerExpose.Client.Http.Controllers.ReplayModifiedLogController→Expose.Client.Logger.RequestLogger
- Direction
- Expose.Client.Http.Controllers uses Expose.Client.Logger, so a change to Expose.Client.Logger can break Expose.Client.Http.Controllers, while a change to Expose.Client.Http.Controllers can't break Expose.Client.Logger.
- Position
- Below the diagonal: Expose.Client.Http.Controllers uses a module listed above it, which is the healthy direction.
19→17 Expose.Client.Http.Controllers uses Expose.Client.Http✕
- Connections
- 3 pairs of types, where a type in Expose.Client.Http.Controllers uses a type in Expose.Client.Http.
- The types involved
Expose.Client.Http.Controllers.GetLogController→Expose.Client.Http.HttpClientExpose.Client.Http.Controllers.ReplayLogController→Expose.Client.Http.HttpClientExpose.Client.Http.Controllers.ReplayModifiedLogController→Expose.Client.Http.HttpClient
- Direction
- Expose.Client.Http.Controllers uses Expose.Client.Http, so a change to Expose.Client.Http can break Expose.Client.Http.Controllers, while a change to Expose.Client.Http.Controllers can't break Expose.Client.Http.
- Position
- Below the diagonal: Expose.Client.Http.Controllers uses a module listed above it, which is the healthy direction.
19→18 Expose.Client.Http.Controllers uses Expose.Client✕
- Connections
- 1 pair of types, where a type in Expose.Client.Http.Controllers uses a type in Expose.Client.
- The types involved
Expose.Client.Http.Controllers.DashboardController→Expose.Client.Configuration
- Direction
- Expose.Client.Http.Controllers uses Expose.Client, so a change to Expose.Client can break Expose.Client.Http.Controllers, while a change to Expose.Client.Http.Controllers can't break Expose.Client.
- Position
- Below the diagonal: Expose.Client.Http.Controllers uses a module listed above it, which is the healthy direction.
20→16 Expose.Client.Http.Modifiers uses Expose.Client.Logger✕
- Connections
- 2 pairs of types, where a type in Expose.Client.Http.Modifiers uses a type in Expose.Client.Logger.
- The types involved
Expose.Client.Http.Modifiers.CheckMagicAuthentication→Expose.Client.Logger.CliLoggerExpose.Client.Http.Modifiers.CheckMagicAuthentication→Expose.Client.Logger.RequestLogger
- Direction
- Expose.Client.Http.Modifiers uses Expose.Client.Logger, so a change to Expose.Client.Logger can break Expose.Client.Http.Modifiers, while a change to Expose.Client.Http.Modifiers can't break Expose.Client.Logger.
- Position
- Below the diagonal: Expose.Client.Http.Modifiers uses a module listed above it, which is the healthy direction.
20→18 Expose.Client.Http.Modifiers uses Expose.Client✕
- Connections
- 2 pairs of types, where a type in Expose.Client.Http.Modifiers uses a type in Expose.Client.
- The types involved
Expose.Client.Http.Modifiers.CheckBasicAuthentication→Expose.Client.ConfigurationExpose.Client.Http.Modifiers.CheckMagicAuthentication→Expose.Client.Configuration
- Direction
- Expose.Client.Http.Modifiers uses Expose.Client, so a change to Expose.Client can break Expose.Client.Http.Modifiers, while a change to Expose.Client.Http.Modifiers can't break Expose.Client.
- Position
- Below the diagonal: Expose.Client.Http.Modifiers uses a module listed above it, which is the healthy direction.
21→16 Expose.Client.Http.Resources uses Expose.Client.Logger✕
- Connections
- 2 pairs of types, where a type in Expose.Client.Http.Resources uses a type in Expose.Client.Logger.
- The types involved
Expose.Client.Http.Resources.CliLogResource→Expose.Client.Logger.LoggedRequestExpose.Client.Http.Resources.LogListResource→Expose.Client.Logger.LoggedRequest
- Direction
- Expose.Client.Http.Resources uses Expose.Client.Logger, so a change to Expose.Client.Logger can break Expose.Client.Http.Resources, while a change to Expose.Client.Http.Resources can't break Expose.Client.Logger.
- Position
- Below the diagonal: Expose.Client.Http.Resources uses a module listed above it, which is the healthy direction.
21→18 Expose.Client.Http.Resources uses Expose.Client✕
- Connections
- 1 pair of types, where a type in Expose.Client.Http.Resources uses a type in Expose.Client.
- The types involved
Expose.Client.Http.Resources.LogListResource→Expose.Client.RequestLog
- Direction
- Expose.Client.Http.Resources uses Expose.Client, so a change to Expose.Client can break Expose.Client.Http.Resources, while a change to Expose.Client.Http.Resources can't break Expose.Client.
- Position
- Below the diagonal: Expose.Client.Http.Resources 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 | 30 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 17 | High / Critical |
| A02:2025 — Security Misconfiguration | 6 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +5.6 pts | Medium | Keyboard semantics |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +3.9 pts | Medium | Forms & labels |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +3.5 pts | Medium | Page structure |
| 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. | +3.4 pts | Medium | Visual & motion safety |
| Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +3.0 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. | +1.1 pts | Low | ADR Quality |
| Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail. | +1.9 pts | Medium | Outbound HTTP resilience |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +1.7 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| app/Commands/ShareCommand.php | 7.0 | Mixed | Cognitive Complexity: ShareCommand.handle (cognitive 17) |
| REDACTED | 7.2 | Mixed | IaC & Container Security: High IaC: REDACTED |
| app/Http/Controllers/ReplayLogController.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (13 corresponding lines) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| resources/js/internal-dashboard/src/lib/utils.ts | 8.5 | Near-clean | Cognitive Complexity: utils.toPhpArray (cognitive 23) |
| app/Logger/LoggedRequest.php | 8.5 | Near-clean | Cognitive Complexity: LoggedRequest.getPostData (cognitive 19) |
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 58 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 — 58 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, 172 of 179 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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. Not scored — 1 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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 composer.json, but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Composer dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — 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.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 (REDACTED). compose up failed (exit 15 — the compose project is invalid) — time="2026-11-17T13:46:19Z" level=warning msg="The \"DOMAIN\" variable is not set. Defaulting to a blank string." time="2026-11-17T13:46:19Z" level=warning msg="The \"ADMIN_USERNAME\" variable is not set. Defaulting to a blank string." time="2026-11-17T13:46:19Z" level=warning msg="The \"ADMIN_PASSWORD\" variable is not set. Defaulting to a blank string." no port specified: 8080:<empty>; 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, Scala, Rust and Java source only, and this repository's , PHP, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's , PHP, Vue components 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.
- P2 Observability — 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. Observability was not assessed: this check recognises the logging, tracing/metrics and health-check idioms of .NET (C#, Visual Basic and F#), the JVM, Go, Python, JavaScript/TypeScript, Rust, Ruby, PHP, Swift, Dart, Elixir and Erlang, and most of this repository's production source is in none of them. Absence of an idiom this check recognises is NOT evidence that this repo lacks structured logging. This is a gap in the analyzer, not a finding about this repository.
- S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- 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.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- 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
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was utils.toPhpArray at 23.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with utils.toPhpArray (cognitive 23), StoreAuthenticationTokenCommand.handle (cognitive 19), LoggedRequest.getPostData (cognitive 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
6 duplicated block group(s) detected. 0.2 % of the production lines (358 of 206,806) are in a reported copy. A further 7 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 Members sharing a duplicated core (7 members, 50+ identical tokens) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (41 corresponding lines) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with ServerAwareCommand.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (npm+Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
1 of 34 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with DatabaseLogger.php. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 153 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 153 package(s) this repository's committed lockfile installs for a consumer — its 11 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 9 `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. Third-party code that ships WITHOUT a manifest entry was read too: 6 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 0 use a banned licence. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares composer.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 29 of the 110 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 206806 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. 32 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 composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Composer, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
18 % of calls cross a namespace and 2 % 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)
30 finding(s): 0 critical, 3 high, 27 medium, 0 low. 2 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. 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 25 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (25 warning-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 2 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 (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
17 finding(s): 0 critical, 14 high, 3 medium, 0 low.
What to do
- Resolve the 14 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
6 finding(s): 1 critical, 4 high, 1 medium, 0 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
10 of 29 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app/Logger/DatabaseLogger.php. Counted over 29 of the 110 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 10 Orphaned file finding(s) in Knowledge Freshness — start with DatabaseLogger.php, CliLogger.php, REDACTED. — One of this dimension's main actionable groups (10 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: ShareCommand.php↔Configuration.php 50%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with ShareCommand.php. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×6) — resources/js/internal-dashboard/src/components/ModifiedReplayModal.vue:218, resources/js/internal-dashboard/src/components/ModifiedReplayModal.vue:231, resources/js/internal-dashboard/src/components/ModifiedReplayModal.vue:331, …
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — resources/js/internal-dashboard/src/components/ui/RowAccordionButton.vue:11
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — resources/js/internal-dashboard/src/components/ui/Search.vue:39
- This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — resources/js/internal-dashboard/src/components/ui/checkbox/MasterCheckbox.vue:47
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. This document's body is only the mount point <div id="internalDashboard">, so there is no content here to wrap — render the <main> from the component mounted into it. (×2) — resources/js/internal-dashboard/index.html:2, resources/views/client/internal_dashboard.blade.php:2
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — resources/js/internal-dashboard/src/components/Requests/Tabs/Response.vue:182
- An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — resources/js/internal-dashboard/src/components/ui/card/CardTitle.vue:11
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — resources/views/client/magic_login.blade.php: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
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — resources/js/internal-dashboard/src/components/Requests/Tabs/Request.vue:175
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — resources/js/internal-dashboard/src/components/ui/checkbox/MasterCheckbox.vue:47
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
- <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×4) — resources/js/internal-dashboard/src/components/ui/HeaderSingleIconButton.vue:21, resources/js/internal-dashboard/src/components/ui/IconButton.vue:26, resources/js/internal-dashboard/src/components/ui/IconCopyButton.vue:28, …
- This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×3) — resources/js/internal-dashboard/src/components/ui/HeaderSingleIconButton.vue:21, resources/js/internal-dashboard/src/components/ui/IconCopyButton.vue:28, resources/js/internal-dashboard/src/components/ui/IconTextButton.vue:16
- <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — resources/js/internal-dashboard/src/components/ui/Search.vue:39, resources/js/internal-dashboard/src/components/ui/input/Input.vue:23
- `button` moves (`transition: background-color 0.2s, transform 0.1s`) 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. — resources/views/client/magic_login.blade.php:130
- `button` sets color: white on background-color: #DE4E78 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — resources/views/client/magic_login.blade.php:118
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
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- 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
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add phpstan or psalm (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 1 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:3
- `resources/js/internal-dashboard/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — resources/js/internal-dashboard/package.json:11
What to do
- Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `Http::withOptions(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — app/Commands/ServerAwareCommand.php:92
- `Http::withHeaders(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — app/Traits/FetchesPlatformData.php:27
- `Http::post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — app/Traits/FetchesPlatformData.php:81, app/Traits/FetchesPlatformData.php:104
What to do
- Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.
P8 · Schema migrations
R1 · Type Safety
R10 · Code Duplication
- 9 duplicated blocks under resources/js/internal-dashboard/src/components/ui/ have copies in at least two of the sibling directories accordion, dialog, dropdown-menu, select, switch, tabs — 4 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuContent.vue:12
- resources/js/internal-dashboard/src/components/ModifiedReplayModal.vue:110 · resources/js/internal-dashboard/src/components/ModifiedReplayModal.vue:136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/internal-dashboard/src/components/ModifiedReplayModal.vue:110
- resources/js/internal-dashboard/src/components/ui/ResponseBadge.vue:12 · resources/js/internal-dashboard/src/components/ui/ResponseBadge.vue:34 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/internal-dashboard/src/components/ui/ResponseBadge.vue:12
- resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuContent.vue:12 · resources/js/internal-dashboard/src/components/ui/select/SelectContent.vue:18 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuContent.vue:12
- resources/js/internal-dashboard/src/components/ui/input/Input.vue:6 · resources/js/internal-dashboard/src/components/ui/input/TableInput.vue:6 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — resources/js/internal-dashboard/src/components/ui/input/Input.vue:6
- resources/js/internal-dashboard/src/components/ui/accordion/AccordionItem.vue:4 · resources/js/internal-dashboard/src/components/ui/dialog/DialogDescription.vue:4 · resources/js/internal-dashboard/src/components/ui/dialog/DialogTitle.vue:4 · resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuSubTrigger.vue:9 · +3 more site(s) not listed — the 7 copies are spread across 7 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — resources/js/internal-dashboard/src/components/ui/accordion/AccordionItem.vue:4
- resources/js/internal-dashboard/src/components/ui/dialog/DialogContent.vue:15 · resources/js/internal-dashboard/src/components/ui/dialog/SidebarDialog.vue:15 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — resources/js/internal-dashboard/src/components/ui/dialog/DialogContent.vue:15
- resources/js/internal-dashboard/src/components/ui/dialog/DialogContent.vue:15 · resources/js/internal-dashboard/src/components/ui/dialog/DialogScrollContent.vue:15 · resources/js/internal-dashboard/src/components/ui/dialog/SidebarDialog.vue:15 · resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuCheckboxItem.vue:13 · +3 more site(s) not listed — the 7 copies are spread across 7 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — resources/js/internal-dashboard/src/components/ui/dialog/DialogContent.vue:15
- resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuCheckboxItem.vue:13 · resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuRadioItem.vue:12 · resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuSubContent.vue:11 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuCheckboxItem.vue:13
- resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuRadioItem.vue:12 · resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuSubContent.vue:11 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuRadioItem.vue:12
- resources/js/internal-dashboard/src/components/ui/accordion/AccordionContent.vue:2 · resources/js/internal-dashboard/src/components/ui/tabs/TabsContent.vue:2 · resources/js/internal-dashboard/src/components/ui/tabs/TabsList.vue:2 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — resources/js/internal-dashboard/src/components/ui/accordion/AccordionContent.vue:2
- resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuItem.vue:6 · resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuLabel.vue:6 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuItem.vue:6
- resources/js/internal-dashboard/src/lib/utils.ts:74 · resources/js/internal-dashboard/src/lib/utils.ts:91 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — resources/js/internal-dashboard/src/lib/utils.ts:74
- resources/js/internal-dashboard/src/components/ui/select/SelectGroup.vue:3 · resources/js/internal-dashboard/src/components/ui/select/SelectScrollDownButton.vue:4 · resources/js/internal-dashboard/src/components/ui/select/SelectScrollUpButton.vue:4 · resources/js/internal-dashboard/src/components/ui/select/SelectSeparator.vue:3 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/internal-dashboard/src/components/ui/select/SelectGroup.vue:3
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- setupKeybindings has cyclomatic complexity 26 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/internal-dashboard/src/InternalDashboard.vue:110
- toPhpArray has cyclomatic complexity 11 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/internal-dashboard/src/lib/utils.ts:21
R3 · Large Files
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 3 application, 5 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (3 application, 5 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (resources/js/internal-dashboard/src/components/ui/toggle-group/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — resources/js/internal-dashboard/src/components/ui/toggle-group/ToggleGroup.vue, resources/js/internal-dashboard/src/components/ui/toggle-group/ToggleGroupItem.vue
- no import path from any entry point (3 application, 5 tooling, 0 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (resources/js/internal-dashboard/src/components/ui/toggle-group/ToggleGroup.vue, resources/js/internal-dashboard/src/components/ui/toggle-group/ToggleGroupItem.vue, resources/js/internal-dashboard/src/components/ui/toggle/Toggle.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/internal-dashboard/src/components/ui/toggle/index.ts
- no import path from any entry point (3 application, 5 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (resources/js/internal-dashboard/src/components/ui/badge/Badge.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/internal-dashboard/src/components/ui/badge/index.ts
- no import path from any entry point (3 application, 5 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (resources/js/internal-dashboard/src/components/ui/toggle/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/internal-dashboard/src/components/ui/toggle/Toggle.vue
- no import path from any entry point (3 application, 5 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (resources/js/internal-dashboard/src/components/ui/switch/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/internal-dashboard/src/components/ui/switch/Switch.vue
- no import path from any entry point (3 application, 5 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (resources/js/internal-dashboard/src/components/ui/badge/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/internal-dashboard/src/components/ui/badge/Badge.vue
- no import path from any entry point (3 application, 5 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (resources/js/internal-dashboard/src/components/ui/card/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×6) — resources/js/internal-dashboard/src/components/ui/card/Card.vue, resources/js/internal-dashboard/src/components/ui/card/CardContent.vue, resources/js/internal-dashboard/src/components/ui/card/CardDescription.vue, …
- no import path from any entry point (3 application, 5 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — resources/js/internal-dashboard/src/components/ui/card/index.ts, resources/js/internal-dashboard/src/components/ui/toggle-group/index.ts, resources/js/internal-dashboard/src/components/ui/switch/index.ts
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in resources/js/internal-dashboard/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2) — resources/js/internal-dashboard/package.json:25, resources/js/internal-dashboard/package.json:15
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- resources/js/internal-dashboard/src/components/ui/badge/Badge.vue → resources/js/internal-dashboard/src/components/ui/badge/index.ts → resources/js/internal-dashboard/src/components/ui/badge/Badge.vue — resources/js/internal-dashboard/src/components/ui/badge/Badge.vue:3
- resources/js/internal-dashboard/src/components/ui/button/Button.vue → resources/js/internal-dashboard/src/components/ui/button/index.ts → resources/js/internal-dashboard/src/components/ui/button/Button.vue — resources/js/internal-dashboard/src/components/ui/button/Button.vue:4
- resources/js/internal-dashboard/src/components/ui/select/SelectContent.vue → resources/js/internal-dashboard/src/components/ui/select/index.ts → resources/js/internal-dashboard/src/components/ui/select/SelectContent.vue — resources/js/internal-dashboard/src/components/ui/select/SelectContent.vue:12
- resources/js/internal-dashboard/src/components/ui/toggle/Toggle.vue → resources/js/internal-dashboard/src/components/ui/toggle/index.ts → resources/js/internal-dashboard/src/components/ui/toggle/Toggle.vue — resources/js/internal-dashboard/src/components/ui/toggle/Toggle.vue:4
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X16 · Unfloored truncation loop
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
- line 75 walks `$this->pluginConfig` by value, so the walk is the snapshot taken when the loop began, and line 78 changes that same collection with `$this->pluginConfig = …` before the next iteration: the loop carries on over the old value while the body now works on the new one. PHP raises nothing, so the loop completes over a different set than the code meant. — REDACTED:75
What to do
- Each finding names the two lines that cannot both stand — the `foreach` over the collection, and the change to it in the body. Confirm from those two, then pick one: build the result instead of editing the walked collection (`$kept = array_filter($items, $keep)`, `$batch->reject(…)`); for a worklist, loop `while (($next = array_shift($queue)) !== null)` so what is added is visited; walk a copy (`foreach (array_values($items) as …)`, `foreach (clone $storage as …)`) and change the original; remove only the CURRENT element (`unset($items[$key])`), which an array walk tolerates; or — where only the first match was ever meant — `break` straight after the change.
X3 · Exception handling
- `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — app/Logger/LoggedRequest.php:107, app/Logger/LoggedRequest.php:283, app/Commands/ServerAwareCommand.php:97
- `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — app/Logger/LoggedResponse.php:38, app/Http/Modifiers/CheckBasicAuthentication.php:101, app/Commands/ShareCurrentWorkingDirectoryCommand.php:66
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — REDACTED:54
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
- `info` at line 222 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Client.php:222
- `info` at line 223 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Client.php:223
- `info` at line 224 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Client.php:224
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 50.6 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 71.5 | Adequate — gated by D26, R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 66.6 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 45.6 | Weak — gated by P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 74.9 | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 38.2 | Weak — gated by AC2, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 66 check(s) not relevant to this codebase
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 15 — the compose project is invalid) — time="2026-11-17T13:46:19Z" level=warning msg="The \"DOMAIN\" variable is not set. Defaulting to a blank string." time="2026-11-17T13:46:19Z" level=warning msg="The \"ADMIN_USERNAME\" variable is not set. Defaulting to a blank string." time="2026-11-17T13:46:19Z" level=warning msg="The \"ADMIN_PASSWORD\" variable is not set. Defaulting to a blank string." no port specified: 8080:<empty>; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~879 lines of test source are present (.php) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 1 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .php 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 included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); its 2 aggregate(s) are ORM models only — persistence, not behaviour: a CRUD model, measured, not claimed as DDD)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — Observability was not assessed: this check recognises the logging, tracing/metrics and health-check idioms of .NET (C#, Visual Basic and F#), the JVM, Go, Python, JavaScript/TypeScript, Rust, Ruby, PHP, Swift, Dart, Elixir and Erlang, and most of this repository's production source is in none of them. Absence of an idiom this check recognises is NOT evidence that this repo lacks structured logging. This is a gap in the analyzer, not a finding about this repository.
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (105 production file(s)) has no JavaScript/TypeScript test, but it is 1.74% of this repository's production source and the other 98.26% carries 879 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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
- X12 Unreachable branch — X12 reached only 2% of this repository's production lines — php (205,863 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
- X17 Uncapped recursion over a caller-supplied document — X17 reached only 2% of this repository's production lines — php (205,863 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 2% of this repository's production lines — php (205,863 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 37 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label resources/js/internal-dashboard/src/components/ModifiedReplayModal.vue:231
- <input> without a programmatic label resources/js/internal-dashboard/src/components/ui/Search.vue:39
- <input> without a programmatic label resources/js/internal-dashboard/src/components/ui/input/Input.vue:23
- <input> without a programmatic label resources/js/internal-dashboard/src/components/ui/input/TableInput.vue:23
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) resources/js/internal-dashboard/src/components/ui/badge/Badge.vue:3
- Import cycle (2 files) resources/js/internal-dashboard/src/components/ui/button/Button.vue:4
- Import cycle (2 files) resources/js/internal-dashboard/src/components/ui/select/SelectContent.vue:12
- Import cycle (2 files) resources/js/internal-dashboard/src/components/ui/toggle/Toggle.vue:4
- <textarea> without a programmatic label resources/js/internal-dashboard/src/components/ModifiedReplayModal.vue:331
- <textarea> without a programmatic label resources/js/internal-dashboard/src/components/ui/textarea/Textarea.vue:23
- REDACTED
- REDACTED
- <select> without a programmatic label resources/js/internal-dashboard/src/components/ModifiedReplayModal.vue:218
- <button> with no accessible text resources/js/internal-dashboard/src/components/ui/RowAccordionButton.vue:11
- Custom control with no accessible name on <div> resources/js/internal-dashboard/src/components/ui/checkbox/MasterCheckbox.vue:47
- <iframe> without a title resources/js/internal-dashboard/src/components/Requests/Tabs/Response.vue:182
- Click handler on a non-interactive <div> resources/js/internal-dashboard/src/components/ui/checkbox/MasterCheckbox.vue:47
- REDACTED
- REDACTED
Serious — 114 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
- Focus outline removed inline resources/js/internal-dashboard/src/components/ui/HeaderSingleIconButton.vue:21
- Focus outline removed inline resources/js/internal-dashboard/src/components/ui/IconButton.vue:26
- Focus outline removed inline resources/js/internal-dashboard/src/components/ui/IconCopyButton.vue:28
- Focus outline removed inline resources/js/internal-dashboard/src/components/ui/IconTextButton.vue:16
- Focus outline removed inline resources/js/internal-dashboard/src/components/ui/Search.vue:39
- Focus outline removed inline resources/js/internal-dashboard/src/components/ui/input/Input.vue:23
- Dead file (~7 LoC) resources/js/internal-dashboard/src/components/ui/card/Card.vue
- Dead file (~7 LoC) resources/js/internal-dashboard/src/components/ui/card/CardContent.vue
- Dead file (~7 LoC) resources/js/internal-dashboard/src/components/ui/card/CardDescription.vue
- Dead file (~7 LoC) resources/js/internal-dashboard/src/components/ui/card/CardFooter.vue
- Dead file (~7 LoC) resources/js/internal-dashboard/src/components/ui/card/CardHeader.vue
- Dead file (~7 LoC) resources/js/internal-dashboard/src/components/ui/card/CardTitle.vue
- Swallowed exception (caught, then discarded) app/Logger/LoggedRequest.php:107
- Swallowed exception (caught, then discarded) app/Logger/LoggedRequest.php:283
- Swallowed exception (caught, then discarded) app/Logger/LoggedResponse.php:38
- Swallowed exception (caught, then discarded) app/Http/Modifiers/CheckBasicAuthentication.php:101
- Swallowed exception (caught, then discarded) app/Commands/ServerAwareCommand.php:97
- Swallowed exception (caught, then discarded) app/Commands/ShareCurrentWorkingDirectoryCommand.php:66
- Outbound HTTP without resilience app/Commands/ServerAwareCommand.php:92
- Outbound HTTP without resilience app/Traits/FetchesPlatformData.php:27
- Outbound HTTP without resilience app/Traits/FetchesPlatformData.php:81
- Outbound HTTP without resilience app/Traits/FetchesPlatformData.php:104
- Page without a main landmark resources/js/internal-dashboard/index.html:2
- Page without a main landmark resources/views/client/internal_dashboard.blade.php:2
- Page without a main landmark resources/views/client/magic_login.blade.php:2
- Low contrast Tailwind colour pair (2.6:1) resources/js/internal-dashboard/src/components/ui/HeaderSingleIconButton.vue:21
- Low contrast Tailwind colour pair (2.6:1) resources/js/internal-dashboard/src/components/ui/IconCopyButton.vue:28
- Low contrast Tailwind colour pair (2.6:1) resources/js/internal-dashboard/src/components/ui/IconTextButton.vue:16
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2 locations) resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuContent.vue:12
- Duplicated block (12 lines × 2 locations) resources/js/internal-dashboard/src/components/ui/input/Input.vue:6
- Duplicated block (7 lines × 7 locations) resources/js/internal-dashboard/src/components/ui/accordion/AccordionItem.vue:4
- Duplicated block (7 lines × 7 locations) resources/js/internal-dashboard/src/components/ui/dialog/DialogContent.vue:15
- Duplicated block (7 lines × 2 locations) resources/js/internal-dashboard/src/components/ui/dialog/DialogContent.vue:15
- Duplicated block (7 lines × 2 locations) resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuRadioItem.vue:12
- Dead file (~27 LoC) resources/js/internal-dashboard/src/components/ui/toggle-group/ToggleGroup.vue
- Dead file (~27 LoC) resources/js/internal-dashboard/src/components/ui/toggle/index.ts
- Dead file (~25 LoC) resources/js/internal-dashboard/src/components/ui/badge/index.ts
- Dead file (~25 LoC) resources/js/internal-dashboard/src/components/ui/toggle/Toggle.vue
- Empty <h3> heading resources/js/internal-dashboard/src/components/ui/card/CardTitle.vue:11
- Anchor without href resources/js/internal-dashboard/src/components/Requests/Tabs/Request.vue:175
- Animation without a prefers-reduced-motion guard resources/views/client/magic_login.blade.php:130
- Low contrast colour pair in CSS (3.8:1) resources/views/client/magic_login.blade.php:118
- utils.toPhpArray (cognitive 23) resources/js/internal-dashboard/src/lib/utils.ts:21
- StoreAuthenticationTokenCommand.handle (cognitive 19) REDACTED:36
- LoggedRequest.getPostData (cognitive 19) app/Logger/LoggedRequest.php:189
- ShareCommand.handle (cognitive 17) app/Commands/ShareCommand.php:36
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change coupling: ShareCommand.php ↔ Configuration.php app/Commands/ShareCommand.php:1
- REDACTED
- Members sharing a duplicated core (7 members, 50+ identical tokens) REDACTED:55
- Edited copy of a member (41 corresponding lines) REDACTED:32
- Edited copy of a member (21 corresponding lines) app/Commands/ServerAwareCommand.php:41
- Edited copy of a member (13 corresponding lines) app/Http/Controllers/ReplayLogController.php:21
- Edited copies of one member (4 members, 14+ corresponding lines) REDACTED:32
- Edited copies of one member (3 members, 7+ corresponding lines) app/Logger/Plugins/GitHubPlugin.php:21
- Edited copies of one member (4 members, 5+ corresponding lines) app/Support/ClearServerNodeVisitor.php:13
- Duplicated block (18 lines × 5) REDACTED:61
- Duplicated block (18 lines × 2) REDACTED:214
- Duplicated block (15–17 lines × 7) REDACTED:55
- Duplicated block (14 lines × 2) REDACTED:32
- Duplicated block (12 lines × 2) app/Logger/Plugins/PaddleBillingPlugin.php:30
- Duplicated block (11 lines × 2) app/Http/Controllers/ReplayLogController.php:23
- Low cohesion: DatabaseLogger (LCOM4 4) app/Logger/DatabaseLogger.php:14
- Duplication concentrated across 6 sibling directories (9 clone groups) resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuContent.vue:12
- Duplicated block (25 lines × 2 locations) resources/js/internal-dashboard/src/components/ModifiedReplayModal.vue:110
- Duplicated block (20 lines × 2 locations) resources/js/internal-dashboard/src/components/ui/ResponseBadge.vue:12
- Duplicated block (7 lines × 3 locations) resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuCheckboxItem.vue:13
- Duplicated block (6 lines × 3 locations) resources/js/internal-dashboard/src/components/ui/accordion/AccordionContent.vue:2
- Duplicated block (6 lines × 2 locations) resources/js/internal-dashboard/src/components/ui/dropdown-menu/DropdownMenuItem.vue:6
- Duplicated block with local edits (6 matched lines × 2 locations) resources/js/internal-dashboard/src/lib/utils.ts:74
- Duplicated block (5 lines × 4 locations) resources/js/internal-dashboard/src/components/ui/select/SelectGroup.vue:3
- Complex function setupKeybindings (cyclomatic 26, cognitive 19) resources/js/internal-dashboard/src/InternalDashboard.vue:110
- Complex function toPhpArray (cyclomatic 11, cognitive 23) resources/js/internal-dashboard/src/lib/utils.ts:21
- No lint script
- Dead file (~23 LoC) resources/js/internal-dashboard/src/components/ui/toggle-group/ToggleGroupItem.vue
- Dead file (~22 LoC) resources/js/internal-dashboard/src/components/ui/switch/Switch.vue
- Dead file (~9 LoC) resources/js/internal-dashboard/src/components/ui/badge/Badge.vue
- Dead file (~6 LoC) resources/js/internal-dashboard/src/components/ui/card/index.ts
- Dead file (~2 LoC) resources/js/internal-dashboard/src/components/ui/toggle-group/index.ts
- Dead file (~1 LoC) resources/js/internal-dashboard/src/components/ui/switch/index.ts
- Unused dependency '@iconify-json/radix-icons' resources/js/internal-dashboard/package.json:25
- Unused dependency 'clipboard' resources/js/internal-dashboard/package.json:15
- Collection is structurally changed while it is being enumerated REDACTED:75
- Swallowed exception (empty catch) REDACTED:54
Minor — 28 finding(s)
- Orphaned file app/Logger/DatabaseLogger.php:1
- Orphaned file app/Logger/CliLogger.php:1
- Orphaned file REDACTED:1
- Orphaned file app/Commands/InfoCommand.php:1
- Orphaned file REDACTED:1
- Orphaned file app/Logger/Plugins/GitHubPlugin.php:1
- Orphaned file app/Traits/FetchesPlatformData.php:1
- Orphaned file resources/js/internal-dashboard/src/lib/utils.ts:1
- Orphaned file app/Commands/ManagePluginsCommand.php:1
- Orphaned file REDACTED:1
- Silent fallback default in catch app/Commands/ServerAwareCommand.php:97
- Silent fallback default in catch app/Commands/ShareCurrentWorkingDirectoryCommand.php:66
- Silent fallback default in catch app/Http/Modifiers/CheckBasicAuthentication.php:101
- Silent fallback default in catch app/Logger/LoggedRequest.php:283
- Interpolated log message defeats structured logging app/Client.php:222
- Interpolated log message defeats structured logging app/Client.php:223
- Interpolated log message defeats structured logging app/Client.php:224
- No ADRs found composer.json:3
- Projects may be oversized for their cohesion composer.json:1
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- CI build step not evidenced
- No SAST REDACTED:3
- No dependency-update automation resources/js/internal-dashboard/package.json:11
- No rollback/health safety
- Duplicated predicate app/Http/Modifiers/CheckBasicAuthentication.php:24
- PHP static analysis does not check null everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-6e4868c72b5748c8afe91a13fd0a9343/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=532" --report-format json --report-path /tmp/watchdog-gitleaks-6e4868c72b5748c8afe91a13fd0a9343/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6e4868c72b5748c8afe91a13fd0a9343/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 --exclude resources/stubs . | 30 | 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/** . | 17 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 6 | 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 |