Executive summary
AlloVince/EvaThumber meets our standard for production. It scores 73.6 out of 100 and is rated Strong, and nine of its 11 critical findings are security problems in the build pipeline.
Production Readiness, at 64.2, is the weakest lens and counts most in the score. The best first step is making the six tests that check nothing check their results, worth about 6.9 points. Adding automated security scanning would lift Production Readiness itself, worth about 6.1 points. Raising Production Readiness to 70 would lift the score to about 76.3.
Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline. Pinning each tool to an exact version and limiting the secret to its own step would close both risks. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 2,211 lines, about β¬8,700 to rebuild.
If Production Readiness rose from 64.2 to 70, the lowest score rated Strong, the score would rise from 73.6 to about 76.3.
Rebuild cost: about β¬8,700 Β· Estimate
| Cost to rebuild | β¬2,900 to β¬15,000, for 48 to 153 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.1 at a score of 74. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 2,211 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture β module dependency graph
Architecture: which parts of the code depend on which
| uses β | 1 EvaThumber | 2 EvaThumber.Cache | 3 EvaThumber.Exception | 4 EvaThumber.Security | 5 EvaThumber.Http | 6 EvaThumber.Source | 7 EvaThumber.Transformation | 8 EvaThumber.Image | 9 EvaThumber.Url |
|---|---|---|---|---|---|---|---|---|---|
| 1 EvaThumber | |||||||||
| 2 EvaThumber.Cache | |||||||||
| 3 EvaThumber.Exception | |||||||||
| 4 EvaThumber.Security | |||||||||
| 5 EvaThumber.Http | 1 | 1 | |||||||
| 6 EvaThumber.Source | 1 | ||||||||
| 7 EvaThumber.Transformation | 1 | ||||||||
| 8 EvaThumber.Image | 1 | 2 | 2 | 5 | |||||
| 9 EvaThumber.Url | 1 | 1 |
5β2 EvaThumber.Http uses EvaThumber.Cache✕
- Connections
- 1 pair of types, where a type in EvaThumber.Http uses a type in EvaThumber.Cache.
- The types involved
EvaThumber.Http.CachedFileResponseβEvaThumber.Cache.CacheEntry
- Direction
- EvaThumber.Http uses EvaThumber.Cache, so a change to EvaThumber.Cache can break EvaThumber.Http, while a change to EvaThumber.Http can't break EvaThumber.Cache.
- Position
- Below the diagonal: EvaThumber.Http uses a module listed above it, which is the healthy direction.
5β4 EvaThumber.Http uses EvaThumber.Security✕
- Connections
- 1 pair of types, where a type in EvaThumber.Http uses a type in EvaThumber.Security.
- The types involved
EvaThumber.Http.SettingsβEvaThumber.Security.Limits
- Direction
- EvaThumber.Http uses EvaThumber.Security, so a change to EvaThumber.Security can break EvaThumber.Http, while a change to EvaThumber.Http can't break EvaThumber.Security.
- Position
- Below the diagonal: EvaThumber.Http uses a module listed above it, which is the healthy direction.
6β4 EvaThumber.Source uses EvaThumber.Security✕
- Connections
- 1 pair of types, where a type in EvaThumber.Source uses a type in EvaThumber.Security.
- The types involved
EvaThumber.Source.LocalSourceβEvaThumber.Security.Limits
- Direction
- EvaThumber.Source uses EvaThumber.Security, so a change to EvaThumber.Security can break EvaThumber.Source, while a change to EvaThumber.Source can't break EvaThumber.Security.
- Position
- Below the diagonal: EvaThumber.Source uses a module listed above it, which is the healthy direction.
7β4 EvaThumber.Transformation uses EvaThumber.Security✕
- Connections
- 1 pair of types, where a type in EvaThumber.Transformation uses a type in EvaThumber.Security.
- The types involved
EvaThumber.Transformation.ParserβEvaThumber.Security.Limits
- Direction
- EvaThumber.Transformation uses EvaThumber.Security, so a change to EvaThumber.Security can break EvaThumber.Transformation, while a change to EvaThumber.Transformation can't break EvaThumber.Security.
- Position
- Below the diagonal: EvaThumber.Transformation uses a module listed above it, which is the healthy direction.
8β4 EvaThumber.Image uses EvaThumber.Security✕
- Connections
- 1 pair of types, where a type in EvaThumber.Image uses a type in EvaThumber.Security.
- The types involved
EvaThumber.Image.PipelineβEvaThumber.Security.Limits
- Direction
- EvaThumber.Image uses EvaThumber.Security, so a change to EvaThumber.Security can break EvaThumber.Image, while a change to EvaThumber.Image can't break EvaThumber.Security.
- Position
- Below the diagonal: EvaThumber.Image uses a module listed above it, which is the healthy direction.
8β5 EvaThumber.Image uses EvaThumber.Http✕
- Connections
- 2 pairs of types, where a type in EvaThumber.Image uses a type in EvaThumber.Http.
- The types involved
EvaThumber.Image.IsolatedProcessorβEvaThumber.Http.SettingsEvaThumber.Image.PoolProcessorβEvaThumber.Http.Settings
- Direction
- EvaThumber.Image uses EvaThumber.Http, so a change to EvaThumber.Http can break EvaThumber.Image, while a change to EvaThumber.Image can't break EvaThumber.Http.
- Position
- Below the diagonal: EvaThumber.Image uses a module listed above it, which is the healthy direction.
8β6 EvaThumber.Image uses EvaThumber.Source✕
- Connections
- 2 pairs of types, where a type in EvaThumber.Image uses a type in EvaThumber.Source.
- The types involved
EvaThumber.Image.PipelineβEvaThumber.Source.SourceImageEvaThumber.Image.ThumberβEvaThumber.Source.SourceImage
- Direction
- EvaThumber.Image uses EvaThumber.Source, so a change to EvaThumber.Source can break EvaThumber.Image, while a change to EvaThumber.Image can't break EvaThumber.Source.
- Position
- Below the diagonal: EvaThumber.Image uses a module listed above it, which is the healthy direction.
8β7 EvaThumber.Image uses EvaThumber.Transformation✕
- Connections
- 5 pairs of types, where a type in EvaThumber.Image uses a type in EvaThumber.Transformation.
- The types involved
EvaThumber.Image.IsolatedProcessorβEvaThumber.Transformation.TransformationEvaThumber.Image.PipelineβEvaThumber.Transformation.StepEvaThumber.Image.PipelineβEvaThumber.Transformation.TransformationEvaThumber.Image.PoolProcessorβEvaThumber.Transformation.TransformationEvaThumber.Image.ThumberβEvaThumber.Transformation.Transformation
- Direction
- EvaThumber.Image uses EvaThumber.Transformation, so a change to EvaThumber.Transformation can break EvaThumber.Image, while a change to EvaThumber.Image can't break EvaThumber.Transformation.
- Position
- Below the diagonal: EvaThumber.Image uses a module listed above it, which is the healthy direction.
9β4 EvaThumber.Url uses EvaThumber.Security✕
- Connections
- 1 pair of types, where a type in EvaThumber.Url uses a type in EvaThumber.Security.
- The types involved
EvaThumber.Url.ParserβEvaThumber.Security.Limits
- Direction
- EvaThumber.Url uses EvaThumber.Security, so a change to EvaThumber.Security can break EvaThumber.Url, while a change to EvaThumber.Url can't break EvaThumber.Security.
- Position
- Below the diagonal: EvaThumber.Url uses a module listed above it, which is the healthy direction.
9β7 EvaThumber.Url uses EvaThumber.Transformation✕
- Connections
- 1 pair of types, where a type in EvaThumber.Url uses a type in EvaThumber.Transformation.
- The types involved
EvaThumber.Url.ImageUrlβEvaThumber.Transformation.Transformation
- Direction
- EvaThumber.Url uses EvaThumber.Transformation, so a change to EvaThumber.Transformation can break EvaThumber.Url, while a change to EvaThumber.Url can't break EvaThumber.Transformation.
- Position
- Below the diagonal: EvaThumber.Url 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 |
|---|---|---|
| A05:2025 β Injection | 9 | High / Critical |
| A03:2025 β Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: Resolve the 6 No assertions finding(s) in Test Quality β start with CacheConcurrencyTest.php (3), PipelineTest.php (2), CachePublicationTest.php; Your ecosystem's static analyzer is declared as a dependency but is not wired into CI β run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 6 No assertions finding(s) in Test Quality β start with CacheConcurrencyTest.php (3), PipelineTest.php (2), CachePublicationTest.php. | +6.9 pts | Low | Test Quality |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI β run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +6.1 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.7 pts | Medium | Release Hygiene |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 3 Off the main sequence finding(s) in Coupling. | +0.5 pts | Low | Coupling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Http/Kernel.php | 5.8 | Mixed | Coupling: Circular dependency |
| src/Image/PoolProcessor.php | 7.0 | Mixed | Cyclomatic Complexity: PoolProcessor.write (cyclomatic 24) |
| src/Cache/DiskCache.php | 7.4 | Mixed | Cyclomatic Complexity: DiskCache.remember (cyclomatic 27) |
| src/Image/Pipeline.php | 7.4 | Mixed | Cyclomatic Complexity: Pipeline.prepare (cyclomatic 18) |
| tests/v2/CacheConcurrencyTest.php | 7.4 | Mixed | Test Quality: No assertions: testAdmissionSlotsBoundMissesAndRecoverAfterProcessDeath |
| src/Transformation/ParameterRules.php | 7.8 | Mixed | Cyclomatic Complexity: ParameterRules.normalize (cyclomatic 51) |
| src/Url/Parser.php | 7.8 | Mixed | Cyclomatic Complexity: Parser.parse (cyclomatic 21) |
| src/Source/LocalSource.php | 7.8 | Mixed | Cyclomatic Complexity: LocalSource.resolve (cyclomatic 19) |
| tests/v2/PipelineTest.php | 7.8 | Mixed | Test Quality: No assertions: testExplicitFormatOverridesDeliveryFormat |
| tests/v2/CachePublicationTest.php | 8.5 | Near-clean | Test Quality: No assertions: testAtomicLinkAndCrashBeforeTemporaryUnlinkPreservePublishedEntry |
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 47 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 β 47 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, 47 of 57 do; the remainder are repo-wide signals β a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score β and this report, byte for byte β is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | β deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | β deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | β deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | β deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | β deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 Β· 0.31.0 | β deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 Β· 0.69.3 Β· 3.2.533 | β deterministic |
Run transparency β what happened this run
- D8 Code Coverage β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem β so this suite was never executed by it. Not scored β this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored β this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 (4 contributor(s) across 134 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 3 hold 1.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.
- D19 Documentation Quality β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D20 ADR Quality β 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. The ADR lexicon (adr-lexicon-1) covers de, en, it, nl. A record identified as another language, or whose language could not be identified (fewer than 25 words of prose, or no clear winner), is never read with English rules: its missing-section, status, consequence-cost and same-question rules abstain, and only the structural rules (title, single option, dangling link, enforcement field) run.
- 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's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach β not a finding about this repository.
- D32 Data Compliance (PII/GDPR) β 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. `src/Cache/DiskCache.php`, `src/Exception/ImageException.php`, `src/Http/Kernel.php`, `src/Http/Settings.php`, `src/Image/IsolatedProcessor.php`, β¦ (+12 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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. An image the Dockerfile builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository. (rule: registry). The renderer reported: compose up failed (exit 17 β an image could not be built) β evathumber Pulling evathumber Warning pull access denied for evathumber, repository does not exist or may require 'docker login': denied: requested access to the resource is denied failed to solve: process "/bin/sh -c composer install --no-dev --no-interaction --prefer-dist --classmap-authoritative --no-scripts" did not complete successfully: exit code: 100; likely cause (our sandbox): an image the Dockerfile builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
- AXR1 Runtime accessibility β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (compose.yaml). compose up failed (exit 17 β an image could not be built) β evathumber Pulling evathumber Warning pull access denied for evathumber, repository does not exist or may require 'docker login': denied: requested access to the resource is denied failed to solve: process "/bin/sh -c composer install --no-dev --no-interaction --prefer-dist --classmap-authoritative --no-scripts" did not complete successfully: exit code: 100; likely cause (our sandbox): an image the Dockerfile builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
- GD1 Unfinished & placeholder code β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's PHP 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 no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's PHP 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 no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach β not a finding that the repository lacks web-security controls.
- X1 Async correctness β 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, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach β not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, 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.
- X13 Undrained process stream β 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, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, 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.
- X17 Uncapped recursion over a caller-supplied document β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, 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.
- X24 Document value interpolated into markup unescaped β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
- X29 Per-element action decided by a fixed element β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules β an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D10 Test Quality: Assertion density is structural β it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles β a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree β a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy β mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history β a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual β undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded β it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D27 Navigability: Indirection/navigability is structural β it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns β a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) β it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases β a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules β it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension β code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS β files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen β a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen β a runtime named only in a 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see β only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) β controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 Β· Cyclomatic Complexity
8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ParameterRules.normalize at 51.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity β start with ParameterRules.normalize (cyclomatic 51). β Refactoring it lifts Cyclomatic Complexity from 5.1 to about 6.9/10.
D2 Β· Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was ParameterRules.normalize at 47.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity β start with ParameterRules.normalize (cognitive 47), DiskCache.remember (cognitive 34). β 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 5.2 to about 6.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 Β· God Classes
0 god class(es) detected.
D4 Β· Code Duplication
2 duplicated block group(s) detected. 4.6 % of the production lines (102 of 2,211) are in a reported copy. One further row reports members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (51 corresponding lines) finding(s) in Code Duplication β start with PoolProcessor.php. β One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (16 lines × 2) finding(s) in Code Duplication β start with PoolProcessor.php. β One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (13 lines × 2) finding(s) in Code Duplication β start with PoolProcessor.php. β One of this dimension's main actionable groups (1 warning-level).
D5 Β· Coupling
10 production modules (source-import), 1 dependency cycle(s), 1 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 3 module(s) off the main sequence, with abstractness counted on 9 of the 10 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 3 Off the main sequence finding(s) in Coupling. β One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Circular dependency finding(s) in Coupling β start with Kernel.php. β One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Unstable project src/Image finding(s) in Coupling. β One of this dimension's main actionable groups (1 warning-level).
D6 Β· Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D7 Β· Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D10 Β· Test Quality
5 skipped (5 with a documented reason), 6 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 56 tests.
What to do
- Resolve the 6 No assertions finding(s) in Test Quality β start with CacheConcurrencyTest.php (3), PipelineTest.php (2), CachePublicationTest.php. β One of this dimension's main actionable groups (6 warning-level).
D12 Β· Dependency Hygiene
0 outdated, 0 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind β whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.
D13 Β· Secret Scanning
Secret scan ran and found no leaked secrets.
D14 Β· License Compliance
0 of 15 locked Composer package(s) use a banned license. Licences were read from this repository's composer.lock, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 26 package(s) under `packages-dev` are not installed for a consumer and are excluded.
D15 Β· Churn × Complexity Hotspots
Top hotspots: src/Transformation/ParameterRules.php (2×51=102); src/Http/Kernel.php (5×16=80); src/Image/Pipeline.php (4×18=72)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots β start with ParameterRules.php, Kernel.php, Pipeline.php. β One of this dimension's main actionable groups (4 warning-level).
D17 Β· Explicit Debt
0 deducted task-comment markers across 2211 LoC (0.0/KLoC) β score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 Β· Documentation Quality
1 of 1 documentation facets pass in full. 28 document(s) read across 1 unit(s).
D27 Β· Navigability
27 % of calls cross a namespace and 0 % go through an interface, but 31 % of collaborators are co-located β so following a call takes several hops. Baseline: small β navigation cost is tolerated.
D28 Β· Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 Β· Static Analysis (SAST)
9 finding(s): 0 critical, 9 high, 0 medium, 0 low. 8 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` β one pinning decision is charged once, not once per lens. semgrep hit a parse error in 17 file(s) β `src/Cache/DiskCache.php` (line 9), `src/Exception/ImageException.php` (line 11, line 12), `src/Http/Kernel.php` (line 19), `src/Http/Settings.php` (line 9), `src/Image/IsolatedProcessor.php` (line 13), β¦ (+12 more) β so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED. β One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) β all 8 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 (8 issue-level, 0 of them charged here).
D30 Β· Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 Β· IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 Β· Knowledge Freshness
Every significant source file has living knowledge β recently and meaningfully worked. Counted over 14 of the 31 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 Β· Change Coupling
No strong hidden change-coupling between production files.
D36 Β· Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. β One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. β One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. β One of this dimension's main actionable groups (1 recommendation-level).
D43 Β· Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 Β· Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 6 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
- The projects src/Http β src/Image β src/Http form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. β src/Http/Kernel.php:9
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 Β· Dependency direction
AX6 Β· Interface segregation
AX8 Β· Test isolation
M1 Β· Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 Β· Architecture documentation
M3 Β· Folder & project structure
M4 Β· Documentation accuracy
P1 Β· CI/CD gates
P10 Β· Library API & versioning
P2 Β· Observability
P3 Β· Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI β run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 Β· Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 Β· Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file β what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X16 Β· Unfloored truncation loop
X18 Β· Disposal-pattern correctness
X21 Β· Side-effecting pattern guard
X25 Β· Inert configuration knob
X27 Β· Collection changed while being enumerated
X28 Β· Index access outside its own emptiness guard
X3 Β· Exception handling
X5 Β· Nullable reference types
Reference β by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 89.4 | Strong | Strongest area. |
| Architecture | 87.7 | Adequate β gated by D5 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Maturity | 86.0 | Strong | Solid. |
| Readiness | 64.2 | Adequate β gated by P3 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Security | 76.8 | Adequate β gated by D36 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
Not evidenced β 1 control(s) we could not find positive evidence for
- P5 DR & Backup β not evidenced β repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included β 69 check(s) not relevant to this codebase
- AC1 Text alternatives β No web markup found β accessibility is not applicable to this repository.
- AC2 Forms & labels β No web markup found β accessibility is not applicable to this repository.
- AC3 Page structure β No web markup found β accessibility is not applicable to this repository.
- AC4 Keyboard semantics β No web markup found β accessibility is not applicable to this repository.
- AC5 ARIA correctness β No web markup found β accessibility is not applicable to this repository.
- AC6 Visual & motion safety β No web markup found β accessibility is not applicable to this repository.
- AX1 Captive dependencies β Not applicable: this repository's PHP imports no dependency-injection container and defines no container of its own β nothing that both registers and resolves bindings, and nothing that names two lifetimes β so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons β Not applicable: PHP builds its object graph per request and shares none of it between requests.
- AX5 Architecture & structure β not assessed β architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion β not applicable β not a vertical-slice architecture
- AX9 CQS / query purity β no CQRS query handlers detected β query purity is not applicable to this codebase
- AXB2 Runtime readiness β Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility β compose up failed (exit 17 β an image could not be built) β evathumber Pulling evathumber Warning pull access denied for evathumber, repository does not exist or may require 'docker login': denied: requested access to the resource is denied failed to solve: process "/bin/sh -c composer install --no-dev --no-interaction --prefer-dist --classmap-authoritative --no-scripts" did not complete successfully: exit code: 100; likely cause (our sandbox): an image the Dockerfile builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection β No personal data detected in a persisted data model β no PII-named field (email, first_name, date_of_birth, phone, β¦) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property β and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls β No access-control surface detected in the analyzed source β this repository registers no route (no Laravel Route::β¦, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here β a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail β No personal data detected in a persisted data model β no PII-named field (email, first_name, date_of_birth, phone_number, β¦) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property β and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention β No personal data detected in a persisted data model β no PII-named field (email, first_name, date_of_birth, phone, β¦) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property β and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights β No personal data detected in a persisted data model β no PII-named field (email, first_name, date_of_birth, phone, β¦) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property β and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability β Test reliability not included β no .php test runner
- D16 Bus Factor β single-maintainer repository β bus factor is not applicable
- D18 Solution Shape β D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality β 2 ADR(s) are written in a language our ADR lexicon does not cover, or are too short to tell (undetermined); their sections and statuses were not judged.
- D21 Naming Consistency β Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency β API consistency is measured on C#, TypeScript, Go only; the exposed PHP surface was not measured.
- D23 Boundary Type-Coupling β No bounded-context organisation was detected either β neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (β₯2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it β e.g. `architecture:` β `contexts:` β `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value β D24 reads C#, Visual Basic, TypeScript and JavaScript comments only β this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance β None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D26 Project Cohesion β This repository is one build unit, `(repository root)` (2211 LoC, 25 module-visible types across 10 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D32 Data Compliance (PII/GDPR) β 17 file(s) were not parsed by semgrep β the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy β No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement β No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement β No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement β No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D8 Code Coverage β Coverage not included β suite not readable by the collector
- DM1 Domain Modelling β not scored β this repository shows only 1 of the 3 signals this lens looks for (16 value object(s))
- ED1 Event-Driven β not scored β this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency β no mutating command handlers or message consumers detected β idempotency check not applicable
- ES1 Event Sourcing β not scored β this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code β no source files were read β this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs β not analysed β these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty β Reported, not scored β and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience β not applicable β no HTTP server, API framework or worker entry point was found in the PHP source, so there is no service whose uptime a failing dependency could take down
- 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.
- S1 Web-Security Posture β Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository β because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness β not 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
- X10 Duplicated predicate β Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch β 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
- X13 Undrained process stream β 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
- 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 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
- X19 Unrestored process-global state β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation β no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) β synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard β This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception β .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped β not 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
- 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. Not a gap in the analyzer and not a finding about your code.
- X29 Per-element action decided by a fixed element β 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
- 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 β 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Project dependency cycle src/Http/Kernel.php:9
- REDACTED
- Circular dependency src/Http/Kernel.php:9
Serious β 36 finding(s)
- No assertions: testAdmissionSlotsBoundMissesAndRecoverAfterProcessDeath tests/v2/CacheConcurrencyTest.php:13
- No assertions: testKilledProducerReleasesLockAndOrphanTemporaryIsCleaned tests/v2/CacheConcurrencyTest.php:129
- No assertions: testConcurrentSameKeyMissReusesPublishedEntry tests/v2/CacheConcurrencyTest.php:171
- No assertions: testAtomicLinkAndCrashBeforeTemporaryUnlinkPreservePublishedEntry tests/v2/CachePublicationTest.php:33
- No assertions: testExplicitFormatOverridesDeliveryFormat tests/v2/PipelineTest.php:16
- No assertions: testNoFormatDefaultsToDeliveryFormat tests/v2/PipelineTest.php:21
- Hotspot: src/Transformation/ParameterRules.php src/Transformation/ParameterRules.php:15
- Hotspot: src/Http/Kernel.php src/Http/Kernel.php:79
- Hotspot: src/Image/Pipeline.php src/Image/Pipeline.php:72
- Hotspot: src/Cache/DiskCache.php src/Cache/DiskCache.php:22
- Off the main sequence: src
- Off the main sequence: src/Exception
- Off the main sequence: src/Security
- ParameterRules.normalize (cyclomatic 51) src/Transformation/ParameterRules.php:15
- DiskCache.remember (cyclomatic 27) src/Cache/DiskCache.php:22
- PoolProcessor.write (cyclomatic 24) src/Image/PoolProcessor.php:78
- PoolProcessor.probe (cyclomatic 21) src/Image/PoolProcessor.php:23
- Parser.parse (cyclomatic 21) src/Url/Parser.php:17
- LocalSource.resolve (cyclomatic 19) src/Source/LocalSource.php:37
- Pipeline.prepare (cyclomatic 18) src/Image/Pipeline.php:72
- Kernel.handleRequest (cyclomatic 16) src/Http/Kernel.php:79
- ParameterRules.normalize (cognitive 47) src/Transformation/ParameterRules.php:15
- DiskCache.remember (cognitive 34) src/Cache/DiskCache.php:22
- Parser.parse (cognitive 29) src/Url/Parser.php:17
- Pipeline.prepare (cognitive 26) src/Image/Pipeline.php:72
- PoolProcessor.write (cognitive 26) src/Image/PoolProcessor.php:78
- PoolProcessor.probe (cognitive 23) src/Image/PoolProcessor.php:23
- LocalSource.resolve (cognitive 22) src/Source/LocalSource.php:37
- Kernel.handleRequest (cognitive 18) src/Http/Kernel.php:79
- Pipeline.resize (cognitive 18) src/Image/Pipeline.php:118
- DiskCache.makeRoom (cognitive 16) src/Cache/DiskCache.php:173
- REDACTED
- Edited copy of a member (51 corresponding lines) src/Image/PoolProcessor.php:25
- Duplicated block (16 lines × 2) src/Image/PoolProcessor.php:46
- Duplicated block (13 lines × 2) src/Image/PoolProcessor.php:32
- Unstable project src/Image
Minor β 5 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No changelog
Minor β 5 finding(s)
- Skipped (documented): testReadinessReflectsSourceAndCacheAvailability tests/v2/HttpTest.php:236
- Skipped (documented): testFailureDoesNotPublishAndReleasesResources tests/v2/PoolLifecycleTest.php:25
- Skipped (documented): testQueueCapacityDeadlineAndHardTimeoutRecover tests/v2/PoolQueueTest.php:22
- Skipped (documented): testLinuxParentDeathKillsBusyStoppedWorkerAndReleasesOwnership tests/v2/PoolRecoveryTest.php:158
- Skipped (documented): testOverBudgetWorkerFinishesItsJobAndIsRecycledOnlyWhileIdle tests/v2/PoolRecoveryTest.php:201
Appendix B β Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 Β· Secrets (history) | gitleaks | β | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cca69a4d5cf54a8b810438c0560f6896/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 Β· Secrets (history) | gitleaks | β | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cca69a4d5cf54a8b810438c0560f6896/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 . | 9 | artifacts/raw/semgrep.json |
| D30 Β· Dependency Vulnerabilities | osv-scanner | β | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 Β· IaC & Container Security | trivy | β | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 Β· Data Compliance (PII/GDPR) | semgrep | β | semgrep: not applicable β No personal data was found crossing a boundary the PII/GDPR ruleset checks β nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 17 file(s) β `src/Cache/DiskCache.php`, `src/Exception/ImageException.php`, `src/Http/Kernel.php`, `src/Http/Settings.php`, `src/Image/IsolatedProcessor.php`, β¦ (+12 more) β so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | β |
| D37 Β· Vulnerability-disclosure Policy | disclosure | β | disclosure: not applicable β No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | β |
| D40 Β· Network Egress Confinement | runtime-hardening | β | runtime-hardening: not applicable β No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | β |
| D41 Β· Kernel & Syscall Confinement | runtime-hardening | β | runtime-hardening: not applicable β No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | β |
| D42 Β· Runtime Threat Enforcement | runtime-hardening | β | runtime-hardening: not applicable β No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | β |
| D43 Β· Malicious Dependencies | osv-scanner | β | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |