Executive summary
nunomaduro/phpinsights falls short of our standard for production because we found no logging, tracing or health checks in the code. It scores 62.1 out of 100 and is rated Adequate, and two of its three critical findings are security problems in its automatic dependency updates and in its servers and containers.
Production Readiness, at 55.5, is the weakest lens, level with Code Health, and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 4.2 points. Adding a diagnostic log would lift Production Readiness itself, worth about 4.8 points. Raising Production Readiness to 70 would lift the score to about 65.6.
One automatic update takes new releases before a bad one can be spotted. One setting leaves the servers or containers unsafe, and one part of the code is no longer understood by anyone working on it. Setting a waiting period for automatic updates, correcting the unsafe settings and having someone learn the forgotten files would close these risks.
The product code is 8,779 lines, about €15,000 to rebuild.
If Production Readiness rose from 55.5 to 70, the lowest score rated Strong, the score would rise from 62.1 to about 65.6.
New since the last survey: 7 findings
- Code Duplication · Edited copy of a member (18 corresponding lines) src/Application/Console/Formatters/Console.php
- Code Duplication · Edited copy of a member (17 corresponding lines) src/Application/Console/Commands/InternalProcessorCommand.php
- Code Duplication · Edited copy of a member (16 corresponding lines) src/Domain/Runner.php
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) src/Domain/Insights/ClassMethodAverageCyclomaticComplexityIsHigh.php
- Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) src/Application/Adapters/Laravel/Preset.php
- Code Duplication · Edited copy of a member (9 corresponding lines) src/Application/Adapters/Drupal/Preset.php
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) src/Domain/InsightLoader/FixerLoader.php
Fixed since the last survey: 1 finding
- Code Duplication · Duplicated block (15 lines × 2) src/Application/Adapters/Magento2/Preset.php
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €4,900 to €25,000, for 82 to 261 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 62. 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: 8,779 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Application.Adapters.Laravel.Commands | 2 Application.Console.Definitions | 3 Application.Injectors | 4 Domain.Contracts.Repositories | 5 Domain.Exceptions | 6 Domain.Helper | 7 Domain.Sniffs | 8 Domain.Contracts | 9 Infrastructure.Repositories | 10 Domain.Insights | 11 Domain.LinkFormatter | 12 Domain.Metrics.Security | 13 Domain.Metrics.Style | 14 Application.Console.Contracts | 15 Domain | 16 Application | 17 Application.Console | 18 Application.Console.Styles | 19 Domain.FileProcessors | 20 Domain.InsightLoader | 21 Domain.Metrics.Architecture | 22 Domain.Metrics.Code | 23 Domain.Metrics.Complexity | 24 Application.Adapters.Drupal | 25 Application.Adapters.Laravel | 26 Application.Adapters.Magento2 | 27 Application.Adapters.Symfony | 28 Application.Adapters.WordPress | 29 Application.Adapters.Yii | 30 Application.Console.Commands | 31 Application.Console.Formatters |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Application.Adapters.Laravel.Commands | |||||||||||||||||||||||||||||||
| 2 Application.Console.Definitions | |||||||||||||||||||||||||||||||
| 3 Application.Injectors | |||||||||||||||||||||||||||||||
| 4 Domain.Contracts.Repositories | |||||||||||||||||||||||||||||||
| 5 Domain.Exceptions | |||||||||||||||||||||||||||||||
| 6 Domain.Helper | |||||||||||||||||||||||||||||||
| 7 Domain.Sniffs | |||||||||||||||||||||||||||||||
| 8 Domain.Contracts | 7 | 1 | |||||||||||||||||||||||||||||
| 9 Infrastructure.Repositories | 1 | ||||||||||||||||||||||||||||||
| 10 Domain.Insights | 2 | 25 | 11 | ||||||||||||||||||||||||||||
| 11 Domain.LinkFormatter | 2 | ||||||||||||||||||||||||||||||
| 12 Domain.Metrics.Security | 1 | ||||||||||||||||||||||||||||||
| 13 Domain.Metrics.Style | 1 | ||||||||||||||||||||||||||||||
| 14 Application.Console.Contracts | 1 | ||||||||||||||||||||||||||||||
| 15 Domain | 1 | 2 | 1 | ||||||||||||||||||||||||||||
| 16 Application | 1 | 1 | |||||||||||||||||||||||||||||
| 17 Application.Console | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 18 Application.Console.Styles | 2 | ||||||||||||||||||||||||||||||
| 19 Domain.FileProcessors | 4 | 1 | |||||||||||||||||||||||||||||
| 20 Domain.InsightLoader | 6 | 3 | |||||||||||||||||||||||||||||
| 21 Domain.Metrics.Architecture | 16 | 8 | |||||||||||||||||||||||||||||
| 22 Domain.Metrics.Code | 17 | 5 | |||||||||||||||||||||||||||||
| 23 Domain.Metrics.Complexity | 2 | 1 | |||||||||||||||||||||||||||||
| 24 Application.Adapters.Drupal | 1 | 1 | |||||||||||||||||||||||||||||
| 25 Application.Adapters.Laravel | 1 | 1 | |||||||||||||||||||||||||||||
| 26 Application.Adapters.Magento2 | 1 | 1 | |||||||||||||||||||||||||||||
| 27 Application.Adapters.Symfony | 1 | 1 | |||||||||||||||||||||||||||||
| 28 Application.Adapters.WordPress | 1 | 1 | |||||||||||||||||||||||||||||
| 29 Application.Adapters.Yii | 1 | 1 | |||||||||||||||||||||||||||||
| 30 Application.Console.Commands | 1 | 2 | 1 | ||||||||||||||||||||||||||||
| 31 Application.Console.Formatters | 2 | 6 | 7 | 5 | 1 |
8→15 Domain.Contracts uses Domain part of a loop✕
- Connections
- 7 pairs of types, where a type in Domain.Contracts uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Domain.Contracts.DetailsCarrier→NunoMaduro.PhpInsights.Domain.DetailsNunoMaduro.PhpInsights.Domain.Contracts.HasAvg→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Contracts.HasMax→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Contracts.HasPercentage→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Contracts.HasValue→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Contracts.InsightLoader→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Contracts.Sniffer→NunoMaduro.PhpInsights.Domain.Collector
- Direction
- Domain.Contracts uses Domain, so a change to Domain can break Domain.Contracts, while a change to Domain.Contracts can't break Domain.
- 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.
8→16 Domain.Contracts uses Application part of a loop✕
- Connections
- 1 pair of types, where a type in Domain.Contracts uses a type in Application.
- The types involved
NunoMaduro.PhpInsights.Domain.Contracts.Preset→NunoMaduro.PhpInsights.Application.Composer
- Direction
- Domain.Contracts uses Application, so a change to Application can break Domain.Contracts, while a change to Domain.Contracts can't break Application.
- 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.
9→4 Infrastructure.Repositories uses Domain.Contracts.Repositories✕
- Connections
- 1 pair of types, where a type in Infrastructure.Repositories uses a type in Domain.Contracts.Repositories.
- The types involved
NunoMaduro.PhpInsights.Infrastructure.Repositories.LocalFilesRepository→NunoMaduro.PhpInsights.Domain.Contracts.Repositories.FilesRepository
- Direction
- Infrastructure.Repositories uses Domain.Contracts.Repositories, so a change to Domain.Contracts.Repositories can break Infrastructure.Repositories, while a change to Infrastructure.Repositories can't break Domain.Contracts.Repositories.
- Position
- Below the diagonal: Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
10→4 Domain.Insights uses Domain.Contracts.Repositories✕
- Connections
- 2 pairs of types, where a type in Domain.Insights uses a type in Domain.Contracts.Repositories.
- The types involved
NunoMaduro.PhpInsights.Domain.Insights.InsightCollectionFactory→NunoMaduro.PhpInsights.Domain.Contracts.Repositories.FilesRepositoryNunoMaduro.PhpInsights.Domain.Insights.InsightFactory→NunoMaduro.PhpInsights.Domain.Contracts.Repositories.FilesRepository
- Direction
- Domain.Insights uses Domain.Contracts.Repositories, so a change to Domain.Contracts.Repositories can break Domain.Insights, while a change to Domain.Insights can't break Domain.Contracts.Repositories.
- Position
- Below the diagonal: Domain.Insights uses a module listed above it, which is the healthy direction.
10→8 Domain.Insights uses Domain.Contracts✕
- Connections
- 25 pairs of types, where a type in Domain.Insights uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Domain.Insights.ClassMethodAverageCyclomaticComplexityIsHigh→NunoMaduro.PhpInsights.Domain.Contracts.GlobalInsightNunoMaduro.PhpInsights.Domain.Insights.ClassMethodAverageCyclomaticComplexityIsHigh→NunoMaduro.PhpInsights.Domain.Contracts.HasDetailsNunoMaduro.PhpInsights.Domain.Insights.CyclomaticComplexityIsHigh→NunoMaduro.PhpInsights.Domain.Contracts.GlobalInsightNunoMaduro.PhpInsights.Domain.Insights.CyclomaticComplexityIsHigh→NunoMaduro.PhpInsights.Domain.Contracts.HasDetailsNunoMaduro.PhpInsights.Domain.Insights.FixerDecorator→NunoMaduro.PhpInsights.Domain.Contracts.DetailsCarrierNunoMaduro.PhpInsights.Domain.Insights.FixerDecorator→NunoMaduro.PhpInsights.Domain.Contracts.FixableNunoMaduro.PhpInsights.Domain.Insights.FixerDecorator→NunoMaduro.PhpInsights.Domain.Contracts.InsightNunoMaduro.PhpInsights.Domain.Insights.ForbiddenDefineFunctions→NunoMaduro.PhpInsights.Domain.Contracts.HasDetailsNunoMaduro.PhpInsights.Domain.Insights.ForbiddenDefineGlobalConstants→NunoMaduro.PhpInsights.Domain.Contracts.HasDetailsNunoMaduro.PhpInsights.Domain.Insights.ForbiddenFinalClasses→NunoMaduro.PhpInsights.Domain.Contracts.HasDetailsNunoMaduro.PhpInsights.Domain.Insights.ForbiddenGlobals→NunoMaduro.PhpInsights.Domain.Contracts.HasDetailsNunoMaduro.PhpInsights.Domain.Insights.ForbiddenNormalClasses→NunoMaduro.PhpInsights.Domain.Contracts.HasDetailsNunoMaduro.PhpInsights.Domain.Insights.ForbiddenSecurityIssues→NunoMaduro.PhpInsights.Domain.Contracts.GlobalInsightNunoMaduro.PhpInsights.Domain.Insights.ForbiddenSecurityIssues→NunoMaduro.PhpInsights.Domain.Contracts.HasDetailsNunoMaduro.PhpInsights.Domain.Insights.ForbiddenTraits→NunoMaduro.PhpInsights.Domain.Contracts.HasDetailsNunoMaduro.PhpInsights.Domain.Insights.Insight→NunoMaduro.PhpInsights.Domain.Contracts.InsightNunoMaduro.PhpInsights.Domain.Insights.InsightCollection→NunoMaduro.PhpInsights.Domain.Contracts.MetricNunoMaduro.PhpInsights.Domain.Insights.InsightFactory→NunoMaduro.PhpInsights.Domain.Contracts.InsightNunoMaduro.PhpInsights.Domain.Insights.MethodCyclomaticComplexityIsHigh→NunoMaduro.PhpInsights.Domain.Contracts.GlobalInsightNunoMaduro.PhpInsights.Domain.Insights.MethodCyclomaticComplexityIsHigh→NunoMaduro.PhpInsights.Domain.Contracts.HasDetailsNunoMaduro.PhpInsights.Domain.Insights.SniffDecorator→NunoMaduro.PhpInsights.Domain.Contracts.DetailsCarrierNunoMaduro.PhpInsights.Domain.Insights.SniffDecorator→NunoMaduro.PhpInsights.Domain.Contracts.FixableNunoMaduro.PhpInsights.Domain.Insights.SniffDecorator→NunoMaduro.PhpInsights.Domain.Contracts.InsightNunoMaduro.PhpInsights.Domain.Insights.SyntaxCheck→NunoMaduro.PhpInsights.Domain.Contracts.GlobalInsightNunoMaduro.PhpInsights.Domain.Insights.SyntaxCheck→NunoMaduro.PhpInsights.Domain.Contracts.HasDetails
- Direction
- Domain.Insights uses Domain.Contracts, so a change to Domain.Contracts can break Domain.Insights, while a change to Domain.Insights can't break Domain.Contracts.
- Position
- Below the diagonal: Domain.Insights uses a module listed above it, which is the healthy direction.
10→15 Domain.Insights uses Domain part of a loop✕
- Connections
- 11 pairs of types, where a type in Domain.Insights uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Domain.Insights.FixerDecorator→NunoMaduro.PhpInsights.Domain.DetailsNunoMaduro.PhpInsights.Domain.Insights.Insight→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Insights.InsightCollection→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Insights.InsightCollection→NunoMaduro.PhpInsights.Domain.ResultsNunoMaduro.PhpInsights.Domain.Insights.InsightCollectionFactory→NunoMaduro.PhpInsights.Domain.AnalyserNunoMaduro.PhpInsights.Domain.Insights.InsightCollectionFactory→NunoMaduro.PhpInsights.Domain.ConfigurationNunoMaduro.PhpInsights.Domain.Insights.InsightFactory→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Insights.InsightFactory→NunoMaduro.PhpInsights.Domain.ConfigurationNunoMaduro.PhpInsights.Domain.Insights.MethodCyclomaticComplexityIsHigh→NunoMaduro.PhpInsights.Domain.DetailsNunoMaduro.PhpInsights.Domain.Insights.SniffDecorator→NunoMaduro.PhpInsights.Domain.DetailsNunoMaduro.PhpInsights.Domain.Insights.SniffDecorator→NunoMaduro.PhpInsights.Domain.File
- Direction
- Domain.Insights uses Domain, so a change to Domain can break Domain.Insights, while a change to Domain.Insights can't break Domain.
- 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→8 Domain.LinkFormatter uses Domain.Contracts✕
- Connections
- 2 pairs of types, where a type in Domain.LinkFormatter uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Domain.LinkFormatter.FileLinkFormatter→NunoMaduro.PhpInsights.Domain.Contracts.FileLinkFormatterNunoMaduro.PhpInsights.Domain.LinkFormatter.NullFileLinkFormatter→NunoMaduro.PhpInsights.Domain.Contracts.FileLinkFormatter
- Direction
- Domain.LinkFormatter uses Domain.Contracts, so a change to Domain.Contracts can break Domain.LinkFormatter, while a change to Domain.LinkFormatter can't break Domain.Contracts.
- Position
- Below the diagonal: Domain.LinkFormatter uses a module listed above it, which is the healthy direction.
12→8 Domain.Metrics.Security uses Domain.Contracts✕
- Connections
- 1 pair of types, where a type in Domain.Metrics.Security uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Domain.Metrics.Security.Security→NunoMaduro.PhpInsights.Domain.Contracts.HasInsights
- Direction
- Domain.Metrics.Security uses Domain.Contracts, so a change to Domain.Contracts can break Domain.Metrics.Security, while a change to Domain.Metrics.Security can't break Domain.Contracts.
- Position
- Below the diagonal: Domain.Metrics.Security uses a module listed above it, which is the healthy direction.
13→8 Domain.Metrics.Style uses Domain.Contracts✕
- Connections
- 1 pair of types, where a type in Domain.Metrics.Style uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Domain.Metrics.Style.Style→NunoMaduro.PhpInsights.Domain.Contracts.HasInsights
- Direction
- Domain.Metrics.Style uses Domain.Contracts, so a change to Domain.Contracts can break Domain.Metrics.Style, while a change to Domain.Metrics.Style can't break Domain.Contracts.
- Position
- Below the diagonal: Domain.Metrics.Style uses a module listed above it, which is the healthy direction.
14→10 Application.Console.Contracts uses Domain.Insights✕
- Connections
- 1 pair of types, where a type in Application.Console.Contracts uses a type in Domain.Insights.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Contracts.Formatter→NunoMaduro.PhpInsights.Domain.Insights.InsightCollection
- Direction
- Application.Console.Contracts uses Domain.Insights, so a change to Domain.Insights can break Application.Console.Contracts, while a change to Application.Console.Contracts can't break Domain.Insights.
- Position
- Below the diagonal: Application.Console.Contracts uses a module listed above it, which is the healthy direction.
15→4 Domain uses Domain.Contracts.Repositories✕
- Connections
- 1 pair of types, where a type in Domain uses a type in Domain.Contracts.Repositories.
- The types involved
NunoMaduro.PhpInsights.Domain.Runner→NunoMaduro.PhpInsights.Domain.Contracts.Repositories.FilesRepository
- Direction
- Domain uses Domain.Contracts.Repositories, so a change to Domain.Contracts.Repositories can break Domain, while a change to Domain can't break Domain.Contracts.Repositories.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
15→8 Domain uses Domain.Contracts✕
- Connections
- 2 pairs of types, where a type in Domain uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Domain.Configuration→NunoMaduro.PhpInsights.Domain.Contracts.FileLinkFormatterNunoMaduro.PhpInsights.Domain.Results→NunoMaduro.PhpInsights.Domain.Contracts.Insight
- Direction
- Domain uses Domain.Contracts, so a change to Domain.Contracts can break Domain, while a change to Domain can't break Domain.Contracts.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
15→10 Domain uses Domain.Insights✕
- Connections
- 1 pair of types, where a type in Domain uses a type in Domain.Insights.
- The types involved
NunoMaduro.PhpInsights.Domain.File→NunoMaduro.PhpInsights.Domain.Insights.SniffDecorator
- Direction
- Domain uses Domain.Insights, so a change to Domain.Insights can break Domain, while a change to Domain can't break Domain.Insights.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
16→8 Application uses Domain.Contracts✕
- Connections
- 1 pair of types, where a type in Application uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.DefaultPreset→NunoMaduro.PhpInsights.Domain.Contracts.Preset
- Direction
- Application uses Domain.Contracts, so a change to Domain.Contracts can break Application, while a change to Application can't break Domain.Contracts.
- Position
- Below the diagonal: Application uses a module listed above it, which is the healthy direction.
16→15 Application uses Domain✕
- Connections
- 1 pair of types, where a type in Application uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Application.ConfigResolver→NunoMaduro.PhpInsights.Domain.Configuration
- Direction
- Application uses Domain, so a change to Domain can break Application, while a change to Application can't break Domain.
- Position
- Below the diagonal: Application uses a module listed above it, which is the healthy direction.
17→10 Application.Console uses Domain.Insights✕
- Connections
- 1 pair of types, where a type in Application.Console uses a type in Domain.Insights.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Analyser→NunoMaduro.PhpInsights.Domain.Insights.InsightCollectionFactory
- Direction
- Application.Console uses Domain.Insights, so a change to Domain.Insights can break Application.Console, while a change to Application.Console can't break Domain.Insights.
- Position
- Below the diagonal: Application.Console uses a module listed above it, which is the healthy direction.
17→14 Application.Console uses Application.Console.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Console uses a type in Application.Console.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Analyser→NunoMaduro.PhpInsights.Application.Console.Contracts.Formatter
- Direction
- Application.Console uses Application.Console.Contracts, so a change to Application.Console.Contracts can break Application.Console, while a change to Application.Console can't break Application.Console.Contracts.
- Position
- Below the diagonal: Application.Console uses a module listed above it, which is the healthy direction.
17→15 Application.Console uses Domain✕
- Connections
- 1 pair of types, where a type in Application.Console uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Analyser→NunoMaduro.PhpInsights.Domain.Results
- Direction
- Application.Console uses Domain, so a change to Domain can break Application.Console, while a change to Application.Console can't break Domain.
- Position
- Below the diagonal: Application.Console uses a module listed above it, which is the healthy direction.
18→14 Application.Console.Styles uses Application.Console.Contracts✕
- Connections
- 2 pairs of types, where a type in Application.Console.Styles uses a type in Application.Console.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Styles.Bold→NunoMaduro.PhpInsights.Application.Console.Contracts.StyleNunoMaduro.PhpInsights.Application.Console.Styles.Title→NunoMaduro.PhpInsights.Application.Console.Contracts.Style
- Direction
- Application.Console.Styles uses Application.Console.Contracts, so a change to Application.Console.Contracts can break Application.Console.Styles, while a change to Application.Console.Styles can't break Application.Console.Contracts.
- Position
- Below the diagonal: Application.Console.Styles uses a module listed above it, which is the healthy direction.
19→8 Domain.FileProcessors uses Domain.Contracts✕
- Connections
- 4 pairs of types, where a type in Domain.FileProcessors uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Domain.FileProcessors.FixerFileProcessor→NunoMaduro.PhpInsights.Domain.Contracts.FileProcessorNunoMaduro.PhpInsights.Domain.FileProcessors.FixerFileProcessor→NunoMaduro.PhpInsights.Domain.Contracts.InsightNunoMaduro.PhpInsights.Domain.FileProcessors.SniffFileProcessor→NunoMaduro.PhpInsights.Domain.Contracts.FileProcessorNunoMaduro.PhpInsights.Domain.FileProcessors.SniffFileProcessor→NunoMaduro.PhpInsights.Domain.Contracts.Insight
- Direction
- Domain.FileProcessors uses Domain.Contracts, so a change to Domain.Contracts can break Domain.FileProcessors, while a change to Domain.FileProcessors can't break Domain.Contracts.
- Position
- Below the diagonal: Domain.FileProcessors uses a module listed above it, which is the healthy direction.
19→15 Domain.FileProcessors uses Domain✕
- Connections
- 1 pair of types, where a type in Domain.FileProcessors uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Domain.FileProcessors.SniffFileProcessor→NunoMaduro.PhpInsights.Domain.FileFactory
- Direction
- Domain.FileProcessors uses Domain, so a change to Domain can break Domain.FileProcessors, while a change to Domain.FileProcessors can't break Domain.
- Position
- Below the diagonal: Domain.FileProcessors uses a module listed above it, which is the healthy direction.
20→8 Domain.InsightLoader uses Domain.Contracts✕
- Connections
- 6 pairs of types, where a type in Domain.InsightLoader uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Domain.InsightLoader.FixerLoader→NunoMaduro.PhpInsights.Domain.Contracts.InsightNunoMaduro.PhpInsights.Domain.InsightLoader.FixerLoader→NunoMaduro.PhpInsights.Domain.Contracts.InsightLoaderNunoMaduro.PhpInsights.Domain.InsightLoader.InsightLoader→NunoMaduro.PhpInsights.Domain.Contracts.InsightNunoMaduro.PhpInsights.Domain.InsightLoader.InsightLoader→NunoMaduro.PhpInsights.Domain.Contracts.InsightLoaderNunoMaduro.PhpInsights.Domain.InsightLoader.SniffLoader→NunoMaduro.PhpInsights.Domain.Contracts.InsightNunoMaduro.PhpInsights.Domain.InsightLoader.SniffLoader→NunoMaduro.PhpInsights.Domain.Contracts.InsightLoader
- Direction
- Domain.InsightLoader uses Domain.Contracts, so a change to Domain.Contracts can break Domain.InsightLoader, while a change to Domain.InsightLoader can't break Domain.Contracts.
- Position
- Below the diagonal: Domain.InsightLoader uses a module listed above it, which is the healthy direction.
20→15 Domain.InsightLoader uses Domain✕
- Connections
- 3 pairs of types, where a type in Domain.InsightLoader uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Domain.InsightLoader.FixerLoader→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.InsightLoader.InsightLoader→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.InsightLoader.SniffLoader→NunoMaduro.PhpInsights.Domain.Collector
- Direction
- Domain.InsightLoader uses Domain, so a change to Domain can break Domain.InsightLoader, while a change to Domain.InsightLoader can't break Domain.
- Position
- Below the diagonal: Domain.InsightLoader uses a module listed above it, which is the healthy direction.
21→8 Domain.Metrics.Architecture uses Domain.Contracts✕
- Connections
- 16 pairs of types, where a type in Domain.Metrics.Architecture uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Domain.Metrics.Architecture.Classes→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Classes→NunoMaduro.PhpInsights.Domain.Contracts.HasValueNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Constants→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Constants→NunoMaduro.PhpInsights.Domain.Contracts.HasValueNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Files→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Files→NunoMaduro.PhpInsights.Domain.Contracts.HasValueNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Functions→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Functions→NunoMaduro.PhpInsights.Domain.Contracts.HasValueNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Globally→NunoMaduro.PhpInsights.Domain.Contracts.HasPercentageNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Interfaces→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Interfaces→NunoMaduro.PhpInsights.Domain.Contracts.HasPercentageNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Interfaces→NunoMaduro.PhpInsights.Domain.Contracts.HasValueNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Namespaces→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Namespaces→NunoMaduro.PhpInsights.Domain.Contracts.HasValueNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Traits→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Traits→NunoMaduro.PhpInsights.Domain.Contracts.HasValue
- Direction
- Domain.Metrics.Architecture uses Domain.Contracts, so a change to Domain.Contracts can break Domain.Metrics.Architecture, while a change to Domain.Metrics.Architecture can't break Domain.Contracts.
- Position
- Below the diagonal: Domain.Metrics.Architecture uses a module listed above it, which is the healthy direction.
21→15 Domain.Metrics.Architecture uses Domain✕
- Connections
- 8 pairs of types, where a type in Domain.Metrics.Architecture uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Domain.Metrics.Architecture.Classes→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Constants→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Files→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Functions→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Globally→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Interfaces→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Namespaces→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Architecture.Traits→NunoMaduro.PhpInsights.Domain.Collector
- Direction
- Domain.Metrics.Architecture uses Domain, so a change to Domain can break Domain.Metrics.Architecture, while a change to Domain.Metrics.Architecture can't break Domain.
- Position
- Below the diagonal: Domain.Metrics.Architecture uses a module listed above it, which is the healthy direction.
22→8 Domain.Metrics.Code uses Domain.Contracts✕
- Connections
- 17 pairs of types, where a type in Domain.Metrics.Code uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Domain.Metrics.Code.Classes→NunoMaduro.PhpInsights.Domain.Contracts.HasAvgNunoMaduro.PhpInsights.Domain.Metrics.Code.Classes→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Code.Classes→NunoMaduro.PhpInsights.Domain.Contracts.HasMaxNunoMaduro.PhpInsights.Domain.Metrics.Code.Classes→NunoMaduro.PhpInsights.Domain.Contracts.HasPercentageNunoMaduro.PhpInsights.Domain.Metrics.Code.Classes→NunoMaduro.PhpInsights.Domain.Contracts.HasValueNunoMaduro.PhpInsights.Domain.Metrics.Code.Code→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Code.Code→NunoMaduro.PhpInsights.Domain.Contracts.HasValueNunoMaduro.PhpInsights.Domain.Metrics.Code.Comments→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Code.Comments→NunoMaduro.PhpInsights.Domain.Contracts.HasPercentageNunoMaduro.PhpInsights.Domain.Metrics.Code.Comments→NunoMaduro.PhpInsights.Domain.Contracts.HasValueNunoMaduro.PhpInsights.Domain.Metrics.Code.Functions→NunoMaduro.PhpInsights.Domain.Contracts.HasAvgNunoMaduro.PhpInsights.Domain.Metrics.Code.Functions→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Code.Functions→NunoMaduro.PhpInsights.Domain.Contracts.HasPercentageNunoMaduro.PhpInsights.Domain.Metrics.Code.Functions→NunoMaduro.PhpInsights.Domain.Contracts.HasValueNunoMaduro.PhpInsights.Domain.Metrics.Code.Globally→NunoMaduro.PhpInsights.Domain.Contracts.HasInsightsNunoMaduro.PhpInsights.Domain.Metrics.Code.Globally→NunoMaduro.PhpInsights.Domain.Contracts.HasPercentageNunoMaduro.PhpInsights.Domain.Metrics.Code.Globally→NunoMaduro.PhpInsights.Domain.Contracts.HasValue
- Direction
- Domain.Metrics.Code uses Domain.Contracts, so a change to Domain.Contracts can break Domain.Metrics.Code, while a change to Domain.Metrics.Code can't break Domain.Contracts.
- Position
- Below the diagonal: Domain.Metrics.Code uses a module listed above it, which is the healthy direction.
22→15 Domain.Metrics.Code uses Domain✕
- Connections
- 5 pairs of types, where a type in Domain.Metrics.Code uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Domain.Metrics.Code.Classes→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Code.Code→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Code.Comments→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Code.Functions→NunoMaduro.PhpInsights.Domain.CollectorNunoMaduro.PhpInsights.Domain.Metrics.Code.Globally→NunoMaduro.PhpInsights.Domain.Collector
- Direction
- Domain.Metrics.Code uses Domain, so a change to Domain can break Domain.Metrics.Code, while a change to Domain.Metrics.Code can't break Domain.
- Position
- Below the diagonal: Domain.Metrics.Code uses a module listed above it, which is the healthy direction.
23→8 Domain.Metrics.Complexity uses Domain.Contracts✕
- Connections
- 2 pairs of types, where a type in Domain.Metrics.Complexity uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Domain.Metrics.Complexity.Complexity→NunoMaduro.PhpInsights.Domain.Contracts.HasAvgNunoMaduro.PhpInsights.Domain.Metrics.Complexity.Complexity→NunoMaduro.PhpInsights.Domain.Contracts.HasInsights
- Direction
- Domain.Metrics.Complexity uses Domain.Contracts, so a change to Domain.Contracts can break Domain.Metrics.Complexity, while a change to Domain.Metrics.Complexity can't break Domain.Contracts.
- Position
- Below the diagonal: Domain.Metrics.Complexity uses a module listed above it, which is the healthy direction.
23→15 Domain.Metrics.Complexity uses Domain✕
- Connections
- 1 pair of types, where a type in Domain.Metrics.Complexity uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Domain.Metrics.Complexity.Complexity→NunoMaduro.PhpInsights.Domain.Collector
- Direction
- Domain.Metrics.Complexity uses Domain, so a change to Domain can break Domain.Metrics.Complexity, while a change to Domain.Metrics.Complexity can't break Domain.
- Position
- Below the diagonal: Domain.Metrics.Complexity uses a module listed above it, which is the healthy direction.
24→8 Application.Adapters.Drupal uses Domain.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Adapters.Drupal uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.Drupal.Preset→NunoMaduro.PhpInsights.Domain.Contracts.Preset
- Direction
- Application.Adapters.Drupal uses Domain.Contracts, so a change to Domain.Contracts can break Application.Adapters.Drupal, while a change to Application.Adapters.Drupal can't break Domain.Contracts.
- Position
- Below the diagonal: Application.Adapters.Drupal uses a module listed above it, which is the healthy direction.
24→16 Application.Adapters.Drupal uses Application✕
- Connections
- 1 pair of types, where a type in Application.Adapters.Drupal uses a type in Application.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.Drupal.Preset→NunoMaduro.PhpInsights.Application.Composer
- Direction
- Application.Adapters.Drupal uses Application, so a change to Application can break Application.Adapters.Drupal, while a change to Application.Adapters.Drupal can't break Application.
- Position
- Below the diagonal: Application.Adapters.Drupal uses a module listed above it, which is the healthy direction.
25→8 Application.Adapters.Laravel uses Domain.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Adapters.Laravel uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.Laravel.Preset→NunoMaduro.PhpInsights.Domain.Contracts.Preset
- Direction
- Application.Adapters.Laravel uses Domain.Contracts, so a change to Domain.Contracts can break Application.Adapters.Laravel, while a change to Application.Adapters.Laravel can't break Domain.Contracts.
- Position
- Below the diagonal: Application.Adapters.Laravel uses a module listed above it, which is the healthy direction.
25→16 Application.Adapters.Laravel uses Application✕
- Connections
- 1 pair of types, where a type in Application.Adapters.Laravel uses a type in Application.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.Laravel.Preset→NunoMaduro.PhpInsights.Application.Composer
- Direction
- Application.Adapters.Laravel uses Application, so a change to Application can break Application.Adapters.Laravel, while a change to Application.Adapters.Laravel can't break Application.
- Position
- Below the diagonal: Application.Adapters.Laravel uses a module listed above it, which is the healthy direction.
26→8 Application.Adapters.Magento2 uses Domain.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Adapters.Magento2 uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.Magento2.Preset→NunoMaduro.PhpInsights.Domain.Contracts.Preset
- Direction
- Application.Adapters.Magento2 uses Domain.Contracts, so a change to Domain.Contracts can break Application.Adapters.Magento2, while a change to Application.Adapters.Magento2 can't break Domain.Contracts.
- Position
- Below the diagonal: Application.Adapters.Magento2 uses a module listed above it, which is the healthy direction.
26→16 Application.Adapters.Magento2 uses Application✕
- Connections
- 1 pair of types, where a type in Application.Adapters.Magento2 uses a type in Application.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.Magento2.Preset→NunoMaduro.PhpInsights.Application.Composer
- Direction
- Application.Adapters.Magento2 uses Application, so a change to Application can break Application.Adapters.Magento2, while a change to Application.Adapters.Magento2 can't break Application.
- Position
- Below the diagonal: Application.Adapters.Magento2 uses a module listed above it, which is the healthy direction.
27→8 Application.Adapters.Symfony uses Domain.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Adapters.Symfony uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.Symfony.Preset→NunoMaduro.PhpInsights.Domain.Contracts.Preset
- Direction
- Application.Adapters.Symfony uses Domain.Contracts, so a change to Domain.Contracts can break Application.Adapters.Symfony, while a change to Application.Adapters.Symfony can't break Domain.Contracts.
- Position
- Below the diagonal: Application.Adapters.Symfony uses a module listed above it, which is the healthy direction.
27→16 Application.Adapters.Symfony uses Application✕
- Connections
- 1 pair of types, where a type in Application.Adapters.Symfony uses a type in Application.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.Symfony.Preset→NunoMaduro.PhpInsights.Application.Composer
- Direction
- Application.Adapters.Symfony uses Application, so a change to Application can break Application.Adapters.Symfony, while a change to Application.Adapters.Symfony can't break Application.
- Position
- Below the diagonal: Application.Adapters.Symfony uses a module listed above it, which is the healthy direction.
28→8 Application.Adapters.WordPress uses Domain.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Adapters.WordPress uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.WordPress.Preset→NunoMaduro.PhpInsights.Domain.Contracts.Preset
- Direction
- Application.Adapters.WordPress uses Domain.Contracts, so a change to Domain.Contracts can break Application.Adapters.WordPress, while a change to Application.Adapters.WordPress can't break Domain.Contracts.
- Position
- Below the diagonal: Application.Adapters.WordPress uses a module listed above it, which is the healthy direction.
28→16 Application.Adapters.WordPress uses Application✕
- Connections
- 1 pair of types, where a type in Application.Adapters.WordPress uses a type in Application.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.WordPress.Preset→NunoMaduro.PhpInsights.Application.Composer
- Direction
- Application.Adapters.WordPress uses Application, so a change to Application can break Application.Adapters.WordPress, while a change to Application.Adapters.WordPress can't break Application.
- Position
- Below the diagonal: Application.Adapters.WordPress uses a module listed above it, which is the healthy direction.
29→8 Application.Adapters.Yii uses Domain.Contracts✕
- Connections
- 1 pair of types, where a type in Application.Adapters.Yii uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.Yii.Preset→NunoMaduro.PhpInsights.Domain.Contracts.Preset
- Direction
- Application.Adapters.Yii uses Domain.Contracts, so a change to Domain.Contracts can break Application.Adapters.Yii, while a change to Application.Adapters.Yii can't break Domain.Contracts.
- Position
- Below the diagonal: Application.Adapters.Yii uses a module listed above it, which is the healthy direction.
29→16 Application.Adapters.Yii uses Application✕
- Connections
- 1 pair of types, where a type in Application.Adapters.Yii uses a type in Application.
- The types involved
NunoMaduro.PhpInsights.Application.Adapters.Yii.Preset→NunoMaduro.PhpInsights.Application.Composer
- Direction
- Application.Adapters.Yii uses Application, so a change to Application can break Application.Adapters.Yii, while a change to Application.Adapters.Yii can't break Application.
- Position
- Below the diagonal: Application.Adapters.Yii uses a module listed above it, which is the healthy direction.
30→10 Application.Console.Commands uses Domain.Insights✕
- Connections
- 1 pair of types, where a type in Application.Console.Commands uses a type in Domain.Insights.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Commands.FixCommand→NunoMaduro.PhpInsights.Domain.Insights.InsightCollectionFactory
- Direction
- Application.Console.Commands uses Domain.Insights, so a change to Domain.Insights can break Application.Console.Commands, while a change to Application.Console.Commands can't break Domain.Insights.
- Position
- Below the diagonal: Application.Console.Commands uses a module listed above it, which is the healthy direction.
30→15 Application.Console.Commands uses Domain✕
- Connections
- 2 pairs of types, where a type in Application.Console.Commands uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Commands.AnalyseCommand→NunoMaduro.PhpInsights.Domain.ConfigurationNunoMaduro.PhpInsights.Application.Console.Commands.InternalProcessorCommand→NunoMaduro.PhpInsights.Domain.Configuration
- Direction
- Application.Console.Commands uses Domain, so a change to Domain can break Application.Console.Commands, while a change to Application.Console.Commands can't break Domain.
- Position
- Below the diagonal: Application.Console.Commands uses a module listed above it, which is the healthy direction.
30→17 Application.Console.Commands uses Application.Console✕
- Connections
- 1 pair of types, where a type in Application.Console.Commands uses a type in Application.Console.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Commands.AnalyseCommand→NunoMaduro.PhpInsights.Application.Console.Analyser
- Direction
- Application.Console.Commands uses Application.Console, so a change to Application.Console can break Application.Console.Commands, while a change to Application.Console.Commands can't break Application.Console.
- Position
- Below the diagonal: Application.Console.Commands uses a module listed above it, which is the healthy direction.
31→8 Application.Console.Formatters uses Domain.Contracts✕
- Connections
- 2 pairs of types, where a type in Application.Console.Formatters uses a type in Domain.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Formatters.Console→NunoMaduro.PhpInsights.Domain.Contracts.FileLinkFormatterNunoMaduro.PhpInsights.Application.Console.Formatters.GithubAction→NunoMaduro.PhpInsights.Domain.Contracts.Insight
- Direction
- Application.Console.Formatters uses Domain.Contracts, so a change to Domain.Contracts can break Application.Console.Formatters, while a change to Application.Console.Formatters can't break Domain.Contracts.
- Position
- Below the diagonal: Application.Console.Formatters uses a module listed above it, which is the healthy direction.
31→10 Application.Console.Formatters uses Domain.Insights✕
- Connections
- 6 pairs of types, where a type in Application.Console.Formatters uses a type in Domain.Insights.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Formatters.Checkstyle→NunoMaduro.PhpInsights.Domain.Insights.InsightCollectionNunoMaduro.PhpInsights.Application.Console.Formatters.CodeClimate→NunoMaduro.PhpInsights.Domain.Insights.InsightCollectionNunoMaduro.PhpInsights.Application.Console.Formatters.Console→NunoMaduro.PhpInsights.Domain.Insights.InsightCollectionNunoMaduro.PhpInsights.Application.Console.Formatters.GithubAction→NunoMaduro.PhpInsights.Domain.Insights.InsightCollectionNunoMaduro.PhpInsights.Application.Console.Formatters.Json→NunoMaduro.PhpInsights.Domain.Insights.InsightCollectionNunoMaduro.PhpInsights.Application.Console.Formatters.Multiple→NunoMaduro.PhpInsights.Domain.Insights.InsightCollection
- Direction
- Application.Console.Formatters uses Domain.Insights, so a change to Domain.Insights can break Application.Console.Formatters, while a change to Application.Console.Formatters can't break Domain.Insights.
- Position
- Below the diagonal: Application.Console.Formatters uses a module listed above it, which is the healthy direction.
31→14 Application.Console.Formatters uses Application.Console.Contracts✕
- Connections
- 7 pairs of types, where a type in Application.Console.Formatters uses a type in Application.Console.Contracts.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Formatters.Checkstyle→NunoMaduro.PhpInsights.Application.Console.Contracts.FormatterNunoMaduro.PhpInsights.Application.Console.Formatters.CodeClimate→NunoMaduro.PhpInsights.Application.Console.Contracts.FormatterNunoMaduro.PhpInsights.Application.Console.Formatters.Console→NunoMaduro.PhpInsights.Application.Console.Contracts.FormatterNunoMaduro.PhpInsights.Application.Console.Formatters.FormatResolver→NunoMaduro.PhpInsights.Application.Console.Contracts.FormatterNunoMaduro.PhpInsights.Application.Console.Formatters.GithubAction→NunoMaduro.PhpInsights.Application.Console.Contracts.FormatterNunoMaduro.PhpInsights.Application.Console.Formatters.Json→NunoMaduro.PhpInsights.Application.Console.Contracts.FormatterNunoMaduro.PhpInsights.Application.Console.Formatters.Multiple→NunoMaduro.PhpInsights.Application.Console.Contracts.Formatter
- Direction
- Application.Console.Formatters uses Application.Console.Contracts, so a change to Application.Console.Contracts can break Application.Console.Formatters, while a change to Application.Console.Formatters can't break Application.Console.Contracts.
- Position
- Below the diagonal: Application.Console.Formatters uses a module listed above it, which is the healthy direction.
31→15 Application.Console.Formatters uses Domain✕
- Connections
- 5 pairs of types, where a type in Application.Console.Formatters uses a type in Domain.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Formatters.Console→NunoMaduro.PhpInsights.Domain.ConfigurationNunoMaduro.PhpInsights.Application.Console.Formatters.Console→NunoMaduro.PhpInsights.Domain.DetailsNunoMaduro.PhpInsights.Application.Console.Formatters.Console→NunoMaduro.PhpInsights.Domain.ResultsNunoMaduro.PhpInsights.Application.Console.Formatters.GithubAction→NunoMaduro.PhpInsights.Domain.DetailsNunoMaduro.PhpInsights.Application.Console.Formatters.PathShortener→NunoMaduro.PhpInsights.Domain.Details
- Direction
- Application.Console.Formatters uses Domain, so a change to Domain can break Application.Console.Formatters, while a change to Application.Console.Formatters can't break Domain.
- Position
- Below the diagonal: Application.Console.Formatters uses a module listed above it, which is the healthy direction.
31→17 Application.Console.Formatters uses Application.Console✕
- Connections
- 1 pair of types, where a type in Application.Console.Formatters uses a type in Application.Console.
- The types involved
NunoMaduro.PhpInsights.Application.Console.Formatters.Console→NunoMaduro.PhpInsights.Application.Console.Style
- Direction
- Application.Console.Formatters uses Application.Console, so a change to Application.Console can break Application.Console.Formatters, while a change to Application.Console.Formatters can't break Application.Console.
- Position
- Below the diagonal: Application.Console.Formatters uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 2 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | High / Critical |
Roadmap
Top priorities: Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. | +4.2 pts | Low | ADR Quality |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +4.9 pts | Medium | Nullable reference types |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +4.8 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. | +3.5 pts | Medium | Architecture documentation |
| Swallowed exception (empty catch) | +2.7 pts | Medium | Exception handling |
| 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.4 pts | Medium | Deployment & Rollback |
| Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with Configuration.php (2), Runner.php, InternalProcessorCommand.php. | +1.9 pts | Medium | Knowledge Freshness |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Console.php. | +1.0 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/Application/Console/Formatters/Console.php | 7.2 | Mixed | Cyclomatic Complexity: Console.issues (cyclomatic 17) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Domain/Analyser.php | 7.4 | Mixed | Cyclomatic Complexity: Analyser.analyseFile (cyclomatic 99) |
| src/Domain/Runner.php | 7.8 | Mixed | Cognitive Complexity: Runner.run (cognitive 18) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/Application/Console/Formatters/Json.php | 8.5 | Near-clean | Cognitive Complexity: Json.issues (cognitive 30) |
| src/Application/Console/Formatters/Checkstyle.php | 8.5 | Near-clean | Cognitive Complexity: Checkstyle.format (cognitive 28) |
| src/Application/Console/Formatters/CodeClimate.php | 8.5 | Near-clean | Cognitive Complexity: CodeClimate.issues (cognitive 28) |
| src/Application/Console/Formatters/GithubAction.php | 8.5 | Near-clean | Cognitive Complexity: GithubAction.format (cognitive 22) |
| src/Domain/Collector.php | 8.5 | Near-clean | God Classes: TooManyMethods: Collector |
| src/Application/Console/Commands/InternalProcessorCommand.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (17 corresponding lines) |
| src/Domain/Insights/ClassMethodAverageCyclomaticComplexityIsHigh.php | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 15+ corresponding lines) |
| src/Application/Adapters/Laravel/Preset.php | 8.5 | Near-clean | Code Duplication: Edited copies of one member (4 members, 12+ corresponding lines) |
| src/Application/Adapters/Drupal/Preset.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (9 corresponding lines) |
| src/Domain/InsightLoader/FixerLoader.php | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 5+ corresponding lines) |
| src/Domain/Insights/FixerDecorator.php | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| src/Domain/Insights/ForbiddenFinalClasses.php | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| src/Application/Adapters/Laravel/Commands/InsightsCommand.php | 8.5 | Near-clean | Change Coupling: Change coupling: InsightsCommand.php ↔ InvokableCommand.php |
| composer.json | 9.5 | Near-clean | ADR Quality: No ADRs found |
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 45 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 — 45 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, 53 of 58 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 14 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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)` (8039 LoC, 125 module-visible types across 31 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 — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D43 Malicious Dependencies — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container and League Container and 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, Vue components 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, Vue components is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- P7 Outbound HTTP resilience — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check recognises outbound HTTP clients, their timeouts and resilience policies, and service entry points in .NET, Go, JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang. No service entry point was found in the PHP source it does read, and the rest of this repository's production source is , which it does not read yet — the service may well be there — a gap in this analyzer's language reach, not a finding about the code.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- 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.
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Analyser.analyseFile at 99.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with Analyser.analyseFile (cyclomatic 99). — Refactoring it lifts Cyclomatic Complexity from 7.9 to about 9.1/10.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was Analyser.analyseFile at 171.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with Analyser.analyseFile (cognitive 171). — Refactoring it lifts Cognitive Complexity from 6.8 to about 7.9/10.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Collector.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with Analyser.php. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. 2.5 % of the production lines (220 of 8,779) are in a reported copy. A further 7 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with Console.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with InternalProcessorCommand.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (16 corresponding lines) finding(s) in Code Duplication — start with Runner.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (npm+Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 20 classes have LCOM4 above 3.
D10 · Test Quality
6 skipped (6 with a documented reason), 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 99 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
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/Application/Adapters/Laravel/Commands/InsightsCommand.php. Counted over 22 of the 130 production source files in this repository: 98 are under the ~2,400-byte size floor this dimension measures over, and the remaining 10 have no attributable history left to measure.
D17 · Explicit Debt
0 deducted task-comment markers across 8779 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 15 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
47 % of calls cross a namespace and 1 % 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)
2 finding(s): 0 critical, 1 high, 1 medium, 0 low. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
2 finding(s): 0 critical, 1 high, 1 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
15 of 32 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Application/Console/Formatters/Console.php. Counted over 32 of the 130 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 14 Orphaned file finding(s) in Knowledge Freshness — start with Configuration.php (2), Runner.php, InternalProcessorCommand.php. — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Console.php. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: InsightsCommand.php↔InvokableCommand.php 70%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with InsightsCommand.php. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
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 14 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, `composer`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `npm`, `composer` — add those `package-ecosystem` entries 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
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
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/Domain/FileProcessors/FixerFileProcessor.php:108
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- 0/1 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 55.5 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96.8 | Exemplary | Strongest area. |
| Maturity | 67.4 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55.5 | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 95.1 | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 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.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — process "/bin/sh -c apk add --no-cache --update git && composer install -d /phpinsights --no-dev --no-ansi --no-interaction --no-scripts --no-progress --prefer-dist && echo 'memory_limit = -1' >> /usr/local/etc/php/conf.d/docker-php-memlimit.ini && ln -sfv /phpinsights/bin/phpinsights /usr/bin/phpinsights" did not complete successfully: exit code: 1; likely cause (the repository): a RUN step of the repository's REDACTED exited with code 1 (`/bin/sh -c apk add --no-cache --update git && composer install -d /phpinsights --no-dev --no-ansi --…`): the build's own command failed, for example a compile or test error; runtime evidence skipped The cause is in the repository, not in our sandbox: a RUN step of the repository's REDACTED exited with code 1 (`/bin/sh -c apk add --no-cache --update git && composer install -d /phpinsights --no-dev --no-ansi --…`): the build's own command failed, for example a compile or test error. Nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 14 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- 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.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files).
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not 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
- 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
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 3 finding(s)
- REDACTED
- REDACTED
- Orphaned knowledge src/Application/Console/Formatters/Console.php:1
Serious — 27 finding(s)
- Analyser.analyseFile (cyclomatic 99) src/Domain/Analyser.php:71
- Console.issues (cyclomatic 17) src/Application/Console/Formatters/Console.php:363
- Analyser.analyseFile (cognitive 171) src/Domain/Analyser.php:71
- Console.issues (cognitive 47) src/Application/Console/Formatters/Console.php:363
- Json.issues (cognitive 30) src/Application/Console/Formatters/Json.php:71
- Checkstyle.format (cognitive 28) src/Application/Console/Formatters/Checkstyle.php:34
- CodeClimate.issues (cognitive 28) src/Application/Console/Formatters/CodeClimate.php:49
- Console.formatFix (cognitive 26) src/Application/Console/Formatters/Console.php:155
- GithubAction.format (cognitive 22) src/Application/Console/Formatters/GithubAction.php:45
- Runner.run (cognitive 18) src/Domain/Runner.php:77
- REDACTED
- TooManyMethods: Collector src/Domain/Collector.php:10
- MethodTooLong: Analyser.analyseFile src/Domain/Analyser.php:71
- REDACTED
- Change coupling: InsightsCommand.php ↔ InvokableCommand.php src/Application/Adapters/Laravel/Commands/InsightsCommand.php:1
- Edited copy of a member (18 corresponding lines) src/Application/Console/Formatters/Console.php:271
- Edited copy of a member (17 corresponding lines) src/Application/Console/Commands/InternalProcessorCommand.php:188
- Edited copy of a member (16 corresponding lines) src/Domain/Runner.php:204
- Edited copies of one member (3 members, 15+ corresponding lines) src/Domain/Insights/ClassMethodAverageCyclomaticComplexityIsHigh.php:45
- Edited copies of one member (4 members, 12+ corresponding lines) src/Application/Adapters/Laravel/Preset.php:77
- Edited copy of a member (9 corresponding lines) src/Application/Adapters/Drupal/Preset.php:48
- Edited copies of one member (3 members, 5+ corresponding lines) src/Domain/InsightLoader/FixerLoader.php:23
- Duplicated block (6 lines × 2) src/Domain/Insights/FixerDecorator.php:104
- Duplicated block (7 lines × 2) src/Domain/Insights/ForbiddenFinalClasses.php:29
- No structured logging
- JavaScript dependencies are not locked docs/package.json:6
- Swallowed exception (empty catch) src/Domain/FileProcessors/FixerFileProcessor.php:108
Minor — 20 finding(s)
- Orphaned file src/Domain/Configuration.php:1
- Orphaned file src/Domain/Runner.php:1
- Orphaned file src/Application/Console/Commands/InternalProcessorCommand.php:1
- Orphaned file src/Domain/Insights/SyntaxCheck.php:1
- Orphaned file src/Application/Console/Formatters/Json.php:1
- Orphaned file src/Application/Console/Formatters/GithubAction.php:1
- Orphaned file src/Domain/Insights/FixerDecorator.php:1
- Orphaned file src/Application/Console/Formatters/CodeClimate.php:1
- Orphaned file src/Domain/FileProcessors/FixerFileProcessor.php:1
- Orphaned file src/Domain/Insights/SniffDecorator.php:1
- Orphaned file src/Domain/Insights/ClassMethodAverageCyclomaticComplexityIsHigh.php:1
- Orphaned file src/Application/Console/Formatters/Checkstyle.php:1
- Orphaned file src/Application/Console/Formatters/FormatResolver.php:1
- Orphaned file src/Application/Injectors/Configuration.php:1
- Off-boarding risk: anonymized user #1
- No ADRs found composer.json:79
- Further orphaned files (smaller)
- No ADRs
- Dependabot does not watch npm/composer REDACTED:2
- PHP static analysis does not check null everywhere
Minor — 8 finding(s)
- Skipped (documented): testGetNumberOfThreads tests/Domain/ConfigurationTest.php:81
- Skipped (documented): testItHasNoIssueOnProjectComposerLock tests/Domain/Insights/ForbiddenSecurityIssuesTest.php:14
- Skipped (documented): testHasIssue tests/Domain/Insights/ReadonlyClassTest.php:15
- Skipped (documented): testHasIssueOnFile tests/Domain/Insights/SyntaxCheckTest.php:13
- Skipped (documented): testHasIssueOnDirectory tests/Domain/Insights/SyntaxCheckTest.php:37
- Skipped (documented): testExcludesPathsFromPreset tests/Domain/Insights/SyntaxCheckTest.php:71
- No assertions (declared): testNotFailingOnSemiColonAfterExtendClass tests/Domain/Insights/InvalidPhpCodeTest.php:11
- No assertions (declared): testNotFailingOnUnclosedComment tests/Domain/Insights/InvalidPhpCodeTest.php:21
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-7357d373124f4ec3ab4554348cae47c1/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=616" --report-format json --report-path /tmp/watchdog-gitleaks-7357d373124f4ec3ab4554348cae47c1/history-1.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7357d373124f4ec3ab4554348cae47c1/tree.json --exit-code 0 --source . | 1 | 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 . | 2 | 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 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). | 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 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |