Executive summary
luyadev/luya is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 43.5 out of 100, which the At risk rating leaves unchanged.
Code Health, at 22.7, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 3.3 points. Adding type checking would lift Code Health itself, worth about 4.9 points. Raising Code Health to 70 would lift the score to about 61.7.
Forty-five known security holes in the packages the code depends on can be used by attackers. Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. The password or key in the code's history needs replacing, with the old one switched off.
The product code is 21,374 lines, about €23,000 to rebuild.
If Code Health rose from 22.7 to 70, the lowest score rated Strong, the score would rise from 43.5 to about 61.7.
Rebuild cost: about €23,000 · Estimate
| Cost to rebuild | €7,800 to €39,000, for 130 to 412 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 43. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 21,374 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 core.resources.lazyload | 3 core.resources.texttospeech | 4 luya.behaviors | 5 luya.components | 6 luya.console.interfaces | 7 luya.rest | 8 luya.tag | 9 luya.theme | 10 luya.traits | 11 luya.validators | 12 luya.web.filters | 13 luya.web.jsonld | 14 luya.tag.tags | 15 luya.web | 16 luya.base | 17 luya | 18 luya.console | 19 luya.helpers | 20 luya.lazyload | 21 luya.texttospeech | 22 luya.widgets | 23 luya.console.commands | 24 luya.dev | 25 luya.exceptions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | |||||||||||||||||||||||||
| 2 core.resources.lazyload | |||||||||||||||||||||||||
| 3 core.resources.texttospeech | |||||||||||||||||||||||||
| 4 luya.behaviors | |||||||||||||||||||||||||
| 5 luya.components | |||||||||||||||||||||||||
| 6 luya.console.interfaces | |||||||||||||||||||||||||
| 7 luya.rest | |||||||||||||||||||||||||
| 8 luya.tag | |||||||||||||||||||||||||
| 9 luya.theme | |||||||||||||||||||||||||
| 10 luya.traits | |||||||||||||||||||||||||
| 11 luya.validators | |||||||||||||||||||||||||
| 12 luya.web.filters | |||||||||||||||||||||||||
| 13 luya.web.jsonld | |||||||||||||||||||||||||
| 14 luya.tag.tags | 3 | ||||||||||||||||||||||||
| 15 luya.web | 2 | ||||||||||||||||||||||||
| 16 luya.base | 1 | 2 | |||||||||||||||||||||||
| 17 luya | 1 | ||||||||||||||||||||||||
| 18 luya.console | 1 | 2 | |||||||||||||||||||||||
| 19 luya.helpers | 1 | ||||||||||||||||||||||||
| 20 luya.lazyload | 2 | 1 | |||||||||||||||||||||||
| 21 luya.texttospeech | 1 | 1 | |||||||||||||||||||||||
| 22 luya.widgets | 1 | ||||||||||||||||||||||||
| 23 luya.console.commands | 1 | 5 | |||||||||||||||||||||||
| 24 luya.dev | 1 | ||||||||||||||||||||||||
| 25 luya.exceptions | 1 |
14→8 luya.tag.tags uses luya.tag✕
- Connections
- 3 pairs of types, where a type in luya.tag.tags uses a type in luya.tag.
- The types involved
luya.tag.tags.LinkTag→luya.tag.BaseTagluya.tag.tags.MailTag→luya.tag.BaseTagluya.tag.tags.TelTag→luya.tag.BaseTag
- Direction
- luya.tag.tags uses luya.tag, so a change to luya.tag can break luya.tag.tags, while a change to luya.tag.tags can't break luya.tag.
- Position
- Below the diagonal: luya.tag.tags uses a module listed above it, which is the healthy direction.
15→16 luya.web uses luya.base part of a loop✕
- Connections
- 2 pairs of types, where a type in luya.web uses a type in luya.base.
- The types involved
luya.web.Bootstrap→luya.base.BaseBootstrapluya.web.Svg→luya.base.Widget
- Direction
- luya.web uses luya.base, so a change to luya.base can break luya.web, while a change to luya.web can't break luya.base.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→6 luya.base uses luya.console.interfaces✕
- Connections
- 1 pair of types, where a type in luya.base uses a type in luya.console.interfaces.
- The types involved
luya.base.Module→luya.console.interfaces.ImportControllerInterface
- Direction
- luya.base uses luya.console.interfaces, so a change to luya.console.interfaces can break luya.base, while a change to luya.base can't break luya.console.interfaces.
- Position
- Below the diagonal: luya.base uses a module listed above it, which is the healthy direction.
16→15 luya.base uses luya.web✕
- Connections
- 2 pairs of types, where a type in luya.base uses a type in luya.web.
- The types involved
luya.base.ModuleReflection→luya.web.Requestluya.base.ModuleReflection→luya.web.UrlManager
- Direction
- luya.base uses luya.web, so a change to luya.web can break luya.base, while a change to luya.base can't break luya.web.
- Position
- Below the diagonal: luya.base uses a module listed above it, which is the healthy direction.
17→16 luya uses luya.base✕
- Connections
- 1 pair of types, where a type in luya uses a type in luya.base.
- The types involved
luya.Boot→luya.base.Boot
- Direction
- luya uses luya.base, so a change to luya.base can break luya, while a change to luya can't break luya.base.
- Position
- Below the diagonal: luya uses a module listed above it, which is the healthy direction.
18→6 luya.console uses luya.console.interfaces✕
- Connections
- 1 pair of types, where a type in luya.console uses a type in luya.console.interfaces.
- The types involved
luya.console.Importer→luya.console.interfaces.ImportControllerInterface
- Direction
- luya.console uses luya.console.interfaces, so a change to luya.console.interfaces can break luya.console, while a change to luya.console can't break luya.console.interfaces.
- Position
- Below the diagonal: luya.console uses a module listed above it, which is the healthy direction.
18→16 luya.console uses luya.base✕
- Connections
- 2 pairs of types, where a type in luya.console uses a type in luya.base.
- The types involved
luya.console.Bootstrap→luya.base.BaseBootstrapluya.console.Importer→luya.base.Module
- Direction
- luya.console uses luya.base, so a change to luya.base can break luya.console, while a change to luya.console can't break luya.base.
- Position
- Below the diagonal: luya.console uses a module listed above it, which is the healthy direction.
19→16 luya.helpers uses luya.base✕
- Connections
- 1 pair of types, where a type in luya.helpers uses a type in luya.base.
- The types involved
luya.helpers.ObjectHelper→luya.base.Module
- Direction
- luya.helpers uses luya.base, so a change to luya.base can break luya.helpers, while a change to luya.helpers can't break luya.base.
- Position
- Below the diagonal: luya.helpers uses a module listed above it, which is the healthy direction.
20→15 luya.lazyload uses luya.web✕
- Connections
- 2 pairs of types, where a type in luya.lazyload uses a type in luya.web.
- The types involved
luya.lazyload.IntersectionObserverPolyfillAsset→luya.web.Assetluya.lazyload.LazyLoadAsset→luya.web.Asset
- Direction
- luya.lazyload uses luya.web, so a change to luya.web can break luya.lazyload, while a change to luya.lazyload can't break luya.web.
- Position
- Below the diagonal: luya.lazyload uses a module listed above it, which is the healthy direction.
20→16 luya.lazyload uses luya.base✕
- Connections
- 1 pair of types, where a type in luya.lazyload uses a type in luya.base.
- The types involved
luya.lazyload.LazyLoad→luya.base.Widget
- Direction
- luya.lazyload uses luya.base, so a change to luya.base can break luya.lazyload, while a change to luya.lazyload can't break luya.base.
- Position
- Below the diagonal: luya.lazyload uses a module listed above it, which is the healthy direction.
21→15 luya.texttospeech uses luya.web✕
- Connections
- 1 pair of types, where a type in luya.texttospeech uses a type in luya.web.
- The types involved
luya.texttospeech.TextToSpeechAsset→luya.web.Asset
- Direction
- luya.texttospeech uses luya.web, so a change to luya.web can break luya.texttospeech, while a change to luya.texttospeech can't break luya.web.
- Position
- Below the diagonal: luya.texttospeech uses a module listed above it, which is the healthy direction.
21→16 luya.texttospeech uses luya.base✕
- Connections
- 1 pair of types, where a type in luya.texttospeech uses a type in luya.base.
- The types involved
luya.texttospeech.TextToSpeechWidget→luya.base.Widget
- Direction
- luya.texttospeech uses luya.base, so a change to luya.base can break luya.texttospeech, while a change to luya.texttospeech can't break luya.base.
- Position
- Below the diagonal: luya.texttospeech uses a module listed above it, which is the healthy direction.
22→16 luya.widgets uses luya.base✕
- Connections
- 1 pair of types, where a type in luya.widgets uses a type in luya.base.
- The types involved
luya.widgets.SubmitButtonWidget→luya.base.Widget
- Direction
- luya.widgets uses luya.base, so a change to luya.base can break luya.widgets, while a change to luya.widgets can't break luya.base.
- Position
- Below the diagonal: luya.widgets uses a module listed above it, which is the healthy direction.
23→6 luya.console.commands uses luya.console.interfaces✕
- Connections
- 1 pair of types, where a type in luya.console.commands uses a type in luya.console.interfaces.
- The types involved
luya.console.commands.ImportController→luya.console.interfaces.ImportControllerInterface
- Direction
- luya.console.commands uses luya.console.interfaces, so a change to luya.console.interfaces can break luya.console.commands, while a change to luya.console.commands can't break luya.console.interfaces.
- Position
- Below the diagonal: luya.console.commands uses a module listed above it, which is the healthy direction.
23→18 luya.console.commands uses luya.console✕
- Connections
- 5 pairs of types, where a type in luya.console.commands uses a type in luya.console.
- The types involved
luya.console.commands.BaseCrudController→luya.console.Commandluya.console.commands.HealthController→luya.console.Commandluya.console.commands.ImportController→luya.console.Commandluya.console.commands.ModuleController→luya.console.Commandluya.console.commands.ThemeController→luya.console.Command
- Direction
- luya.console.commands uses luya.console, so a change to luya.console can break luya.console.commands, while a change to luya.console.commands can't break luya.console.
- Position
- Below the diagonal: luya.console.commands uses a module listed above it, which is the healthy direction.
24→18 luya.dev uses luya.console✕
- Connections
- 1 pair of types, where a type in luya.dev uses a type in luya.console.
- The types involved
luya.dev.BaseDevCommand→luya.console.Command
- Direction
- luya.dev uses luya.console, so a change to luya.console can break luya.dev, while a change to luya.dev can't break luya.console.
- Position
- Below the diagonal: luya.dev uses a module listed above it, which is the healthy direction.
25→17 luya.exceptions uses luya✕
- Connections
- 1 pair of types, where a type in luya.exceptions uses a type in luya.
- The types involved
luya.exceptions.WhitelistedException→luya.Exception
- Direction
- luya.exceptions uses luya, so a change to luya can break luya.exceptions, while a change to luya.exceptions can't break luya.
- Position
- Below the diagonal: luya.exceptions 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 59 | High / Critical |
| A05:2025 — Injection | 16 | High / Critical |
| A07:2025 — Authentication Failures | 5 | High / Critical |
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; Resolve the 66 Orphaned file finding(s) in Knowledge Freshness — start with Controller.php (2), PlaceTrait.php, Composition.php.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. | +3.3 pts | Low | ADR Quality |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +4.9 pts | Medium | Type Safety |
| Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. | +4.9 pts | Medium | Dead Code |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +2.2 pts | Low | Documentation Quality |
| Resolve the 66 Orphaned file finding(s) in Knowledge Freshness — start with Controller.php (2), PlaceTrait.php, Composition.php. | +3.5 pts | Medium | Knowledge Freshness |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +3.4 pts | Medium | Observability |
| Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package. | +2.9 pts | Medium | Large Files |
| 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. | +2.9 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.3 | Slop | Static Analysis (SAST): High: REDACTED |
| core/resources/lazyload/intersectionObserver.polyfill.src.js | 6.5 | Mixed | Cyclomatic Complexity: (anonymous) (cyclomatic 28) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| dev/RepoController.php | 7.4 | Mixed | Cyclomatic Complexity: RepoController.actionInit (cyclomatic 16) |
| core/console/commands/BaseCrudController.php | 7.8 | Mixed | Cyclomatic Complexity: BaseCrudController.generateRules (cyclomatic 28) |
| core/console/commands/HealthController.php | 8.5 | Near-clean | Cognitive Complexity: HealthController.actionIndex (cognitive 24) |
| core/web/CompositionResolver.php | 8.5 | Near-clean | Cognitive Complexity: CompositionResolver.getInternalResolverArray (cognitive 23) |
| core/traits/ErrorHandlerTrait.php | 8.5 | Near-clean | Cognitive Complexity: ErrorHandlerTrait.buildTraceItem (cognitive 21) |
| core/resources/texttospeech/texttospeech.src.js | 8.5 | Near-clean | Cognitive Complexity: textToSpeech (cognitive 19) |
| core/web/Request.php | 8.5 | Near-clean | Cognitive Complexity: Request.getIsAdmin (cognitive 18) |
| core/web/jsonld/CreativeWorkTrait.php | 8.5 | Near-clean | God Classes: TooManyMethods: CreativeWorkTrait |
| core/web/jsonld/OrganizationTrait.php | 8.5 | Near-clean | God Classes: TooManyMethods: OrganizationTrait |
| core/web/jsonld/PersonTrait.php | 8.5 | Near-clean | God Classes: TooManyMethods: PersonTrait |
| core/web/jsonld/PlaceTrait.php | 8.5 | Near-clean | God Classes: TooManyMethods: PlaceTrait |
| core/web/jsonld/EventTrait.php | 8.5 | Near-clean | God Classes: TooManyMethods: EventTrait |
| core/web/jsonld/BaseThing.php | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: BaseThing (LCOM4 14) |
| core/web/Application.php | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Application (LCOM4 7) |
| core/console/Application.php | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Application (LCOM4 6) |
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 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 52 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, 208 of 217 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — the repository root (karma) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`phpunit --verbose --coverage`) shows coverage is measured in your own CI.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 2 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 139 test source file(s) (.php) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php, .js) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 8 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed REDACTED resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares a composer.json but commits no REDACTED this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (65 contributor(s) across 7497 commit(s) sampled, automation and bot accounts excluded). One of them holds 81% of the history; the other 64 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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 Yii's 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.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> luya@1.0.0 dev / > karma start karma.conf.js / sh: 1: karma: not found" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> luya@1.0.0 dev / > karma start karma.conf.js / sh: 1: karma: not found" No runtime evidence was gathered.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
- P7 Outbound HTTP resilience — 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 recognises outbound HTTP clients, their timeouts and resilience policies, and service entry points in .NET, Go, JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang. The JavaScript/TypeScript, PHP source it reads makes no outbound call, and the rest of this repository's production source is , which it does not read yet — the calls may well be there — a gap in this analyzer's language reach, not a finding about the code.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BaseCrudController.generateRules at 28.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with BaseCrudController.generateRules (cyclomatic 28), (anonymous) (cyclomatic 28), intersectionObserver.polyfill.src.IntersectionObserver._computeTargetAndRootIntersection (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 5 together lifts Cyclomatic Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
17 method(s) exceeded the cognitive complexity threshold of 15; the worst was intersectionObserver.polyfill.src.IntersectionObserver._computeTargetAndRootIntersection at 47.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with intersectionObserver.polyfill.src.IntersectionObserver._computeTargetAndRootIntersection (cognitive 47), (anonymous) (cognitive 31). — 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 7.4 to about 7.9/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with CreativeWorkTrait.php, OrganizationTrait.php, PersonTrait.php. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with intersectionObserver.polyfill.src.js. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
0 duplicated block group(s) detected. 0.0 % of the production lines (0 of 21,374) are in a reported copy.
D5 · Coupling
3 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 2 of the 3 (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)
3 of 41 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with Application.php (2), BaseThing.php. — One of this dimension's main actionable groups (3 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2 tests. Measured on the JavaScript/TypeScript suite only — at least 139 test source file(s) (.php) went unread, so its test quality is unmeasured and is not in these counts.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 21374 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 3 document(s) read across 2 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 composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
2 of 99 judged comments only repeat the code they sit on (2.0 %). 17 comment(s) in another language or script were not judged.
What to do
- Resolve the 2 redundant comment finding(s) in Comment Value — start with intersectionObserver.polyfill.src.js, LazyLoadTest.js. — One of this dimension's main actionable groups (2 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Composer, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
23 % of calls cross a namespace and 0 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
4 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
16 finding(s): 0 critical, 12 high, 4 medium, 0 low. 10 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.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
59 finding(s): 15 critical, 30 high, 13 medium, 1 low.
What to do
- Resolve the 30 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (30). — One of this dimension's main actionable groups (30 issue-level).
- Resolve the 15 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14), REDACTED. — One of this dimension's main actionable groups (15 issue-level).
- Resolve the 13 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 warning-level).
D34 · Knowledge Freshness
69 of 69 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/web/jsonld/CreativeWorkTrait.php. Counted over 69 of the 193 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 66 Orphaned file finding(s) in Knowledge Freshness — start with Controller.php (2), PlaceTrait.php, Composition.php. — One of this dimension's main actionable groups (66 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with CreativeWorkTrait.php, OrganizationTrait.php, PersonTrait.php. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase 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.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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 8 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
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `CreativeWorkInterface` declares 132 methods: `getAbout`, `setAbout`, `getAccessMode`, `setAccessMode`, `getAccessModeSufficient`, `setAccessModeSufficient`, `getAccessibilityAPI`, `setAccessibilityAPI`, `getAccessibilityControl`, `setAccessibilityControl`, `getAccessibilityFeature`, `setAccessibilityFeature`, `getAccessibilityHazard`, `setAccessibilityHazard`, `getAccessibilitySummary`, `setAccessibilitySummary`, `getAccountablePerson`, `setAccountablePerson`, `getAlternativeHeadline`, `setAlternativeHeadline`, `getAssociatedMedia`, `setAssociatedMedia`, `getAuthor`, `setAuthor`, `getAward`, `setAward`, `getCharacter`, `setCharacter`, `getCitation`, `setCitation`, `getComment`, `setComment`, `getCommentCount`, `setCommentCount`, `getContentLocation`, `setContentLocation`, `getContentRating`, `setContentRating`, `getContentReferenceTime`, `setContentReferenceTime`, and 92 more. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/web/jsonld/CreativeWorkInterface.php:13
- `EventInterface` declares 54 methods: `getAbout`, `setAbout`, `getActor`, `setActor`, `getAttendee`, `setAttendee`, `getComposer`, `setComposer`, `getContributor`, `setContributor`, `getDirector`, `setDirector`, `getDoorTime`, `setDoorTime`, `getDuration`, `setDuration`, `getEndDate`, `setEndDate`, `getFunder`, `setFunder`, `getInLanguage`, `setInLanguage`, `isAccessibleForFree`, `setIsAccessibleForFree`, `getLocation`, `setLocation`, `getMaximumAttendeeCapacity`, `setMaximumAttendeeCapacity`, `getOrganizer`, `setOrganizer`, `getPerformer`, `setPerformer`, `getPreviousStartDate`, `setPreviousStartDate`, `getRecordedIn`, `setRecordedIn`, `getRemainingAttendeeCapacity`, `setRemainingAttendeeCapacity`, `getSponsor`, `setSponsor`, and 14 more. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/web/jsonld/EventInterface.php:11
- `OrganizationInterface` declares 92 methods: `getActionableFeedbackPolicy`, `setActionableFeedbackPolicy`, `getAddress`, `setAddress`, `getAggregateRating`, `setAggregateRating`, `getAlumni`, `setAlumni`, `getAreaServed`, `setAreaServed`, `getAward`, `setAward`, `getBrand`, `setBrand`, `getContactPoint`, `setContactPoint`, `getCorrectionsPolicy`, `setCorrectionsPolicy`, `getDepartment`, `setDepartment`, `getDissolutionDate`, `setDissolutionDate`, `getDiversityPolicy`, `setDiversityPolicy`, `getDuns`, `setDuns`, `getEmail`, `setEmail`, `getEmployee`, `setEmployee`, `getEthicsPolicy`, `setEthicsPolicy`, `getEvent`, `setEvent`, `getFaxNumber`, `setFaxNumber`, `getFounder`, `setFounder`, `getFoundingDate`, `setFoundingDate`, and 52 more. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/web/jsonld/OrganizationInterface.php:11
- `PersonInterface` declares 90 methods: `getAdditionalName`, `setAdditionalName`, `getAddress`, `setAddress`, `getAffiliation`, `setAffiliation`, `getAward`, `setAward`, `getBirthDate`, `setBirthDate`, `getBirthPlace`, `setBirthPlace`, `getBrand`, `setBrand`, `getChildren`, `setChildren`, `getColleague`, `setColleague`, `getContactPoint`, `setContactPoint`, `getDeathDate`, `setDeathDate`, `getDeathPlace`, `setDeathPlace`, `getDuns`, `setDuns`, `getEmail`, `setEmail`, `getFamilyName`, `setFamilyName`, `getFaxNumber`, `setFaxNumber`, `getFollows`, `setFollows`, `getFunder`, `setFunder`, `getGender`, `setGender`, `getGivenName`, `setGivenName`, and 50 more. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/web/jsonld/PersonInterface.php:13
- `PlaceInterface` declares 66 methods: `getAdditionalProperty`, `setAdditionalProperty`, `getAddress`, `setAddress`, `getAggregateRating`, `setAggregateRating`, `getAmenityFeature`, `setAmenityFeature`, `getBranchCode`, `setBranchCode`, `getContainedInPlace`, `setContainedInPlace`, `getContainsPlace`, `setContainsPlace`, `getEvent`, `setEvent`, `getFaxNumber`, `setFaxNumber`, `getGeo`, `setGeo`, `getGeospatiallyContains`, `setGeospatiallyContains`, `getGeospatiallyCoveredBy`, `setGeospatiallyCoveredBy`, `getGeospatiallyCovers`, `setGeospatiallyCovers`, `getGeospatiallyCrosses`, `setGeospatiallyCrosses`, `getGeospatiallyDisjoint`, `setGeospatiallyDisjoint`, `getGeospatiallyEquals`, `setGeospatiallyEquals`, `getGeospatiallyIntersects`, `setGeospatiallyIntersects`, `getGeospatiallyOverlaps`, `setGeospatiallyOverlaps`, `getGeospatiallyTouches`, `setGeospatiallyTouches`, `getGeospatiallyWithin`, `setGeospatiallyWithin`, and 26 more. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/web/jsonld/PlaceInterface.php:11
- `ThingInterface` declares 24 methods: `getAdditionalType`, `setAdditionalType`, `getAlternateName`, `setAlternateName`, `getDescription`, `setDescription`, `getDisambiguatingDescription`, `setDisambiguatingDescription`, `getIdentifier`, `setIdentifier`, `getImage`, `setImage`, `getMainEntityOfPage`, `setMainEntityOfPage`, `getName`, `setName`, `getSameAs`, `setSameAs`, `getSubjectOf`, `setSubjectOf`, `getUrl`, `setUrl`, `setOffers`, `getOffers`. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/web/jsonld/ThingInterface.php:11
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:8
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
R1 · Type Safety
- 0 typed · 7 plain JS — the untyped files are actions.karma.conf.js, core/resources/lazyload/intersectionObserver.polyfill.src.js, core/resources/lazyload/lazyload.src.js, core/resources/texttospeech/texttospeech.src.js, karma.conf.js, tests/js/LazyLoadTest.js (+1 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- core/resources/lazyload/intersectionObserver.polyfill.src.js:473 · core/resources/lazyload/intersectionObserver.polyfill.src.js:516 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/resources/lazyload/intersectionObserver.polyfill.src.js:473
- core/resources/lazyload/intersectionObserver.polyfill.src.js:1359 · core/resources/lazyload/intersectionObserver.polyfill.src.js:1377 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — core/resources/lazyload/intersectionObserver.polyfill.src.js:1359
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 28 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/resources/lazyload/intersectionObserver.polyfill.src.js:47
- _computeTargetAndRootIntersection has cyclomatic complexity 25 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/resources/lazyload/intersectionObserver.polyfill.src.js:1118
- defineProperty has cyclomatic complexity 14 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/resources/lazyload/intersectionObserver.polyfill.src.js:385
- getOwnPropertyDescriptor has cyclomatic complexity 12 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/resources/lazyload/intersectionObserver.polyfill.src.js:128
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/resources/lazyload/intersectionObserver.polyfill.src.js:1064
- _hasCrossedThreshold has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/resources/lazyload/intersectionObserver.polyfill.src.js:1251
R3 · Large Files
- core/resources/lazyload/intersectionObserver.polyfill.src.js has 1368 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/resources/lazyload/intersectionObserver.polyfill.src.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 2 application, 2 tooling and 3 test entry point(s) detected in this repo. Nothing this repository declares compiles or type-checks these files, so a wrong deletion here would raise no compile error — gate removals on `yarn test`, which loads the modules, and note that it only covers what it exercises. An undetected custom entry would make these reachable.
- no import path from any entry point (2 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — core/resources/lazyload/intersectionObserver.polyfill.src.js, core/resources/lazyload/lazyload.src.js, core/resources/texttospeech/texttospeech.src.js
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
R9 · Circular Imports
X16 · Unfloored truncation loop
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
- line 144 walks `$rules` by value, so the walk is the snapshot taken when the loop began, and line 147 changes that same collection with `$rules[] = …` before the next iteration: the added element is never visited by this loop, so whatever it was added for is not done here. PHP raises nothing, so the loop completes over a different set than the code meant. — core/web/UrlManager.php:144
- line 133 walks `$traits` by value, so the walk is the snapshot taken when the loop began, and line 134 changes that same collection with `$traits = …` before the next iteration: the loop carries on over the old value while the body now works on the new one. PHP raises nothing, so the loop completes over a different set than the code meant. — core/helpers/ObjectHelper.php:133
What to do
- Each finding names the two lines that cannot both stand — the `foreach` over the collection, and the change to it in the body. Confirm from those two, then pick one: build the result instead of editing the walked collection (`$kept = array_filter($items, $keep)`, `$batch->reject(…)`); for a worklist, loop `while (($next = array_shift($queue)) !== null)` so what is added is visited; walk a copy (`foreach (array_values($items) as …)`, `foreach (clone $storage as …)`) and change the original; remove only the CURRENT element (`unset($items[$key])`), which an array walk tolerates; or — where only the first match was ever meant — `break` straight after the change.
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — core/resources/lazyload/intersectionObserver.polyfill.src.js:138, core/resources/lazyload/intersectionObserver.polyfill.src.js:397, core/resources/lazyload/intersectionObserver.polyfill.src.js:462, …
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- 0/1 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 22.7 | Critical — gated by R1, R3, R7, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 73.8 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 60.2 | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55.8 | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 86.9 | Strong | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> luya@1.0.0 dev / > karma start karma.conf.js / sh: 1: karma: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 8 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed REDACTED resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Composer package licences not graded — this repository commits no REDACTED and this pass does not run Composer's solver
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, 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
- P7 Outbound HTTP resilience — 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
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — 3 test file(s) reach none of 3 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 8% of this repository's production lines — php (21,276 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
- 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.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 58 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 68 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: CreativeWorkTrait core/web/jsonld/CreativeWorkTrait.php:15
- TooManyMethods: OrganizationTrait core/web/jsonld/OrganizationTrait.php:11
- TooManyMethods: PersonTrait core/web/jsonld/PersonTrait.php:15
- TooManyMethods: PlaceTrait core/web/jsonld/PlaceTrait.php:13
- TooManyMethods: EventTrait core/web/jsonld/EventTrait.php:15
- Swallowed exception (empty catch) core/resources/lazyload/intersectionObserver.polyfill.src.js:138
- Swallowed exception (empty catch) core/resources/lazyload/intersectionObserver.polyfill.src.js:397
- Swallowed exception (empty catch) core/resources/lazyload/intersectionObserver.polyfill.src.js:462
- Swallowed exception (empty catch) core/resources/lazyload/intersectionObserver.polyfill.src.js:1423
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: BaseThing (LCOM4 14) core/web/jsonld/BaseThing.php:18
- Low cohesion: Application (LCOM4 7) core/web/Application.php:29
- Low cohesion: Application (LCOM4 6) core/console/Application.php:15
- Collection is structurally changed while it is being enumerated core/web/UrlManager.php:144
- Collection is structurally changed while it is being enumerated core/helpers/ObjectHelper.php:133
- BaseCrudController.generateRules (cyclomatic 28) core/console/commands/BaseCrudController.php:63
- (anonymous) (cyclomatic 28) core/resources/lazyload/intersectionObserver.polyfill.src.js:47
- intersectionObserver.polyfill.src.IntersectionObserver._computeTargetAndRootIntersection (cyclomatic 25) core/resources/lazyload/intersectionObserver.polyfill.src.js:1118
- RepoController.actionInit (cyclomatic 16) dev/RepoController.php:81
- intersectionObserver.polyfill.src.IntersectionObserver._checkForIntersections (cyclomatic 16) core/resources/lazyload/intersectionObserver.polyfill.src.js:1055
- intersectionObserver.polyfill.src.IntersectionObserver._computeTargetAndRootIntersection (cognitive 47) core/resources/lazyload/intersectionObserver.polyfill.src.js:1118
- (anonymous) (cognitive 31) core/resources/lazyload/intersectionObserver.polyfill.src.js:47
- RepoController.actionInit (cognitive 27) dev/RepoController.php:81
- BaseCrudController.generateRules (cognitive 26) core/console/commands/BaseCrudController.php:63
- HealthController.actionIndex (cognitive 24) core/console/commands/HealthController.php:40
- CompositionResolver.getInternalResolverArray (cognitive 23) core/web/CompositionResolver.php:121
- ErrorHandlerTrait.buildTraceItem (cognitive 21) core/traits/ErrorHandlerTrait.php:253
- defineProperty (cognitive 20) core/resources/lazyload/intersectionObserver.polyfill.src.js:385
- getOwnPropertyDescriptor (cognitive 19) core/resources/lazyload/intersectionObserver.polyfill.src.js:128
- textToSpeech (cognitive 19) core/resources/texttospeech/texttospeech.src.js:2
- Request.getIsAdmin (cognitive 18) core/web/Request.php:60
- RepoController.actionClone (cognitive 16) dev/RepoController.php:174
- intersectionObserver.polyfill.src.IntersectionObserver._monitorIntersections (cognitive 16) core/resources/lazyload/intersectionObserver.polyfill.src.js:920
- _checkForIntersections (cognitive 16) core/resources/lazyload/intersectionObserver.polyfill.src.js:1055
- REDACTED
- FileTooLong: lazyload/intersectionObserver.polyfill.src.js core/resources/lazyload/intersectionObserver.polyfill.src.js
- REDACTED
- Coverage collected but not gated
- No structured logging
- Type Safety
- Duplicated block (16 lines × 2 locations) core/resources/lazyload/intersectionObserver.polyfill.src.js:473
- Duplicated block (8 lines × 2 locations) core/resources/lazyload/intersectionObserver.polyfill.src.js:1359
- Complex function (anonymous) (cyclomatic 28, cognitive 31) core/resources/lazyload/intersectionObserver.polyfill.src.js:47
- Complex function _computeTargetAndRootIntersection (cyclomatic 25, cognitive 47) core/resources/lazyload/intersectionObserver.polyfill.src.js:1118
- Complex function defineProperty (cyclomatic 14, cognitive 20) core/resources/lazyload/intersectionObserver.polyfill.src.js:385
- Complex function getOwnPropertyDescriptor (cyclomatic 12, cognitive 19) core/resources/lazyload/intersectionObserver.polyfill.src.js:128
- Complex function (anonymous) (cyclomatic 11, cognitive 12) core/resources/lazyload/intersectionObserver.polyfill.src.js:1064
- Complex function _hasCrossedThreshold (cyclomatic 11, cognitive 10) core/resources/lazyload/intersectionObserver.polyfill.src.js:1251
- core/resources/lazyload/intersectionObserver.polyfill.src.js: 1368 lines of code core/resources/lazyload/intersectionObserver.polyfill.src.js:1
- No typecheck script
- Dead file (~1562 LoC) core/resources/lazyload/intersectionObserver.polyfill.src.js
- Dead file (~235 LoC) core/resources/lazyload/lazyload.src.js
- Dead file (~136 LoC) core/resources/texttospeech/texttospeech.src.js
Minor — 90 finding(s)
- Orphaned file core/web/jsonld/PlaceTrait.php:1
- Orphaned file core/web/Composition.php:1
- Orphaned file core/components/Mail.php:1
- Orphaned file core/web/UrlManager.php:1
- Orphaned file core/web/jsonld/CreativeWorkInterface.php:1
- Orphaned file core/web/jsonld/EventTrait.php:1
- Orphaned file core/base/Module.php:1
- Orphaned file core/Config.php:1
- Orphaned file dev/RepoController.php:1
- Orphaned file core/traits/ApplicationTrait.php:1
- Orphaned file core/traits/ErrorHandlerTrait.php:1
- Orphaned file core/web/JsonLd.php:1
- Orphaned file core/web/jsonld/OrganizationInterface.php:1
- Orphaned file core/web/jsonld/PersonInterface.php:1
- Orphaned file core/console/commands/BaseCrudController.php:1
- Orphaned file core/base/Boot.php:1
- Orphaned file core/web/Element.php:1
- Orphaned file core/base/ModuleReflection.php:1
- Orphaned file core/helpers/ObjectHelper.php:1
- Orphaned file core/theme/ThemeManager.php:1
- Orphaned file core/web/jsonld/PlaceInterface.php:1
- Orphaned file core/traits/RestBehaviorsTrait.php:1
- Orphaned file core/console/commands/ImportController.php:1
- Orphaned file core/lazyload/LazyLoad.php:1
- Orphaned file core/texttospeech/TextToSpeechWidget.php:1
- Fat interface: CreativeWorkInterface (132 methods) core/web/jsonld/CreativeWorkInterface.php:13
- Fat interface: EventInterface (54 methods) core/web/jsonld/EventInterface.php:11
- Fat interface: OrganizationInterface (92 methods) core/web/jsonld/OrganizationInterface.php:11
- Fat interface: PersonInterface (90 methods) core/web/jsonld/PersonInterface.php:13
- Fat interface: PlaceInterface (66 methods) core/web/jsonld/PlaceInterface.php:11
- Fat interface: ThingInterface (24 methods) core/web/jsonld/ThingInterface.php:11
- REDACTED
- REDACTED
- REDACTED
- Most significant orphaned file core/web/jsonld/CreativeWorkTrait.php:1
- Most significant orphaned file core/web/jsonld/OrganizationTrait.php:1
- Most significant orphaned file core/web/jsonld/PersonTrait.php:1
- redundant comment core/resources/lazyload/intersectionObserver.polyfill.src.js:714
- redundant comment tests/js/LazyLoadTest.js:36
- Documentation: no build, run or usage example core/README.md:1
- No ADRs found composer.json:4
- Projects may be oversized for their cohesion core/composer.json:1
- REDACTED
- REDACTED
- Dormant codebase
- REDACTED
- No ADRs
- No dependency-update automation package.json:8
- PHP static analysis does not check null everywhere
Minor — 1 finding(s)
- doc comments repeat the names core/resources/lazyload/intersectionObserver.polyfill.src.js:1495
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-9c442a7f1f0e4194864eaa2e6a58330c/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-9c442a7f1f0e4194864eaa2e6a58330c/history-1.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-9c442a7f1f0e4194864eaa2e6a58330c/history-2.json --exit-code 0 --source . | 7 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=3297" --report-format json --report-path /tmp/watchdog-gitleaks-9c442a7f1f0e4194864eaa2e6a58330c/history-3.json --exit-code 0 --source . | 8 | artifacts/raw/gitleaks-history-3.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-9c442a7f1f0e4194864eaa2e6a58330c/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 . | 16 | 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/** . | 59 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 |