Executive summary
3pontos-tech/firaga is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because it has form fields without a label. It scores 50.8 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 45.6, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 4.2 points. Improving the documentation comes next, worth about 1.9 points. Raising Accessibility to 70 would lift the score to about 55.3.
Fifteen known security holes in the packages the code depends on can be used by attackers. Twelve form fields can't be read by a screen reader, and three settings leave the servers or containers unsafe. Updating the vulnerable packages, labelling the form fields and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and pinning each tool to an exact version would deal with the pipeline tool referenced by a changeable name.
The product code is 14,387 lines, about €15,000 to rebuild.
If Accessibility rose from 45.6 to 70, the lowest score rated Strong, the score would rise from 50.8 to about 55.3.
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €5,100 to €26,000, for 85 to 268 hours of work, about 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 51. 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: 14,387 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 App.Actions.Payments | 2 App.Enums.Payments | 3 App.Filament.Components | 4 App.Filament.Exports | 5 App.Filament.Pages | 6 App.Filament.Plugins.KnowledgeBase | 7 App.Filament.Resources.Authors | 8 App.Filament.Resources.Authors.Pages | 9 App.Filament.Resources.CMS | 10 App.Filament.Resources.CMS.Categories | 11 App.Filament.Resources.CMS.Categories.Pages | 12 App.Filament.Resources.CMS.Categories.RelationManagers | 13 App.Filament.Resources.CMS.Menus | 14 App.Filament.Resources.CMS.Menus.Pages | 15 App.Filament.Resources.CMS.Menus.RelationManagers | 16 App.Filament.Resources.CMS.Pages | 17 App.Filament.Resources.CMS.Pages.Pages | 18 App.Filament.Resources.CMS.Posts | 19 App.Filament.Resources.CMS.Posts.Pages | 20 App.Filament.Resources.CMS.Posts.RelationManagers | 21 App.Filament.Resources.Contacts | 22 App.Filament.Resources.Contacts.Pages | 23 App.Filament.Resources.Terms | 24 App.Filament.Resources.Terms.Pages | 25 App.Filament.Resources.Terms.Schemas | 26 App.Filament.Resources.Terms.Tables | 27 App.Filament.Resources.Testimonials | 28 App.Models | 29 App.Models.CMS | 30 App.Enums | 31 App.View | 32 Database.Factories.CMS | 33 App.Actions.Leads | 34 App.Filament.Components.DTOs | 35 App.Providers.Filament | 36 App.Actions.GoHighLevel | 37 App.Http.Requests | 38 App.Console.Commands | 39 App.Http.Controllers | 40 App.Jobs |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 App.Actions.Payments | ||||||||||||||||||||||||||||||||||||||||
| 2 App.Enums.Payments | ||||||||||||||||||||||||||||||||||||||||
| 3 App.Filament.Components | ||||||||||||||||||||||||||||||||||||||||
| 4 App.Filament.Exports | ||||||||||||||||||||||||||||||||||||||||
| 5 App.Filament.Pages | ||||||||||||||||||||||||||||||||||||||||
| 6 App.Filament.Plugins.KnowledgeBase | ||||||||||||||||||||||||||||||||||||||||
| 7 App.Filament.Resources.Authors | ||||||||||||||||||||||||||||||||||||||||
| 8 App.Filament.Resources.Authors.Pages | ||||||||||||||||||||||||||||||||||||||||
| 9 App.Filament.Resources.CMS | ||||||||||||||||||||||||||||||||||||||||
| 10 App.Filament.Resources.CMS.Categories | ||||||||||||||||||||||||||||||||||||||||
| 11 App.Filament.Resources.CMS.Categories.Pages | ||||||||||||||||||||||||||||||||||||||||
| 12 App.Filament.Resources.CMS.Categories.RelationManagers | ||||||||||||||||||||||||||||||||||||||||
| 13 App.Filament.Resources.CMS.Menus | ||||||||||||||||||||||||||||||||||||||||
| 14 App.Filament.Resources.CMS.Menus.Pages | ||||||||||||||||||||||||||||||||||||||||
| 15 App.Filament.Resources.CMS.Menus.RelationManagers | ||||||||||||||||||||||||||||||||||||||||
| 16 App.Filament.Resources.CMS.Pages | ||||||||||||||||||||||||||||||||||||||||
| 17 App.Filament.Resources.CMS.Pages.Pages | ||||||||||||||||||||||||||||||||||||||||
| 18 App.Filament.Resources.CMS.Posts | ||||||||||||||||||||||||||||||||||||||||
| 19 App.Filament.Resources.CMS.Posts.Pages | ||||||||||||||||||||||||||||||||||||||||
| 20 App.Filament.Resources.CMS.Posts.RelationManagers | ||||||||||||||||||||||||||||||||||||||||
| 21 App.Filament.Resources.Contacts | ||||||||||||||||||||||||||||||||||||||||
| 22 App.Filament.Resources.Contacts.Pages | ||||||||||||||||||||||||||||||||||||||||
| 23 App.Filament.Resources.Terms | ||||||||||||||||||||||||||||||||||||||||
| 24 App.Filament.Resources.Terms.Pages | ||||||||||||||||||||||||||||||||||||||||
| 25 App.Filament.Resources.Terms.Schemas | ||||||||||||||||||||||||||||||||||||||||
| 26 App.Filament.Resources.Terms.Tables | ||||||||||||||||||||||||||||||||||||||||
| 27 App.Filament.Resources.Testimonials | ||||||||||||||||||||||||||||||||||||||||
| 28 App.Models | ||||||||||||||||||||||||||||||||||||||||
| 29 App.Models.CMS | ||||||||||||||||||||||||||||||||||||||||
| 30 App.Enums | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 App.View | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 Database.Factories.CMS | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 33 App.Actions.Leads | 3 | |||||||||||||||||||||||||||||||||||||||
| 34 App.Filament.Components.DTOs | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 App.Providers.Filament | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 App.Actions.GoHighLevel | 3 | |||||||||||||||||||||||||||||||||||||||
| 37 App.Http.Requests | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 App.Console.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 App.Http.Controllers | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 App.Jobs | 3 | 4 |
30→3 App.Enums uses App.Filament.Components✕
- Connections
- 1 pair of types, where a type in App.Enums uses a type in App.Filament.Components.
- The types involved
App.Enums.CustomComponent→App.Filament.Components.AbstractCustomComponent
- Direction
- App.Enums uses App.Filament.Components, so a change to App.Filament.Components can break App.Enums, while a change to App.Enums can't break App.Filament.Components.
- Position
- Below the diagonal: App.Enums uses a module listed above it, which is the healthy direction.
31→3 App.View uses App.Filament.Components✕
- Connections
- 1 pair of types, where a type in App.View uses a type in App.Filament.Components.
- The types involved
App.View.TemplateRenderer→App.Filament.Components.AbstractCustomComponent
- Direction
- App.View uses App.Filament.Components, so a change to App.Filament.Components can break App.View, while a change to App.View can't break App.Filament.Components.
- Position
- Below the diagonal: App.View uses a module listed above it, which is the healthy direction.
32→28 Database.Factories.CMS uses App.Models✕
- Connections
- 1 pair of types, where a type in Database.Factories.CMS uses a type in App.Models.
- The types involved
Database.Factories.CMS.PostFactory→App.Models.Author
- Direction
- Database.Factories.CMS uses App.Models, so a change to App.Models can break Database.Factories.CMS, while a change to Database.Factories.CMS can't break App.Models.
- Position
- Below the diagonal: Database.Factories.CMS uses a module listed above it, which is the healthy direction.
32→29 Database.Factories.CMS uses App.Models.CMS✕
- Connections
- 6 pairs of types, where a type in Database.Factories.CMS uses a type in App.Models.CMS.
- The types involved
Database.Factories.CMS.MenuFactory→App.Models.CMS.MenuDatabase.Factories.CMS.MenuItemFactory→App.Models.CMS.MenuDatabase.Factories.CMS.MenuItemFactory→App.Models.CMS.PageDatabase.Factories.CMS.PageFactory→App.Models.CMS.PageDatabase.Factories.CMS.PostFactory→App.Models.CMS.CategoryDatabase.Factories.CMS.PostFactory→App.Models.CMS.Post
- Direction
- Database.Factories.CMS uses App.Models.CMS, so a change to App.Models.CMS can break Database.Factories.CMS, while a change to Database.Factories.CMS can't break App.Models.CMS.
- Position
- Below the diagonal: Database.Factories.CMS uses a module listed above it, which is the healthy direction.
33→30 App.Actions.Leads uses App.Enums✕
- Connections
- 3 pairs of types, where a type in App.Actions.Leads uses a type in App.Enums.
- The types involved
App.Actions.Leads.LeadData→App.Enums.ContactWindowApp.Actions.Leads.LeadData→App.Enums.FinancialGoalApp.Actions.Leads.LeadData→App.Enums.FinancialSituation
- Direction
- App.Actions.Leads uses App.Enums, so a change to App.Enums can break App.Actions.Leads, while a change to App.Actions.Leads can't break App.Enums.
- Position
- Below the diagonal: App.Actions.Leads uses a module listed above it, which is the healthy direction.
34→30 App.Filament.Components.DTOs uses App.Enums✕
- Connections
- 1 pair of types, where a type in App.Filament.Components.DTOs uses a type in App.Enums.
- The types involved
App.Filament.Components.DTOs.ImageComponent→App.Enums.CustomComponent
- Direction
- App.Filament.Components.DTOs uses App.Enums, so a change to App.Enums can break App.Filament.Components.DTOs, while a change to App.Filament.Components.DTOs can't break App.Enums.
- Position
- Below the diagonal: App.Filament.Components.DTOs uses a module listed above it, which is the healthy direction.
35→30 App.Providers.Filament uses App.Enums✕
- Connections
- 1 pair of types, where a type in App.Providers.Filament uses a type in App.Enums.
- The types involved
App.Providers.Filament.AdminPanelServiceProvider→App.Enums.FilamentPanel
- Direction
- App.Providers.Filament uses App.Enums, so a change to App.Enums can break App.Providers.Filament, while a change to App.Providers.Filament can't break App.Enums.
- Position
- Below the diagonal: App.Providers.Filament uses a module listed above it, which is the healthy direction.
36→33 App.Actions.GoHighLevel uses App.Actions.Leads✕
- Connections
- 3 pairs of types, where a type in App.Actions.GoHighLevel uses a type in App.Actions.Leads.
- The types involved
App.Actions.GoHighLevel.CreateAppointment→App.Actions.Leads.LeadDataApp.Actions.GoHighLevel.CreateOpportunity→App.Actions.Leads.LeadDataApp.Actions.GoHighLevel.UpsertContact→App.Actions.Leads.LeadData
- Direction
- App.Actions.GoHighLevel uses App.Actions.Leads, so a change to App.Actions.Leads can break App.Actions.GoHighLevel, while a change to App.Actions.GoHighLevel can't break App.Actions.Leads.
- Position
- Below the diagonal: App.Actions.GoHighLevel uses a module listed above it, which is the healthy direction.
37→33 App.Http.Requests uses App.Actions.Leads✕
- Connections
- 1 pair of types, where a type in App.Http.Requests uses a type in App.Actions.Leads.
- The types involved
App.Http.Requests.StoreLeadRequest→App.Actions.Leads.LeadData
- Direction
- App.Http.Requests uses App.Actions.Leads, so a change to App.Actions.Leads can break App.Http.Requests, while a change to App.Http.Requests can't break App.Actions.Leads.
- Position
- Below the diagonal: App.Http.Requests uses a module listed above it, which is the healthy direction.
38→36 App.Console.Commands uses App.Actions.GoHighLevel✕
- Connections
- 1 pair of types, where a type in App.Console.Commands uses a type in App.Actions.GoHighLevel.
- The types involved
App.Console.Commands.CheckGoHighLevelCustomFields→App.Actions.GoHighLevel.GoHighLevelClient
- Direction
- App.Console.Commands uses App.Actions.GoHighLevel, so a change to App.Actions.GoHighLevel can break App.Console.Commands, while a change to App.Console.Commands can't break App.Actions.GoHighLevel.
- Position
- Below the diagonal: App.Console.Commands uses a module listed above it, which is the healthy direction.
39→29 App.Http.Controllers uses App.Models.CMS✕
- Connections
- 2 pairs of types, where a type in App.Http.Controllers uses a type in App.Models.CMS.
- The types involved
App.Http.Controllers.BlogController→App.Models.CMS.PostApp.Http.Controllers.MarketingLandingController→App.Models.CMS.Page
- Direction
- App.Http.Controllers uses App.Models.CMS, so a change to App.Models.CMS can break App.Http.Controllers, while a change to App.Http.Controllers can't break App.Models.CMS.
- Position
- Below the diagonal: App.Http.Controllers uses a module listed above it, which is the healthy direction.
39→37 App.Http.Controllers uses App.Http.Requests✕
- Connections
- 1 pair of types, where a type in App.Http.Controllers uses a type in App.Http.Requests.
- The types involved
App.Http.Controllers.LeadController→App.Http.Requests.StoreLeadRequest
- Direction
- App.Http.Controllers uses App.Http.Requests, so a change to App.Http.Requests can break App.Http.Controllers, while a change to App.Http.Controllers can't break App.Http.Requests.
- Position
- Below the diagonal: App.Http.Controllers uses a module listed above it, which is the healthy direction.
40→33 App.Jobs uses App.Actions.Leads✕
- Connections
- 3 pairs of types, where a type in App.Jobs uses a type in App.Actions.Leads.
- The types involved
App.Jobs.CreateLeadAppointment→App.Actions.Leads.LeadDataApp.Jobs.CreateLeadOpportunity→App.Actions.Leads.LeadDataApp.Jobs.SyncLeadWithGoHighLevel→App.Actions.Leads.LeadData
- Direction
- App.Jobs uses App.Actions.Leads, so a change to App.Actions.Leads can break App.Jobs, while a change to App.Jobs can't break App.Actions.Leads.
- Position
- Below the diagonal: App.Jobs uses a module listed above it, which is the healthy direction.
40→36 App.Jobs uses App.Actions.GoHighLevel✕
- Connections
- 4 pairs of types, where a type in App.Jobs uses a type in App.Actions.GoHighLevel.
- The types involved
App.Jobs.CreateLeadAppointment→App.Actions.GoHighLevel.CreateAppointmentApp.Jobs.CreateLeadOpportunity→App.Actions.GoHighLevel.CreateOpportunityApp.Jobs.SyncLeadWithGoHighLevel→App.Actions.GoHighLevel.GoHighLevelClientApp.Jobs.SyncLeadWithGoHighLevel→App.Actions.GoHighLevel.UpsertContact
- Direction
- App.Jobs uses App.Actions.GoHighLevel, so a change to App.Actions.GoHighLevel can break App.Jobs, while a change to App.Jobs can't break App.Actions.GoHighLevel.
- Position
- Below the diagonal: App.Jobs 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 22 | High / Critical |
| A01:2025 — Broken Access Control | 20 | Medium |
| A02:2025 — Security Misconfiguration | 9 | High / Critical |
| A05:2025 — Injection | 4 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Resolve the 1 finding(s) in DR & Backup; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +4.2 pts | Medium | Keyboard semantics |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +1.9 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with artisan. | +1.9 pts | Low | ADR Quality |
| Resolve the 1 finding(s) in DR & Backup. | +3.1 pts | Medium | DR & Backup |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +2.9 pts | Medium | Forms & labels |
| 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. | +2.4 pts | Medium | Security & performance tooling |
| Resolve the 20 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (6), REDACTED (5), REDACTED (3). | +1.1 pts | Medium | Data Compliance (PII/GDPR) |
| 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. | +1.9 pts | Medium | Text alternatives |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.1 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.8 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.5 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| REDACTED | 5.0 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.9 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| app/Filament/Pages/Authentication.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/Http/Controllers/LandingController.php | 8.5 | Near-clean | God Classes: MethodTooLong: LandingController.__invoke |
| app/Filament/Resources/CMS/Pages/PageResource.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (40 corresponding lines) |
| app/Enums/PageStatus.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (5 corresponding lines) |
| database/seeders/CMS/PostsSeeder.php | 8.5 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
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 53 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 53 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, 101 of 121 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its Composer package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no REDACTED, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (7360 LoC, 131 module-visible types across 53 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D32 Data Compliance (PII/GDPR) — 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. `app/Actions/GoHighLevel/CreateAppointment.php`, `app/Actions/GoHighLevel/CreateOpportunity.php`, `app/Actions/GoHighLevel/UpsertContact.php`, `app/Actions/Leads/LeadData.php`, `app/Enums/ContactWindow.php`, … (+5 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AC6 Visual & motion safety — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (docker-compose.yml). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — firaga-db Warning pull access denied for postgres.local, repository does not exist or may require 'docker login': denied: requested access to the resource is denied firaga-db Built firaga-mailpit Built firaga-redis Built container firaga-db exited (1); runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was (anonymous) at 30.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with (anonymous) (cyclomatic 30), app.document.addEventListener("alpine:init") (cyclomatic 25). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was (anonymous) at 30.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with (anonymous) (cognitive 30), app.document.addEventListener("alpine:init") (cognitive 24). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with LandingController.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
3 duplicated block group(s) detected. 1.3 % of the production lines (182 of 14,387) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (40 corresponding lines) finding(s) in Code Duplication — start with PageResource.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (5 corresponding lines) finding(s) in Code Duplication — start with PageStatus.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with PostsSeeder.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (npm+Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (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).
D6 · Cohesion (LCOM4)
0 of 12 classes have LCOM4 above 3.
D12 · Dependency Hygiene
10 outdated, 0 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 164 locked Composer package(s) use a banned license. Licences were read from this repository's REDACTED, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 66 package(s) under `packages-dev` are not installed for a consumer and are excluded. ★ COVERAGE OF THIS VERDICT: it grades this repository's Composer package dependencies and nothing else. The repository also declares REDACTED, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: REDACTED (2×25=50)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is resources/views/pages/blog-show.blade.php. Counted over 46 of the 219 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
2 deducted task-comment markers across 14387 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.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with REDACTED, Authentication.php. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 29 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with artisan. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 3 high, 1 medium, 0 low. 1 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 10 file(s) — `app/Actions/GoHighLevel/CreateAppointment.php` (line 14), `app/Actions/GoHighLevel/CreateOpportunity.php` (line 13, line 53), `app/Actions/GoHighLevel/UpsertContact.php` (line 17), `app/Actions/Leads/LeadData.php` (line 11), `app/Enums/ContactWindow.php` (line 15), … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 1 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (1 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
22 finding(s): 2 critical, 13 high, 6 medium, 1 low.
What to do
- Resolve the 13 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (5), REDACTED (2). — One of this dimension's main actionable groups (13 issue-level).
- Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
9 finding(s): 0 critical, 3 high, 3 medium, 3 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
D32 · Data Compliance (PII/GDPR)
20 finding(s): 0 critical, 0 high, 20 medium, 0 low. semgrep could not parse 10 file(s) — `app/Actions/GoHighLevel/CreateAppointment.php`, `app/Actions/GoHighLevel/CreateOpportunity.php`, `app/Actions/GoHighLevel/UpsertContact.php`, `app/Actions/Leads/LeadData.php`, `app/Enums/ContactWindow.php`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
What to do
- Resolve the 20 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (6), REDACTED (5), REDACTED (3). — One of this dimension's main actionable groups (20 warning-level).
D34 · Knowledge Freshness
11 of 46 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app/Http/Controllers/LandingController.php. Counted over 46 of the 219 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 11 Orphaned file finding(s) in Knowledge Freshness — start with LandingController.php, Post.php, TestimonialResource.php. — One of this dimension's main actionable groups (11 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.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 18 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
- Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). — resources/views/pages/quem-somos.blade.php:179
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×9) — REDACTED:89, resources/views/components/lead-form.blade.php:52, resources/views/components/newsletter-banner.blade.php:32, …
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — resources/views/components/lead-form.blade.php:36, resources/views/components/lead-form.blade.php:42, resources/views/components/partner-form.blade.php:101
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
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — resources/views/success.blade.php:46
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. — resources/views/components/lead-capture-modal.blade.php:21
- This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — resources/views/components/lead-capture-modal.blade.php:29
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
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
C3 · Audit Trail
- An audit mechanism is present, but the trail is not yet complete — missing: a write-side hook every change flows through (a change-history library's model trait, an Eloquent model event or observer, or a Doctrine lifecycle listener recording each change), per-model coverage (LogsActivity / Auditable / RevisionableTrait or #[Gedmo\Loggable] on each model that needs a who-changed-what trail).
What to do
- Back the audit convention with a structural mechanism: a change-history library on each model that needs a who-changed-what trail (spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable) or an Eloquent observer / Doctrine listener writing each sensitive change to an audit-log table, with the acting user and time on every entry.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md links to `docs/nightwatch.md`, but `docs/nightwatch.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:16
What to do
- Reconcile the README with reality: README.md links to `docs/nightwatch.md`, but `docs/nightwatch.md` does not exist.
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:15
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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
P8 · Schema migrations
S1 · Web-Security Posture
- `https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.11.1/highlight.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — resources/views/filament/components/preview-json.blade.php:33
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X3 · Exception handling
X4 · Structured logging
X5 · Nullable reference types
- 0/2 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 |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 72.0 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 86.9 | Strong | Strongest area. |
| Maturity | 58.8 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47.9 | Weak — gated by P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 56.5 | Adequate — gated by D32, 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 — 2 control(s) we could not find positive evidence for
- 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. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 62 check(s) not relevant to this codebase
- AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — firaga-db Warning pull access denied for postgres.local, repository does not exist or may require 'docker login': denied: requested access to the resource is denied firaga-db Built firaga-mailpit Built firaga-redis Built container firaga-db exited (1); runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D10 Test Quality — ~1798 lines of test source are present (.php) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Models), 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 — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 9 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 22 value object(s); its 9 aggregate(s) are ORM models only — persistence, not behaviour: a CRUD model, measured, not claimed as DDD
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 4% of this repository's production lines — php (7,089 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — 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.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. 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 — X29 reached only 4% of this repository's production lines — php (7,089 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 34 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label REDACTED:89
- <input> without a programmatic label resources/views/components/lead-form.blade.php:36
- <input> without a programmatic label resources/views/components/newsletter-banner.blade.php:32
- <input> without a programmatic label resources/views/components/partner-form.blade.php:67
- <input> without a programmatic label resources/views/components/partner-form.blade.php:88
- <input> without a programmatic label REDACTED:403
- <input> without a programmatic label REDACTED:412
- <input> without a programmatic label REDACTED:421
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label resources/views/components/lead-form.blade.php:42
- <select> without a programmatic label resources/views/components/partner-form.blade.php:101
- <textarea> without a programmatic label resources/views/components/lead-form.blade.php:52
- <textarea> without a programmatic label resources/views/components/partner-form.blade.php:113
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <div> resources/views/components/lead-capture-modal.blade.php:21
- REDACTED
Serious — 50 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment REDACTED:42
- TodoComment app/Filament/Pages/Authentication.php:13
- <video> without a captions track resources/views/pages/quem-somos.blade.php:179
- Heading level jumps from h1 to h3 resources/views/success.blade.php:46
- Modal dialog does not manage focus resources/views/components/lead-capture-modal.blade.php:29
- (anonymous) (cyclomatic 30) REDACTED:62
- app.document.addEventListener("alpine:init") (cyclomatic 25) REDACTED:62
- Hotspot: REDACTED REDACTED:62
- (anonymous) (cognitive 30) REDACTED:62
- app.document.addEventListener("alpine:init") (cognitive 24) REDACTED:62
- REDACTED
- MethodTooLong: LandingController.__invoke app/Http/Controllers/LandingController.php:13
- FunctionTooLong: app.document.addEventListener("alpine:init") REDACTED:62
- REDACTED
- Edited copy of a member (40 corresponding lines) app/Filament/Resources/CMS/Pages/PageResource.php:156
- Edited copy of a member (5 corresponding lines) app/Enums/PageStatus.php:17
- Duplicated block (11 lines × 2) database/seeders/CMS/PostsSeeder.php:31
- Duplicated block (17 lines × 3) database/factories/CMS/CategoryFactory.php:20
- Duplicated block (17 lines × 2) app/Filament/Resources/CMS/Categories/RelationManagers/PostsRelationManager.php:36
- No DR/backup evidence
- Third-party script without Subresource Integrity resources/views/filament/components/preview-json.blade.php:33
Minor — 27 finding(s)
- Orphaned file app/Http/Controllers/LandingController.php:1
- Orphaned file app/Models/CMS/Post.php:1
- Orphaned file app/Filament/Resources/Testimonials/TestimonialResource.php:1
- Orphaned file app/Filament/Resources/CMS/Menus/RelationManagers/ItemsRelationManager.php:1
- Orphaned file database/seeders/CMS/PostsSeeder.php:1
- Orphaned file app/Filament/Resources/Users/UserResource.php:1
- Orphaned file app/Filament/Resources/Contacts/ContactResource.php:1
- Orphaned file app/Models/CMS/Page.php:1
- Orphaned file app/Filament/Components/DTOs/HeadlineComponent.php:1
- Orphaned file app/Filament/Resources/CMS/Categories/CategoryResource.php:1
- Orphaned file app/Filament/Resources/CMS/Menus/MenuResource.php:1
- REDACTED
- REDACTED
- REDACTED
- Partial audit-trail evidence
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Documentation: no build, run or usage example README.md:1
- No ADRs found artisan:1
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- README/code drift README.md:16
- No dependency-update automation REDACTED:15
- No changelog
- PHP static analysis does not check null everywhere
Minor — 10 finding(s)
- Outdated: basementdevs/filament-better-mails
- Outdated: filament/filament
- Outdated: filament/spatie-laravel-media-library-plugin
- Outdated: guava/filament-knowledge-base
- Outdated: joaopaulolndev/filament-edit-profile
- Outdated: league/flysystem-sftp-v3
- Outdated: owenvoke/blade-fontawesome
- Outdated: saloonphp/saloon
- Outdated: stechstudio/filament-impersonate
- Outdated: tpetry/laravel-postgresql-enhanced
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-98383119104647a3bfe988a6b42cad89/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=127" --report-format json --report-path /tmp/watchdog-gitleaks-98383119104647a3bfe988a6b42cad89/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-98383119104647a3bfe988a6b42cad89/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude public/css/filament . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 22 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 9 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude public/css/filament . | 20 | artifacts/raw/semgrep-gdpr.json |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |