Executive summary
shlinkio/shlink falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 61.0 out of 100 and is rated Adequate, and 43 of its 45 critical findings are security problems.
Production Readiness, at 51.6, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 8.2 points. Adding automated security scanning comes next, worth about 7.1 points. Raising Production Readiness to 70 would lift the score to about 67.7.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirteen settings leave the servers or containers unsafe, and three pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, correcting the unsafe settings and passing outside input through environment variables would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 18,050 lines, about €58,000 to rebuild.
If Production Readiness rose from 51.6 to 70, the lowest score rated Strong, the score would rise from 61.0 to about 67.7.
New since the last survey: 23 findings
- Code Duplication · Edited copy of a member (39 corresponding lines) module/Core/src/Visit/Listener/OrphanVisitsCountTracker.php
- Code Duplication · Edited copy of a member (16 corresponding lines) module/Core/migrations/Version20240318084804.php
- Code Duplication · Edited copy of a member (26 corresponding lines) module/Core/src/EventDispatcher/Async/AbstractNotifyNewShortUrlListener.php
- Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) module/Core/migrations/Version20240227080629.php
- Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) module/Core/src/Exception/DeleteShortUrlException.php
- Code Duplication · Edited copy of a member (15 corresponding lines) module/Core/src/Visit/Listener/OrphanVisitsCountTracker.php
- Code Duplication · Edited copy of a member (13 corresponding lines) module/CLI/src/Command/Api/DeleteKeyCommand.php
- Code Duplication · Edited copy of a member (11 corresponding lines) module/CLI/src/Command/Api/DeleteKeyCommand.php
- Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) module/Core/src/Visit/VisitsStatsHelper.php
- Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) module/Core/src/Exception/TagConflictException.php
- Code Duplication · Edited copy of a member (14 corresponding lines) module/Core/src/ShortUrl/Persistence/ShortUrlsCountFiltering.php
- Code Duplication · Edited copy of a member (13 corresponding lines) module/Core/src/Tag/Paginator/Adapter/AbstractTagsPaginatorAdapter.php
- Code Duplication · Edited copy of a member (8 corresponding lines) module/Rest/src/Exception/MercureException.php
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) module/CLI/src/Command/Tag/GetTagVisitsCommand.php
- Code Duplication · Edited copy of a member (8 corresponding lines) module/Core/src/Visit/Paginator/Adapter/NonOrphanVisitsPaginatorAdapter.php
- Code Duplication · Edited copy of a member (4 corresponding lines) module/Core/migrations/Version20230211171904.php
- Code Duplication · Edited copy of a member (10 corresponding lines) module/Core/src/Visit/Paginator/Adapter/DomainVisitsPaginatorAdapter.php
- Code Duplication · Edited copy of a member (3 corresponding lines) module/Core/migrations/Version20241124112257.php
- Code Duplication · Edited copy of a member (6 corresponding lines) module/Core/src/Visit/Paginator/Adapter/NonOrphanVisitsPaginatorAdapter.php
- Code Duplication · Edited copy of a member (8 corresponding lines) module/Core/src/Visit/Paginator/Adapter/DomainVisitsPaginatorAdapter.php
- Code Duplication · Edited copy of a member (4 corresponding lines) module/Core/src/Domain/Repository/DomainRepository.php
- Coupling · Circular dependency config/autoload/cache.global.php
- Change Coupling · Change coupling: ApiKeyRepository.php ↔ ApiKeyService.php module/Rest/src/ApiKey/Repository/ApiKeyRepository.php
Fixed since the last survey: 4 findings
- Code Duplication · Duplicated block (9 lines × 2) module/Rest/test-api/Fixtures/VisitsFixture.php
- Code Duplication · Duplicated block (8 lines × 2) module/Rest/test-api/Fixtures/VisitsFixture.php
- Documentation (README) · README may be stale
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €58,000 · Estimate
| Cost to rebuild | €19,000 to €97,000, for 323 to 1,024 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 61. 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: 18,050 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 CLI.Input | 2 Core.Model | 3 Core.RedirectRule | 4 Core.ShortUrl.Repository | 5 Core.Util | 6 Core.Visit.Model | 7 Core.Config | 8 Core.ShortUrl.Helper | 9 Core.Tag.Model | 10 Core.Domain.Entity | 11 Core.ShortUrl.Model | 12 Core.ShortUrl.Transformer | 13 Core.Tag | 14 Core.Exception | 15 Core.ShortUrl.Entity | 16 Rest.ApiKey.Model | 17 Core.Visit.Entity | 18 Core.Visit.Repository | 19 Rest.Entity | 20 Core.Matomo | 21 Core.Visit.Geolocation | 22 Rest.Service | 23 Core.EventDispatcher | 24 Core.Config.Options | 25 Core.Domain | 26 Core.EventDispatcher.Async | 27 Core.ShortUrl.Resolver | 28 Core.Visit | 29 Core.Visit.Paginator.Adapter | 30 Rest.Action | 31 CLI.ApiKey | 32 CLI.Command.Domain | 33 CLI.Command.Visit | 34 Core.ErrorHandler | 35 Core.Importer | 36 Core.ShortUrl | 37 CLI.Command.Api | 38 CLI.Command.ShortUrl | 39 Core.Action | 40 Core.ShortUrl.Middleware |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 CLI.Input | ||||||||||||||||||||||||||||||||||||||||
| 2 Core.Model | ||||||||||||||||||||||||||||||||||||||||
| 3 Core.RedirectRule | 4 | |||||||||||||||||||||||||||||||||||||||
| 4 Core.ShortUrl.Repository | 8 | |||||||||||||||||||||||||||||||||||||||
| 5 Core.Util | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 Core.Visit.Model | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 Core.Config | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Core.ShortUrl.Helper | 1 | 1 | 1 | 4 | 4 | |||||||||||||||||||||||||||||||||||
| 9 Core.Tag.Model | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 Core.Domain.Entity | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 Core.ShortUrl.Model | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 12 Core.ShortUrl.Transformer | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Core.Tag | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 Core.Exception | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 15 Core.ShortUrl.Entity | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 Rest.ApiKey.Model | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Core.Visit.Entity | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 Core.Visit.Repository | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 Rest.Entity | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 Core.Matomo | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 Core.Visit.Geolocation | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Rest.Service | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 Core.EventDispatcher | 1 | 2 | 4 | 3 | ||||||||||||||||||||||||||||||||||||
| 24 Core.Config.Options | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 Core.Domain | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 Core.EventDispatcher.Async | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 27 Core.ShortUrl.Resolver | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Core.Visit | 2 | 10 | 2 | 4 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 29 Core.Visit.Paginator.Adapter | 5 | 1 | 5 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 Rest.Action | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 CLI.ApiKey | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 CLI.Command.Domain | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 CLI.Command.Visit | 3 | 1 | 2 | 3 | 3 | |||||||||||||||||||||||||||||||||||
| 34 Core.ErrorHandler | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 Core.Importer | 2 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 36 Core.ShortUrl | 2 | 4 | 3 | 18 | 6 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||
| 37 CLI.Command.Api | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 CLI.Command.ShortUrl | 1 | 2 | 3 | 1 | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||
| 39 Core.Action | 1 | 1 | 3 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 40 Core.ShortUrl.Middleware | 1 | 1 | 2 | 1 | 1 |
3→15 Core.RedirectRule uses Core.ShortUrl.Entity part of a loop✕
- Connections
- 4 pairs of types, where a type in Core.RedirectRule uses a type in Core.ShortUrl.Entity.
- The types involved
Shlinkio.Shlink.Core.RedirectRule.ShortUrlRedirectRuleService→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.RedirectRule.ShortUrlRedirectRuleServiceInterface→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.RedirectRule.ShortUrlRedirectionResolver→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.RedirectRule.ShortUrlRedirectionResolverInterface→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl
- Direction
- Core.RedirectRule uses Core.ShortUrl.Entity, so a change to Core.ShortUrl.Entity can break Core.RedirectRule, while a change to Core.RedirectRule can't break Core.ShortUrl.Entity.
- 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.
4→11 Core.ShortUrl.Repository uses Core.ShortUrl.Model part of a loop✕
- Connections
- 8 pairs of types, where a type in Core.ShortUrl.Repository uses a type in Core.ShortUrl.Model.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Repository.ExpiredShortUrlsRepository→Shlinkio.Shlink.Core.ShortUrl.Model.ExpiredShortUrlsConditionsShlinkio.Shlink.Core.ShortUrl.Repository.ExpiredShortUrlsRepositoryInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ExpiredShortUrlsConditionsShlinkio.Shlink.Core.ShortUrl.Repository.ShortUrlRepository→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlCreationShlinkio.Shlink.Core.ShortUrl.Repository.ShortUrlRepository→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.ShortUrl.Repository.ShortUrlRepository→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlModeShlinkio.Shlink.Core.ShortUrl.Repository.ShortUrlRepositoryInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlCreationShlinkio.Shlink.Core.ShortUrl.Repository.ShortUrlRepositoryInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.ShortUrl.Repository.ShortUrlRepositoryInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlMode
- Direction
- Core.ShortUrl.Repository uses Core.ShortUrl.Model, so a change to Core.ShortUrl.Model can break Core.ShortUrl.Repository, while a change to Core.ShortUrl.Repository can't break Core.ShortUrl.Model.
- 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.
5→24 Core.Util uses Core.Config.Options part of a loop✕
- Connections
- 1 pair of types, where a type in Core.Util uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.Util.RedirectResponseHelper→Shlinkio.Shlink.Core.Config.Options.RedirectOptions
- Direction
- Core.Util uses Core.Config.Options, so a change to Core.Config.Options can break Core.Util, while a change to Core.Util can't break Core.Config.Options.
- 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.
6→2 Core.Visit.Model uses Core.Model✕
- Connections
- 1 pair of types, where a type in Core.Visit.Model uses a type in Core.Model.
- The types involved
Shlinkio.Shlink.Core.Visit.Model.VisitsParams→Shlinkio.Shlink.Core.Model.AbstractInfinitePaginableListParams
- Direction
- Core.Visit.Model uses Core.Model, so a change to Core.Model can break Core.Visit.Model, while a change to Core.Visit.Model can't break Core.Model.
- Position
- Below the diagonal: Core.Visit.Model uses a module listed above it, which is the healthy direction.
6→24 Core.Visit.Model uses Core.Config.Options part of a loop✕
- Connections
- 1 pair of types, where a type in Core.Visit.Model uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.Visit.Model.Visitor→Shlinkio.Shlink.Core.Config.Options.TrackingOptions
- Direction
- Core.Visit.Model uses Core.Config.Options, so a change to Core.Config.Options can break Core.Visit.Model, while a change to Core.Visit.Model can't break Core.Config.Options.
- 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.
7→5 Core.Config uses Core.Util✕
- Connections
- 1 pair of types, where a type in Core.Config uses a type in Core.Util.
- The types involved
Shlinkio.Shlink.Core.Config.NotFoundRedirectResolver→Shlinkio.Shlink.Core.Util.RedirectResponseHelperInterface
- Direction
- Core.Config uses Core.Util, so a change to Core.Util can break Core.Config, while a change to Core.Config can't break Core.Util.
- Position
- Below the diagonal: Core.Config uses a module listed above it, which is the healthy direction.
8→3 Core.ShortUrl.Helper uses Core.RedirectRule✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Helper uses a type in Core.RedirectRule.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlRedirectionBuilder→Shlinkio.Shlink.Core.RedirectRule.ShortUrlRedirectionResolverInterface
- Direction
- Core.ShortUrl.Helper uses Core.RedirectRule, so a change to Core.RedirectRule can break Core.ShortUrl.Helper, while a change to Core.ShortUrl.Helper can't break Core.RedirectRule.
- Position
- Below the diagonal: Core.ShortUrl.Helper uses a module listed above it, which is the healthy direction.
8→4 Core.ShortUrl.Helper uses Core.ShortUrl.Repository✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Helper uses a type in Core.ShortUrl.Repository.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Helper.ShortCodeUniquenessHelper→Shlinkio.Shlink.Core.ShortUrl.Repository.ShortUrlRepositoryInterface
- Direction
- Core.ShortUrl.Helper uses Core.ShortUrl.Repository, so a change to Core.ShortUrl.Repository can break Core.ShortUrl.Helper, while a change to Core.ShortUrl.Helper can't break Core.ShortUrl.Repository.
- Position
- Below the diagonal: Core.ShortUrl.Helper uses a module listed above it, which is the healthy direction.
8→11 Core.ShortUrl.Helper uses Core.ShortUrl.Model part of a loop✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Helper uses a type in Core.ShortUrl.Model.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlStringifier→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifier
- Direction
- Core.ShortUrl.Helper uses Core.ShortUrl.Model, so a change to Core.ShortUrl.Model can break Core.ShortUrl.Helper, while a change to Core.ShortUrl.Helper can't break Core.ShortUrl.Model.
- 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→15 Core.ShortUrl.Helper uses Core.ShortUrl.Entity part of a loop✕
- Connections
- 4 pairs of types, where a type in Core.ShortUrl.Helper uses a type in Core.ShortUrl.Entity.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Helper.ShortCodeUniquenessHelper→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.ShortUrl.Helper.ShortCodeUniquenessHelperInterface→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlRedirectionBuilder→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlRedirectionBuilderInterface→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl
- Direction
- Core.ShortUrl.Helper uses Core.ShortUrl.Entity, so a change to Core.ShortUrl.Entity can break Core.ShortUrl.Helper, while a change to Core.ShortUrl.Helper can't break Core.ShortUrl.Entity.
- 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→24 Core.ShortUrl.Helper uses Core.Config.Options part of a loop✕
- Connections
- 4 pairs of types, where a type in Core.ShortUrl.Helper uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Helper.ShortCodeUniquenessHelper→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptionsShlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlRedirectionBuilder→Shlinkio.Shlink.Core.Config.Options.TrackingOptionsShlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlStringifier→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptionsShlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlTitleResolutionHelper→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptions
- Direction
- Core.ShortUrl.Helper uses Core.Config.Options, so a change to Core.Config.Options can break Core.ShortUrl.Helper, while a change to Core.ShortUrl.Helper can't break Core.Config.Options.
- 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→2 Core.Tag.Model uses Core.Model✕
- Connections
- 2 pairs of types, where a type in Core.Tag.Model uses a type in Core.Model.
- The types involved
Shlinkio.Shlink.Core.Tag.Model.TagsParams→Shlinkio.Shlink.Core.Model.AbstractInfinitePaginableListParamsShlinkio.Shlink.Core.Tag.Model.TagsParams→Shlinkio.Shlink.Core.Model.Ordering
- Direction
- Core.Tag.Model uses Core.Model, so a change to Core.Model can break Core.Tag.Model, while a change to Core.Tag.Model can't break Core.Model.
- Position
- Below the diagonal: Core.Tag.Model uses a module listed above it, which is the healthy direction.
9→6 Core.Tag.Model uses Core.Visit.Model✕
- Connections
- 1 pair of types, where a type in Core.Tag.Model uses a type in Core.Visit.Model.
- The types involved
Shlinkio.Shlink.Core.Tag.Model.TagInfo→Shlinkio.Shlink.Core.Visit.Model.VisitsSummary
- Direction
- Core.Tag.Model uses Core.Visit.Model, so a change to Core.Visit.Model can break Core.Tag.Model, while a change to Core.Tag.Model can't break Core.Visit.Model.
- Position
- Below the diagonal: Core.Tag.Model uses a module listed above it, which is the healthy direction.
10→7 Core.Domain.Entity uses Core.Config✕
- Connections
- 2 pairs of types, where a type in Core.Domain.Entity uses a type in Core.Config.
- The types involved
Shlinkio.Shlink.Core.Domain.Entity.Domain→Shlinkio.Shlink.Core.Config.NotFoundRedirectConfigInterfaceShlinkio.Shlink.Core.Domain.Entity.Domain→Shlinkio.Shlink.Core.Config.NotFoundRedirects
- Direction
- Core.Domain.Entity uses Core.Config, so a change to Core.Config can break Core.Domain.Entity, while a change to Core.Domain.Entity can't break Core.Config.
- Position
- Below the diagonal: Core.Domain.Entity uses a module listed above it, which is the healthy direction.
11→2 Core.ShortUrl.Model uses Core.Model✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Model uses a type in Core.Model.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlsParams→Shlinkio.Shlink.Core.Model.Ordering
- Direction
- Core.ShortUrl.Model uses Core.Model, so a change to Core.Model can break Core.ShortUrl.Model, while a change to Core.ShortUrl.Model can't break Core.Model.
- Position
- Below the diagonal: Core.ShortUrl.Model uses a module listed above it, which is the healthy direction.
11→8 Core.ShortUrl.Model uses Core.ShortUrl.Helper✕
- Connections
- 2 pairs of types, where a type in Core.ShortUrl.Model uses a type in Core.ShortUrl.Helper.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlCreation→Shlinkio.Shlink.Core.ShortUrl.Helper.TitleResolutionModelInterfaceShlinkio.Shlink.Core.ShortUrl.Model.ShortUrlEdition→Shlinkio.Shlink.Core.ShortUrl.Helper.TitleResolutionModelInterface
- Direction
- Core.ShortUrl.Model uses Core.ShortUrl.Helper, so a change to Core.ShortUrl.Helper can break Core.ShortUrl.Model, while a change to Core.ShortUrl.Model can't break Core.ShortUrl.Helper.
- Position
- Below the diagonal: Core.ShortUrl.Model uses a module listed above it, which is the healthy direction.
11→15 Core.ShortUrl.Model uses Core.ShortUrl.Entity part of a loop✕
- Connections
- 3 pairs of types, where a type in Core.ShortUrl.Model uses a type in Core.ShortUrl.Entity.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifier→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.ShortUrl.Model.ShortUrlWithDeps→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.ShortUrl.Model.UrlShorteningResult→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl
- Direction
- Core.ShortUrl.Model uses Core.ShortUrl.Entity, so a change to Core.ShortUrl.Entity can break Core.ShortUrl.Model, while a change to Core.ShortUrl.Model can't break Core.ShortUrl.Entity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→8 Core.ShortUrl.Transformer uses Core.ShortUrl.Helper✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Transformer uses a type in Core.ShortUrl.Helper.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Transformer.ShortUrlDataTransformer→Shlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlStringifierInterface
- Direction
- Core.ShortUrl.Transformer uses Core.ShortUrl.Helper, so a change to Core.ShortUrl.Helper can break Core.ShortUrl.Transformer, while a change to Core.ShortUrl.Transformer can't break Core.ShortUrl.Helper.
- Position
- Below the diagonal: Core.ShortUrl.Transformer uses a module listed above it, which is the healthy direction.
13→2 Core.Tag uses Core.Model✕
- Connections
- 2 pairs of types, where a type in Core.Tag uses a type in Core.Model.
- The types involved
Shlinkio.Shlink.Core.Tag.TagService→Shlinkio.Shlink.Core.Model.RenamingShlinkio.Shlink.Core.Tag.TagServiceInterface→Shlinkio.Shlink.Core.Model.Renaming
- Direction
- Core.Tag uses Core.Model, so a change to Core.Model can break Core.Tag, while a change to Core.Tag can't break Core.Model.
- Position
- Below the diagonal: Core.Tag uses a module listed above it, which is the healthy direction.
13→9 Core.Tag uses Core.Tag.Model✕
- Connections
- 2 pairs of types, where a type in Core.Tag uses a type in Core.Tag.Model.
- The types involved
Shlinkio.Shlink.Core.Tag.TagService→Shlinkio.Shlink.Core.Tag.Model.TagsParamsShlinkio.Shlink.Core.Tag.TagServiceInterface→Shlinkio.Shlink.Core.Tag.Model.TagsParams
- Direction
- Core.Tag uses Core.Tag.Model, so a change to Core.Tag.Model can break Core.Tag, while a change to Core.Tag can't break Core.Tag.Model.
- Position
- Below the diagonal: Core.Tag uses a module listed above it, which is the healthy direction.
14→2 Core.Exception uses Core.Model✕
- Connections
- 1 pair of types, where a type in Core.Exception uses a type in Core.Model.
- The types involved
Shlinkio.Shlink.Core.Exception.TagConflictException→Shlinkio.Shlink.Core.Model.Renaming
- Direction
- Core.Exception uses Core.Model, so a change to Core.Model can break Core.Exception, while a change to Core.Exception can't break Core.Model.
- Position
- Below the diagonal: Core.Exception uses a module listed above it, which is the healthy direction.
14→6 Core.Exception uses Core.Visit.Model✕
- Connections
- 1 pair of types, where a type in Core.Exception uses a type in Core.Visit.Model.
- The types involved
Shlinkio.Shlink.Core.Exception.IpCannotBeLocatedException→Shlinkio.Shlink.Core.Visit.Model.UnlocatableIpType
- Direction
- Core.Exception uses Core.Visit.Model, so a change to Core.Visit.Model can break Core.Exception, while a change to Core.Exception can't break Core.Visit.Model.
- Position
- Below the diagonal: Core.Exception uses a module listed above it, which is the healthy direction.
14→11 Core.Exception uses Core.ShortUrl.Model✕
- Connections
- 2 pairs of types, where a type in Core.Exception uses a type in Core.ShortUrl.Model.
- The types involved
Shlinkio.Shlink.Core.Exception.DeleteShortUrlException→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.Exception.ShortUrlNotFoundException→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifier
- Direction
- Core.Exception uses Core.ShortUrl.Model, so a change to Core.ShortUrl.Model can break Core.Exception, while a change to Core.Exception can't break Core.ShortUrl.Model.
- Position
- Below the diagonal: Core.Exception uses a module listed above it, which is the healthy direction.
15→11 Core.ShortUrl.Entity uses Core.ShortUrl.Model✕
- Connections
- 3 pairs of types, where a type in Core.ShortUrl.Entity uses a type in Core.ShortUrl.Model.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlCreationShlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlEditionShlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlMode
- Direction
- Core.ShortUrl.Entity uses Core.ShortUrl.Model, so a change to Core.ShortUrl.Model can break Core.ShortUrl.Entity, while a change to Core.ShortUrl.Entity can't break Core.ShortUrl.Model.
- Position
- Below the diagonal: Core.ShortUrl.Entity uses a module listed above it, which is the healthy direction.
16→10 Rest.ApiKey.Model uses Core.Domain.Entity✕
- Connections
- 1 pair of types, where a type in Rest.ApiKey.Model uses a type in Core.Domain.Entity.
- The types involved
Shlinkio.Shlink.Rest.ApiKey.Model.RoleDefinition→Shlinkio.Shlink.Core.Domain.Entity.Domain
- Direction
- Rest.ApiKey.Model uses Core.Domain.Entity, so a change to Core.Domain.Entity can break Rest.ApiKey.Model, while a change to Rest.ApiKey.Model can't break Core.Domain.Entity.
- Position
- Below the diagonal: Rest.ApiKey.Model uses a module listed above it, which is the healthy direction.
17→6 Core.Visit.Entity uses Core.Visit.Model✕
- Connections
- 2 pairs of types, where a type in Core.Visit.Entity uses a type in Core.Visit.Model.
- The types involved
Shlinkio.Shlink.Core.Visit.Entity.Visit→Shlinkio.Shlink.Core.Visit.Model.VisitTypeShlinkio.Shlink.Core.Visit.Entity.Visit→Shlinkio.Shlink.Core.Visit.Model.Visitor
- Direction
- Core.Visit.Entity uses Core.Visit.Model, so a change to Core.Visit.Model can break Core.Visit.Entity, while a change to Core.Visit.Entity can't break Core.Visit.Model.
- Position
- Below the diagonal: Core.Visit.Entity uses a module listed above it, which is the healthy direction.
17→15 Core.Visit.Entity uses Core.ShortUrl.Entity✕
- Connections
- 2 pairs of types, where a type in Core.Visit.Entity uses a type in Core.ShortUrl.Entity.
- The types involved
Shlinkio.Shlink.Core.Visit.Entity.ShortUrlVisitsCount→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.Visit.Entity.Visit→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl
- Direction
- Core.Visit.Entity uses Core.ShortUrl.Entity, so a change to Core.ShortUrl.Entity can break Core.Visit.Entity, while a change to Core.Visit.Entity can't break Core.ShortUrl.Entity.
- Position
- Below the diagonal: Core.Visit.Entity uses a module listed above it, which is the healthy direction.
18→11 Core.Visit.Repository uses Core.ShortUrl.Model✕
- Connections
- 2 pairs of types, where a type in Core.Visit.Repository uses a type in Core.ShortUrl.Model.
- The types involved
Shlinkio.Shlink.Core.Visit.Repository.VisitRepository→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.Visit.Repository.VisitRepositoryInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifier
- Direction
- Core.Visit.Repository uses Core.ShortUrl.Model, so a change to Core.ShortUrl.Model can break Core.Visit.Repository, while a change to Core.Visit.Repository can't break Core.ShortUrl.Model.
- Position
- Below the diagonal: Core.Visit.Repository uses a module listed above it, which is the healthy direction.
18→15 Core.Visit.Repository uses Core.ShortUrl.Entity✕
- Connections
- 2 pairs of types, where a type in Core.Visit.Repository uses a type in Core.ShortUrl.Entity.
- The types involved
Shlinkio.Shlink.Core.Visit.Repository.VisitDeleterRepository→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.Visit.Repository.VisitDeleterRepositoryInterface→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl
- Direction
- Core.Visit.Repository uses Core.ShortUrl.Entity, so a change to Core.ShortUrl.Entity can break Core.Visit.Repository, while a change to Core.Visit.Repository can't break Core.ShortUrl.Entity.
- Position
- Below the diagonal: Core.Visit.Repository uses a module listed above it, which is the healthy direction.
19→16 Rest.Entity uses Rest.ApiKey.Model✕
- Connections
- 2 pairs of types, where a type in Rest.Entity uses a type in Rest.ApiKey.Model.
- The types involved
Shlinkio.Shlink.Rest.Entity.ApiKey→Shlinkio.Shlink.Rest.ApiKey.Model.ApiKeyMetaShlinkio.Shlink.Rest.Entity.ApiKey→Shlinkio.Shlink.Rest.ApiKey.Model.RoleDefinition
- Direction
- Rest.Entity uses Rest.ApiKey.Model, so a change to Rest.ApiKey.Model can break Rest.Entity, while a change to Rest.Entity can't break Rest.ApiKey.Model.
- Position
- Below the diagonal: Rest.Entity uses a module listed above it, which is the healthy direction.
20→8 Core.Matomo uses Core.ShortUrl.Helper✕
- Connections
- 1 pair of types, where a type in Core.Matomo uses a type in Core.ShortUrl.Helper.
- The types involved
Shlinkio.Shlink.Core.Matomo.MatomoVisitSender→Shlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlStringifier
- Direction
- Core.Matomo uses Core.ShortUrl.Helper, so a change to Core.ShortUrl.Helper can break Core.Matomo, while a change to Core.Matomo can't break Core.ShortUrl.Helper.
- Position
- Below the diagonal: Core.Matomo uses a module listed above it, which is the healthy direction.
20→17 Core.Matomo uses Core.Visit.Entity✕
- Connections
- 2 pairs of types, where a type in Core.Matomo uses a type in Core.Visit.Entity.
- The types involved
Shlinkio.Shlink.Core.Matomo.MatomoVisitSender→Shlinkio.Shlink.Core.Visit.Entity.VisitShlinkio.Shlink.Core.Matomo.MatomoVisitSenderInterface→Shlinkio.Shlink.Core.Visit.Entity.Visit
- Direction
- Core.Matomo uses Core.Visit.Entity, so a change to Core.Visit.Entity can break Core.Matomo, while a change to Core.Matomo can't break Core.Visit.Entity.
- Position
- Below the diagonal: Core.Matomo uses a module listed above it, which is the healthy direction.
20→18 Core.Matomo uses Core.Visit.Repository✕
- Connections
- 1 pair of types, where a type in Core.Matomo uses a type in Core.Visit.Repository.
- The types involved
Shlinkio.Shlink.Core.Matomo.MatomoVisitSender→Shlinkio.Shlink.Core.Visit.Repository.VisitIterationRepositoryInterface
- Direction
- Core.Matomo uses Core.Visit.Repository, so a change to Core.Visit.Repository can break Core.Matomo, while a change to Core.Matomo can't break Core.Visit.Repository.
- Position
- Below the diagonal: Core.Matomo uses a module listed above it, which is the healthy direction.
21→17 Core.Visit.Geolocation uses Core.Visit.Entity✕
- Connections
- 6 pairs of types, where a type in Core.Visit.Geolocation uses a type in Core.Visit.Entity.
- The types involved
Shlinkio.Shlink.Core.Visit.Geolocation.VisitGeolocationHelperInterface→Shlinkio.Shlink.Core.Visit.Entity.VisitShlinkio.Shlink.Core.Visit.Geolocation.VisitGeolocationHelperInterface→Shlinkio.Shlink.Core.Visit.Entity.VisitLocationShlinkio.Shlink.Core.Visit.Geolocation.VisitLocator→Shlinkio.Shlink.Core.Visit.Entity.VisitShlinkio.Shlink.Core.Visit.Geolocation.VisitLocator→Shlinkio.Shlink.Core.Visit.Entity.VisitLocationShlinkio.Shlink.Core.Visit.Geolocation.VisitToLocationHelper→Shlinkio.Shlink.Core.Visit.Entity.VisitShlinkio.Shlink.Core.Visit.Geolocation.VisitToLocationHelperInterface→Shlinkio.Shlink.Core.Visit.Entity.Visit
- Direction
- Core.Visit.Geolocation uses Core.Visit.Entity, so a change to Core.Visit.Entity can break Core.Visit.Geolocation, while a change to Core.Visit.Geolocation can't break Core.Visit.Entity.
- Position
- Below the diagonal: Core.Visit.Geolocation uses a module listed above it, which is the healthy direction.
21→18 Core.Visit.Geolocation uses Core.Visit.Repository✕
- Connections
- 1 pair of types, where a type in Core.Visit.Geolocation uses a type in Core.Visit.Repository.
- The types involved
Shlinkio.Shlink.Core.Visit.Geolocation.VisitLocator→Shlinkio.Shlink.Core.Visit.Repository.VisitIterationRepositoryInterface
- Direction
- Core.Visit.Geolocation uses Core.Visit.Repository, so a change to Core.Visit.Repository can break Core.Visit.Geolocation, while a change to Core.Visit.Geolocation can't break Core.Visit.Repository.
- Position
- Below the diagonal: Core.Visit.Geolocation uses a module listed above it, which is the healthy direction.
22→2 Rest.Service uses Core.Model✕
- Connections
- 2 pairs of types, where a type in Rest.Service uses a type in Core.Model.
- The types involved
Shlinkio.Shlink.Rest.Service.ApiKeyService→Shlinkio.Shlink.Core.Model.RenamingShlinkio.Shlink.Rest.Service.ApiKeyServiceInterface→Shlinkio.Shlink.Core.Model.Renaming
- Direction
- Rest.Service uses Core.Model, so a change to Core.Model can break Rest.Service, while a change to Rest.Service can't break Core.Model.
- Position
- Below the diagonal: Rest.Service uses a module listed above it, which is the healthy direction.
22→16 Rest.Service uses Rest.ApiKey.Model✕
- Connections
- 2 pairs of types, where a type in Rest.Service uses a type in Rest.ApiKey.Model.
- The types involved
Shlinkio.Shlink.Rest.Service.ApiKeyService→Shlinkio.Shlink.Rest.ApiKey.Model.ApiKeyMetaShlinkio.Shlink.Rest.Service.ApiKeyServiceInterface→Shlinkio.Shlink.Rest.ApiKey.Model.ApiKeyMeta
- Direction
- Rest.Service uses Rest.ApiKey.Model, so a change to Rest.ApiKey.Model can break Rest.Service, while a change to Rest.Service can't break Rest.ApiKey.Model.
- Position
- Below the diagonal: Rest.Service uses a module listed above it, which is the healthy direction.
22→19 Rest.Service uses Rest.Entity✕
- Connections
- 2 pairs of types, where a type in Rest.Service uses a type in Rest.Entity.
- The types involved
Shlinkio.Shlink.Rest.Service.ApiKeyService→Shlinkio.Shlink.Rest.Entity.ApiKeyShlinkio.Shlink.Rest.Service.ApiKeyServiceInterface→Shlinkio.Shlink.Rest.Entity.ApiKey
- Direction
- Rest.Service uses Rest.Entity, so a change to Rest.Entity can break Rest.Service, while a change to Rest.Service can't break Rest.Entity.
- Position
- Below the diagonal: Rest.Service uses a module listed above it, which is the healthy direction.
23→12 Core.EventDispatcher uses Core.ShortUrl.Transformer✕
- Connections
- 1 pair of types, where a type in Core.EventDispatcher uses a type in Core.ShortUrl.Transformer.
- The types involved
Shlinkio.Shlink.Core.EventDispatcher.PublishingUpdatesGenerator→Shlinkio.Shlink.Core.ShortUrl.Transformer.ShortUrlDataTransformerInterface
- Direction
- Core.EventDispatcher uses Core.ShortUrl.Transformer, so a change to Core.ShortUrl.Transformer can break Core.EventDispatcher, while a change to Core.EventDispatcher can't break Core.ShortUrl.Transformer.
- Position
- Below the diagonal: Core.EventDispatcher uses a module listed above it, which is the healthy direction.
23→15 Core.EventDispatcher uses Core.ShortUrl.Entity✕
- Connections
- 2 pairs of types, where a type in Core.EventDispatcher uses a type in Core.ShortUrl.Entity.
- The types involved
Shlinkio.Shlink.Core.EventDispatcher.PublishingUpdatesGenerator→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.EventDispatcher.PublishingUpdatesGeneratorInterface→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl
- Direction
- Core.EventDispatcher uses Core.ShortUrl.Entity, so a change to Core.ShortUrl.Entity can break Core.EventDispatcher, while a change to Core.EventDispatcher can't break Core.ShortUrl.Entity.
- Position
- Below the diagonal: Core.EventDispatcher uses a module listed above it, which is the healthy direction.
23→17 Core.EventDispatcher uses Core.Visit.Entity✕
- Connections
- 4 pairs of types, where a type in Core.EventDispatcher uses a type in Core.Visit.Entity.
- The types involved
Shlinkio.Shlink.Core.EventDispatcher.LocateUnlocatedVisits→Shlinkio.Shlink.Core.Visit.Entity.VisitShlinkio.Shlink.Core.EventDispatcher.LocateUnlocatedVisits→Shlinkio.Shlink.Core.Visit.Entity.VisitLocationShlinkio.Shlink.Core.EventDispatcher.PublishingUpdatesGenerator→Shlinkio.Shlink.Core.Visit.Entity.VisitShlinkio.Shlink.Core.EventDispatcher.PublishingUpdatesGeneratorInterface→Shlinkio.Shlink.Core.Visit.Entity.Visit
- Direction
- Core.EventDispatcher uses Core.Visit.Entity, so a change to Core.Visit.Entity can break Core.EventDispatcher, while a change to Core.EventDispatcher can't break Core.Visit.Entity.
- Position
- Below the diagonal: Core.EventDispatcher uses a module listed above it, which is the healthy direction.
23→21 Core.EventDispatcher uses Core.Visit.Geolocation✕
- Connections
- 3 pairs of types, where a type in Core.EventDispatcher uses a type in Core.Visit.Geolocation.
- The types involved
Shlinkio.Shlink.Core.EventDispatcher.LocateUnlocatedVisits→Shlinkio.Shlink.Core.Visit.Geolocation.VisitGeolocationHelperInterfaceShlinkio.Shlink.Core.EventDispatcher.LocateUnlocatedVisits→Shlinkio.Shlink.Core.Visit.Geolocation.VisitLocatorInterfaceShlinkio.Shlink.Core.EventDispatcher.LocateUnlocatedVisits→Shlinkio.Shlink.Core.Visit.Geolocation.VisitToLocationHelperInterface
- Direction
- Core.EventDispatcher uses Core.Visit.Geolocation, so a change to Core.Visit.Geolocation can break Core.EventDispatcher, while a change to Core.EventDispatcher can't break Core.Visit.Geolocation.
- Position
- Below the diagonal: Core.EventDispatcher uses a module listed above it, which is the healthy direction.
24→5 Core.Config.Options uses Core.Util✕
- Connections
- 1 pair of types, where a type in Core.Config.Options uses a type in Core.Util.
- The types involved
Shlinkio.Shlink.Core.Config.Options.RedirectOptions→Shlinkio.Shlink.Core.Util.RedirectStatus
- Direction
- Core.Config.Options uses Core.Util, so a change to Core.Util can break Core.Config.Options, while a change to Core.Config.Options can't break Core.Util.
- Position
- Below the diagonal: Core.Config.Options uses a module listed above it, which is the healthy direction.
24→7 Core.Config.Options uses Core.Config✕
- Connections
- 1 pair of types, where a type in Core.Config.Options uses a type in Core.Config.
- The types involved
Shlinkio.Shlink.Core.Config.Options.NotFoundRedirectOptions→Shlinkio.Shlink.Core.Config.NotFoundRedirectConfigInterface
- Direction
- Core.Config.Options uses Core.Config, so a change to Core.Config can break Core.Config.Options, while a change to Core.Config.Options can't break Core.Config.
- Position
- Below the diagonal: Core.Config.Options uses a module listed above it, which is the healthy direction.
24→11 Core.Config.Options uses Core.ShortUrl.Model✕
- Connections
- 1 pair of types, where a type in Core.Config.Options uses a type in Core.ShortUrl.Model.
- The types involved
Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptions→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlMode
- Direction
- Core.Config.Options uses Core.ShortUrl.Model, so a change to Core.ShortUrl.Model can break Core.Config.Options, while a change to Core.Config.Options can't break Core.ShortUrl.Model.
- Position
- Below the diagonal: Core.Config.Options uses a module listed above it, which is the healthy direction.
24→23 Core.Config.Options uses Core.EventDispatcher✕
- Connections
- 1 pair of types, where a type in Core.Config.Options uses a type in Core.EventDispatcher.
- The types involved
Shlinkio.Shlink.Core.Config.Options.RealTimeUpdatesOptions→Shlinkio.Shlink.Core.EventDispatcher.Topic
- Direction
- Core.Config.Options uses Core.EventDispatcher, so a change to Core.EventDispatcher can break Core.Config.Options, while a change to Core.Config.Options can't break Core.EventDispatcher.
- Position
- Below the diagonal: Core.Config.Options uses a module listed above it, which is the healthy direction.
25→7 Core.Domain uses Core.Config✕
- Connections
- 2 pairs of types, where a type in Core.Domain uses a type in Core.Config.
- The types involved
Shlinkio.Shlink.Core.Domain.DomainService→Shlinkio.Shlink.Core.Config.NotFoundRedirectsShlinkio.Shlink.Core.Domain.DomainServiceInterface→Shlinkio.Shlink.Core.Config.NotFoundRedirects
- Direction
- Core.Domain uses Core.Config, so a change to Core.Config can break Core.Domain, while a change to Core.Domain can't break Core.Config.
- Position
- Below the diagonal: Core.Domain uses a module listed above it, which is the healthy direction.
25→10 Core.Domain uses Core.Domain.Entity✕
- Connections
- 2 pairs of types, where a type in Core.Domain uses a type in Core.Domain.Entity.
- The types involved
Shlinkio.Shlink.Core.Domain.DomainService→Shlinkio.Shlink.Core.Domain.Entity.DomainShlinkio.Shlink.Core.Domain.DomainServiceInterface→Shlinkio.Shlink.Core.Domain.Entity.Domain
- Direction
- Core.Domain uses Core.Domain.Entity, so a change to Core.Domain.Entity can break Core.Domain, while a change to Core.Domain can't break Core.Domain.Entity.
- Position
- Below the diagonal: Core.Domain uses a module listed above it, which is the healthy direction.
25→24 Core.Domain uses Core.Config.Options✕
- Connections
- 1 pair of types, where a type in Core.Domain uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.Domain.DomainService→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptions
- Direction
- Core.Domain uses Core.Config.Options, so a change to Core.Config.Options can break Core.Domain, while a change to Core.Domain can't break Core.Config.Options.
- Position
- Below the diagonal: Core.Domain uses a module listed above it, which is the healthy direction.
26→17 Core.EventDispatcher.Async uses Core.Visit.Entity✕
- Connections
- 1 pair of types, where a type in Core.EventDispatcher.Async uses a type in Core.Visit.Entity.
- The types involved
Shlinkio.Shlink.Core.EventDispatcher.Async.AbstractNotifyVisitListener→Shlinkio.Shlink.Core.Visit.Entity.Visit
- Direction
- Core.EventDispatcher.Async uses Core.Visit.Entity, so a change to Core.Visit.Entity can break Core.EventDispatcher.Async, while a change to Core.EventDispatcher.Async can't break Core.Visit.Entity.
- Position
- Below the diagonal: Core.EventDispatcher.Async uses a module listed above it, which is the healthy direction.
26→23 Core.EventDispatcher.Async uses Core.EventDispatcher✕
- Connections
- 2 pairs of types, where a type in Core.EventDispatcher.Async uses a type in Core.EventDispatcher.
- The types involved
Shlinkio.Shlink.Core.EventDispatcher.Async.AbstractNotifyNewShortUrlListener→Shlinkio.Shlink.Core.EventDispatcher.PublishingUpdatesGeneratorInterfaceShlinkio.Shlink.Core.EventDispatcher.Async.AbstractNotifyVisitListener→Shlinkio.Shlink.Core.EventDispatcher.PublishingUpdatesGeneratorInterface
- Direction
- Core.EventDispatcher.Async uses Core.EventDispatcher, so a change to Core.EventDispatcher can break Core.EventDispatcher.Async, while a change to Core.EventDispatcher.Async can't break Core.EventDispatcher.
- Position
- Below the diagonal: Core.EventDispatcher.Async uses a module listed above it, which is the healthy direction.
26→24 Core.EventDispatcher.Async uses Core.Config.Options✕
- Connections
- 2 pairs of types, where a type in Core.EventDispatcher.Async uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.EventDispatcher.Async.AbstractNotifyNewShortUrlListener→Shlinkio.Shlink.Core.Config.Options.RealTimeUpdatesOptionsShlinkio.Shlink.Core.EventDispatcher.Async.AbstractNotifyVisitListener→Shlinkio.Shlink.Core.Config.Options.RealTimeUpdatesOptions
- Direction
- Core.EventDispatcher.Async uses Core.Config.Options, so a change to Core.Config.Options can break Core.EventDispatcher.Async, while a change to Core.EventDispatcher.Async can't break Core.Config.Options.
- Position
- Below the diagonal: Core.EventDispatcher.Async uses a module listed above it, which is the healthy direction.
27→10 Core.ShortUrl.Resolver uses Core.Domain.Entity✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Resolver uses a type in Core.Domain.Entity.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Resolver.PersistenceShortUrlRelationResolver→Shlinkio.Shlink.Core.Domain.Entity.Domain
- Direction
- Core.ShortUrl.Resolver uses Core.Domain.Entity, so a change to Core.Domain.Entity can break Core.ShortUrl.Resolver, while a change to Core.ShortUrl.Resolver can't break Core.Domain.Entity.
- Position
- Below the diagonal: Core.ShortUrl.Resolver uses a module listed above it, which is the healthy direction.
27→24 Core.ShortUrl.Resolver uses Core.Config.Options✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Resolver uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Resolver.PersistenceShortUrlRelationResolver→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptions
- Direction
- Core.ShortUrl.Resolver uses Core.Config.Options, so a change to Core.Config.Options can break Core.ShortUrl.Resolver, while a change to Core.ShortUrl.Resolver can't break Core.Config.Options.
- Position
- Below the diagonal: Core.ShortUrl.Resolver uses a module listed above it, which is the healthy direction.
28→2 Core.Visit uses Core.Model✕
- Connections
- 2 pairs of types, where a type in Core.Visit uses a type in Core.Model.
- The types involved
Shlinkio.Shlink.Core.Visit.VisitsDeleter→Shlinkio.Shlink.Core.Model.BulkDeleteResultShlinkio.Shlink.Core.Visit.VisitsDeleterInterface→Shlinkio.Shlink.Core.Model.BulkDeleteResult
- Direction
- Core.Visit uses Core.Model, so a change to Core.Model can break Core.Visit, while a change to Core.Visit can't break Core.Model.
- Position
- Below the diagonal: Core.Visit uses a module listed above it, which is the healthy direction.
28→6 Core.Visit uses Core.Visit.Model✕
- Connections
- 10 pairs of types, where a type in Core.Visit uses a type in Core.Visit.Model.
- The types involved
Shlinkio.Shlink.Core.Visit.VisitsStatsHelper→Shlinkio.Shlink.Core.Visit.Model.OrphanVisitsParamsShlinkio.Shlink.Core.Visit.VisitsStatsHelper→Shlinkio.Shlink.Core.Visit.Model.VisitsParamsShlinkio.Shlink.Core.Visit.VisitsStatsHelper→Shlinkio.Shlink.Core.Visit.Model.VisitsStatsShlinkio.Shlink.Core.Visit.VisitsStatsHelper→Shlinkio.Shlink.Core.Visit.Model.WithDomainVisitsParamsShlinkio.Shlink.Core.Visit.VisitsStatsHelperInterface→Shlinkio.Shlink.Core.Visit.Model.OrphanVisitsParamsShlinkio.Shlink.Core.Visit.VisitsStatsHelperInterface→Shlinkio.Shlink.Core.Visit.Model.VisitsParamsShlinkio.Shlink.Core.Visit.VisitsStatsHelperInterface→Shlinkio.Shlink.Core.Visit.Model.VisitsStatsShlinkio.Shlink.Core.Visit.VisitsStatsHelperInterface→Shlinkio.Shlink.Core.Visit.Model.WithDomainVisitsParamsShlinkio.Shlink.Core.Visit.VisitsTracker→Shlinkio.Shlink.Core.Visit.Model.VisitorShlinkio.Shlink.Core.Visit.VisitsTrackerInterface→Shlinkio.Shlink.Core.Visit.Model.Visitor
- Direction
- Core.Visit uses Core.Visit.Model, so a change to Core.Visit.Model can break Core.Visit, while a change to Core.Visit can't break Core.Visit.Model.
- Position
- Below the diagonal: Core.Visit uses a module listed above it, which is the healthy direction.
28→11 Core.Visit uses Core.ShortUrl.Model✕
- Connections
- 2 pairs of types, where a type in Core.Visit uses a type in Core.ShortUrl.Model.
- The types involved
Shlinkio.Shlink.Core.Visit.VisitsStatsHelper→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.Visit.VisitsStatsHelperInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifier
- Direction
- Core.Visit uses Core.ShortUrl.Model, so a change to Core.ShortUrl.Model can break Core.Visit, while a change to Core.Visit can't break Core.ShortUrl.Model.
- Position
- Below the diagonal: Core.Visit uses a module listed above it, which is the healthy direction.
28→15 Core.Visit uses Core.ShortUrl.Entity✕
- Connections
- 4 pairs of types, where a type in Core.Visit uses a type in Core.ShortUrl.Entity.
- The types involved
Shlinkio.Shlink.Core.Visit.RequestTracker→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.Visit.RequestTrackerInterface→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.Visit.VisitsTracker→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.Visit.VisitsTrackerInterface→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl
- Direction
- Core.Visit uses Core.ShortUrl.Entity, so a change to Core.ShortUrl.Entity can break Core.Visit, while a change to Core.Visit can't break Core.ShortUrl.Entity.
- Position
- Below the diagonal: Core.Visit uses a module listed above it, which is the healthy direction.
28→18 Core.Visit uses Core.Visit.Repository✕
- Connections
- 1 pair of types, where a type in Core.Visit uses a type in Core.Visit.Repository.
- The types involved
Shlinkio.Shlink.Core.Visit.VisitsDeleter→Shlinkio.Shlink.Core.Visit.Repository.VisitDeleterRepositoryInterface
- Direction
- Core.Visit uses Core.Visit.Repository, so a change to Core.Visit.Repository can break Core.Visit, while a change to Core.Visit can't break Core.Visit.Repository.
- Position
- Below the diagonal: Core.Visit uses a module listed above it, which is the healthy direction.
28→24 Core.Visit uses Core.Config.Options✕
- Connections
- 3 pairs of types, where a type in Core.Visit uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.Visit.RequestTracker→Shlinkio.Shlink.Core.Config.Options.TrackingOptionsShlinkio.Shlink.Core.Visit.VisitsStatsHelper→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptionsShlinkio.Shlink.Core.Visit.VisitsTracker→Shlinkio.Shlink.Core.Config.Options.TrackingOptions
- Direction
- Core.Visit uses Core.Config.Options, so a change to Core.Config.Options can break Core.Visit, while a change to Core.Visit can't break Core.Config.Options.
- Position
- Below the diagonal: Core.Visit uses a module listed above it, which is the healthy direction.
29→6 Core.Visit.Paginator.Adapter uses Core.Visit.Model✕
- Connections
- 5 pairs of types, where a type in Core.Visit.Paginator.Adapter uses a type in Core.Visit.Model.
- The types involved
Shlinkio.Shlink.Core.Visit.Paginator.Adapter.DomainVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Visit.Model.VisitsParamsShlinkio.Shlink.Core.Visit.Paginator.Adapter.NonOrphanVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Visit.Model.WithDomainVisitsParamsShlinkio.Shlink.Core.Visit.Paginator.Adapter.OrphanVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Visit.Model.OrphanVisitsParamsShlinkio.Shlink.Core.Visit.Paginator.Adapter.ShortUrlVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Visit.Model.VisitsParamsShlinkio.Shlink.Core.Visit.Paginator.Adapter.TagVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Visit.Model.WithDomainVisitsParams
- Direction
- Core.Visit.Paginator.Adapter uses Core.Visit.Model, so a change to Core.Visit.Model can break Core.Visit.Paginator.Adapter, while a change to Core.Visit.Paginator.Adapter can't break Core.Visit.Model.
- Position
- Below the diagonal: Core.Visit.Paginator.Adapter uses a module listed above it, which is the healthy direction.
29→11 Core.Visit.Paginator.Adapter uses Core.ShortUrl.Model✕
- Connections
- 1 pair of types, where a type in Core.Visit.Paginator.Adapter uses a type in Core.ShortUrl.Model.
- The types involved
Shlinkio.Shlink.Core.Visit.Paginator.Adapter.ShortUrlVisitsPaginatorAdapter→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifier
- Direction
- Core.Visit.Paginator.Adapter uses Core.ShortUrl.Model, so a change to Core.ShortUrl.Model can break Core.Visit.Paginator.Adapter, while a change to Core.Visit.Paginator.Adapter can't break Core.ShortUrl.Model.
- Position
- Below the diagonal: Core.Visit.Paginator.Adapter uses a module listed above it, which is the healthy direction.
29→18 Core.Visit.Paginator.Adapter uses Core.Visit.Repository✕
- Connections
- 5 pairs of types, where a type in Core.Visit.Paginator.Adapter uses a type in Core.Visit.Repository.
- The types involved
Shlinkio.Shlink.Core.Visit.Paginator.Adapter.DomainVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Visit.Repository.VisitRepositoryInterfaceShlinkio.Shlink.Core.Visit.Paginator.Adapter.NonOrphanVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Visit.Repository.VisitRepositoryInterfaceShlinkio.Shlink.Core.Visit.Paginator.Adapter.OrphanVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Visit.Repository.VisitRepositoryInterfaceShlinkio.Shlink.Core.Visit.Paginator.Adapter.ShortUrlVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Visit.Repository.VisitRepositoryInterfaceShlinkio.Shlink.Core.Visit.Paginator.Adapter.TagVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Visit.Repository.VisitRepositoryInterface
- Direction
- Core.Visit.Paginator.Adapter uses Core.Visit.Repository, so a change to Core.Visit.Repository can break Core.Visit.Paginator.Adapter, while a change to Core.Visit.Paginator.Adapter can't break Core.Visit.Repository.
- Position
- Below the diagonal: Core.Visit.Paginator.Adapter uses a module listed above it, which is the healthy direction.
29→24 Core.Visit.Paginator.Adapter uses Core.Config.Options✕
- Connections
- 1 pair of types, where a type in Core.Visit.Paginator.Adapter uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.Visit.Paginator.Adapter.OrphanVisitsPaginatorAdapter→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptions
- Direction
- Core.Visit.Paginator.Adapter uses Core.Config.Options, so a change to Core.Config.Options can break Core.Visit.Paginator.Adapter, while a change to Core.Visit.Paginator.Adapter can't break Core.Config.Options.
- Position
- Below the diagonal: Core.Visit.Paginator.Adapter uses a module listed above it, which is the healthy direction.
30→24 Rest.Action uses Core.Config.Options✕
- Connections
- 1 pair of types, where a type in Rest.Action uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Rest.Action.HealthAction→Shlinkio.Shlink.Core.Config.Options.AppOptions
- Direction
- Rest.Action uses Core.Config.Options, so a change to Core.Config.Options can break Rest.Action, while a change to Rest.Action can't break Core.Config.Options.
- Position
- Below the diagonal: Rest.Action uses a module listed above it, which is the healthy direction.
31→16 CLI.ApiKey uses Rest.ApiKey.Model✕
- Connections
- 1 pair of types, where a type in CLI.ApiKey uses a type in Rest.ApiKey.Model.
- The types involved
Shlinkio.Shlink.CLI.ApiKey.RoleResolver→Shlinkio.Shlink.Rest.ApiKey.Model.RoleDefinition
- Direction
- CLI.ApiKey uses Rest.ApiKey.Model, so a change to Rest.ApiKey.Model can break CLI.ApiKey, while a change to CLI.ApiKey can't break Rest.ApiKey.Model.
- Position
- Below the diagonal: CLI.ApiKey uses a module listed above it, which is the healthy direction.
31→24 CLI.ApiKey uses Core.Config.Options✕
- Connections
- 1 pair of types, where a type in CLI.ApiKey uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.CLI.ApiKey.RoleResolver→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptions
- Direction
- CLI.ApiKey uses Core.Config.Options, so a change to Core.Config.Options can break CLI.ApiKey, while a change to CLI.ApiKey can't break Core.Config.Options.
- Position
- Below the diagonal: CLI.ApiKey uses a module listed above it, which is the healthy direction.
31→25 CLI.ApiKey uses Core.Domain✕
- Connections
- 1 pair of types, where a type in CLI.ApiKey uses a type in Core.Domain.
- The types involved
Shlinkio.Shlink.CLI.ApiKey.RoleResolver→Shlinkio.Shlink.Core.Domain.DomainServiceInterface
- Direction
- CLI.ApiKey uses Core.Domain, so a change to Core.Domain can break CLI.ApiKey, while a change to CLI.ApiKey can't break Core.Domain.
- Position
- Below the diagonal: CLI.ApiKey uses a module listed above it, which is the healthy direction.
32→1 CLI.Command.Domain uses CLI.Input✕
- Connections
- 1 pair of types, where a type in CLI.Command.Domain uses a type in CLI.Input.
- The types involved
Shlinkio.Shlink.CLI.Command.Domain.GetDomainVisitsCommand→Shlinkio.Shlink.CLI.Input.VisitsListInput
- Direction
- CLI.Command.Domain uses CLI.Input, so a change to CLI.Input can break CLI.Command.Domain, while a change to CLI.Command.Domain can't break CLI.Input.
- Position
- Below the diagonal: CLI.Command.Domain uses a module listed above it, which is the healthy direction.
32→7 CLI.Command.Domain uses Core.Config✕
- Connections
- 1 pair of types, where a type in CLI.Command.Domain uses a type in Core.Config.
- The types involved
Shlinkio.Shlink.CLI.Command.Domain.ListDomainsCommand→Shlinkio.Shlink.Core.Config.NotFoundRedirectConfigInterface
- Direction
- CLI.Command.Domain uses Core.Config, so a change to Core.Config can break CLI.Command.Domain, while a change to CLI.Command.Domain can't break Core.Config.
- Position
- Below the diagonal: CLI.Command.Domain uses a module listed above it, which is the healthy direction.
32→25 CLI.Command.Domain uses Core.Domain✕
- Connections
- 2 pairs of types, where a type in CLI.Command.Domain uses a type in Core.Domain.
- The types involved
Shlinkio.Shlink.CLI.Command.Domain.DomainRedirectsCommand→Shlinkio.Shlink.Core.Domain.DomainServiceInterfaceShlinkio.Shlink.CLI.Command.Domain.ListDomainsCommand→Shlinkio.Shlink.Core.Domain.DomainServiceInterface
- Direction
- CLI.Command.Domain uses Core.Domain, so a change to Core.Domain can break CLI.Command.Domain, while a change to CLI.Command.Domain can't break Core.Domain.
- Position
- Below the diagonal: CLI.Command.Domain uses a module listed above it, which is the healthy direction.
32→28 CLI.Command.Domain uses Core.Visit✕
- Connections
- 1 pair of types, where a type in CLI.Command.Domain uses a type in Core.Visit.
- The types involved
Shlinkio.Shlink.CLI.Command.Domain.GetDomainVisitsCommand→Shlinkio.Shlink.Core.Visit.VisitsStatsHelperInterface
- Direction
- CLI.Command.Domain uses Core.Visit, so a change to Core.Visit can break CLI.Command.Domain, while a change to CLI.Command.Domain can't break Core.Visit.
- Position
- Below the diagonal: CLI.Command.Domain uses a module listed above it, which is the healthy direction.
33→1 CLI.Command.Visit uses CLI.Input✕
- Connections
- 3 pairs of types, where a type in CLI.Command.Visit uses a type in CLI.Input.
- The types involved
Shlinkio.Shlink.CLI.Command.Visit.GetNonOrphanVisitsCommand→Shlinkio.Shlink.CLI.Input.VisitsListInputShlinkio.Shlink.CLI.Command.Visit.GetOrphanVisitsCommand→Shlinkio.Shlink.CLI.Input.VisitsListInputShlinkio.Shlink.CLI.Command.Visit.VisitsCommandUtils→Shlinkio.Shlink.CLI.Input.VisitsListInput
- Direction
- CLI.Command.Visit uses CLI.Input, so a change to CLI.Input can break CLI.Command.Visit, while a change to CLI.Command.Visit can't break CLI.Input.
- Position
- Below the diagonal: CLI.Command.Visit uses a module listed above it, which is the healthy direction.
33→14 CLI.Command.Visit uses Core.Exception✕
- Connections
- 1 pair of types, where a type in CLI.Command.Visit uses a type in Core.Exception.
- The types involved
Shlinkio.Shlink.CLI.Command.Visit.DownloadGeoLiteDbCommand→Shlinkio.Shlink.Core.Exception.GeolocationDbUpdateFailedException
- Direction
- CLI.Command.Visit uses Core.Exception, so a change to Core.Exception can break CLI.Command.Visit, while a change to CLI.Command.Visit can't break Core.Exception.
- Position
- Below the diagonal: CLI.Command.Visit uses a module listed above it, which is the healthy direction.
33→17 CLI.Command.Visit uses Core.Visit.Entity✕
- Connections
- 2 pairs of types, where a type in CLI.Command.Visit uses a type in Core.Visit.Entity.
- The types involved
Shlinkio.Shlink.CLI.Command.Visit.LocateVisitsCommand→Shlinkio.Shlink.Core.Visit.Entity.VisitShlinkio.Shlink.CLI.Command.Visit.LocateVisitsCommand→Shlinkio.Shlink.Core.Visit.Entity.VisitLocation
- Direction
- CLI.Command.Visit uses Core.Visit.Entity, so a change to Core.Visit.Entity can break CLI.Command.Visit, while a change to CLI.Command.Visit can't break Core.Visit.Entity.
- Position
- Below the diagonal: CLI.Command.Visit uses a module listed above it, which is the healthy direction.
33→21 CLI.Command.Visit uses Core.Visit.Geolocation✕
- Connections
- 3 pairs of types, where a type in CLI.Command.Visit uses a type in Core.Visit.Geolocation.
- The types involved
Shlinkio.Shlink.CLI.Command.Visit.LocateVisitsCommand→Shlinkio.Shlink.Core.Visit.Geolocation.VisitGeolocationHelperInterfaceShlinkio.Shlink.CLI.Command.Visit.LocateVisitsCommand→Shlinkio.Shlink.Core.Visit.Geolocation.VisitLocatorInterfaceShlinkio.Shlink.CLI.Command.Visit.LocateVisitsCommand→Shlinkio.Shlink.Core.Visit.Geolocation.VisitToLocationHelperInterface
- Direction
- CLI.Command.Visit uses Core.Visit.Geolocation, so a change to Core.Visit.Geolocation can break CLI.Command.Visit, while a change to CLI.Command.Visit can't break Core.Visit.Geolocation.
- Position
- Below the diagonal: CLI.Command.Visit uses a module listed above it, which is the healthy direction.
33→28 CLI.Command.Visit uses Core.Visit✕
- Connections
- 3 pairs of types, where a type in CLI.Command.Visit uses a type in Core.Visit.
- The types involved
Shlinkio.Shlink.CLI.Command.Visit.DeleteOrphanVisitsCommand→Shlinkio.Shlink.Core.Visit.VisitsDeleterInterfaceShlinkio.Shlink.CLI.Command.Visit.GetNonOrphanVisitsCommand→Shlinkio.Shlink.Core.Visit.VisitsStatsHelperInterfaceShlinkio.Shlink.CLI.Command.Visit.GetOrphanVisitsCommand→Shlinkio.Shlink.Core.Visit.VisitsStatsHelperInterface
- Direction
- CLI.Command.Visit uses Core.Visit, so a change to Core.Visit can break CLI.Command.Visit, while a change to CLI.Command.Visit can't break Core.Visit.
- Position
- Below the diagonal: CLI.Command.Visit uses a module listed above it, which is the healthy direction.
34→7 Core.ErrorHandler uses Core.Config✕
- Connections
- 1 pair of types, where a type in Core.ErrorHandler uses a type in Core.Config.
- The types involved
Shlinkio.Shlink.Core.ErrorHandler.NotFoundRedirectHandler→Shlinkio.Shlink.Core.Config.NotFoundRedirectResolverInterface
- Direction
- Core.ErrorHandler uses Core.Config, so a change to Core.Config can break Core.ErrorHandler, while a change to Core.ErrorHandler can't break Core.Config.
- Position
- Below the diagonal: Core.ErrorHandler uses a module listed above it, which is the healthy direction.
34→24 Core.ErrorHandler uses Core.Config.Options✕
- Connections
- 1 pair of types, where a type in Core.ErrorHandler uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.ErrorHandler.NotFoundRedirectHandler→Shlinkio.Shlink.Core.Config.Options.NotFoundRedirectOptions
- Direction
- Core.ErrorHandler uses Core.Config.Options, so a change to Core.Config.Options can break Core.ErrorHandler, while a change to Core.ErrorHandler can't break Core.Config.Options.
- Position
- Below the diagonal: Core.ErrorHandler uses a module listed above it, which is the healthy direction.
34→25 Core.ErrorHandler uses Core.Domain✕
- Connections
- 1 pair of types, where a type in Core.ErrorHandler uses a type in Core.Domain.
- The types involved
Shlinkio.Shlink.Core.ErrorHandler.NotFoundRedirectHandler→Shlinkio.Shlink.Core.Domain.DomainServiceInterface
- Direction
- Core.ErrorHandler uses Core.Domain, so a change to Core.Domain can break Core.ErrorHandler, while a change to Core.ErrorHandler can't break Core.Domain.
- Position
- Below the diagonal: Core.ErrorHandler uses a module listed above it, which is the healthy direction.
34→28 Core.ErrorHandler uses Core.Visit✕
- Connections
- 1 pair of types, where a type in Core.ErrorHandler uses a type in Core.Visit.
- The types involved
Shlinkio.Shlink.Core.ErrorHandler.NotFoundTrackerMiddleware→Shlinkio.Shlink.Core.Visit.RequestTrackerInterface
- Direction
- Core.ErrorHandler uses Core.Visit, so a change to Core.Visit can break Core.ErrorHandler, while a change to Core.ErrorHandler can't break Core.Visit.
- Position
- Below the diagonal: Core.ErrorHandler uses a module listed above it, which is the healthy direction.
35→3 Core.Importer uses Core.RedirectRule✕
- Connections
- 2 pairs of types, where a type in Core.Importer uses a type in Core.RedirectRule.
- The types involved
Shlinkio.Shlink.Core.Importer.ImportedLinksProcessor→Shlinkio.Shlink.Core.RedirectRule.ShortUrlRedirectRuleServiceInterfaceShlinkio.Shlink.Core.Importer.ShortUrlImporting→Shlinkio.Shlink.Core.RedirectRule.ShortUrlRedirectRuleServiceInterface
- Direction
- Core.Importer uses Core.RedirectRule, so a change to Core.RedirectRule can break Core.Importer, while a change to Core.Importer can't break Core.RedirectRule.
- Position
- Below the diagonal: Core.Importer uses a module listed above it, which is the healthy direction.
35→5 Core.Importer uses Core.Util✕
- Connections
- 1 pair of types, where a type in Core.Importer uses a type in Core.Util.
- The types involved
Shlinkio.Shlink.Core.Importer.ImportedLinksProcessor→Shlinkio.Shlink.Core.Util.DoctrineBatchHelperInterface
- Direction
- Core.Importer uses Core.Util, so a change to Core.Util can break Core.Importer, while a change to Core.Importer can't break Core.Util.
- Position
- Below the diagonal: Core.Importer uses a module listed above it, which is the healthy direction.
35→8 Core.Importer uses Core.ShortUrl.Helper✕
- Connections
- 1 pair of types, where a type in Core.Importer uses a type in Core.ShortUrl.Helper.
- The types involved
Shlinkio.Shlink.Core.Importer.ImportedLinksProcessor→Shlinkio.Shlink.Core.ShortUrl.Helper.ShortCodeUniquenessHelperInterface
- Direction
- Core.Importer uses Core.ShortUrl.Helper, so a change to Core.ShortUrl.Helper can break Core.Importer, while a change to Core.Importer can't break Core.ShortUrl.Helper.
- Position
- Below the diagonal: Core.Importer uses a module listed above it, which is the healthy direction.
35→15 Core.Importer uses Core.ShortUrl.Entity✕
- Connections
- 2 pairs of types, where a type in Core.Importer uses a type in Core.ShortUrl.Entity.
- The types involved
Shlinkio.Shlink.Core.Importer.ImportedLinksProcessor→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.Importer.ShortUrlImporting→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl
- Direction
- Core.Importer uses Core.ShortUrl.Entity, so a change to Core.ShortUrl.Entity can break Core.Importer, while a change to Core.Importer can't break Core.ShortUrl.Entity.
- Position
- Below the diagonal: Core.Importer uses a module listed above it, which is the healthy direction.
35→27 Core.Importer uses Core.ShortUrl.Resolver✕
- Connections
- 1 pair of types, where a type in Core.Importer uses a type in Core.ShortUrl.Resolver.
- The types involved
Shlinkio.Shlink.Core.Importer.ImportedLinksProcessor→Shlinkio.Shlink.Core.ShortUrl.Resolver.ShortUrlRelationResolverInterface
- Direction
- Core.Importer uses Core.ShortUrl.Resolver, so a change to Core.ShortUrl.Resolver can break Core.Importer, while a change to Core.Importer can't break Core.ShortUrl.Resolver.
- Position
- Below the diagonal: Core.Importer uses a module listed above it, which is the healthy direction.
36→2 Core.ShortUrl uses Core.Model✕
- Connections
- 2 pairs of types, where a type in Core.ShortUrl uses a type in Core.Model.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.ShortUrlVisitsDeleter→Shlinkio.Shlink.Core.Model.BulkDeleteResultShlinkio.Shlink.Core.ShortUrl.ShortUrlVisitsDeleterInterface→Shlinkio.Shlink.Core.Model.BulkDeleteResult
- Direction
- Core.ShortUrl uses Core.Model, so a change to Core.Model can break Core.ShortUrl, while a change to Core.ShortUrl can't break Core.Model.
- Position
- Below the diagonal: Core.ShortUrl uses a module listed above it, which is the healthy direction.
36→4 Core.ShortUrl uses Core.ShortUrl.Repository✕
- Connections
- 4 pairs of types, where a type in Core.ShortUrl uses a type in Core.ShortUrl.Repository.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.DeleteShortUrlService→Shlinkio.Shlink.Core.ShortUrl.Repository.ExpiredShortUrlsRepositoryInterfaceShlinkio.Shlink.Core.ShortUrl.ShortUrlListService→Shlinkio.Shlink.Core.ShortUrl.Repository.ShortUrlListRepositoryInterfaceShlinkio.Shlink.Core.ShortUrl.ShortUrlResolver→Shlinkio.Shlink.Core.ShortUrl.Repository.ShortUrlRepositoryInterfaceShlinkio.Shlink.Core.ShortUrl.UrlShortener→Shlinkio.Shlink.Core.ShortUrl.Repository.ShortUrlRepositoryInterface
- Direction
- Core.ShortUrl uses Core.ShortUrl.Repository, so a change to Core.ShortUrl.Repository can break Core.ShortUrl, while a change to Core.ShortUrl can't break Core.ShortUrl.Repository.
- Position
- Below the diagonal: Core.ShortUrl uses a module listed above it, which is the healthy direction.
36→8 Core.ShortUrl uses Core.ShortUrl.Helper✕
- Connections
- 3 pairs of types, where a type in Core.ShortUrl uses a type in Core.ShortUrl.Helper.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.ShortUrlService→Shlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlTitleResolutionHelperInterfaceShlinkio.Shlink.Core.ShortUrl.UrlShortener→Shlinkio.Shlink.Core.ShortUrl.Helper.ShortCodeUniquenessHelperInterfaceShlinkio.Shlink.Core.ShortUrl.UrlShortener→Shlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlTitleResolutionHelperInterface
- Direction
- Core.ShortUrl uses Core.ShortUrl.Helper, so a change to Core.ShortUrl.Helper can break Core.ShortUrl, while a change to Core.ShortUrl can't break Core.ShortUrl.Helper.
- Position
- Below the diagonal: Core.ShortUrl uses a module listed above it, which is the healthy direction.
36→11 Core.ShortUrl uses Core.ShortUrl.Model✕
- Connections
- 18 pairs of types, where a type in Core.ShortUrl uses a type in Core.ShortUrl.Model.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.DeleteShortUrlService→Shlinkio.Shlink.Core.ShortUrl.Model.ExpiredShortUrlsConditionsShlinkio.Shlink.Core.ShortUrl.DeleteShortUrlService→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.ShortUrl.DeleteShortUrlServiceInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ExpiredShortUrlsConditionsShlinkio.Shlink.Core.ShortUrl.DeleteShortUrlServiceInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.ShortUrl.ShortUrlListService→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlsParamsShlinkio.Shlink.Core.ShortUrl.ShortUrlListServiceInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlsParamsShlinkio.Shlink.Core.ShortUrl.ShortUrlResolver→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.ShortUrl.ShortUrlResolverInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.ShortUrl.ShortUrlService→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlEditionShlinkio.Shlink.Core.ShortUrl.ShortUrlService→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.ShortUrl.ShortUrlServiceInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlEditionShlinkio.Shlink.Core.ShortUrl.ShortUrlServiceInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.ShortUrl.ShortUrlVisitsDeleter→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.ShortUrl.ShortUrlVisitsDeleterInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.Core.ShortUrl.UrlShortener→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlCreationShlinkio.Shlink.Core.ShortUrl.UrlShortener→Shlinkio.Shlink.Core.ShortUrl.Model.UrlShorteningResultShlinkio.Shlink.Core.ShortUrl.UrlShortenerInterface→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlCreationShlinkio.Shlink.Core.ShortUrl.UrlShortenerInterface→Shlinkio.Shlink.Core.ShortUrl.Model.UrlShorteningResult
- Direction
- Core.ShortUrl uses Core.ShortUrl.Model, so a change to Core.ShortUrl.Model can break Core.ShortUrl, while a change to Core.ShortUrl can't break Core.ShortUrl.Model.
- Position
- Below the diagonal: Core.ShortUrl uses a module listed above it, which is the healthy direction.
36→15 Core.ShortUrl uses Core.ShortUrl.Entity✕
- Connections
- 6 pairs of types, where a type in Core.ShortUrl uses a type in Core.ShortUrl.Entity.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.DeleteShortUrlService→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.ShortUrl.ShortUrlResolver→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.ShortUrl.ShortUrlResolverInterface→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.ShortUrl.ShortUrlService→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.ShortUrl.ShortUrlServiceInterface→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.ShortUrl.UrlShortener→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl
- Direction
- Core.ShortUrl uses Core.ShortUrl.Entity, so a change to Core.ShortUrl.Entity can break Core.ShortUrl, while a change to Core.ShortUrl can't break Core.ShortUrl.Entity.
- Position
- Below the diagonal: Core.ShortUrl uses a module listed above it, which is the healthy direction.
36→18 Core.ShortUrl uses Core.Visit.Repository✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl uses a type in Core.Visit.Repository.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.ShortUrlVisitsDeleter→Shlinkio.Shlink.Core.Visit.Repository.VisitDeleterRepositoryInterface
- Direction
- Core.ShortUrl uses Core.Visit.Repository, so a change to Core.Visit.Repository can break Core.ShortUrl, while a change to Core.ShortUrl can't break Core.Visit.Repository.
- Position
- Below the diagonal: Core.ShortUrl uses a module listed above it, which is the healthy direction.
36→24 Core.ShortUrl uses Core.Config.Options✕
- Connections
- 3 pairs of types, where a type in Core.ShortUrl uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.DeleteShortUrlService→Shlinkio.Shlink.Core.Config.Options.DeleteShortUrlsOptionsShlinkio.Shlink.Core.ShortUrl.ShortUrlListService→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptionsShlinkio.Shlink.Core.ShortUrl.ShortUrlResolver→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptions
- Direction
- Core.ShortUrl uses Core.Config.Options, so a change to Core.Config.Options can break Core.ShortUrl, while a change to Core.ShortUrl can't break Core.Config.Options.
- Position
- Below the diagonal: Core.ShortUrl uses a module listed above it, which is the healthy direction.
36→27 Core.ShortUrl uses Core.ShortUrl.Resolver✕
- Connections
- 2 pairs of types, where a type in Core.ShortUrl uses a type in Core.ShortUrl.Resolver.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.ShortUrlService→Shlinkio.Shlink.Core.ShortUrl.Resolver.ShortUrlRelationResolverInterfaceShlinkio.Shlink.Core.ShortUrl.UrlShortener→Shlinkio.Shlink.Core.ShortUrl.Resolver.ShortUrlRelationResolverInterface
- Direction
- Core.ShortUrl uses Core.ShortUrl.Resolver, so a change to Core.ShortUrl.Resolver can break Core.ShortUrl, while a change to Core.ShortUrl can't break Core.ShortUrl.Resolver.
- Position
- Below the diagonal: Core.ShortUrl uses a module listed above it, which is the healthy direction.
37→19 CLI.Command.Api uses Rest.Entity✕
- Connections
- 1 pair of types, where a type in CLI.Command.Api uses a type in Rest.Entity.
- The types involved
Shlinkio.Shlink.CLI.Command.Api.ListKeysCommand→Shlinkio.Shlink.Rest.Entity.ApiKey
- Direction
- CLI.Command.Api uses Rest.Entity, so a change to Rest.Entity can break CLI.Command.Api, while a change to CLI.Command.Api can't break Rest.Entity.
- Position
- Below the diagonal: CLI.Command.Api uses a module listed above it, which is the healthy direction.
37→22 CLI.Command.Api uses Rest.Service✕
- Connections
- 6 pairs of types, where a type in CLI.Command.Api uses a type in Rest.Service.
- The types involved
Shlinkio.Shlink.CLI.Command.Api.DeleteKeyCommand→Shlinkio.Shlink.Rest.Service.ApiKeyServiceInterfaceShlinkio.Shlink.CLI.Command.Api.DisableKeyCommand→Shlinkio.Shlink.Rest.Service.ApiKeyServiceInterfaceShlinkio.Shlink.CLI.Command.Api.GenerateKeyCommand→Shlinkio.Shlink.Rest.Service.ApiKeyServiceInterfaceShlinkio.Shlink.CLI.Command.Api.InitialApiKeyCommand→Shlinkio.Shlink.Rest.Service.ApiKeyServiceInterfaceShlinkio.Shlink.CLI.Command.Api.ListKeysCommand→Shlinkio.Shlink.Rest.Service.ApiKeyServiceInterfaceShlinkio.Shlink.CLI.Command.Api.RenameApiKeyCommand→Shlinkio.Shlink.Rest.Service.ApiKeyServiceInterface
- Direction
- CLI.Command.Api uses Rest.Service, so a change to Rest.Service can break CLI.Command.Api, while a change to CLI.Command.Api can't break Rest.Service.
- Position
- Below the diagonal: CLI.Command.Api uses a module listed above it, which is the healthy direction.
37→31 CLI.Command.Api uses CLI.ApiKey✕
- Connections
- 1 pair of types, where a type in CLI.Command.Api uses a type in CLI.ApiKey.
- The types involved
Shlinkio.Shlink.CLI.Command.Api.GenerateKeyCommand→Shlinkio.Shlink.CLI.ApiKey.RoleResolverInterface
- Direction
- CLI.Command.Api uses CLI.ApiKey, so a change to CLI.ApiKey can break CLI.Command.Api, while a change to CLI.Command.Api can't break CLI.ApiKey.
- Position
- Below the diagonal: CLI.Command.Api uses a module listed above it, which is the healthy direction.
38→1 CLI.Command.ShortUrl uses CLI.Input✕
- Connections
- 1 pair of types, where a type in CLI.Command.ShortUrl uses a type in CLI.Input.
- The types involved
Shlinkio.Shlink.CLI.Command.ShortUrl.GetShortUrlVisitsCommand→Shlinkio.Shlink.CLI.Input.VisitsListInput
- Direction
- CLI.Command.ShortUrl uses CLI.Input, so a change to CLI.Input can break CLI.Command.ShortUrl, while a change to CLI.Command.ShortUrl can't break CLI.Input.
- Position
- Below the diagonal: CLI.Command.ShortUrl uses a module listed above it, which is the healthy direction.
38→8 CLI.Command.ShortUrl uses Core.ShortUrl.Helper✕
- Connections
- 2 pairs of types, where a type in CLI.Command.ShortUrl uses a type in Core.ShortUrl.Helper.
- The types involved
Shlinkio.Shlink.CLI.Command.ShortUrl.CreateShortUrlCommand→Shlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlStringifierInterfaceShlinkio.Shlink.CLI.Command.ShortUrl.EditShortUrlCommand→Shlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlStringifierInterface
- Direction
- CLI.Command.ShortUrl uses Core.ShortUrl.Helper, so a change to Core.ShortUrl.Helper can break CLI.Command.ShortUrl, while a change to CLI.Command.ShortUrl can't break Core.ShortUrl.Helper.
- Position
- Below the diagonal: CLI.Command.ShortUrl uses a module listed above it, which is the healthy direction.
38→11 CLI.Command.ShortUrl uses Core.ShortUrl.Model✕
- Connections
- 3 pairs of types, where a type in CLI.Command.ShortUrl uses a type in Core.ShortUrl.Model.
- The types involved
Shlinkio.Shlink.CLI.Command.ShortUrl.DeleteShortUrlCommand→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.CLI.Command.ShortUrl.DeleteShortUrlVisitsCommand→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlIdentifierShlinkio.Shlink.CLI.Command.ShortUrl.ListShortUrlsCommand→Shlinkio.Shlink.Core.ShortUrl.Model.ShortUrlsParams
- Direction
- CLI.Command.ShortUrl uses Core.ShortUrl.Model, so a change to Core.ShortUrl.Model can break CLI.Command.ShortUrl, while a change to CLI.Command.ShortUrl can't break Core.ShortUrl.Model.
- Position
- Below the diagonal: CLI.Command.ShortUrl uses a module listed above it, which is the healthy direction.
38→12 CLI.Command.ShortUrl uses Core.ShortUrl.Transformer✕
- Connections
- 1 pair of types, where a type in CLI.Command.ShortUrl uses a type in Core.ShortUrl.Transformer.
- The types involved
Shlinkio.Shlink.CLI.Command.ShortUrl.ListShortUrlsCommand→Shlinkio.Shlink.Core.ShortUrl.Transformer.ShortUrlDataTransformerInterface
- Direction
- CLI.Command.ShortUrl uses Core.ShortUrl.Transformer, so a change to Core.ShortUrl.Transformer can break CLI.Command.ShortUrl, while a change to CLI.Command.ShortUrl can't break Core.ShortUrl.Transformer.
- Position
- Below the diagonal: CLI.Command.ShortUrl uses a module listed above it, which is the healthy direction.
38→24 CLI.Command.ShortUrl uses Core.Config.Options✕
- Connections
- 1 pair of types, where a type in CLI.Command.ShortUrl uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.CLI.Command.ShortUrl.CreateShortUrlCommand→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptions
- Direction
- CLI.Command.ShortUrl uses Core.Config.Options, so a change to Core.Config.Options can break CLI.Command.ShortUrl, while a change to CLI.Command.ShortUrl can't break Core.Config.Options.
- Position
- Below the diagonal: CLI.Command.ShortUrl uses a module listed above it, which is the healthy direction.
38→28 CLI.Command.ShortUrl uses Core.Visit✕
- Connections
- 1 pair of types, where a type in CLI.Command.ShortUrl uses a type in Core.Visit.
- The types involved
Shlinkio.Shlink.CLI.Command.ShortUrl.GetShortUrlVisitsCommand→Shlinkio.Shlink.Core.Visit.VisitsStatsHelperInterface
- Direction
- CLI.Command.ShortUrl uses Core.Visit, so a change to Core.Visit can break CLI.Command.ShortUrl, while a change to CLI.Command.ShortUrl can't break Core.Visit.
- Position
- Below the diagonal: CLI.Command.ShortUrl uses a module listed above it, which is the healthy direction.
38→36 CLI.Command.ShortUrl uses Core.ShortUrl✕
- Connections
- 7 pairs of types, where a type in CLI.Command.ShortUrl uses a type in Core.ShortUrl.
- The types involved
Shlinkio.Shlink.CLI.Command.ShortUrl.CreateShortUrlCommand→Shlinkio.Shlink.Core.ShortUrl.UrlShortenerInterfaceShlinkio.Shlink.CLI.Command.ShortUrl.DeleteExpiredShortUrlsCommand→Shlinkio.Shlink.Core.ShortUrl.DeleteShortUrlServiceInterfaceShlinkio.Shlink.CLI.Command.ShortUrl.DeleteShortUrlCommand→Shlinkio.Shlink.Core.ShortUrl.DeleteShortUrlServiceInterfaceShlinkio.Shlink.CLI.Command.ShortUrl.DeleteShortUrlVisitsCommand→Shlinkio.Shlink.Core.ShortUrl.ShortUrlVisitsDeleterInterfaceShlinkio.Shlink.CLI.Command.ShortUrl.EditShortUrlCommand→Shlinkio.Shlink.Core.ShortUrl.ShortUrlServiceInterfaceShlinkio.Shlink.CLI.Command.ShortUrl.ListShortUrlsCommand→Shlinkio.Shlink.Core.ShortUrl.ShortUrlListServiceInterfaceShlinkio.Shlink.CLI.Command.ShortUrl.ResolveUrlCommand→Shlinkio.Shlink.Core.ShortUrl.ShortUrlResolverInterface
- Direction
- CLI.Command.ShortUrl uses Core.ShortUrl, so a change to Core.ShortUrl can break CLI.Command.ShortUrl, while a change to CLI.Command.ShortUrl can't break Core.ShortUrl.
- Position
- Below the diagonal: CLI.Command.ShortUrl uses a module listed above it, which is the healthy direction.
39→5 Core.Action uses Core.Util✕
- Connections
- 1 pair of types, where a type in Core.Action uses a type in Core.Util.
- The types involved
Shlinkio.Shlink.Core.Action.RedirectAction→Shlinkio.Shlink.Core.Util.RedirectResponseHelperInterface
- Direction
- Core.Action uses Core.Util, so a change to Core.Util can break Core.Action, while a change to Core.Action can't break Core.Util.
- Position
- Below the diagonal: Core.Action uses a module listed above it, which is the healthy direction.
39→8 Core.Action uses Core.ShortUrl.Helper✕
- Connections
- 1 pair of types, where a type in Core.Action uses a type in Core.ShortUrl.Helper.
- The types involved
Shlinkio.Shlink.Core.Action.RedirectAction→Shlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlRedirectionBuilderInterface
- Direction
- Core.Action uses Core.ShortUrl.Helper, so a change to Core.ShortUrl.Helper can break Core.Action, while a change to Core.Action can't break Core.ShortUrl.Helper.
- Position
- Below the diagonal: Core.Action uses a module listed above it, which is the healthy direction.
39→15 Core.Action uses Core.ShortUrl.Entity✕
- Connections
- 3 pairs of types, where a type in Core.Action uses a type in Core.ShortUrl.Entity.
- The types involved
Shlinkio.Shlink.Core.Action.AbstractTrackingAction→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.Action.PixelAction→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrlShlinkio.Shlink.Core.Action.RedirectAction→Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl
- Direction
- Core.Action uses Core.ShortUrl.Entity, so a change to Core.ShortUrl.Entity can break Core.Action, while a change to Core.Action can't break Core.ShortUrl.Entity.
- Position
- Below the diagonal: Core.Action uses a module listed above it, which is the healthy direction.
39→24 Core.Action uses Core.Config.Options✕
- Connections
- 1 pair of types, where a type in Core.Action uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.Action.RobotsAction→Shlinkio.Shlink.Core.Config.Options.RobotsOptions
- Direction
- Core.Action uses Core.Config.Options, so a change to Core.Config.Options can break Core.Action, while a change to Core.Action can't break Core.Config.Options.
- Position
- Below the diagonal: Core.Action uses a module listed above it, which is the healthy direction.
39→28 Core.Action uses Core.Visit✕
- Connections
- 2 pairs of types, where a type in Core.Action uses a type in Core.Visit.
- The types involved
Shlinkio.Shlink.Core.Action.AbstractTrackingAction→Shlinkio.Shlink.Core.Visit.RequestTrackerInterfaceShlinkio.Shlink.Core.Action.RedirectAction→Shlinkio.Shlink.Core.Visit.RequestTrackerInterface
- Direction
- Core.Action uses Core.Visit, so a change to Core.Visit can break Core.Action, while a change to Core.Action can't break Core.Visit.
- Position
- Below the diagonal: Core.Action uses a module listed above it, which is the healthy direction.
39→36 Core.Action uses Core.ShortUrl✕
- Connections
- 2 pairs of types, where a type in Core.Action uses a type in Core.ShortUrl.
- The types involved
Shlinkio.Shlink.Core.Action.AbstractTrackingAction→Shlinkio.Shlink.Core.ShortUrl.ShortUrlResolverInterfaceShlinkio.Shlink.Core.Action.RedirectAction→Shlinkio.Shlink.Core.ShortUrl.ShortUrlResolverInterface
- Direction
- Core.Action uses Core.ShortUrl, so a change to Core.ShortUrl can break Core.Action, while a change to Core.Action can't break Core.ShortUrl.
- Position
- Below the diagonal: Core.Action uses a module listed above it, which is the healthy direction.
40→5 Core.ShortUrl.Middleware uses Core.Util✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Middleware uses a type in Core.Util.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Middleware.ExtraPathRedirectMiddleware→Shlinkio.Shlink.Core.Util.RedirectResponseHelperInterface
- Direction
- Core.ShortUrl.Middleware uses Core.Util, so a change to Core.Util can break Core.ShortUrl.Middleware, while a change to Core.ShortUrl.Middleware can't break Core.Util.
- Position
- Below the diagonal: Core.ShortUrl.Middleware uses a module listed above it, which is the healthy direction.
40→8 Core.ShortUrl.Middleware uses Core.ShortUrl.Helper✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Middleware uses a type in Core.ShortUrl.Helper.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Middleware.ExtraPathRedirectMiddleware→Shlinkio.Shlink.Core.ShortUrl.Helper.ShortUrlRedirectionBuilderInterface
- Direction
- Core.ShortUrl.Middleware uses Core.ShortUrl.Helper, so a change to Core.ShortUrl.Helper can break Core.ShortUrl.Middleware, while a change to Core.ShortUrl.Middleware can't break Core.ShortUrl.Helper.
- Position
- Below the diagonal: Core.ShortUrl.Middleware uses a module listed above it, which is the healthy direction.
40→24 Core.ShortUrl.Middleware uses Core.Config.Options✕
- Connections
- 2 pairs of types, where a type in Core.ShortUrl.Middleware uses a type in Core.Config.Options.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Middleware.ExtraPathRedirectMiddleware→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptionsShlinkio.Shlink.Core.ShortUrl.Middleware.TrimTrailingSlashMiddleware→Shlinkio.Shlink.Core.Config.Options.UrlShortenerOptions
- Direction
- Core.ShortUrl.Middleware uses Core.Config.Options, so a change to Core.Config.Options can break Core.ShortUrl.Middleware, while a change to Core.ShortUrl.Middleware can't break Core.Config.Options.
- Position
- Below the diagonal: Core.ShortUrl.Middleware uses a module listed above it, which is the healthy direction.
40→28 Core.ShortUrl.Middleware uses Core.Visit✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Middleware uses a type in Core.Visit.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Middleware.ExtraPathRedirectMiddleware→Shlinkio.Shlink.Core.Visit.RequestTrackerInterface
- Direction
- Core.ShortUrl.Middleware uses Core.Visit, so a change to Core.Visit can break Core.ShortUrl.Middleware, while a change to Core.ShortUrl.Middleware can't break Core.Visit.
- Position
- Below the diagonal: Core.ShortUrl.Middleware uses a module listed above it, which is the healthy direction.
40→36 Core.ShortUrl.Middleware uses Core.ShortUrl✕
- Connections
- 1 pair of types, where a type in Core.ShortUrl.Middleware uses a type in Core.ShortUrl.
- The types involved
Shlinkio.Shlink.Core.ShortUrl.Middleware.ExtraPathRedirectMiddleware→Shlinkio.Shlink.Core.ShortUrl.ShortUrlResolverInterface
- Direction
- Core.ShortUrl.Middleware uses Core.ShortUrl, so a change to Core.ShortUrl can break Core.ShortUrl.Middleware, while a change to Core.ShortUrl.Middleware can't break Core.ShortUrl.
- Position
- Below the diagonal: Core.ShortUrl.Middleware uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 35 | High / Critical |
| A02:2025 — Security Misconfiguration | 34 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | Medium |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +8.2 pts | Low | REDACTED Scanning |
| Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +7.1 pts | Medium | Security & performance tooling |
| Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding. | +3.2 pts | Medium | Deployment & Rollback |
| Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.2 pts | Low | Supply-chain Provenance & Signing |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +2.3 pts | Medium | Nullable reference types |
| Swallowed exception (caught, then discarded) | +1.3 pts | Medium | Exception handling |
| Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands. | +1.2 pts | Medium | Web-Security Posture |
| Resolve the 9 ADR has no Consequences section finding(s) in ADR Quality — start with 2021-01-17-support-restrictions-and-permissions-in-api-keys.md, 2021-02-07-track-visits-to-base-url-invalid-short-url-and-regular-404.md, 2021-08-05-migrate-to-a-new-caching-library.md. | +0.5 pts | Low | ADR Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| module/Core/src/Tag/Paginator/Adapter/AbstractTagsPaginatorAdapter.php | 6.7 | Mixed | Explicit Debt: FixmeComment |
| module/Core/src/Domain/Repository/DomainRepository.php | 6.7 | Mixed | Explicit Debt: FixmeComment |
| module/Core/src/ShortUrl/Model/ShortUrlCreation.php | 6.7 | Mixed | Explicit Debt: TodoComment |
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 50 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 — 50 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, 153 of 162 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 — 42 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (27 contributor(s) across 4892 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 26 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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)` (17096 LoC, 370 module-visible types across 98 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D32 Data Compliance (PII/GDPR) — 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. `bin/roadrunner-worker.php`, `config/autoload/geolocation.global.php`, `module/CLI/src/Command/Api/DeleteKeyCommand.php`, `module/CLI/src/Command/Api/DisableKeyCommand.php`, `module/CLI/src/Command/Api/GenerateKeyCommand.php`, … (+165 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 64 commits in the last 90 days, yet 38 of 65 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- 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 Laminas ServiceManager 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.
- DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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 measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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").
- 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.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ShortUrlListRepository.createListQueryBuilder at 18. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being EnvVars.defaultValue at 33 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: module/Core/src/Config/EnvVars.php (EnvVars.defaultValue at 33). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with ShortUrlListRepository.createListQueryBuilder (cyclomatic 18). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was ShortUrlListRepository.createListQueryBuilder at 23.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with ShortUrlListRepository.createListQueryBuilder (cognitive 23). — Refactoring it lifts Cognitive Complexity from 9.5 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
8 duplicated block group(s) detected. 3.1 % of the production lines (564 of 18,050) are in a reported copy. A further 21 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with MercureException.php, NonOrphanVisitsPaginatorAdapter.php, DomainVisitsPaginatorAdapter.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with NonUniqueSlugException.php, REDACTED, CreateDatabaseCommand.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with DeleteKeyCommand.php, AbstractTagsPaginatorAdapter.php. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
3 production modules (source-import), 1 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence, with abstractness counted on 1 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Circular dependency finding(s) in Coupling — start with cache.global.php. — One of this dimension's main actionable groups (1 issue-level).
D6 · Cohesion (LCOM4)
0 of 82 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D10 · Test Quality
2 skipped (2 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 593 tests.
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
19 deducted task-comment markers across 18050 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 12 TodoComment finding(s) in Explicit Debt — start with CorsTest.php, ApiKey.php, REDACTED. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 7 FixmeComment finding(s) in Explicit Debt — start with RedirectCondition.php (2), AbstractTagsPaginatorAdapter.php, ShortUrlRepository.php. — One of this dimension's main actionable groups (7 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D20 · ADR Quality
9 of 9 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What to do
- Resolve the 9 ADR has no Consequences section finding(s) in ADR Quality — start with 2021-01-17-support-restrictions-and-permissions-in-api-keys.md, 2021-02-07-track-visits-to-base-url-invalid-short-url-and-regular-404.md, 2021-08-05-migrate-to-a-new-caching-library.md. — One of this dimension's main actionable groups (9 recommendation-level).
D27 · Navigability
52 % of calls cross a namespace and 21 % go through an interface, but 99 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
35 finding(s): 0 critical, 27 high, 8 medium, 0 low. 18 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 172 file(s) — `bin/roadrunner-worker.php` (line 41), `config/autoload/geolocation.global.php` (line 13), `module/CLI/src/Command/Api/DeleteKeyCommand.php` (line 39, line 41), `module/CLI/src/Command/Api/DisableKeyCommand.php` (line 39, line 41), `module/CLI/src/Command/Api/GenerateKeyCommand.php` (line 43, line 46, line 47), … (+167 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) charged to Static Analysis (SAST) — the other 16 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (19 issue-level, 3 of them charged here).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D31 · IaC & Container Security
34 finding(s): 0 critical, 13 high, 17 medium, 4 low.
What to do
- Resolve the 17 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (13), REDACTED, REDACTED. — One of this dimension's main actionable groups (17 warning-level).
- Resolve the 13 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (13 issue-level).
- Resolve the 4 Low IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: ShortUrlCreation.php↔ShortUrlEdition.php 73%; GetTagVisitsCommand.php↔GetOrphanVisitsCommand.php 70%; ApiKeyRepository.php↔ApiKeyService.php 70%
What to do
- Resolve the 7 Change coupling finding(s) in Change Coupling — start with ShortUrlCreation.php, GetTagVisitsCommand.php, ApiKeyRepository.php. — One of this dimension's main actionable groups (7 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 42 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
AC3 · Page structure
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — module/Core/templates/404.html:26
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
AX10 · Code composition
AX3 · Project dependency cycles
- The projects config → module → config form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — config/autoload/cache.global.php:5
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
DM10 · One transaction, one aggregate
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add phpstan or psalm (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
P8 · Schema migrations
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `mercure_proxy_vhost.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — data/infra/mercure_proxy_vhost.conf:1
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — module/Rest/src/Action/HealthAction.php:38, module/Core/src/ShortUrl/Helper/ShortUrlTitleResolutionHelper.php:92
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
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.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 64.1 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 80.0 | Adequate — gated by D5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 79.9 | Strong | Solid. |
| Readiness | 51.6 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 66.0 | Adequate — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100.0 | Exemplary | Strongest area. |
| Accessibility | 75.0 | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 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 — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- 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 — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c docker-php-ext-install pdo_mysql" 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 docker-php-ext-install pdo_mysql`): 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 docker-php-ext-install pdo_mysql`): 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 — 42 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
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 9 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- D32 Data Compliance (PII/GDPR) — 170 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (command argument 1, environment variable 2); M4 checks only links and versions and artefact counts.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the PHP source, so there is no service whose uptime a failing dependency could take down
- 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.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- 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.
- 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 — 45 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Project dependency cycle config/autoload/cache.global.php:5
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Circular dependency config/autoload/cache.global.php:5
Serious — 92 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment module/Rest/test-api/Middleware/CorsTest.php:72
- TodoComment module/Rest/src/Entity/ApiKey.php:26
- TodoComment REDACTED:282
- TodoComment module/Core/src/ShortUrl/Model/ShortUrlCreation.php:92
- TodoComment module/Core/src/ShortUrl/Model/ShortUrlEdition.php:60
- TodoComment module/Core/src/RedirectRule/Model/RedirectConditionType.php:38
- TodoComment module/Core/src/Geolocation/GeolocationDbUpdater.php:29
- TodoComment module/Core/src/Exception/ValidationException.php:44
- TodoComment module/Core/functions/functions.php:255
- TodoComment module/Core/config/entities-mappings/Shlinkio.Shlink.Core.ShortUrl.Entity.ShortUrl.php:96
- TodoComment module/CLI/src/Command/Integration/MatomoSendVisitsCommand.php:76
- TodoComment config/test/test_config.global.php:142
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FixmeComment module/Core/src/Tag/Paginator/Adapter/AbstractTagsPaginatorAdapter.php:32
- FixmeComment module/Core/src/ShortUrl/Repository/ShortUrlRepository.php:41
- FixmeComment module/Core/src/RedirectRule/Entity/RedirectCondition.php:263
- FixmeComment module/Core/src/RedirectRule/Entity/RedirectCondition.php:267
- FixmeComment module/Core/src/Geolocation/GeolocationDbUpdater.php:84
- FixmeComment module/Core/src/Domain/Repository/DomainRepository.php:83
- FixmeComment module/Core/migrations/Version20260607082210.php:58
- Change coupling: ShortUrlCreation.php ↔ ShortUrlEdition.php module/Core/src/ShortUrl/Model/ShortUrlCreation.php:1
- Change coupling: GetTagVisitsCommand.php ↔ GetOrphanVisitsCommand.php module/CLI/src/Command/Tag/GetTagVisitsCommand.php:1
- Change coupling: ApiKeyRepository.php ↔ ApiKeyService.php module/Rest/src/ApiKey/Repository/ApiKeyRepository.php:1
- Change coupling: NotifyNewShortUrlToRabbitMq.php ↔ NotifyVisitToRabbitMq.php module/Core/src/EventDispatcher/RabbitMq/NotifyNewShortUrlToRabbitMq.php:1
- Change coupling: GetShortUrlVisitsCommand.php ↔ GetTagVisitsCommand.php module/CLI/src/Command/ShortUrl/GetShortUrlVisitsCommand.php:1
- Change coupling: TagService.php ↔ UpdateTagAction.php module/Core/src/Tag/TagService.php:1
- Change coupling: OrphanVisitsPaginatorAdapter.php ↔ REDACTED module/Core/src/Visit/Paginator/Adapter/OrphanVisitsPaginatorAdapter.php:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (8 corresponding lines) module/Rest/src/Exception/MercureException.php:22
- Edited copy of a member (8 corresponding lines) module/Core/src/Visit/Paginator/Adapter/NonOrphanVisitsPaginatorAdapter.php:39
- Edited copy of a member (8 corresponding lines) module/Core/src/Visit/Paginator/Adapter/DomainVisitsPaginatorAdapter.php:31
- Duplicated block (6 lines × 2) module/Core/src/Exception/NonUniqueSlugException.php:24
- Duplicated block (6 lines × 2) REDACTED:108
- Duplicated block (6 lines × 2) module/CLI/src/Command/Db/CreateDatabaseCommand.php:48
- Edited copy of a member (13 corresponding lines) module/CLI/src/Command/Api/DeleteKeyCommand.php:67
- Edited copy of a member (13 corresponding lines) module/Core/src/Tag/Paginator/Adapter/AbstractTagsPaginatorAdapter.php:31
- Edited copies of one member (3 members, 9+ corresponding lines) module/Core/src/Visit/VisitsStatsHelper.php:75
- Edited copies of one member (3 members, 9+ corresponding lines) module/Core/src/Exception/TagConflictException.php:24
- Edited copy of a member (4 corresponding lines) module/Core/migrations/Version20230211171904.php:19
- Edited copy of a member (4 corresponding lines) module/Core/src/Domain/Repository/DomainRepository.php:57
- Duplicated block (10 lines × 2) module/Core/src/Visit/Listener/OrphanVisitsCountTracker.php:109
- Duplicated block (10 lines × 2) module/Core/src/Visit/Listener/OrphanVisitsCountTracker.php:138
- Swallowed exception (caught, then discarded) module/Rest/src/Action/HealthAction.php:38
- Swallowed exception (caught, then discarded) module/Core/src/ShortUrl/Helper/ShortUrlTitleResolutionHelper.php:92
- Heading level jumps from h1 to h3 module/Core/templates/404.html:26
- ShortUrlListRepository.createListQueryBuilder (cyclomatic 18) REDACTED:95
- ShortUrlListRepository.createListQueryBuilder (cognitive 23) REDACTED:95
- REDACTED
- Edited copy of a member (39 corresponding lines) module/Core/src/Visit/Listener/OrphanVisitsCountTracker.php:109
- Edited copy of a member (16 corresponding lines) module/Core/migrations/Version20240318084804.php:19
- Edited copy of a member (26 corresponding lines) module/Core/src/EventDispatcher/Async/AbstractNotifyNewShortUrlListener.php:29
- Edited copies of one member (3 members, 25+ corresponding lines) module/Core/migrations/Version20240227080629.php:28
- Edited copies of one member (3 members, 14+ corresponding lines) module/Core/src/Exception/DeleteShortUrlException.php:24
- Edited copy of a member (15 corresponding lines) module/Core/src/Visit/Listener/OrphanVisitsCountTracker.php:52
- Edited copy of a member (11 corresponding lines) module/CLI/src/Command/Api/DeleteKeyCommand.php:49
- Edited copy of a member (14 corresponding lines) module/Core/src/ShortUrl/Persistence/ShortUrlsCountFiltering.php:52
- Edited copies of one member (3 members, 7+ corresponding lines) module/CLI/src/Command/Tag/GetTagVisitsCommand.php:42
- Edited copy of a member (10 corresponding lines) module/Core/src/Visit/Paginator/Adapter/DomainVisitsPaginatorAdapter.php:44
- Edited copy of a member (3 corresponding lines) module/Core/migrations/Version20241124112257.php:33
- Edited copy of a member (6 corresponding lines) module/Core/src/Visit/Paginator/Adapter/NonOrphanVisitsPaginatorAdapter.php:28
- Duplicated block (18–19 lines × 2) module/Core/src/Visit/Listener/OrphanVisitsCountTracker.php:120
- Duplicated block (9 lines × 2) module/Core/src/Visit/Listener/OrphanVisitsCountTracker.php:35
- Duplicated block (8 lines × 2) module/Core/src/Exception/ForbiddenTagOperationException.php:32
- Coverage collected but not gated
Minor — 23 finding(s)
- ADR has no Consequences section docs/adr/2021-01-17-support-restrictions-and-permissions-in-api-keys.md:1
- ADR has no Consequences section docs/adr/2021-02-07-track-visits-to-base-url-invalid-short-url-and-regular-404.md:1
- ADR has no Consequences section docs/adr/2021-08-05-migrate-to-a-new-caching-library.md:1
- ADR has no Consequences section docs/adr/2022-01-15-update-env-vars-behavior-to-have-precedence-over-installer-options.md:1
- ADR has no Consequences section docs/adr/2022-08-05-support-multi-segment-custom-slugs.md:1
- ADR has no Consequences section docs/adr/2023-01-06-support-any-http-method-in-short-urls.md:1
- ADR has no Consequences section docs/adr/2023-07-09-build-latest-docker-image-only-for-actual-releases.md:1
- ADR has no Consequences section docs/adr/2024-10-24-handle-dev-and-tests-config-via-env-vars-instead-of-local-config-files.md:1
- ADR has no Consequences section docs/adr/2026-05-14-map-requests-using-valinor.md:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No SAST REDACTED:4
- No rollback/health safety
- No security response headers detected data/infra/mercure_proxy_vhost.conf:1
- Duplicated predicate module/Core/src/Visit/Listener/OrphanVisitsCountTracker.php:63
- PHP static analysis does not check null everywhere
Minor — 2 finding(s)
- Skipped (documented): malformedLookupsPreservePostgresTransactionsAndEarlierWrites module/Core/test-db/ShortUrl/Repository/ShortUrlRepositoryTest.php:173
- Skipped (documented): missingTablesAreNotReportedAsMissingShortUrls module/Core/test-db/ShortUrl/Repository/ShortUrlRepositoryTest.php:237
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-122754610ceb4069b9c327208db8ae30/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-122754610ceb4069b9c327208db8ae30/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-122754610ceb4069b9c327208db8ae30/history-2.json --exit-code 0 --source . | 4 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=701" --report-format json --report-path /tmp/watchdog-gitleaks-122754610ceb4069b9c327208db8ae30/history-3.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-3.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-122754610ceb4069b9c327208db8ae30/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 . | 35 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 34 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 170 file(s) — `bin/roadrunner-worker.php`, `config/autoload/geolocation.global.php`, `module/CLI/src/Command/Api/DeleteKeyCommand.php`, `module/CLI/src/Command/Api/DisableKeyCommand.php`, `module/CLI/src/Command/Api/GenerateKeyCommand.php`, … (+165 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |