Executive summary
Respect/Validation falls short of our standard for production because we found no logging, tracing or health checks in the code. It scores 58.8 out of 100 and is rated Adequate, and 24 of its 27 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Production Readiness, at 51.7, is the weakest lens and counts most in the score. The best first step is logging through a logging library, worth about 4.7 points. Recording design decisions comes next, worth about 4.4 points. Raising Production Readiness to 70 would lift the score to about 63.3.
Seventeen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, passing outside input through environment variables and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. 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 17,223 lines, about €44,000 to rebuild. Two of our security checks couldn't finish, among them the one for known security holes in its packages, so those results are missing, not clean passes.
If Production Readiness rose from 51.7 to 70, the lowest score rated Strong, the score would rise from 58.8 to about 63.3.
New since the last survey: 17 findings
- Code Duplication · Edited copy of a member (18 corresponding lines) src/Validators/All.php
- Code Duplication · Edited copy of a member (21 corresponding lines) src/Validators/Pesel.php
- Code Duplication · Edited copy of a member (10 corresponding lines) src/Validators/Contains.php
- Code Duplication · Edited copy of a member (13 corresponding lines) src/Validators/Image.php
- Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) src/Validators/CountryCode.php
- Code Duplication · Edited copy of a member (14 corresponding lines) src/ResultQuery.php
- Code Duplication · Edited copy of a member (10 corresponding lines) src/Validators/AllOf.php
- Code Duplication · Edited copy of a member (7 corresponding lines) src/Validators/Key.php
- Code Duplication · Edited copy of a member (6 corresponding lines) src/Validators/KeyOptional.php
- Code Duplication · Edited copy of a member (11 corresponding lines) src/Validators/EndsWith.php
- Code Duplication · Edited copy of a member (10 corresponding lines) src/Validators/UndefOr.php
- Code Duplication · Edited copy of a member (8 corresponding lines) src/Validators/Between.php
- Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) src/Validators/Date.php
- Code Duplication · Edited copy of a member (9 corresponding lines) src/Validators/Base64.php
- Code Duplication · Edited copy of a member (6 corresponding lines) src/Validators/Max.php
- Coupling · Circular dependency src/FluentValidatorFactory.php
- Test isolation · Production project references a test project: src-dev → tests src-dev/Commands/SmokeTestsCheckCompleteCommand.php
Fixed since the last survey: 2 findings
- Code Duplication · Duplicated block (26 lines × 2) src-dev/Spdx/HeaderRebuilder/HtmlHeaderRebuilder.php
- Documentation (README) · README may be stale
Rebuild cost: about €44,000 · Estimate
| Cost to rebuild | €15,000 to €73,000, for 242 to 769 hours of work, about 0.3 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.8 at a score of 59. 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: 17,223 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 Dev.Differ | 2 Dev.Helpers | 3 Dev.Markdown | 4 Dev.Spdx | 5 Dev.Spdx.ContributorExtractor | 6 Dev.Spdx.HeaderRebuilder | 7 Validation.Transformers | 8 Dev.Commands | 9 Dev.Markdown.Linters | 10 Validation.Message.Formatter | 11 Validation.Validators.Core | 12 Validation.Message | 13 Validation | 14 Validation.Exceptions | 15 Validation.Helpers | 16 Validation.Message.Parameters | 17 Validation.Mixins | 18 Validation.Validators |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Dev.Differ | ||||||||||||||||||
| 2 Dev.Helpers | ||||||||||||||||||
| 3 Dev.Markdown | ||||||||||||||||||
| 4 Dev.Spdx | ||||||||||||||||||
| 5 Dev.Spdx.ContributorExtractor | ||||||||||||||||||
| 6 Dev.Spdx.HeaderRebuilder | ||||||||||||||||||
| 7 Validation.Transformers | ||||||||||||||||||
| 8 Dev.Commands | 3 | 3 | 1 | 2 | 2 | |||||||||||||
| 9 Dev.Markdown.Linters | 13 | |||||||||||||||||
| 10 Validation.Message.Formatter | 7 | 5 | ||||||||||||||||
| 11 Validation.Validators.Core | 17 | |||||||||||||||||
| 12 Validation.Message | 1 | 4 | ||||||||||||||||
| 13 Validation | 2 | 2 | 6 | |||||||||||||||
| 14 Validation.Exceptions | 1 | |||||||||||||||||
| 15 Validation.Helpers | 2 | |||||||||||||||||
| 16 Validation.Message.Parameters | 1 | |||||||||||||||||
| 17 Validation.Mixins | 14 | |||||||||||||||||
| 18 Validation.Validators | 113 | 126 |
8→1 Dev.Commands uses Dev.Differ✕
- Connections
- 3 pairs of types, where a type in Dev.Commands uses a type in Dev.Differ.
- The types involved
Respect.Dev.Commands.LintDocsCommand→Respect.Dev.Differ.ConsoleDifferRespect.Dev.Commands.LintMixinCommand→Respect.Dev.Differ.ConsoleDifferRespect.Dev.Commands.LintSpdxCommand→Respect.Dev.Differ.ConsoleDiffer
- Direction
- Dev.Commands uses Dev.Differ, so a change to Dev.Differ can break Dev.Commands, while a change to Dev.Commands can't break Dev.Differ.
- Position
- Below the diagonal: Dev.Commands uses a module listed above it, which is the healthy direction.
8→2 Dev.Commands uses Dev.Helpers✕
- Connections
- 3 pairs of types, where a type in Dev.Commands uses a type in Dev.Helpers.
- The types involved
Respect.Dev.Commands.UpdateDomainSuffixesCommand→Respect.Dev.Helpers.DataSaverRespect.Dev.Commands.UpdateDomainToplevelCommand→Respect.Dev.Helpers.DataSaverRespect.Dev.Commands.UpdatePostalCodesCommand→Respect.Dev.Helpers.DataSaver
- Direction
- Dev.Commands uses Dev.Helpers, so a change to Dev.Helpers can break Dev.Commands, while a change to Dev.Commands can't break Dev.Helpers.
- Position
- Below the diagonal: Dev.Commands uses a module listed above it, which is the healthy direction.
8→3 Dev.Commands uses Dev.Markdown✕
- Connections
- 1 pair of types, where a type in Dev.Commands uses a type in Dev.Markdown.
- The types involved
Respect.Dev.Commands.LintDocsCommand→Respect.Dev.Markdown.Linter
- Direction
- Dev.Commands uses Dev.Markdown, so a change to Dev.Markdown can break Dev.Commands, while a change to Dev.Commands can't break Dev.Markdown.
- Position
- Below the diagonal: Dev.Commands uses a module listed above it, which is the healthy direction.
8→5 Dev.Commands uses Dev.Spdx.ContributorExtractor✕
- Connections
- 2 pairs of types, where a type in Dev.Commands uses a type in Dev.Spdx.ContributorExtractor.
- The types involved
Respect.Dev.Commands.LintSpdxCommand→Respect.Dev.Spdx.ContributorExtractor.GitBlameContributorExtractorRespect.Dev.Commands.LintSpdxCommand→Respect.Dev.Spdx.ContributorExtractor.GitLogContributorExtractor
- Direction
- Dev.Commands uses Dev.Spdx.ContributorExtractor, so a change to Dev.Spdx.ContributorExtractor can break Dev.Commands, while a change to Dev.Commands can't break Dev.Spdx.ContributorExtractor.
- Position
- Below the diagonal: Dev.Commands uses a module listed above it, which is the healthy direction.
8→6 Dev.Commands uses Dev.Spdx.HeaderRebuilder✕
- Connections
- 2 pairs of types, where a type in Dev.Commands uses a type in Dev.Spdx.HeaderRebuilder.
- The types involved
Respect.Dev.Commands.LintSpdxCommand→Respect.Dev.Spdx.HeaderRebuilder.HtmlHeaderRebuilderRespect.Dev.Commands.LintSpdxCommand→Respect.Dev.Spdx.HeaderRebuilder.PhpHeaderRebuilder
- Direction
- Dev.Commands uses Dev.Spdx.HeaderRebuilder, so a change to Dev.Spdx.HeaderRebuilder can break Dev.Commands, while a change to Dev.Commands can't break Dev.Spdx.HeaderRebuilder.
- Position
- Below the diagonal: Dev.Commands uses a module listed above it, which is the healthy direction.
9→3 Dev.Markdown.Linters uses Dev.Markdown✕
- Connections
- 13 pairs of types, where a type in Dev.Markdown.Linters uses a type in Dev.Markdown.
- The types involved
Respect.Dev.Markdown.Linters.AssertionMessageLinter→Respect.Dev.Markdown.ContentRespect.Dev.Markdown.Linters.AssertionMessageLinter→Respect.Dev.Markdown.FileRespect.Dev.Markdown.Linters.AssertionMessageLinter→Respect.Dev.Markdown.LinterRespect.Dev.Markdown.Linters.ValidatorChangelogLinter→Respect.Dev.Markdown.FileRespect.Dev.Markdown.Linters.ValidatorChangelogLinter→Respect.Dev.Markdown.LinterRespect.Dev.Markdown.Linters.ValidatorHeaderLinter→Respect.Dev.Markdown.FileRespect.Dev.Markdown.Linters.ValidatorHeaderLinter→Respect.Dev.Markdown.LinterRespect.Dev.Markdown.Linters.ValidatorIndexLinter→Respect.Dev.Markdown.FileRespect.Dev.Markdown.Linters.ValidatorIndexLinter→Respect.Dev.Markdown.LinterRespect.Dev.Markdown.Linters.ValidatorRelatedLinter→Respect.Dev.Markdown.FileRespect.Dev.Markdown.Linters.ValidatorRelatedLinter→Respect.Dev.Markdown.LinterRespect.Dev.Markdown.Linters.ValidatorTemplatesLinter→Respect.Dev.Markdown.FileRespect.Dev.Markdown.Linters.ValidatorTemplatesLinter→Respect.Dev.Markdown.Linter
- Direction
- Dev.Markdown.Linters uses Dev.Markdown, so a change to Dev.Markdown can break Dev.Markdown.Linters, while a change to Dev.Markdown.Linters can't break Dev.Markdown.
- Position
- Below the diagonal: Dev.Markdown.Linters uses a module listed above it, which is the healthy direction.
10→12 Validation.Message.Formatter uses Validation.Message part of a loop✕
- Connections
- 7 pairs of types, where a type in Validation.Message.Formatter uses a type in Validation.Message.
- The types involved
Respect.Validation.Message.Formatter.FirstResultStringFormatter→Respect.Validation.Message.RendererRespect.Validation.Message.Formatter.FirstResultStringFormatter→Respect.Validation.Message.StringFormatterRespect.Validation.Message.Formatter.NestedArrayFormatter→Respect.Validation.Message.ArrayFormatterRespect.Validation.Message.Formatter.NestedArrayFormatter→Respect.Validation.Message.RendererRespect.Validation.Message.Formatter.NestedListStringFormatter→Respect.Validation.Message.RendererRespect.Validation.Message.Formatter.NestedListStringFormatter→Respect.Validation.Message.StringFormatterRespect.Validation.Message.Formatter.TemplateResolver→Respect.Validation.Message.TemplateRegistry
- Direction
- Validation.Message.Formatter uses Validation.Message, so a change to Validation.Message can break Validation.Message.Formatter, while a change to Validation.Message.Formatter can't break Validation.Message.
- 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.
10→13 Validation.Message.Formatter uses Validation part of a loop✕
- Connections
- 5 pairs of types, where a type in Validation.Message.Formatter uses a type in Validation.
- The types involved
Respect.Validation.Message.Formatter.FirstResultStringFormatter→Respect.Validation.ResultRespect.Validation.Message.Formatter.NestedArrayFormatter→Respect.Validation.ResultRespect.Validation.Message.Formatter.NestedListStringFormatter→Respect.Validation.ResultRespect.Validation.Message.Formatter.TemplateResolver→Respect.Validation.PathRespect.Validation.Message.Formatter.TemplateResolver→Respect.Validation.Result
- Direction
- Validation.Message.Formatter uses Validation, so a change to Validation can break Validation.Message.Formatter, while a change to Validation.Message.Formatter can't break Validation.
- 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.
11→13 Validation.Validators.Core uses Validation part of a loop✕
- Connections
- 17 pairs of types, where a type in Validation.Validators.Core uses a type in Validation.
- The types involved
Respect.Validation.Validators.Core.Comparison→Respect.Validation.ResultRespect.Validation.Validators.Core.Comparison→Respect.Validation.ValidatorRespect.Validation.Validators.Core.Envelope→Respect.Validation.ResultRespect.Validation.Validators.Core.Envelope→Respect.Validation.ValidatorRespect.Validation.Validators.Core.FilteredArray→Respect.Validation.ResultRespect.Validation.Validators.Core.FilteredArray→Respect.Validation.ValidatorRespect.Validation.Validators.Core.FilteredString→Respect.Validation.ResultRespect.Validation.Validators.Core.FilteredString→Respect.Validation.ValidatorRespect.Validation.Validators.Core.KeyRelated→Respect.Validation.ValidatorRespect.Validation.Validators.Core.LogicalComposite→Respect.Validation.ValidatorRespect.Validation.Validators.Core.Nameable→Respect.Validation.ValidatorRespect.Validation.Validators.Core.Reducer→Respect.Validation.ResultRespect.Validation.Validators.Core.Reducer→Respect.Validation.ValidatorRespect.Validation.Validators.Core.ShortCircuitable→Respect.Validation.ResultRespect.Validation.Validators.Core.ShortCircuitable→Respect.Validation.ValidatorRespect.Validation.Validators.Core.Simple→Respect.Validation.ResultRespect.Validation.Validators.Core.Simple→Respect.Validation.Validator
- Direction
- Validation.Validators.Core uses Validation, so a change to Validation can break Validation.Validators.Core, while a change to Validation.Validators.Core can't break Validation.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→10 Validation.Message uses Validation.Message.Formatter✕
- Connections
- 1 pair of types, where a type in Validation.Message uses a type in Validation.Message.Formatter.
- The types involved
Respect.Validation.Message.InterpolationRenderer→Respect.Validation.Message.Formatter.TemplateResolver
- Direction
- Validation.Message uses Validation.Message.Formatter, so a change to Validation.Message.Formatter can break Validation.Message, while a change to Validation.Message can't break Validation.Message.Formatter.
- Position
- Below the diagonal: Validation.Message uses a module listed above it, which is the healthy direction.
12→13 Validation.Message uses Validation part of a loop✕
- Connections
- 4 pairs of types, where a type in Validation.Message uses a type in Validation.
- The types involved
Respect.Validation.Message.ArrayFormatter→Respect.Validation.ResultRespect.Validation.Message.InterpolationRenderer→Respect.Validation.ResultRespect.Validation.Message.Renderer→Respect.Validation.ResultRespect.Validation.Message.StringFormatter→Respect.Validation.Result
- Direction
- Validation.Message uses Validation, so a change to Validation can break Validation.Message, while a change to Validation.Message can't break Validation.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→7 Validation uses Validation.Transformers✕
- Connections
- 2 pairs of types, where a type in Validation uses a type in Validation.Transformers.
- The types involved
Respect.Validation.NamespacedValidatorFactory→Respect.Validation.Transformers.TransformerRespect.Validation.NamespacedValidatorFactory→Respect.Validation.Transformers.ValidatorSpec
- Direction
- Validation uses Validation.Transformers, so a change to Validation.Transformers can break Validation, while a change to Validation can't break Validation.Transformers.
- Position
- Below the diagonal: Validation uses a module listed above it, which is the healthy direction.
13→11 Validation uses Validation.Validators.Core✕
- Connections
- 2 pairs of types, where a type in Validation uses a type in Validation.Validators.Core.
- The types involved
Respect.Validation.ValidatorBuilder→Respect.Validation.Validators.Core.NameableRespect.Validation.ValidatorBuilder→Respect.Validation.Validators.Core.ShortCircuitable
- Direction
- Validation uses Validation.Validators.Core, so a change to Validation.Validators.Core can break Validation, while a change to Validation can't break Validation.Validators.Core.
- Position
- Below the diagonal: Validation uses a module listed above it, which is the healthy direction.
13→12 Validation uses Validation.Message✕
- Connections
- 6 pairs of types, where a type in Validation uses a type in Validation.Message.
- The types involved
Respect.Validation.ResultQuery→Respect.Validation.Message.ArrayFormatterRespect.Validation.ResultQuery→Respect.Validation.Message.RendererRespect.Validation.ResultQuery→Respect.Validation.Message.StringFormatterRespect.Validation.ValidatorBuilder→Respect.Validation.Message.ArrayFormatterRespect.Validation.ValidatorBuilder→Respect.Validation.Message.RendererRespect.Validation.ValidatorBuilder→Respect.Validation.Message.StringFormatter
- Direction
- Validation uses Validation.Message, so a change to Validation.Message can break Validation, while a change to Validation can't break Validation.Message.
- Position
- Below the diagonal: Validation uses a module listed above it, which is the healthy direction.
14→13 Validation.Exceptions uses Validation✕
- Connections
- 1 pair of types, where a type in Validation.Exceptions uses a type in Validation.
- The types involved
Respect.Validation.Exceptions.ValidationException→Respect.Validation.ResultQuery
- Direction
- Validation.Exceptions uses Validation, so a change to Validation can break Validation.Exceptions, while a change to Validation.Exceptions can't break Validation.
- Position
- Below the diagonal: Validation.Exceptions uses a module listed above it, which is the healthy direction.
15→13 Validation.Helpers uses Validation✕
- Connections
- 2 pairs of types, where a type in Validation.Helpers uses a type in Validation.
- The types involved
Respect.Validation.Helpers.CanEvaluateShortCircuit→Respect.Validation.ResultRespect.Validation.Helpers.CanEvaluateShortCircuit→Respect.Validation.Validator
- Direction
- Validation.Helpers uses Validation, so a change to Validation can break Validation.Helpers, while a change to Validation.Helpers can't break Validation.
- Position
- Below the diagonal: Validation.Helpers uses a module listed above it, which is the healthy direction.
16→13 Validation.Message.Parameters uses Validation✕
- Connections
- 1 pair of types, where a type in Validation.Message.Parameters uses a type in Validation.
- The types involved
Respect.Validation.Message.Parameters.PathHandler→Respect.Validation.Path
- Direction
- Validation.Message.Parameters uses Validation, so a change to Validation can break Validation.Message.Parameters, while a change to Validation.Message.Parameters can't break Validation.
- Position
- Below the diagonal: Validation.Message.Parameters uses a module listed above it, which is the healthy direction.
17→13 Validation.Mixins uses Validation✕
- Connections
- 14 pairs of types, where a type in Validation.Mixins uses a type in Validation.
- The types involved
Respect.Validation.Mixins.AllBuilder→Respect.Validation.ValidatorRespect.Validation.Mixins.AllChain→Respect.Validation.ValidatorRespect.Validation.Mixins.Builder→Respect.Validation.ValidatorRespect.Validation.Mixins.Chain→Respect.Validation.ValidatorRespect.Validation.Mixins.KeyBuilder→Respect.Validation.ValidatorRespect.Validation.Mixins.KeyChain→Respect.Validation.ValidatorRespect.Validation.Mixins.NotBuilder→Respect.Validation.ValidatorRespect.Validation.Mixins.NotChain→Respect.Validation.ValidatorRespect.Validation.Mixins.NullOrBuilder→Respect.Validation.ValidatorRespect.Validation.Mixins.NullOrChain→Respect.Validation.ValidatorRespect.Validation.Mixins.PropertyBuilder→Respect.Validation.ValidatorRespect.Validation.Mixins.PropertyChain→Respect.Validation.ValidatorRespect.Validation.Mixins.UndefOrBuilder→Respect.Validation.ValidatorRespect.Validation.Mixins.UndefOrChain→Respect.Validation.Validator
- Direction
- Validation.Mixins uses Validation, so a change to Validation can break Validation.Mixins, while a change to Validation.Mixins can't break Validation.
- Position
- Below the diagonal: Validation.Mixins uses a module listed above it, which is the healthy direction.
18→11 Validation.Validators uses Validation.Validators.Core✕
- Connections
- 113 pairs of types, where a type in Validation.Validators uses a type in Validation.Validators.Core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Respect.Validation.Validators.All→Respect.Validation.Validators.Core.FilteredArrayRespect.Validation.Validators.All→Respect.Validation.Validators.Core.ShortCircuitableRespect.Validation.Validators.AllOf→Respect.Validation.Validators.Core.LogicalCompositeRespect.Validation.Validators.AllOf→Respect.Validation.Validators.Core.ShortCircuitableRespect.Validation.Validators.Alnum→Respect.Validation.Validators.Core.FilteredStringRespect.Validation.Validators.Alpha→Respect.Validation.Validators.Core.FilteredStringRespect.Validation.Validators.AlwaysInvalid→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.AlwaysValid→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.AnyOf→Respect.Validation.Validators.Core.LogicalCompositeRespect.Validation.Validators.AnyOf→Respect.Validation.Validators.Core.ShortCircuitableRespect.Validation.Validators.ArrayType→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.ArrayVal→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.Base64→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.Between→Respect.Validation.Validators.Core.EnvelopeRespect.Validation.Validators.BetweenExclusive→Respect.Validation.Validators.Core.EnvelopeRespect.Validation.Validators.BoolType→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.BoolVal→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.Bsn→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.CallableType→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.Cnh→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.Cnpj→Respect.Validation.Validators.Core.SimpleRespect.Validation.Validators.Consonant→Respect.Validation.Validators.Core.FilteredStringRespect.Validation.Validators.ContainsAny→Respect.Validation.Validators.Core.EnvelopeRespect.Validation.Validators.Control→Respect.Validation.Validators.Core.FilteredStringRespect.Validation.Validators.Countable→Respect.Validation.Validators.Core.Simple
- Direction
- Validation.Validators uses Validation.Validators.Core, so a change to Validation.Validators.Core can break Validation.Validators, while a change to Validation.Validators can't break Validation.Validators.Core.
- Position
- Below the diagonal: Validation.Validators uses a module listed above it, which is the healthy direction.
18→13 Validation.Validators uses Validation✕
- Connections
- 126 pairs of types, where a type in Validation.Validators uses a type in Validation. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Respect.Validation.Validators.After→Respect.Validation.ResultRespect.Validation.Validators.After→Respect.Validation.ValidatorRespect.Validation.Validators.All→Respect.Validation.ResultRespect.Validation.Validators.AllOf→Respect.Validation.ResultRespect.Validation.Validators.AnyOf→Respect.Validation.ResultRespect.Validation.Validators.Attributes→Respect.Validation.ResultRespect.Validation.Validators.Attributes→Respect.Validation.ValidatorRespect.Validation.Validators.Base→Respect.Validation.ResultRespect.Validation.Validators.Base→Respect.Validation.ValidatorRespect.Validation.Validators.Blank→Respect.Validation.ResultRespect.Validation.Validators.Blank→Respect.Validation.ValidatorRespect.Validation.Validators.Charset→Respect.Validation.ResultRespect.Validation.Validators.Charset→Respect.Validation.ValidatorRespect.Validation.Validators.Contains→Respect.Validation.ResultRespect.Validation.Validators.Contains→Respect.Validation.ValidatorRespect.Validation.Validators.ContainsCount→Respect.Validation.ResultRespect.Validation.Validators.ContainsCount→Respect.Validation.ValidatorRespect.Validation.Validators.CountryCode→Respect.Validation.ResultRespect.Validation.Validators.CountryCode→Respect.Validation.ValidatorRespect.Validation.Validators.CreditCard→Respect.Validation.ResultRespect.Validation.Validators.CreditCard→Respect.Validation.ValidatorRespect.Validation.Validators.CurrencyCode→Respect.Validation.ResultRespect.Validation.Validators.CurrencyCode→Respect.Validation.ValidatorRespect.Validation.Validators.Date→Respect.Validation.ResultRespect.Validation.Validators.Date→Respect.Validation.Validator
- Direction
- Validation.Validators uses Validation, so a change to Validation can break Validation.Validators, while a change to Validation.Validators can't break Validation.
- Position
- Below the diagonal: Validation.Validators uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 24 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
Roadmap
Top priorities: Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run; 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; Resolve the 22 Orphaned file finding(s) in Knowledge Freshness — start with AssertionMessageLinter.php, Content.php, ValidatorBuilder.php.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run. | +4.7 pts | Medium | Observability |
| 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. | +4.4 pts | Medium | Architecture documentation |
| Resolve the 22 Orphaned file finding(s) in Knowledge Freshness — start with AssertionMessageLinter.php, Content.php, ValidatorBuilder.php. | +3.0 pts | Medium | Knowledge Freshness |
| Expand the README with getting-started, architecture overview and a project map. | +2.7 pts | Medium | Documentation (README) |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.2 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.2 pts | Medium | Release Hygiene |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. | +0.9 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Circular dependency finding(s) in Coupling — start with FluentValidatorFactory.php. | +0.8 pts | Low | Coupling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Validators/AllOf.php | 7.0 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
| src/Validators/Key.php | 7.0 | Mixed | Code Duplication: Edited copy of a member (7 corresponding lines) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src-dev/Markdown/Linters/AssertionMessageLinter.php | 7.8 | Mixed | Cyclomatic Complexity: AssertionMessageLinter.processCode (cyclomatic 19) |
| src-dev/Commands/UpdateDomainSuffixesCommand.php | 7.8 | Mixed | Cognitive Complexity: UpdateDomainSuffixesCommand.parseTldsList (cognitive 17) |
| src/Validators/All.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (18 corresponding lines) |
| src/Validators/EndsWith.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (11 corresponding lines) |
| src/Validators/Date.php | 7.8 | Mixed | Code Duplication: Edited copies of one member (4 members, 6+ corresponding lines) |
| src-dev/Commands/LintDocsCommand.php | 7.8 | Mixed | Code Duplication: Duplicated block (12 lines × 2) |
| src/FluentValidatorFactory.php | 8.0 | Near-clean | Coupling: Circular dependency |
| src/Validators/PortugueseNif.php | 8.5 | Near-clean | Cyclomatic Complexity: PortugueseNif.isValid (cyclomatic 22) |
| src/Validators/Attributes.php | 8.5 | Near-clean | Cognitive Complexity: Attributes.containsSelf (cognitive 20) |
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 44 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 — 44 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, 108 of 119 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its Composer package dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — 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.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (12625 LoC, 260 module-visible types across 18 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D30 Dependency Vulnerabilities — 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. Osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 1 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the 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-dev/Commands/LintDocsCommand.php`, `src-dev/Commands/LintMixinCommand.php`, `src-dev/Commands/LintSpdxCommand.php`, `src-dev/Commands/UpdateDomainSuffixesCommand.php`, `src-dev/Commands/UpdateDomainToplevelCommand.php`, … (+110 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.
- D43 Malicious 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. Osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 1 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
- 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 a PSR-11 container (Psr\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.
- 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.
- 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, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java 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, Java, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, 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.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PortugueseNif.isValid at 22.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PortugueseNif.isValid (cyclomatic 22), AssertionMessageLinter.processCode (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was AssertionMessageLinter.processCode at 44.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with AssertionMessageLinter.processCode (cognitive 44), Attributes.containsSelf (cognitive 20), UpdateDomainSuffixesCommand.parseTldsList (cognitive 17). — 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 3 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
10 duplicated block group(s) detected. 2.5 % of the production lines (439 of 17,223) are in a reported copy. A further 15 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with Contains.php, AllOf.php, UndefOr.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with KeyOptional.php, Max.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with Content.php, EndsWith.php. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
9 production modules (source-import), 1 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence, with abstractness counted on 7 of the 9 (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 1 Circular dependency finding(s) in Coupling — start with FluentValidatorFactory.php. — One of this dimension's main actionable groups (1 issue-level).
D6 · Cohesion (LCOM4)
0 of 49 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 348 tests.
D12 · Dependency Hygiene
2 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 10 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 89 package(s) under `packages-dev` are not installed for a consumer and are excluded. ★ COVERAGE OF THIS VERDICT: it grades this repository's Composer package dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/ResultQuery.php. Counted over 49 of the 240 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 17223 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D27 · Navigability
38 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
24 finding(s): 0 critical, 24 high, 0 medium, 0 low. 14 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 116 file(s) — `src-dev/Commands/LintDocsCommand.php` (line 35, line 36), `src-dev/Commands/LintMixinCommand.php` (line 46, line 85), `src-dev/Commands/LintSpdxCommand.php` (line 48, line 52, line 60, …), `src-dev/Commands/SmokeTestsCheckCompleteCommand.php` (line 51), `src-dev/Commands/UpdateDomainSuffixesCommand.php` (line 50, line 53), … (+111 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 REDACTED finding(s) charged to Static Analysis (SAST) — the other 14 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (17 issue-level, 3 of them charged here).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
22 of 49 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src-dev/Markdown/Linters/AssertionMessageLinter.php. Counted over 49 of the 240 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 22 Orphaned file finding(s) in Knowledge Freshness — start with AssertionMessageLinter.php, Content.php, ValidatorBuilder.php. — One of this dimension's main actionable groups (22 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: AllOf.php↔AnyOf.php 80%; AllOf.php↔NoneOf.php 77%; Key.php↔Property.php 73%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with Key.php, Alnum.php, DateTime.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with AllOf.php. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (.github/SECURITY.md) is published with a reporting contact.
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
- The projects src → src/Exceptions → src (one cycle inside a mutually-dependent group of 5 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — src/FluentValidatorFactory.php:17
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
- `AllChain` declares 144 methods: `allAfter`, `allAllOf`, `allAlnum`, `allAlpha`, `allAlwaysInvalid`, `allAlwaysValid`, `allAnyOf`, `allArrayType`, `allArrayVal`, `allBase`, `allBase64`, `allBetween`, `allBetweenExclusive`, `allBlank`, `allBoolType`, `allBoolVal`, `allBsn`, `allCallableType`, `allCharset`, `allCnh`, `allCnpj`, `allConsonant`, `allContains`, `allContainsAny`, `allContainsCount`, `allControl`, `allCountable`, `allCountryCode`, `allCpf`, `allCreditCard`, `allCurrencyCode`, `allDate`, `allDateTime`, `allDateTimeDiff`, `allDecimal`, `allDigit`, `allDirectory`, `allDomain`, `allEach`, `allEachKey`, and 104 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. — src/Mixins/AllChain.php:18
- `Chain` declares 162 methods: `after`, `all`, `allOf`, `alnum`, `alpha`, `alwaysInvalid`, `alwaysValid`, `anyOf`, `arrayType`, `arrayVal`, `attributes`, `base`, `base64`, `between`, `betweenExclusive`, `blank`, `boolType`, `boolVal`, `bsn`, `callableType`, `charset`, `cnh`, `cnpj`, `consonant`, `contains`, `containsAny`, `containsCount`, `control`, `countable`, `countryCode`, `cpf`, `creditCard`, `currencyCode`, `date`, `dateTime`, `dateTimeDiff`, `decimal`, `digit`, `directory`, `domain`, and 122 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. — src/Mixins/Chain.php:24
- `KeyChain` declares 145 methods: `keyAfter`, `keyAll`, `keyAllOf`, `keyAlnum`, `keyAlpha`, `keyAlwaysInvalid`, `keyAlwaysValid`, `keyAnyOf`, `keyArrayType`, `keyArrayVal`, `keyBase`, `keyBase64`, `keyBetween`, `keyBetweenExclusive`, `keyBlank`, `keyBoolType`, `keyBoolVal`, `keyBsn`, `keyCallableType`, `keyCharset`, `keyCnh`, `keyCnpj`, `keyConsonant`, `keyContains`, `keyContainsAny`, `keyContainsCount`, `keyControl`, `keyCountable`, `keyCountryCode`, `keyCpf`, `keyCreditCard`, `keyCurrencyCode`, `keyDate`, `keyDateTime`, `keyDateTimeDiff`, `keyDecimal`, `keyDigit`, `keyDirectory`, `keyDomain`, `keyEach`, and 105 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. — src/Mixins/KeyChain.php:18
- `LengthChain` declares 17 methods: `lengthBetween`, `lengthBetweenExclusive`, `lengthEquals`, `lengthEquivalent`, `lengthEven`, `lengthFactor`, `lengthFinite`, `lengthGreaterThan`, `lengthGreaterThanOrEqual`, `lengthIdentical`, `lengthIn`, `lengthInfinite`, `lengthLessThan`, `lengthLessThanOrEqual`, `lengthMultiple`, `lengthOdd`, `lengthPositive`. 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. — src/Mixins/LengthChain.php:14
- `MaxChain` declares 17 methods: `maxBetween`, `maxBetweenExclusive`, `maxEquals`, `maxEquivalent`, `maxEven`, `maxFactor`, `maxFinite`, `maxGreaterThan`, `maxGreaterThanOrEqual`, `maxIdentical`, `maxIn`, `maxInfinite`, `maxLessThan`, `maxLessThanOrEqual`, `maxMultiple`, `maxOdd`, `maxPositive`. 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. — src/Mixins/MaxChain.php:14
- `MinChain` declares 17 methods: `minBetween`, `minBetweenExclusive`, `minEquals`, `minEquivalent`, `minEven`, `minFactor`, `minFinite`, `minGreaterThan`, `minGreaterThanOrEqual`, `minIdentical`, `minIn`, `minInfinite`, `minLessThan`, `minLessThanOrEqual`, `minMultiple`, `minOdd`, `minPositive`. 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. — src/Mixins/MinChain.php:14
- `NotChain` declares 153 methods: `notAfter`, `notAll`, `notAllOf`, `notAlnum`, `notAlpha`, `notAlwaysInvalid`, `notAlwaysValid`, `notAnyOf`, `notArrayType`, `notArrayVal`, `notBase`, `notBase64`, `notBetween`, `notBetweenExclusive`, `notBlank`, `notBoolType`, `notBoolVal`, `notBsn`, `notCallableType`, `notCharset`, `notCnh`, `notCnpj`, `notConsonant`, `notContains`, `notContainsAny`, `notContainsCount`, `notControl`, `notCountable`, `notCountryCode`, `notCpf`, `notCreditCard`, `notCurrencyCode`, `notDate`, `notDateTime`, `notDateTimeDiff`, `notDecimal`, `notDigit`, `notDirectory`, `notDomain`, `notEach`, and 113 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. — src/Mixins/NotChain.php:18
- `NullOrChain` declares 153 methods: `nullOrAfter`, `nullOrAll`, `nullOrAllOf`, `nullOrAlnum`, `nullOrAlpha`, `nullOrAlwaysInvalid`, `nullOrAlwaysValid`, `nullOrAnyOf`, `nullOrArrayType`, `nullOrArrayVal`, `nullOrAttributes`, `nullOrBase`, `nullOrBase64`, `nullOrBetween`, `nullOrBetweenExclusive`, `nullOrBoolType`, `nullOrBoolVal`, `nullOrBsn`, `nullOrCallableType`, `nullOrCharset`, `nullOrCnh`, `nullOrCnpj`, `nullOrConsonant`, `nullOrContains`, `nullOrContainsAny`, `nullOrContainsCount`, `nullOrControl`, `nullOrCountable`, `nullOrCountryCode`, `nullOrCpf`, `nullOrCreditCard`, `nullOrCurrencyCode`, `nullOrDate`, `nullOrDateTime`, `nullOrDateTimeDiff`, `nullOrDecimal`, `nullOrDigit`, `nullOrDirectory`, `nullOrDomain`, `nullOrEach`, and 113 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. — src/Mixins/NullOrChain.php:18
- `PropertyChain` declares 145 methods: `propertyAfter`, `propertyAll`, `propertyAllOf`, `propertyAlnum`, `propertyAlpha`, `propertyAlwaysInvalid`, `propertyAlwaysValid`, `propertyAnyOf`, `propertyArrayType`, `propertyArrayVal`, `propertyBase`, `propertyBase64`, `propertyBetween`, `propertyBetweenExclusive`, `propertyBlank`, `propertyBoolType`, `propertyBoolVal`, `propertyBsn`, `propertyCallableType`, `propertyCharset`, `propertyCnh`, `propertyCnpj`, `propertyConsonant`, `propertyContains`, `propertyContainsAny`, `propertyContainsCount`, `propertyControl`, `propertyCountable`, `propertyCountryCode`, `propertyCpf`, `propertyCreditCard`, `propertyCurrencyCode`, `propertyDate`, `propertyDateTime`, `propertyDateTimeDiff`, `propertyDecimal`, `propertyDigit`, `propertyDirectory`, `propertyDomain`, `propertyEach`, and 105 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. — src/Mixins/PropertyChain.php:18
- `UndefOrChain` declares 152 methods: `undefOrAfter`, `undefOrAll`, `undefOrAllOf`, `undefOrAlnum`, `undefOrAlpha`, `undefOrAlwaysInvalid`, `undefOrAlwaysValid`, `undefOrAnyOf`, `undefOrArrayType`, `undefOrArrayVal`, `undefOrBase`, `undefOrBase64`, `undefOrBetween`, `undefOrBetweenExclusive`, `undefOrBoolType`, `undefOrBoolVal`, `undefOrBsn`, `undefOrCallableType`, `undefOrCharset`, `undefOrCnh`, `undefOrCnpj`, `undefOrConsonant`, `undefOrContains`, `undefOrContainsAny`, `undefOrContainsCount`, `undefOrControl`, `undefOrCountable`, `undefOrCountryCode`, `undefOrCpf`, `undefOrCreditCard`, `undefOrCurrencyCode`, `undefOrDate`, `undefOrDateTime`, `undefOrDateTimeDiff`, `undefOrDecimal`, `undefOrDigit`, `undefOrDirectory`, `undefOrDomain`, `undefOrEach`, `undefOrEachKey`, and 112 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. — src/Mixins/UndefOrChain.php:18
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
- `src-dev` (production) references the test project `tests`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — src-dev/Commands/SmokeTestsCheckCompleteCommand.php:14
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
M1 · Documentation (README)
- The root README is 56 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 562 PHP production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (PHP: PSR-3 loggers (Monolog), Laravel's Log facade, error_log()) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run.
- Add a health-check endpoint (Laravel's /up health route or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — REDACTED:11
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.
PF1 · Benchmark discipline
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — src/Validators/DateTimeDiff.php:137, src/Helpers/CanCompareValues.php:43
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81.1 | Strong | Solid. |
| Architecture | 81.3 | Adequate — gated by D5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 54.6 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 51.7 | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 63.5 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — D19 withholds "Documentation: empty section": 7 candidate(s) were measured and not published.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — 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 — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Scanner failed to run — not a clean result
- 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) — 115 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Scanner failed to run — not a clean result
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (62 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
- M4 Documentation accuracy — Not applicable: the 177 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — 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.
- 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
- 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
- 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
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not 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.
- 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.
- 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 — 27 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
- Project dependency cycle src/FluentValidatorFactory.php:17
- Production project references a test project: src-dev → tests src-dev/Commands/SmokeTestsCheckCompleteCommand.php:14
- REDACTED
- Circular dependency src/FluentValidatorFactory.php:17
Serious — 42 finding(s)
- Change coupling: Key.php ↔ Property.php src/Validators/Key.php:1
- Change coupling: Alnum.php ↔ Alpha.php src/Validators/Alnum.php:1
- Change coupling: DateTime.php ↔ Ip.php src/Validators/DateTime.php:1
- Edited copy of a member (10 corresponding lines) src/Validators/Contains.php:43
- Edited copy of a member (10 corresponding lines) src/Validators/AllOf.php:63
- Edited copy of a member (10 corresponding lines) src/Validators/UndefOr.php:49
- REDACTED
- REDACTED
- Edited copy of a member (6 corresponding lines) src/Validators/KeyOptional.php:38
- Edited copy of a member (6 corresponding lines) src/Validators/Max.php:38
- Duplicated block (11 lines × 2) src-dev/Markdown/Content.php:168
- Duplicated block (11 lines × 2) src/Validators/EndsWith.php:58
- Swallowed exception (caught, then discarded) src/Validators/DateTimeDiff.php:137
- Swallowed exception (caught, then discarded) src/Helpers/CanCompareValues.php:43
- PortugueseNif.isValid (cyclomatic 22) src/Validators/PortugueseNif.php:39
- AssertionMessageLinter.processCode (cyclomatic 19) src-dev/Markdown/Linters/AssertionMessageLinter.php:134
- AssertionMessageLinter.processCode (cognitive 44) src-dev/Markdown/Linters/AssertionMessageLinter.php:134
- Attributes.containsSelf (cognitive 20) src/Validators/Attributes.php:174
- UpdateDomainSuffixesCommand.parseTldsList (cognitive 17) src-dev/Commands/UpdateDomainSuffixesCommand.php:132
- Change coupling clique: AllOf.php, AnyOf.php, NoneOf.php src/Validators/AllOf.php
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (18 corresponding lines) src/Validators/All.php:41
- Edited copy of a member (21 corresponding lines) src/Validators/Pesel.php:34
- Edited copy of a member (13 corresponding lines) src/Validators/Image.php:40
- Edited copies of one member (3 members, 18+ corresponding lines) src/Validators/CountryCode.php:48
- Edited copy of a member (14 corresponding lines) src/ResultQuery.php:42
- Edited copy of a member (7 corresponding lines) src/Validators/Key.php:50
- Edited copy of a member (11 corresponding lines) src/Validators/EndsWith.php:73
- Edited copy of a member (8 corresponding lines) src/Validators/Between.php:36
- Edited copies of one member (4 members, 6+ corresponding lines) src/Validators/Date.php:52
- Edited copy of a member (9 corresponding lines) src/Validators/Base64.php:38
- Duplicated block (19 lines × 3) src-dev/Commands/UpdateDomainSuffixesCommand.php:60
- Duplicated block (14 lines × 2) src-dev/Commands/LintMixinCommand.php:148
- Duplicated block (12 lines × 2) src-dev/Commands/LintDocsCommand.php:69
- Duplicated block (9–10 lines × 2) src/Validators/All.php:41
- Duplicated block (9 lines × 3) src-dev/Commands/LintDocsCommand.php:72
- Duplicated block (7 lines × 2) src/Validators/NullOr.php:61
- Duplicated block (5 lines × 2) src/Validators/Date.php:53
- Duplicated block (9 lines × 2) src/Validators/Readable.php:38
- No structured logging
Minor — 48 finding(s)
- Orphaned file src-dev/Markdown/Linters/AssertionMessageLinter.php:1
- Orphaned file src-dev/Markdown/Content.php:1
- Orphaned file src/ValidatorBuilder.php:1
- Orphaned file src/Validators/Ip.php:1
- Orphaned file src-dev/Markdown/Linters/ValidatorHeaderLinter.php:1
- Orphaned file src-dev/Commands/UpdateDomainSuffixesCommand.php:1
- Orphaned file src/Validators/DateTimeDiff.php:1
- Orphaned file src/Validators/Iban.php:1
- Orphaned file src/Validators/CreditCard.php:1
- Orphaned file src-dev/Commands/UpdatePostalCodesCommand.php:1
- Orphaned file src/Validators/OneOf.php:1
- Orphaned file src-dev/Markdown/Linters/ValidatorTemplatesLinter.php:1
- Orphaned file src/Validators/PortugueseNif.php:1
- Orphaned file src/Validators/Domain.php:1
- Orphaned file src/Validators/Nif.php:1
- Orphaned file src/Validators/Sorted.php:1
- Orphaned file src/Validators/EachKey.php:1
- Orphaned file src/Validators/All.php:1
- Orphaned file src/Validators/Cnpj.php:1
- Orphaned file src/Validators/SubdivisionCode.php:1
- Orphaned file src-dev/Commands/LintDocsCommand.php:1
- Orphaned file src/Validators/LanguageCode.php:1
- Fat interface: AllChain (144 methods) src/Mixins/AllChain.php:18
- Fat interface: Chain (162 methods) src/Mixins/Chain.php:24
- Fat interface: KeyChain (145 methods) src/Mixins/KeyChain.php:18
- Fat interface: LengthChain (17 methods) src/Mixins/LengthChain.php:14
- Fat interface: MaxChain (17 methods) src/Mixins/MaxChain.php:14
- Fat interface: MinChain (17 methods) src/Mixins/MinChain.php:14
- Fat interface: NotChain (153 methods) src/Mixins/NotChain.php:18
- Fat interface: NullOrChain (153 methods) src/Mixins/NullOrChain.php:18
- Fat interface: PropertyChain (145 methods) src/Mixins/PropertyChain.php:18
- Fat interface: UndefOrChain (152 methods) src/Mixins/UndefOrChain.php:18
- Duplicated predicate src/Validators/Contains.php:48
- Duplicated predicate src/Validators/CountryCode.php:57
- Duplicated predicate src-dev/Spdx/ContributorExtractor/GitBlameContributorExtractor.php:38
- Duplicated predicate src-dev/Commands/UpdateDomainToplevelCommand.php:68
- Silent fallback default on parse failure src-dev/Markdown/Linters/ValidatorChangelogLinter.php:48
- Silent fallback default on parse failure src-dev/Markdown/Linters/ValidatorRelatedLinter.php:59
- Off-boarding risk: anonymized user #1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- Dependabot does not watch pip REDACTED:2
- No release approval gate REDACTED:11
- No changelog
Minor — 2 finding(s)
- Outdated: symfony/polyfill-intl-idn
- Outdated: symfony/polyfill-mbstring
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-ec7486d3f4554fcfb9315c49742c7ec6/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-ec7486d3f4554fcfb9315c49742c7ec6/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1520" --report-format json --report-path /tmp/watchdog-gitleaks-ec7486d3f4554fcfb9315c49742c7ec6/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ec7486d3f4554fcfb9315c49742c7ec6/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/Mixins . | 24 | 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: 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. semgrep could not parse 115 file(s) — `src-dev/Commands/LintDocsCommand.php`, `src-dev/Commands/LintMixinCommand.php`, `src-dev/Commands/LintSpdxCommand.php`, `src-dev/Commands/UpdateDomainSuffixesCommand.php`, `src-dev/Commands/UpdateDomainToplevelCommand.php`, … (+110 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |