Executive summary
laravel/jetstream falls short of our standard for production, in part because we found no logging, tracing or health checks in the code. It scores 42.6 out of 100 and is rated Weak, and four of its 20 critical findings are security problems.
Production Readiness, at 38.9, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 4.2 points. Logging through a logging library would lift Production Readiness itself, worth about 2.9 points. Raising Production Readiness to 70 would lift the score to about 46.1.
Two passwords or keys in the code's history and one in the code are open to anyone who can read the repository. One automatic update takes new releases before a bad one can be spotted, and five controls can't be used without a mouse. Replacing each exposed password or key, setting a waiting period for automatic updates and making the controls work with a keyboard would close these risks. The three buttons or links with no name need a name, even when they only show an icon.
The product code is 7,970 lines, about €9,700 to rebuild.
If Production Readiness rose from 38.9 to 70, the lowest score rated Strong, the score would rise from 42.6 to about 46.1.
New since the last survey: 7 findings
- Code Duplication · Near-duplicate member pair (57 shared lines) src/Console/InstallCommand.php
- Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) src/Http/Controllers/Inertia/OtherBrowserSessionsController.php
- Code Duplication · Edited copy of a member (8 corresponding lines) stubs/app/Actions/Jetstream/AddTeamMember.php
- Code Duplication · Edited copy of a member (4 corresponding lines) src/HasTeams.php
- Coupling · Circular dependency database/factories/UserFactory.php
- Coupling · Off the main sequence: src/Console
- Coupling · Off the main sequence: src/Events
Fixed since the last survey: 8 findings
- Code Duplication · Near-duplicate member pair (64 shared lines) src/Console/InstallCommand.php
- Code Duplication · Edited copy of a member (17 corresponding lines) src/Console/InstallCommand.php
- Code Duplication · Duplicated block (11 lines × 2) src/Console/InstallCommand.php
- Code Duplication · Duplicated block (6–7 lines × 2) src/Console/InstallCommand.php
- Secrets (history) · High secret: REDACTED database/factories/UserFactory.php
- Secrets (history) · High secret: REDACTED src/Http/Controllers/Inertia/CurrentUserController.php
- Secrets (history) · High secret: REDACTED src/Http/Controllers/Inertia/OtherBrowserSessionsController.php
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €9,700 · Estimate
| Cost to rebuild | €3,200 to €16,000, for 53 to 170 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 43. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 7,970 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 App.Http.Middleware | 2 App.Providers | 3 App.View.Components | 4 Database.Factories | 5 Database.Seeders | 6 Laravel.Jetstream | 7 Laravel.Jetstream.Actions | 8 Laravel.Jetstream.Console | 9 Laravel.Jetstream.Contracts | 10 Laravel.Jetstream.Events | 11 Laravel.Jetstream.Http.Controllers | 12 Laravel.Jetstream.Http.Controllers.Inertia | 13 Laravel.Jetstream.Http.Controllers.Inertia.Concerns | 14 Laravel.Jetstream.Http.Controllers.Livewire | 15 Laravel.Jetstream.Http.Middleware | 16 Laravel.Jetstream.Rules | 17 App.Models | 18 Laravel.Jetstream.Http.Livewire | 19 Laravel.Jetstream.Mail | 20 App.Actions.Fortify | 21 App.Actions.Jetstream | 22 App.Policies |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 App.Http.Middleware | ||||||||||||||||||||||
| 2 App.Providers | ||||||||||||||||||||||
| 3 App.View.Components | ||||||||||||||||||||||
| 4 Database.Factories | ||||||||||||||||||||||
| 5 Database.Seeders | ||||||||||||||||||||||
| 6 Laravel.Jetstream | ||||||||||||||||||||||
| 7 Laravel.Jetstream.Actions | ||||||||||||||||||||||
| 8 Laravel.Jetstream.Console | ||||||||||||||||||||||
| 9 Laravel.Jetstream.Contracts | ||||||||||||||||||||||
| 10 Laravel.Jetstream.Events | ||||||||||||||||||||||
| 11 Laravel.Jetstream.Http.Controllers | ||||||||||||||||||||||
| 12 Laravel.Jetstream.Http.Controllers.Inertia | ||||||||||||||||||||||
| 13 Laravel.Jetstream.Http.Controllers.Inertia.Concerns | ||||||||||||||||||||||
| 14 Laravel.Jetstream.Http.Controllers.Livewire | ||||||||||||||||||||||
| 15 Laravel.Jetstream.Http.Middleware | ||||||||||||||||||||||
| 16 Laravel.Jetstream.Rules | ||||||||||||||||||||||
| 17 App.Models | 3 | |||||||||||||||||||||
| 18 Laravel.Jetstream.Http.Livewire | 2 | 5 | ||||||||||||||||||||
| 19 Laravel.Jetstream.Mail | 1 | |||||||||||||||||||||
| 20 App.Actions.Fortify | 2 | |||||||||||||||||||||
| 21 App.Actions.Jetstream | 7 | 12 | ||||||||||||||||||||
| 22 App.Policies | 2 |
17→6 App.Models uses Laravel.Jetstream✕
- Connections
- 3 pairs of types, where a type in App.Models uses a type in Laravel.Jetstream.
- The types involved
App.Models.Membership→Laravel.Jetstream.MembershipApp.Models.Team→Laravel.Jetstream.TeamApp.Models.TeamInvitation→Laravel.Jetstream.TeamInvitation
- Direction
- App.Models uses Laravel.Jetstream, so a change to Laravel.Jetstream can break App.Models, while a change to App.Models can't break Laravel.Jetstream.
- Position
- Below the diagonal: App.Models uses a module listed above it, which is the healthy direction.
18→7 Laravel.Jetstream.Http.Livewire uses Laravel.Jetstream.Actions✕
- Connections
- 2 pairs of types, where a type in Laravel.Jetstream.Http.Livewire uses a type in Laravel.Jetstream.Actions.
- The types involved
Laravel.Jetstream.Http.Livewire.DeleteTeamForm→Laravel.Jetstream.Actions.ValidateTeamDeletionLaravel.Jetstream.Http.Livewire.TeamMemberManager→Laravel.Jetstream.Actions.UpdateTeamMemberRole
- Direction
- Laravel.Jetstream.Http.Livewire uses Laravel.Jetstream.Actions, so a change to Laravel.Jetstream.Actions can break Laravel.Jetstream.Http.Livewire, while a change to Laravel.Jetstream.Http.Livewire can't break Laravel.Jetstream.Actions.
- Position
- Below the diagonal: Laravel.Jetstream.Http.Livewire uses a module listed above it, which is the healthy direction.
18→9 Laravel.Jetstream.Http.Livewire uses Laravel.Jetstream.Contracts✕
- Connections
- 5 pairs of types, where a type in Laravel.Jetstream.Http.Livewire uses a type in Laravel.Jetstream.Contracts.
- The types involved
Laravel.Jetstream.Http.Livewire.CreateTeamForm→Laravel.Jetstream.Contracts.CreatesTeamsLaravel.Jetstream.Http.Livewire.DeleteTeamForm→Laravel.Jetstream.Contracts.DeletesTeamsLaravel.Jetstream.Http.Livewire.DeleteUserForm→Laravel.Jetstream.Contracts.DeletesUsersLaravel.Jetstream.Http.Livewire.TeamMemberManager→Laravel.Jetstream.Contracts.RemovesTeamMembersLaravel.Jetstream.Http.Livewire.UpdateTeamNameForm→Laravel.Jetstream.Contracts.UpdatesTeamNames
- Direction
- Laravel.Jetstream.Http.Livewire uses Laravel.Jetstream.Contracts, so a change to Laravel.Jetstream.Contracts can break Laravel.Jetstream.Http.Livewire, while a change to Laravel.Jetstream.Http.Livewire can't break Laravel.Jetstream.Contracts.
- Position
- Below the diagonal: Laravel.Jetstream.Http.Livewire uses a module listed above it, which is the healthy direction.
19→6 Laravel.Jetstream.Mail uses Laravel.Jetstream✕
- Connections
- 1 pair of types, where a type in Laravel.Jetstream.Mail uses a type in Laravel.Jetstream.
- The types involved
Laravel.Jetstream.Mail.TeamInvitation→Laravel.Jetstream.TeamInvitation
- Direction
- Laravel.Jetstream.Mail uses Laravel.Jetstream, so a change to Laravel.Jetstream can break Laravel.Jetstream.Mail, while a change to Laravel.Jetstream.Mail can't break Laravel.Jetstream.
- Position
- Below the diagonal: Laravel.Jetstream.Mail uses a module listed above it, which is the healthy direction.
20→17 App.Actions.Fortify uses App.Models✕
- Connections
- 2 pairs of types, where a type in App.Actions.Fortify uses a type in App.Models.
- The types involved
App.Actions.Fortify.CreateNewUser→App.Models.UserApp.Actions.Fortify.UpdateUserProfileInformation→App.Models.User
- Direction
- App.Actions.Fortify uses App.Models, so a change to App.Models can break App.Actions.Fortify, while a change to App.Actions.Fortify can't break App.Models.
- Position
- Below the diagonal: App.Actions.Fortify uses a module listed above it, which is the healthy direction.
21→9 App.Actions.Jetstream uses Laravel.Jetstream.Contracts✕
- Connections
- 7 pairs of types, where a type in App.Actions.Jetstream uses a type in Laravel.Jetstream.Contracts.
- The types involved
App.Actions.Jetstream.AddTeamMember→Laravel.Jetstream.Contracts.AddsTeamMembersApp.Actions.Jetstream.CreateTeam→Laravel.Jetstream.Contracts.CreatesTeamsApp.Actions.Jetstream.DeleteTeam→Laravel.Jetstream.Contracts.DeletesTeamsApp.Actions.Jetstream.DeleteUser→Laravel.Jetstream.Contracts.DeletesUsersApp.Actions.Jetstream.InviteTeamMember→Laravel.Jetstream.Contracts.InvitesTeamMembersApp.Actions.Jetstream.RemoveTeamMember→Laravel.Jetstream.Contracts.RemovesTeamMembersApp.Actions.Jetstream.UpdateTeamName→Laravel.Jetstream.Contracts.UpdatesTeamNames
- Direction
- App.Actions.Jetstream uses Laravel.Jetstream.Contracts, so a change to Laravel.Jetstream.Contracts can break App.Actions.Jetstream, while a change to App.Actions.Jetstream can't break Laravel.Jetstream.Contracts.
- Position
- Below the diagonal: App.Actions.Jetstream uses a module listed above it, which is the healthy direction.
21→17 App.Actions.Jetstream uses App.Models✕
- Connections
- 12 pairs of types, where a type in App.Actions.Jetstream uses a type in App.Models.
- The types involved
App.Actions.Jetstream.AddTeamMember→App.Models.TeamApp.Actions.Jetstream.AddTeamMember→App.Models.UserApp.Actions.Jetstream.CreateTeam→App.Models.TeamApp.Actions.Jetstream.CreateTeam→App.Models.UserApp.Actions.Jetstream.DeleteTeam→App.Models.TeamApp.Actions.Jetstream.DeleteUser→App.Models.UserApp.Actions.Jetstream.InviteTeamMember→App.Models.TeamApp.Actions.Jetstream.InviteTeamMember→App.Models.UserApp.Actions.Jetstream.RemoveTeamMember→App.Models.TeamApp.Actions.Jetstream.RemoveTeamMember→App.Models.UserApp.Actions.Jetstream.UpdateTeamName→App.Models.TeamApp.Actions.Jetstream.UpdateTeamName→App.Models.User
- Direction
- App.Actions.Jetstream uses App.Models, so a change to App.Models can break App.Actions.Jetstream, while a change to App.Actions.Jetstream can't break App.Models.
- Position
- Below the diagonal: App.Actions.Jetstream uses a module listed above it, which is the healthy direction.
22→17 App.Policies uses App.Models✕
- Connections
- 2 pairs of types, where a type in App.Policies uses a type in App.Models.
- The types involved
App.Policies.TeamPolicy→App.Models.TeamApp.Policies.TeamPolicy→App.Models.User
- Direction
- App.Policies uses App.Models, so a change to App.Models can break App.Policies, while a change to App.Policies can't break App.Models.
- Position
- Below the diagonal: App.Policies 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 |
|---|---|---|
| A07:2025 — Authentication Failures | 4 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run; Add tests that import the unreached modules (directly or through their public entry).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +4.2 pts | Low | Secret Scanning |
| Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run. | +2.9 pts | Medium | Observability |
| Add tests that import the unreached modules (directly or through their public entry). | +2.9 pts | Medium | Test Coverage |
| 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. | +2.9 pts | Medium | Architecture documentation |
| Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with navigation-menu.blade.php, welcome.blade.php, Agent.php. | +1.4 pts | Low | Knowledge Freshness |
| Expand the README with getting-started, architecture overview and a project map. | +2.6 pts | Medium | Documentation (README) |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +1.5 pts | Medium | Security & performance tooling |
| Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault — not only APP_KEY in .env) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps. | +1.4 pts | Medium | Data Protection |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| src/Console/InstallCommand.php | 7.0 | Mixed | God Classes: ClassTooLong: InstallCommand |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| stubs/app/Actions/Jetstream/AddTeamMember.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (8 corresponding lines) |
| database/factories/UserFactory.php | 8.0 | Near-clean | Coupling: Circular dependency |
| src/Jetstream.php | 8.5 | Near-clean | God Classes: TooManyMethods: Jetstream |
| src/Http/Controllers/Inertia/OtherBrowserSessionsController.php | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 8+ corresponding lines) |
| src/HasTeams.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (4 corresponding lines) |
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 48 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 48 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, 56 of 69 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: 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 — 5 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 — 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 — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (composer.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 108 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- C2 Access Controls — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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").
- 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.
- 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").
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- 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.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Jetstream.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with InstallCommand.php. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
8 duplicated block group(s) detected. 2.3 % of the production lines (186 of 7,970) are in a reported copy. A further 4 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with InstallCommand.php (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with InstallCommand.php, AddTeamMember.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Near-duplicate member pair (57 shared lines) finding(s) in Code Duplication — start with InstallCommand.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
12 production modules (source-import), 1 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 2 module(s) off the main sequence, with abstractness counted on 10 of the 12 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Circular dependency finding(s) in Coupling — start with UserFactory.php. — One of this dimension's main actionable groups (1 issue-level).
D6 · Cohesion (LCOM4)
0 of 11 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3 tests.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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 30 of the 158 production source files in this repository: 125 are under the ~2,400-byte size floor this dimension measures over, and the remaining 3 have no attributable history left to measure.
D17 · Explicit Debt
0 deducted task-comment markers across 7970 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.
D27 · Navigability
29 % of calls cross a namespace and 2 % go through an interface, but 16 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
6 of 33 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is stubs/livewire/resources/views/navigation-menu.blade.php. Counted over 33 of the 158 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 6 Orphaned file finding(s) in Knowledge Freshness — start with navigation-menu.blade.php, welcome.blade.php, Agent.php. — One of this dimension's main actionable groups (6 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
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 5 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — stubs/inertia/resources/js/Pages/Welcome.vue:32
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — stubs/inertia/resources/js/Components/Checkbox.vue:30, stubs/inertia/resources/js/Components/TextInput.vue:22
- 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). (×2) — stubs/inertia/resources/js/Layouts/AppLayout.vue:164, stubs/inertia/resources/js/Pages/Auth/TwoFactorChallenge.vue:88
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×3) — REDACTED:73, stubs/livewire/resources/views/api/api-token-manager.blade.php:27, stubs/livewire/resources/views/api/api-token-manager.blade.php:130
- A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — stubs/livewire/resources/views/components/authentication-card-logo.blade.php:1
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
- An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. (×2) — stubs/inertia/resources/js/Components/ConfirmationModal.vue:42, stubs/inertia/resources/js/Components/SectionTitle.vue:4
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — stubs/inertia/resources/views/app.blade.php:2, stubs/livewire/resources/views/layouts/guest.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
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×5) — stubs/inertia/resources/js/Components/ConfirmsPassword.vue:75, stubs/inertia/resources/js/Components/Dropdown.vue:51, stubs/inertia/resources/js/Components/Dropdown.vue:56, …
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- <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). (×2) — stubs/inertia/resources/js/Components/Banner.vue:39, stubs/livewire/resources/views/teams/team-member-manager.blade.php:102
- <a> 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). (×3) — stubs/inertia/resources/js/Pages/Welcome.vue:69, stubs/inertia/resources/js/Pages/Welcome.vue:110, stubs/inertia/resources/js/Pages/Welcome.vue:129
- 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. — stubs/livewire/resources/views/api/api-token-manager.blade.php:107
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
- The projects database → src → stubs → database (one cycle inside a mutually-dependent group of 7 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — database/factories/UserFactory.php:10
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
AX8 · Test isolation
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault — not only APP_KEY in .env) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps.
- Enforce HTTPS (URL::forceScheme('https') / URL::forceHttps() in Laravel, or requires_channel: https / route schemes in Symfony) so data in transit is always encrypted.
C2 · Access Controls
M1 · Documentation (README)
- The root README is 17 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- No logging call was found in the 162 JavaScript/TypeScript, PHP production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; PHP: PSR-3 loggers (Monolog), Laravel's Log facade, error_log()) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run.
- Add a health-check endpoint (Laravel's /up health route or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `composer`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Dependabot is configured but does not watch `composer` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
P8 · Schema migrations
R1 · Type Safety
- 0 typed · 54 plain JS — the untyped files are stubs/inertia/resources/js/Components/ActionMessage.vue, stubs/inertia/resources/js/Components/ActionSection.vue, stubs/inertia/resources/js/Components/ApplicationLogo.vue, stubs/inertia/resources/js/Components/ApplicationMark.vue, stubs/inertia/resources/js/Components/AuthenticationCard.vue, stubs/inertia/resources/js/Components/AuthenticationCardLogo.vue (+48 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- stubs/inertia/resources/js/Pages/Profile/Partials/DeleteUserForm.vue:11 · stubs/inertia/resources/js/Pages/Profile/Partials/LogoutOtherBrowserSessionsForm.vue:14 — the 2 copies are spread across 2 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. — stubs/inertia/resources/js/Pages/Profile/Partials/DeleteUserForm.vue:11
- stubs/inertia/resources/js/Components/ConfirmationModal.vue:4 · stubs/inertia/resources/js/Components/DialogModal.vue:4 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — stubs/inertia/resources/js/Components/ConfirmationModal.vue:4
- stubs/inertia/resources/js/Components/Dropdown.vue:19 · stubs/inertia/resources/js/Components/Modal.vue:41 — the two spans are one implementation copied and then locally edited — 51 tokens are still identical, in the same order in both files, 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. — stubs/inertia/resources/js/Components/Dropdown.vue:19
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
R3 · Large Files
R4 · Test Coverage
- 0% of 54 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R7 · Dead Code
- Unreachable from the 1 application, 6 tooling and 0 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
- no import path from any entry point (1 application, 6 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 — stubs/inertia/resources/js/ssr.js
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R9 · Circular Imports
X27 · Collection changed while being enumerated
X3 · Exception handling
X5 · Nullable reference types
- 0/1 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
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 |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 49.9 | Weak — gated by R1, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 82.7 | Adequate — gated by D5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 40.1 | Weak — gated by M1, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 38.9 | Weak — gated by R4, P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 52.1 | Adequate — gated by D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 45.6 | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, a change-history library on the models — spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable, venturecraft/revisionable, Gedmo Loggable — or an Eloquent model event, observer or Doctrine listener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. A delete/anonymise identifier was seen but did not co-occur with GDPR vocabulary or a subject-id shape, so it was not credited (e.g. a save-slot DeleteAccount()). Implement erasure, data export/portability and consent tracking over the subject's records.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no interface, protocol or abstract type declares an operation an implementer must write
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 5 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 — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
- 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.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (stubs), which is a layered codebase, not two contexts. 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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (5997 LoC, 94 module-visible types across 23 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- 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 (4 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); its 4 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript, PHP source (service entry point: stubs/inertia/routes/web.php:7 (Route::get())
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — 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.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 36% of this repository's production lines — php (5,997 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.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 20 finding(s)
- Click handler on a non-interactive <div> stubs/inertia/resources/js/Components/Dropdown.vue:51
- Click handler on a non-interactive <div> stubs/inertia/resources/js/Components/Dropdown.vue:56
- Click handler on a non-interactive <div> stubs/inertia/resources/js/Components/Dropdown.vue:66
- Click handler on a non-interactive <div> stubs/inertia/resources/js/Components/Modal.vue:82
- <label> that labels no control REDACTED:73
- <label> that labels no control stubs/livewire/resources/views/api/api-token-manager.blade.php:27
- <label> that labels no control stubs/livewire/resources/views/api/api-token-manager.blade.php:130
- <input> without a programmatic label stubs/inertia/resources/js/Components/Checkbox.vue:30
- <input> without a programmatic label stubs/inertia/resources/js/Components/TextInput.vue:22
- <button> with no accessible text stubs/inertia/resources/js/Layouts/AppLayout.vue:164
- <button> with no accessible text stubs/inertia/resources/js/Pages/Auth/TwoFactorChallenge.vue:88
- REDACTED
- REDACTED
- <img> without a text alternative stubs/inertia/resources/js/Pages/Welcome.vue:32
- Link with no accessible name stubs/livewire/resources/views/components/authentication-card-logo.blade.php:1
- Click handler on a non-interactive <span> stubs/inertia/resources/js/Components/ConfirmsPassword.vue:75
- Project dependency cycle database/factories/UserFactory.php:10
- REDACTED
- REDACTED
- Circular dependency database/factories/UserFactory.php:10
Serious — 33 finding(s)
- Focus outline removed inline stubs/inertia/resources/js/Components/Banner.vue:39
- Focus outline removed inline stubs/inertia/resources/js/Pages/Welcome.vue:69
- Focus outline removed inline stubs/inertia/resources/js/Pages/Welcome.vue:110
- Focus outline removed inline stubs/inertia/resources/js/Pages/Welcome.vue:129
- Focus outline removed inline stubs/livewire/resources/views/teams/team-member-manager.blade.php:102
- Empty <h3> heading stubs/inertia/resources/js/Components/ConfirmationModal.vue:42
- Empty <h3> heading stubs/inertia/resources/js/Components/SectionTitle.vue:4
- Page without a main landmark stubs/inertia/resources/views/app.blade.php:2
- Page without a main landmark stubs/livewire/resources/views/layouts/guest.blade.php:2
- Duplicated block (9 lines × 2) src/Console/InstallCommand.php:188
- Duplicated block (9 lines × 2) src/Console/InstallCommand.php:209
- Duplicated block (7 lines × 2) src/Console/InstallCommand.php:254
- Duplicated block (7 lines × 2) stubs/app/Actions/Jetstream/AddTeamMember.php:74
- Off the main sequence: src/Console
- Off the main sequence: src/Events
- Low contrast Tailwind colour pair (4.4:1) stubs/livewire/resources/views/api/api-token-manager.blade.php:107
- TooManyMethods: Jetstream src/Jetstream.php:15
- ClassTooLong: InstallCommand src/Console/InstallCommand.php:24
- Near-duplicate member pair (57 shared lines) src/Console/InstallCommand.php:153
- Edited copies of one member (3 members, 8+ corresponding lines) src/Http/Controllers/Inertia/OtherBrowserSessionsController.php:48
- Edited copy of a member (8 corresponding lines) stubs/app/Actions/Jetstream/AddTeamMember.php:44
- Edited copy of a member (4 corresponding lines) src/HasTeams.php:83
- Duplicated block (19 lines × 2) src/Console/InstallCommand.php:269
- Duplicated block (16 lines × 2) src/Console/InstallCommand.php:696
- Duplicated block (7–9 lines × 2) src/Console/InstallCommand.php:176
- Duplicated block (6 lines × 4) src/Console/InstallCommand.php:248
- No structured logging
- Type Safety
- Duplicated block (21 lines × 2 locations) stubs/inertia/resources/js/Pages/Profile/Partials/DeleteUserForm.vue:11
- Duplicated block (18 lines × 2 locations) stubs/inertia/resources/js/Components/ConfirmationModal.vue:4
- Duplicated block with local edits (9 matched lines × 2 locations) stubs/inertia/resources/js/Components/Dropdown.vue:19
- Test Coverage
- Dead file (~25 LoC) stubs/inertia/resources/js/ssr.js
Minor — 16 finding(s)
- Orphaned file stubs/livewire/resources/views/navigation-menu.blade.php:1
- Orphaned file stubs/livewire/resources/views/components/welcome.blade.php:1
- Orphaned file src/Agent.php:1
- Orphaned file stubs/livewire/resources/views/components/banner.blade.php:1
- Orphaned file stubs/livewire/resources/views/components/application-logo.blade.php:1
- Orphaned file src/Http/Controllers/Inertia/Concerns/ConfirmsTwoFactorAuthentication.php:1
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- Dependabot does not watch composer REDACTED:2
- 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-09485a42d967412fa6db4fb5e7b6c4ca/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=800" --report-format json --report-path /tmp/watchdog-gitleaks-09485a42d967412fa6db4fb5e7b6c4ca/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=188" --report-format json --report-path /tmp/watchdog-gitleaks-09485a42d967412fa6db4fb5e7b6c4ca/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.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-09485a42d967412fa6db4fb5e7b6c4ca/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 . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |