Executive summary
archtechx/tenancy falls short of our standard for production, in part because we found no logging, tracing or health checks in the code. It scores 52.4 out of 100 and is rated Adequate, and 19 of its 22 critical findings are security problems in the build pipeline and in its servers and containers.
Production Readiness, at 34.4, is the weakest lens and counts most in the score. The best first steps are logging through a logging library and planning backups and recovery, each worth about 7.2 points. Raising Production Readiness to 70 would lift the score to about 67.0.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five settings leave the servers or containers unsafe, and two pipeline steps run downloads nobody checks. Pinning each tool to an exact version, correcting the unsafe settings and checking each download against a checksum would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command. 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 12,065 lines, about €26,000 to rebuild.
If Production Readiness rose from 34.4 to 70, the lowest score rated Strong, the score would rise from 52.4 to about 67.0.
New since the last survey: 19 findings
- Cyclomatic Complexity · CheckTenantForMaintenanceMode.handle (cyclomatic 16) src/Middleware/CheckTenantForMaintenanceMode.php
- Code Duplication · Edited copy of a member (42 corresponding lines) src/Commands/Migrate.php
- Code Duplication · Edited copy of a member (29 corresponding lines) src/Bootstrappers/BroadcastChannelPrefixBootstrapper.php
- Code Duplication · Edited copy of a member (24 corresponding lines) src/Bootstrappers/PersistentQueueTenancyBootstrapper.php
- Code Duplication · Edited copy of a member (16 corresponding lines) src/Bootstrappers/CacheTenancyBootstrapper.php
- Code Duplication · Edited copy of a member (17 corresponding lines) src/Database/TenantDatabaseManagers/PermissionControlledMicrosoftSQLServerDatabaseManager.php
- Code Duplication · Edited copy of a member (10 corresponding lines) src/Database/Concerns/BelongsToPrimaryModel.php
- Code Duplication · Edited copy of a member (14 corresponding lines) src/Bootstrappers/BroadcastingConfigBootstrapper.php
- Code Duplication · Edited copy of a member (8 corresponding lines) src/Actions/CreateStorageSymlinksAction.php
- Code Duplication · Edited copy of a member (7 corresponding lines) src/Database/Concerns/BelongsToPrimaryModel.php
- Coupling · Circular dependency src/TenancyServiceProvider.php
- Coupling · Unstable project src/Jobs
- Coupling · Unstable project src/ResourceSyncing
- Coupling · Off the main sequence: typedefs
- Coupling · Off the main sequence: src/Events
- Explicit Debt · TodoComment tests/CommandsTest.php
- Explicit Debt · TodoComment tests/RLS/PolicyTest.php
- Explicit Debt · TodoComment tests/Bootstrappers/DatabaseTenancyBootstrapperTest.php
- Explicit Debt · TodoComment tests/RLS/PolicyTest.php
Fixed since the last survey: 2 findings
- Explicit Debt · TodoComment tests/RLS/PolicyTest.php
- Documentation (README) · README may be stale
Rebuild cost: about €26,000 · Estimate
| Cost to rebuild | €8,700 to €44,000, for 146 to 462 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. 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: 12,065 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 (global) | 2 App.Providers | 3 Stancl.Tenancy.Contracts | 4 Stancl.Tenancy.Controllers | 5 Stancl.Tenancy.Enums | 6 Stancl.Tenancy.Facades | 7 Stancl.Tenancy.Overrides | 8 Stancl.Tenancy.RLS.Exceptions | 9 Stancl.Tenancy.RLS.PolicyManagers | 10 Stancl.Tenancy.ResourceSyncing | 11 Stancl.Tenancy | 12 Stancl.Tenancy.Actions | 13 Stancl.Tenancy.Bootstrappers.Integrations | 14 Stancl.Tenancy.Concerns | 15 Stancl.Tenancy.Database.Contracts | 16 Stancl.Tenancy.Database.Exceptions | 17 Stancl.Tenancy.Exceptions | 18 Stancl.Tenancy.Features | 19 Stancl.Tenancy.Resolvers.Contracts | 20 Stancl.Tenancy.UniqueIdentifierGenerators | 21 Stancl.Tenancy.Database | 22 Stancl.Tenancy.Events.Contracts | 23 Stancl.Tenancy.Resolvers | 24 Stancl.Tenancy.ResourceSyncing.Events | 25 Stancl.Tenancy.Bootstrappers | 26 Stancl.Tenancy.Database.Concerns | 27 Stancl.Tenancy.Database.Models | 28 Stancl.Tenancy.Database.TenantDatabaseManagers | 29 Stancl.Tenancy.Events | 30 Stancl.Tenancy.Jobs | 31 Stancl.Tenancy.Middleware | 32 Stancl.Tenancy.Commands | 33 Stancl.Tenancy.Listeners | 34 Stancl.Tenancy.ResourceSyncing.Listeners |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||
| 2 App.Providers | ||||||||||||||||||||||||||||||||||
| 3 Stancl.Tenancy.Contracts | ||||||||||||||||||||||||||||||||||
| 4 Stancl.Tenancy.Controllers | ||||||||||||||||||||||||||||||||||
| 5 Stancl.Tenancy.Enums | ||||||||||||||||||||||||||||||||||
| 6 Stancl.Tenancy.Facades | ||||||||||||||||||||||||||||||||||
| 7 Stancl.Tenancy.Overrides | ||||||||||||||||||||||||||||||||||
| 8 Stancl.Tenancy.RLS.Exceptions | ||||||||||||||||||||||||||||||||||
| 9 Stancl.Tenancy.RLS.PolicyManagers | ||||||||||||||||||||||||||||||||||
| 10 Stancl.Tenancy.ResourceSyncing | ||||||||||||||||||||||||||||||||||
| 11 Stancl.Tenancy | 1 | |||||||||||||||||||||||||||||||||
| 12 Stancl.Tenancy.Actions | 2 | |||||||||||||||||||||||||||||||||
| 13 Stancl.Tenancy.Bootstrappers.Integrations | 4 | |||||||||||||||||||||||||||||||||
| 14 Stancl.Tenancy.Concerns | 1 | 2 | ||||||||||||||||||||||||||||||||
| 15 Stancl.Tenancy.Database.Contracts | 1 | 2 | ||||||||||||||||||||||||||||||||
| 16 Stancl.Tenancy.Database.Exceptions | 2 | |||||||||||||||||||||||||||||||||
| 17 Stancl.Tenancy.Exceptions | 7 | |||||||||||||||||||||||||||||||||
| 18 Stancl.Tenancy.Features | 7 | |||||||||||||||||||||||||||||||||
| 19 Stancl.Tenancy.Resolvers.Contracts | 2 | |||||||||||||||||||||||||||||||||
| 20 Stancl.Tenancy.UniqueIdentifierGenerators | 6 | |||||||||||||||||||||||||||||||||
| 21 Stancl.Tenancy.Database | 2 | |||||||||||||||||||||||||||||||||
| 22 Stancl.Tenancy.Events.Contracts | 2 | 1 | ||||||||||||||||||||||||||||||||
| 23 Stancl.Tenancy.Resolvers | 3 | 3 | ||||||||||||||||||||||||||||||||
| 24 Stancl.Tenancy.ResourceSyncing.Events | 2 | |||||||||||||||||||||||||||||||||
| 25 Stancl.Tenancy.Bootstrappers | 34 | 1 | 2 | |||||||||||||||||||||||||||||||
| 26 Stancl.Tenancy.Database.Concerns | 2 | 1 | 2 | |||||||||||||||||||||||||||||||
| 27 Stancl.Tenancy.Database.Models | 2 | 1 | ||||||||||||||||||||||||||||||||
| 28 Stancl.Tenancy.Database.TenantDatabaseManagers | 12 | 4 | ||||||||||||||||||||||||||||||||
| 29 Stancl.Tenancy.Events | 46 | |||||||||||||||||||||||||||||||||
| 30 Stancl.Tenancy.Jobs | 3 | 1 | ||||||||||||||||||||||||||||||||
| 31 Stancl.Tenancy.Middleware | 3 | 3 | ||||||||||||||||||||||||||||||||
| 32 Stancl.Tenancy.Commands | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 33 Stancl.Tenancy.Listeners | 3 | 5 | 2 | |||||||||||||||||||||||||||||||
| 34 Stancl.Tenancy.ResourceSyncing.Listeners | 1 | 1 | 6 | 1 | 7 |
11→3 Stancl.Tenancy uses Stancl.Tenancy.Contracts✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Tenancy→Stancl.Tenancy.Contracts.Tenant
- Direction
- Stancl.Tenancy uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy, while a change to Stancl.Tenancy can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy uses a module listed above it, which is the healthy direction.
12→3 Stancl.Tenancy.Actions uses Stancl.Tenancy.Contracts✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Actions uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Actions.CreateStorageSymlinksAction→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Actions.RemoveStorageSymlinksAction→Stancl.Tenancy.Contracts.Tenant
- Direction
- Stancl.Tenancy.Actions uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Actions, while a change to Stancl.Tenancy.Actions can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Actions uses a module listed above it, which is the healthy direction.
13→3 Stancl.Tenancy.Bootstrappers.Integrations uses Stancl.Tenancy.Contracts✕
- Connections
- 4 pairs of types, where a type in Stancl.Tenancy.Bootstrappers.Integrations uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Bootstrappers.Integrations.FortifyRouteBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.Integrations.FortifyRouteBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.Integrations.ScoutPrefixBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.Integrations.ScoutPrefixBootstrapper→Stancl.Tenancy.Contracts.Tenant
- Direction
- Stancl.Tenancy.Bootstrappers.Integrations uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Bootstrappers.Integrations, while a change to Stancl.Tenancy.Bootstrappers.Integrations can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Bootstrappers.Integrations uses a module listed above it, which is the healthy direction.
14→3 Stancl.Tenancy.Concerns uses Stancl.Tenancy.Contracts✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.Concerns uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Concerns.DealsWithTenantSymlinks→Stancl.Tenancy.Contracts.Tenant
- Direction
- Stancl.Tenancy.Concerns uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Concerns, while a change to Stancl.Tenancy.Concerns can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Concerns uses a module listed above it, which is the healthy direction.
14→5 Stancl.Tenancy.Concerns uses Stancl.Tenancy.Enums✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Concerns uses a type in Stancl.Tenancy.Enums.
- The types involved
Stancl.Tenancy.Concerns.DealsWithRouteContexts→Stancl.Tenancy.Enums.RouteModeStancl.Tenancy.Concerns.UsableWithEarlyIdentification→Stancl.Tenancy.Enums.Context
- Direction
- Stancl.Tenancy.Concerns uses Stancl.Tenancy.Enums, so a change to Stancl.Tenancy.Enums can break Stancl.Tenancy.Concerns, while a change to Stancl.Tenancy.Concerns can't break Stancl.Tenancy.Enums.
- Position
- Below the diagonal: Stancl.Tenancy.Concerns uses a module listed above it, which is the healthy direction.
15→3 Stancl.Tenancy.Database.Contracts uses Stancl.Tenancy.Contracts✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.Database.Contracts uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Database.Contracts.TenantWithDatabase→Stancl.Tenancy.Contracts.Tenant
- Direction
- Stancl.Tenancy.Database.Contracts uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Database.Contracts, while a change to Stancl.Tenancy.Database.Contracts can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Database.Contracts uses a module listed above it, which is the healthy direction.
15→21 Stancl.Tenancy.Database.Contracts uses Stancl.Tenancy.Database part of a loop✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Database.Contracts uses a type in Stancl.Tenancy.Database.
- The types involved
Stancl.Tenancy.Database.Contracts.ManagesDatabaseUsers→Stancl.Tenancy.Database.DatabaseConfigStancl.Tenancy.Database.Contracts.TenantWithDatabase→Stancl.Tenancy.Database.DatabaseConfig
- Direction
- Stancl.Tenancy.Database.Contracts uses Stancl.Tenancy.Database, so a change to Stancl.Tenancy.Database can break Stancl.Tenancy.Database.Contracts, while a change to Stancl.Tenancy.Database.Contracts can't break Stancl.Tenancy.Database.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→3 Stancl.Tenancy.Database.Exceptions uses Stancl.Tenancy.Contracts✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Database.Exceptions uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Database.Exceptions.TenantDatabaseAlreadyExistsException→Stancl.Tenancy.Contracts.TenantCannotBeCreatedExceptionStancl.Tenancy.Database.Exceptions.TenantDatabaseUserAlreadyExistsException→Stancl.Tenancy.Contracts.TenantCannotBeCreatedException
- Direction
- Stancl.Tenancy.Database.Exceptions uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Database.Exceptions, while a change to Stancl.Tenancy.Database.Exceptions can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Database.Exceptions uses a module listed above it, which is the healthy direction.
17→3 Stancl.Tenancy.Exceptions uses Stancl.Tenancy.Contracts✕
- Connections
- 7 pairs of types, where a type in Stancl.Tenancy.Exceptions uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Exceptions.TenantColumnNotWhitelistedException→Stancl.Tenancy.Contracts.TenantCouldNotBeIdentifiedExceptionStancl.Tenancy.Exceptions.TenantCouldNotBeIdentifiedByIdException→Stancl.Tenancy.Contracts.TenantCouldNotBeIdentifiedExceptionStancl.Tenancy.Exceptions.TenantCouldNotBeIdentifiedByPathException→Stancl.Tenancy.Contracts.TenantCouldNotBeIdentifiedExceptionStancl.Tenancy.Exceptions.TenantCouldNotBeIdentifiedByRequestDataException→Stancl.Tenancy.Contracts.TenantCouldNotBeIdentifiedExceptionStancl.Tenancy.Exceptions.TenantCouldNotBeIdentifiedOnDomainException→Stancl.Tenancy.Contracts.TenantCouldNotBeIdentifiedExceptionStancl.Tenancy.Exceptions.TenantIsPendingException→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Exceptions.TenantIsPendingException→Stancl.Tenancy.Contracts.TenantCouldNotBeIdentifiedException
- Direction
- Stancl.Tenancy.Exceptions uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Exceptions, while a change to Stancl.Tenancy.Exceptions can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Exceptions uses a module listed above it, which is the healthy direction.
18→3 Stancl.Tenancy.Features uses Stancl.Tenancy.Contracts✕
- Connections
- 7 pairs of types, where a type in Stancl.Tenancy.Features uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Features.CrossDomainRedirect→Stancl.Tenancy.Contracts.FeatureStancl.Tenancy.Features.DisallowSqliteAttach→Stancl.Tenancy.Contracts.FeatureStancl.Tenancy.Features.TelescopeTags→Stancl.Tenancy.Contracts.FeatureStancl.Tenancy.Features.TenantConfig→Stancl.Tenancy.Contracts.FeatureStancl.Tenancy.Features.TenantConfig→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Features.UserImpersonation→Stancl.Tenancy.Contracts.FeatureStancl.Tenancy.Features.ViteBundler→Stancl.Tenancy.Contracts.Feature
- Direction
- Stancl.Tenancy.Features uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Features, while a change to Stancl.Tenancy.Features can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Features uses a module listed above it, which is the healthy direction.
19→3 Stancl.Tenancy.Resolvers.Contracts uses Stancl.Tenancy.Contracts✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Resolvers.Contracts uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Resolvers.Contracts.CachedTenantResolver→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Resolvers.Contracts.CachedTenantResolver→Stancl.Tenancy.Contracts.TenantResolver
- Direction
- Stancl.Tenancy.Resolvers.Contracts uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Resolvers.Contracts, while a change to Stancl.Tenancy.Resolvers.Contracts can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Resolvers.Contracts uses a module listed above it, which is the healthy direction.
20→3 Stancl.Tenancy.UniqueIdentifierGenerators uses Stancl.Tenancy.Contracts✕
- Connections
- 6 pairs of types, where a type in Stancl.Tenancy.UniqueIdentifierGenerators uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.UniqueIdentifierGenerators.RandomHexGenerator→Stancl.Tenancy.Contracts.UniqueIdentifierGeneratorStancl.Tenancy.UniqueIdentifierGenerators.RandomIntGenerator→Stancl.Tenancy.Contracts.UniqueIdentifierGeneratorStancl.Tenancy.UniqueIdentifierGenerators.RandomStringGenerator→Stancl.Tenancy.Contracts.UniqueIdentifierGeneratorStancl.Tenancy.UniqueIdentifierGenerators.ULIDGenerator→Stancl.Tenancy.Contracts.UniqueIdentifierGeneratorStancl.Tenancy.UniqueIdentifierGenerators.UUIDGenerator→Stancl.Tenancy.Contracts.UniqueIdentifierGeneratorStancl.Tenancy.UniqueIdentifierGenerators.UUIDv7Generator→Stancl.Tenancy.Contracts.UniqueIdentifierGenerator
- Direction
- Stancl.Tenancy.UniqueIdentifierGenerators uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.UniqueIdentifierGenerators, while a change to Stancl.Tenancy.UniqueIdentifierGenerators can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.UniqueIdentifierGenerators uses a module listed above it, which is the healthy direction.
21→15 Stancl.Tenancy.Database uses Stancl.Tenancy.Database.Contracts✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Database uses a type in Stancl.Tenancy.Database.Contracts.
- The types involved
Stancl.Tenancy.Database.DatabaseConfig→Stancl.Tenancy.Database.Contracts.TenantDatabaseManagerStancl.Tenancy.Database.DatabaseManager→Stancl.Tenancy.Database.Contracts.TenantWithDatabase
- Direction
- Stancl.Tenancy.Database uses Stancl.Tenancy.Database.Contracts, so a change to Stancl.Tenancy.Database.Contracts can break Stancl.Tenancy.Database, while a change to Stancl.Tenancy.Database can't break Stancl.Tenancy.Database.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Database uses a module listed above it, which is the healthy direction.
22→3 Stancl.Tenancy.Events.Contracts uses Stancl.Tenancy.Contracts✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Events.Contracts uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Events.Contracts.DomainEvent→Stancl.Tenancy.Contracts.DomainStancl.Tenancy.Events.Contracts.TenantEvent→Stancl.Tenancy.Contracts.Tenant
- Direction
- Stancl.Tenancy.Events.Contracts uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Events.Contracts, while a change to Stancl.Tenancy.Events.Contracts can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Events.Contracts uses a module listed above it, which is the healthy direction.
22→11 Stancl.Tenancy.Events.Contracts uses Stancl.Tenancy✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.Events.Contracts uses a type in Stancl.Tenancy.
- The types involved
Stancl.Tenancy.Events.Contracts.TenancyEvent→Stancl.Tenancy.Tenancy
- Direction
- Stancl.Tenancy.Events.Contracts uses Stancl.Tenancy, so a change to Stancl.Tenancy can break Stancl.Tenancy.Events.Contracts, while a change to Stancl.Tenancy.Events.Contracts can't break Stancl.Tenancy.
- Position
- Below the diagonal: Stancl.Tenancy.Events.Contracts uses a module listed above it, which is the healthy direction.
23→3 Stancl.Tenancy.Resolvers uses Stancl.Tenancy.Contracts✕
- Connections
- 3 pairs of types, where a type in Stancl.Tenancy.Resolvers uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Resolvers.DomainTenantResolver→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Resolvers.PathTenantResolver→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Resolvers.RequestDataTenantResolver→Stancl.Tenancy.Contracts.Tenant
- Direction
- Stancl.Tenancy.Resolvers uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Resolvers, while a change to Stancl.Tenancy.Resolvers can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Resolvers uses a module listed above it, which is the healthy direction.
23→19 Stancl.Tenancy.Resolvers uses Stancl.Tenancy.Resolvers.Contracts✕
- Connections
- 3 pairs of types, where a type in Stancl.Tenancy.Resolvers uses a type in Stancl.Tenancy.Resolvers.Contracts.
- The types involved
Stancl.Tenancy.Resolvers.DomainTenantResolver→Stancl.Tenancy.Resolvers.Contracts.CachedTenantResolverStancl.Tenancy.Resolvers.PathTenantResolver→Stancl.Tenancy.Resolvers.Contracts.CachedTenantResolverStancl.Tenancy.Resolvers.RequestDataTenantResolver→Stancl.Tenancy.Resolvers.Contracts.CachedTenantResolver
- Direction
- Stancl.Tenancy.Resolvers uses Stancl.Tenancy.Resolvers.Contracts, so a change to Stancl.Tenancy.Resolvers.Contracts can break Stancl.Tenancy.Resolvers, while a change to Stancl.Tenancy.Resolvers can't break Stancl.Tenancy.Resolvers.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Resolvers uses a module listed above it, which is the healthy direction.
24→15 Stancl.Tenancy.ResourceSyncing.Events uses Stancl.Tenancy.Database.Contracts✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.ResourceSyncing.Events uses a type in Stancl.Tenancy.Database.Contracts.
- The types involved
Stancl.Tenancy.ResourceSyncing.Events.CentralResourceAttachedToTenant→Stancl.Tenancy.Database.Contracts.TenantWithDatabaseStancl.Tenancy.ResourceSyncing.Events.CentralResourceDetachedFromTenant→Stancl.Tenancy.Database.Contracts.TenantWithDatabase
- Direction
- Stancl.Tenancy.ResourceSyncing.Events uses Stancl.Tenancy.Database.Contracts, so a change to Stancl.Tenancy.Database.Contracts can break Stancl.Tenancy.ResourceSyncing.Events, while a change to Stancl.Tenancy.ResourceSyncing.Events can't break Stancl.Tenancy.Database.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.ResourceSyncing.Events uses a module listed above it, which is the healthy direction.
25→3 Stancl.Tenancy.Bootstrappers uses Stancl.Tenancy.Contracts✕
- Connections
- 34 pairs of types, where a type in Stancl.Tenancy.Bootstrappers uses a type in Stancl.Tenancy.Contracts. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Stancl.Tenancy.Bootstrappers.BroadcastChannelPrefixBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.BroadcastChannelPrefixBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.BroadcastingConfigBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.BroadcastingConfigBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.CacheTagsBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.CacheTagsBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.CacheTenancyBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.CacheTenancyBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.DatabaseCacheBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.DatabaseCacheBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.DatabaseSessionBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.DatabaseSessionBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.DatabaseTenancyBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.DatabaseTenancyBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.FilesystemTenancyBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.FilesystemTenancyBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.LogChannelBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.LogChannelBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.MailConfigBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.MailConfigBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.PersistentQueueTenancyBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.PersistentQueueTenancyBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.PostgresRLSBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapperStancl.Tenancy.Bootstrappers.PostgresRLSBootstrapper→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Bootstrappers.QueueTenancyBootstrapper→Stancl.Tenancy.Contracts.TenancyBootstrapper
- Direction
- Stancl.Tenancy.Bootstrappers uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Bootstrappers, while a change to Stancl.Tenancy.Bootstrappers can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Bootstrappers uses a module listed above it, which is the healthy direction.
25→15 Stancl.Tenancy.Bootstrappers uses Stancl.Tenancy.Database.Contracts✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.Bootstrappers uses a type in Stancl.Tenancy.Database.Contracts.
- The types involved
Stancl.Tenancy.Bootstrappers.PostgresRLSBootstrapper→Stancl.Tenancy.Database.Contracts.TenantWithDatabase
- Direction
- Stancl.Tenancy.Bootstrappers uses Stancl.Tenancy.Database.Contracts, so a change to Stancl.Tenancy.Database.Contracts can break Stancl.Tenancy.Bootstrappers, while a change to Stancl.Tenancy.Bootstrappers can't break Stancl.Tenancy.Database.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Bootstrappers uses a module listed above it, which is the healthy direction.
25→21 Stancl.Tenancy.Bootstrappers uses Stancl.Tenancy.Database✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Bootstrappers uses a type in Stancl.Tenancy.Database.
- The types involved
Stancl.Tenancy.Bootstrappers.DatabaseTenancyBootstrapper→Stancl.Tenancy.Database.DatabaseManagerStancl.Tenancy.Bootstrappers.PostgresRLSBootstrapper→Stancl.Tenancy.Database.DatabaseManager
- Direction
- Stancl.Tenancy.Bootstrappers uses Stancl.Tenancy.Database, so a change to Stancl.Tenancy.Database can break Stancl.Tenancy.Bootstrappers, while a change to Stancl.Tenancy.Bootstrappers can't break Stancl.Tenancy.Database.
- Position
- Below the diagonal: Stancl.Tenancy.Bootstrappers uses a module listed above it, which is the healthy direction.
26→3 Stancl.Tenancy.Database.Concerns uses Stancl.Tenancy.Contracts✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Database.Concerns uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Database.Concerns.HasDomains→Stancl.Tenancy.Contracts.DomainStancl.Tenancy.Database.Concerns.HasPending→Stancl.Tenancy.Contracts.Tenant
- Direction
- Stancl.Tenancy.Database.Concerns uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Database.Concerns, while a change to Stancl.Tenancy.Database.Concerns can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Database.Concerns uses a module listed above it, which is the healthy direction.
26→15 Stancl.Tenancy.Database.Concerns uses Stancl.Tenancy.Database.Contracts✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.Database.Concerns uses a type in Stancl.Tenancy.Database.Contracts.
- The types involved
Stancl.Tenancy.Database.Concerns.CreatesDatabaseUsers→Stancl.Tenancy.Database.Contracts.TenantWithDatabase
- Direction
- Stancl.Tenancy.Database.Concerns uses Stancl.Tenancy.Database.Contracts, so a change to Stancl.Tenancy.Database.Contracts can break Stancl.Tenancy.Database.Concerns, while a change to Stancl.Tenancy.Database.Concerns can't break Stancl.Tenancy.Database.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Database.Concerns uses a module listed above it, which is the healthy direction.
26→21 Stancl.Tenancy.Database.Concerns uses Stancl.Tenancy.Database✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Database.Concerns uses a type in Stancl.Tenancy.Database.
- The types involved
Stancl.Tenancy.Database.Concerns.HasDatabase→Stancl.Tenancy.Database.DatabaseConfigStancl.Tenancy.Database.Concerns.ManagesPostgresUsers→Stancl.Tenancy.Database.DatabaseConfig
- Direction
- Stancl.Tenancy.Database.Concerns uses Stancl.Tenancy.Database, so a change to Stancl.Tenancy.Database can break Stancl.Tenancy.Database.Concerns, while a change to Stancl.Tenancy.Database.Concerns can't break Stancl.Tenancy.Database.
- Position
- Below the diagonal: Stancl.Tenancy.Database.Concerns uses a module listed above it, which is the healthy direction.
27→3 Stancl.Tenancy.Database.Models uses Stancl.Tenancy.Contracts✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Database.Models uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Database.Models.Domain→Stancl.Tenancy.Contracts.DomainStancl.Tenancy.Database.Models.Tenant→Stancl.Tenancy.Contracts.Tenant
- Direction
- Stancl.Tenancy.Database.Models uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Database.Models, while a change to Stancl.Tenancy.Database.Models can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Database.Models uses a module listed above it, which is the healthy direction.
27→21 Stancl.Tenancy.Database.Models uses Stancl.Tenancy.Database✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.Database.Models uses a type in Stancl.Tenancy.Database.
- The types involved
Stancl.Tenancy.Database.Models.Tenant→Stancl.Tenancy.Database.TenantCollection
- Direction
- Stancl.Tenancy.Database.Models uses Stancl.Tenancy.Database, so a change to Stancl.Tenancy.Database can break Stancl.Tenancy.Database.Models, while a change to Stancl.Tenancy.Database.Models can't break Stancl.Tenancy.Database.
- Position
- Below the diagonal: Stancl.Tenancy.Database.Models uses a module listed above it, which is the healthy direction.
28→15 Stancl.Tenancy.Database.TenantDatabaseManagers uses Stancl.Tenancy.Database.Contracts✕
- Connections
- 12 pairs of types, where a type in Stancl.Tenancy.Database.TenantDatabaseManagers uses a type in Stancl.Tenancy.Database.Contracts.
- The types involved
Stancl.Tenancy.Database.TenantDatabaseManagers.MicrosoftSQLDatabaseManager→Stancl.Tenancy.Database.Contracts.TenantWithDatabaseStancl.Tenancy.Database.TenantDatabaseManagers.MySQLDatabaseManager→Stancl.Tenancy.Database.Contracts.TenantWithDatabaseStancl.Tenancy.Database.TenantDatabaseManagers.PermissionControlledMicrosoftSQLServerDatabaseManager→Stancl.Tenancy.Database.Contracts.ManagesDatabaseUsersStancl.Tenancy.Database.TenantDatabaseManagers.PermissionControlledMicrosoftSQLServerDatabaseManager→Stancl.Tenancy.Database.Contracts.TenantWithDatabaseStancl.Tenancy.Database.TenantDatabaseManagers.PermissionControlledMySQLDatabaseManager→Stancl.Tenancy.Database.Contracts.ManagesDatabaseUsersStancl.Tenancy.Database.TenantDatabaseManagers.PermissionControlledPostgreSQLDatabaseManager→Stancl.Tenancy.Database.Contracts.ManagesDatabaseUsersStancl.Tenancy.Database.TenantDatabaseManagers.PermissionControlledPostgreSQLSchemaManager→Stancl.Tenancy.Database.Contracts.ManagesDatabaseUsersStancl.Tenancy.Database.TenantDatabaseManagers.PostgreSQLDatabaseManager→Stancl.Tenancy.Database.Contracts.TenantWithDatabaseStancl.Tenancy.Database.TenantDatabaseManagers.PostgreSQLSchemaManager→Stancl.Tenancy.Database.Contracts.TenantWithDatabaseStancl.Tenancy.Database.TenantDatabaseManagers.SQLiteDatabaseManager→Stancl.Tenancy.Database.Contracts.TenantDatabaseManagerStancl.Tenancy.Database.TenantDatabaseManagers.SQLiteDatabaseManager→Stancl.Tenancy.Database.Contracts.TenantWithDatabaseStancl.Tenancy.Database.TenantDatabaseManagers.TenantDatabaseManager→Stancl.Tenancy.Database.Contracts.StatefulTenantDatabaseManager
- Direction
- Stancl.Tenancy.Database.TenantDatabaseManagers uses Stancl.Tenancy.Database.Contracts, so a change to Stancl.Tenancy.Database.Contracts can break Stancl.Tenancy.Database.TenantDatabaseManagers, while a change to Stancl.Tenancy.Database.TenantDatabaseManagers can't break Stancl.Tenancy.Database.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Database.TenantDatabaseManagers uses a module listed above it, which is the healthy direction.
28→21 Stancl.Tenancy.Database.TenantDatabaseManagers uses Stancl.Tenancy.Database✕
- Connections
- 4 pairs of types, where a type in Stancl.Tenancy.Database.TenantDatabaseManagers uses a type in Stancl.Tenancy.Database.
- The types involved
Stancl.Tenancy.Database.TenantDatabaseManagers.PermissionControlledMicrosoftSQLServerDatabaseManager→Stancl.Tenancy.Database.DatabaseConfigStancl.Tenancy.Database.TenantDatabaseManagers.PermissionControlledMySQLDatabaseManager→Stancl.Tenancy.Database.DatabaseConfigStancl.Tenancy.Database.TenantDatabaseManagers.PermissionControlledPostgreSQLDatabaseManager→Stancl.Tenancy.Database.DatabaseConfigStancl.Tenancy.Database.TenantDatabaseManagers.PermissionControlledPostgreSQLSchemaManager→Stancl.Tenancy.Database.DatabaseConfig
- Direction
- Stancl.Tenancy.Database.TenantDatabaseManagers uses Stancl.Tenancy.Database, so a change to Stancl.Tenancy.Database can break Stancl.Tenancy.Database.TenantDatabaseManagers, while a change to Stancl.Tenancy.Database.TenantDatabaseManagers can't break Stancl.Tenancy.Database.
- Position
- Below the diagonal: Stancl.Tenancy.Database.TenantDatabaseManagers uses a module listed above it, which is the healthy direction.
29→22 Stancl.Tenancy.Events uses Stancl.Tenancy.Events.Contracts✕
- Connections
- 46 pairs of types, where a type in Stancl.Tenancy.Events uses a type in Stancl.Tenancy.Events.Contracts. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Stancl.Tenancy.Events.BootstrappingTenancy→Stancl.Tenancy.Events.Contracts.TenancyEventStancl.Tenancy.Events.CreatingDatabase→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.CreatingDomain→Stancl.Tenancy.Events.Contracts.DomainEventStancl.Tenancy.Events.CreatingPendingTenant→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.CreatingStorageSymlink→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.CreatingTenant→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.DatabaseCreated→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.DatabaseDeleted→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.DatabaseMigrated→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.DatabaseRolledBack→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.DatabaseSeeded→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.DeletingDatabase→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.DeletingDomain→Stancl.Tenancy.Events.Contracts.DomainEventStancl.Tenancy.Events.DeletingTenant→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.DomainCreated→Stancl.Tenancy.Events.Contracts.DomainEventStancl.Tenancy.Events.DomainDeleted→Stancl.Tenancy.Events.Contracts.DomainEventStancl.Tenancy.Events.DomainSaved→Stancl.Tenancy.Events.Contracts.DomainEventStancl.Tenancy.Events.DomainUpdated→Stancl.Tenancy.Events.Contracts.DomainEventStancl.Tenancy.Events.EndingTenancy→Stancl.Tenancy.Events.Contracts.TenancyEventStancl.Tenancy.Events.InitializingTenancy→Stancl.Tenancy.Events.Contracts.TenancyEventStancl.Tenancy.Events.MigratingDatabase→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.PendingTenantCreated→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.PendingTenantPulled→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.PullingPendingTenant→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Events.RemovingStorageSymlink→Stancl.Tenancy.Events.Contracts.TenantEvent
- Direction
- Stancl.Tenancy.Events uses Stancl.Tenancy.Events.Contracts, so a change to Stancl.Tenancy.Events.Contracts can break Stancl.Tenancy.Events, while a change to Stancl.Tenancy.Events can't break Stancl.Tenancy.Events.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Events uses a module listed above it, which is the healthy direction.
30→3 Stancl.Tenancy.Jobs uses Stancl.Tenancy.Contracts✕
- Connections
- 3 pairs of types, where a type in Stancl.Tenancy.Jobs uses a type in Stancl.Tenancy.Contracts.
- The types involved
Stancl.Tenancy.Jobs.CreateStorageSymlinks→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Jobs.DeleteTenantStorage→Stancl.Tenancy.Contracts.TenantStancl.Tenancy.Jobs.RemoveStorageSymlinks→Stancl.Tenancy.Contracts.Tenant
- Direction
- Stancl.Tenancy.Jobs uses Stancl.Tenancy.Contracts, so a change to Stancl.Tenancy.Contracts can break Stancl.Tenancy.Jobs, while a change to Stancl.Tenancy.Jobs can't break Stancl.Tenancy.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Jobs uses a module listed above it, which is the healthy direction.
30→21 Stancl.Tenancy.Jobs uses Stancl.Tenancy.Database✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.Jobs uses a type in Stancl.Tenancy.Database.
- The types involved
Stancl.Tenancy.Jobs.CreateDatabase→Stancl.Tenancy.Database.DatabaseManager
- Direction
- Stancl.Tenancy.Jobs uses Stancl.Tenancy.Database, so a change to Stancl.Tenancy.Database can break Stancl.Tenancy.Jobs, while a change to Stancl.Tenancy.Jobs can't break Stancl.Tenancy.Database.
- Position
- Below the diagonal: Stancl.Tenancy.Jobs uses a module listed above it, which is the healthy direction.
31→11 Stancl.Tenancy.Middleware uses Stancl.Tenancy✕
- Connections
- 3 pairs of types, where a type in Stancl.Tenancy.Middleware uses a type in Stancl.Tenancy.
- The types involved
Stancl.Tenancy.Middleware.InitializeTenancyByDomain→Stancl.Tenancy.TenancyStancl.Tenancy.Middleware.InitializeTenancyByPath→Stancl.Tenancy.TenancyStancl.Tenancy.Middleware.InitializeTenancyByRequestData→Stancl.Tenancy.Tenancy
- Direction
- Stancl.Tenancy.Middleware uses Stancl.Tenancy, so a change to Stancl.Tenancy can break Stancl.Tenancy.Middleware, while a change to Stancl.Tenancy.Middleware can't break Stancl.Tenancy.
- Position
- Below the diagonal: Stancl.Tenancy.Middleware uses a module listed above it, which is the healthy direction.
31→23 Stancl.Tenancy.Middleware uses Stancl.Tenancy.Resolvers✕
- Connections
- 3 pairs of types, where a type in Stancl.Tenancy.Middleware uses a type in Stancl.Tenancy.Resolvers.
- The types involved
Stancl.Tenancy.Middleware.InitializeTenancyByDomain→Stancl.Tenancy.Resolvers.DomainTenantResolverStancl.Tenancy.Middleware.InitializeTenancyByPath→Stancl.Tenancy.Resolvers.PathTenantResolverStancl.Tenancy.Middleware.InitializeTenancyByRequestData→Stancl.Tenancy.Resolvers.RequestDataTenantResolver
- Direction
- Stancl.Tenancy.Middleware uses Stancl.Tenancy.Resolvers, so a change to Stancl.Tenancy.Resolvers can break Stancl.Tenancy.Middleware, while a change to Stancl.Tenancy.Middleware can't break Stancl.Tenancy.Resolvers.
- Position
- Below the diagonal: Stancl.Tenancy.Middleware uses a module listed above it, which is the healthy direction.
32→15 Stancl.Tenancy.Commands uses Stancl.Tenancy.Database.Contracts✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.Commands uses a type in Stancl.Tenancy.Database.Contracts.
- The types involved
Stancl.Tenancy.Commands.MigrateFresh→Stancl.Tenancy.Database.Contracts.TenantWithDatabase
- Direction
- Stancl.Tenancy.Commands uses Stancl.Tenancy.Database.Contracts, so a change to Stancl.Tenancy.Database.Contracts can break Stancl.Tenancy.Commands, while a change to Stancl.Tenancy.Commands can't break Stancl.Tenancy.Database.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Commands uses a module listed above it, which is the healthy direction.
32→21 Stancl.Tenancy.Commands uses Stancl.Tenancy.Database✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.Commands uses a type in Stancl.Tenancy.Database.
- The types involved
Stancl.Tenancy.Commands.CreateUserWithRLSPolicies→Stancl.Tenancy.Database.DatabaseConfig
- Direction
- Stancl.Tenancy.Commands uses Stancl.Tenancy.Database, so a change to Stancl.Tenancy.Database can break Stancl.Tenancy.Commands, while a change to Stancl.Tenancy.Commands can't break Stancl.Tenancy.Database.
- Position
- Below the diagonal: Stancl.Tenancy.Commands uses a module listed above it, which is the healthy direction.
32→28 Stancl.Tenancy.Commands uses Stancl.Tenancy.Database.TenantDatabaseManagers✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.Commands uses a type in Stancl.Tenancy.Database.TenantDatabaseManagers.
- The types involved
Stancl.Tenancy.Commands.CreateUserWithRLSPolicies→Stancl.Tenancy.Database.TenantDatabaseManagers.PermissionControlledPostgreSQLSchemaManager
- Direction
- Stancl.Tenancy.Commands uses Stancl.Tenancy.Database.TenantDatabaseManagers, so a change to Stancl.Tenancy.Database.TenantDatabaseManagers can break Stancl.Tenancy.Commands, while a change to Stancl.Tenancy.Commands can't break Stancl.Tenancy.Database.TenantDatabaseManagers.
- Position
- Below the diagonal: Stancl.Tenancy.Commands uses a module listed above it, which is the healthy direction.
33→21 Stancl.Tenancy.Listeners uses Stancl.Tenancy.Database✕
- Connections
- 3 pairs of types, where a type in Stancl.Tenancy.Listeners uses a type in Stancl.Tenancy.Database.
- The types involved
Stancl.Tenancy.Listeners.CreateTenantConnection→Stancl.Tenancy.Database.DatabaseManagerStancl.Tenancy.Listeners.UseCentralConnection→Stancl.Tenancy.Database.DatabaseManagerStancl.Tenancy.Listeners.UseTenantConnection→Stancl.Tenancy.Database.DatabaseManager
- Direction
- Stancl.Tenancy.Listeners uses Stancl.Tenancy.Database, so a change to Stancl.Tenancy.Database can break Stancl.Tenancy.Listeners, while a change to Stancl.Tenancy.Listeners can't break Stancl.Tenancy.Database.
- Position
- Below the diagonal: Stancl.Tenancy.Listeners uses a module listed above it, which is the healthy direction.
33→22 Stancl.Tenancy.Listeners uses Stancl.Tenancy.Events.Contracts✕
- Connections
- 5 pairs of types, where a type in Stancl.Tenancy.Listeners uses a type in Stancl.Tenancy.Events.Contracts.
- The types involved
Stancl.Tenancy.Listeners.CreateTenantConnection→Stancl.Tenancy.Events.Contracts.TenancyEventStancl.Tenancy.Listeners.CreateTenantStorage→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Listeners.DeleteTenantStorage→Stancl.Tenancy.Events.Contracts.TenantEventStancl.Tenancy.Listeners.UseCentralConnection→Stancl.Tenancy.Events.Contracts.TenancyEventStancl.Tenancy.Listeners.UseTenantConnection→Stancl.Tenancy.Events.Contracts.TenancyEvent
- Direction
- Stancl.Tenancy.Listeners uses Stancl.Tenancy.Events.Contracts, so a change to Stancl.Tenancy.Events.Contracts can break Stancl.Tenancy.Listeners, while a change to Stancl.Tenancy.Listeners can't break Stancl.Tenancy.Events.Contracts.
- Position
- Below the diagonal: Stancl.Tenancy.Listeners uses a module listed above it, which is the healthy direction.
33→29 Stancl.Tenancy.Listeners uses Stancl.Tenancy.Events✕
- Connections
- 2 pairs of types, where a type in Stancl.Tenancy.Listeners uses a type in Stancl.Tenancy.Events.
- The types involved
Stancl.Tenancy.Listeners.BootstrapTenancy→Stancl.Tenancy.Events.TenancyInitializedStancl.Tenancy.Listeners.RevertToCentralContext→Stancl.Tenancy.Events.TenancyEnded
- Direction
- Stancl.Tenancy.Listeners uses Stancl.Tenancy.Events, so a change to Stancl.Tenancy.Events can break Stancl.Tenancy.Listeners, while a change to Stancl.Tenancy.Listeners can't break Stancl.Tenancy.Events.
- Position
- Below the diagonal: Stancl.Tenancy.Listeners uses a module listed above it, which is the healthy direction.
34→10 Stancl.Tenancy.ResourceSyncing.Listeners uses Stancl.Tenancy.ResourceSyncing✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.ResourceSyncing.Listeners uses a type in Stancl.Tenancy.ResourceSyncing.
- The types involved
Stancl.Tenancy.ResourceSyncing.Listeners.UpdateOrCreateSyncedResource→Stancl.Tenancy.ResourceSyncing.Syncable
- Direction
- Stancl.Tenancy.ResourceSyncing.Listeners uses Stancl.Tenancy.ResourceSyncing, so a change to Stancl.Tenancy.ResourceSyncing can break Stancl.Tenancy.ResourceSyncing.Listeners, while a change to Stancl.Tenancy.ResourceSyncing.Listeners can't break Stancl.Tenancy.ResourceSyncing.
- Position
- Below the diagonal: Stancl.Tenancy.ResourceSyncing.Listeners uses a module listed above it, which is the healthy direction.
34→21 Stancl.Tenancy.ResourceSyncing.Listeners uses Stancl.Tenancy.Database✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.ResourceSyncing.Listeners uses a type in Stancl.Tenancy.Database.
- The types involved
Stancl.Tenancy.ResourceSyncing.Listeners.UpdateOrCreateSyncedResource→Stancl.Tenancy.Database.TenantCollection
- Direction
- Stancl.Tenancy.ResourceSyncing.Listeners uses Stancl.Tenancy.Database, so a change to Stancl.Tenancy.Database can break Stancl.Tenancy.ResourceSyncing.Listeners, while a change to Stancl.Tenancy.ResourceSyncing.Listeners can't break Stancl.Tenancy.Database.
- Position
- Below the diagonal: Stancl.Tenancy.ResourceSyncing.Listeners uses a module listed above it, which is the healthy direction.
34→24 Stancl.Tenancy.ResourceSyncing.Listeners uses Stancl.Tenancy.ResourceSyncing.Events✕
- Connections
- 6 pairs of types, where a type in Stancl.Tenancy.ResourceSyncing.Listeners uses a type in Stancl.Tenancy.ResourceSyncing.Events.
- The types involved
Stancl.Tenancy.ResourceSyncing.Listeners.CreateTenantResource→Stancl.Tenancy.ResourceSyncing.Events.CentralResourceAttachedToTenantStancl.Tenancy.ResourceSyncing.Listeners.DeleteResourceInTenant→Stancl.Tenancy.ResourceSyncing.Events.CentralResourceDetachedFromTenantStancl.Tenancy.ResourceSyncing.Listeners.DeleteResourceMapping→Stancl.Tenancy.ResourceSyncing.Events.SyncedResourceDeletedStancl.Tenancy.ResourceSyncing.Listeners.DeleteResourcesInTenants→Stancl.Tenancy.ResourceSyncing.Events.SyncMasterDeletedStancl.Tenancy.ResourceSyncing.Listeners.RestoreResourcesInTenants→Stancl.Tenancy.ResourceSyncing.Events.SyncMasterRestoredStancl.Tenancy.ResourceSyncing.Listeners.UpdateOrCreateSyncedResource→Stancl.Tenancy.ResourceSyncing.Events.SyncedResourceSaved
- Direction
- Stancl.Tenancy.ResourceSyncing.Listeners uses Stancl.Tenancy.ResourceSyncing.Events, so a change to Stancl.Tenancy.ResourceSyncing.Events can break Stancl.Tenancy.ResourceSyncing.Listeners, while a change to Stancl.Tenancy.ResourceSyncing.Listeners can't break Stancl.Tenancy.ResourceSyncing.Events.
- Position
- Below the diagonal: Stancl.Tenancy.ResourceSyncing.Listeners uses a module listed above it, which is the healthy direction.
34→29 Stancl.Tenancy.ResourceSyncing.Listeners uses Stancl.Tenancy.Events✕
- Connections
- 1 pair of types, where a type in Stancl.Tenancy.ResourceSyncing.Listeners uses a type in Stancl.Tenancy.Events.
- The types involved
Stancl.Tenancy.ResourceSyncing.Listeners.DeleteAllTenantMappings→Stancl.Tenancy.Events.TenantDeleted
- Direction
- Stancl.Tenancy.ResourceSyncing.Listeners uses Stancl.Tenancy.Events, so a change to Stancl.Tenancy.Events can break Stancl.Tenancy.ResourceSyncing.Listeners, while a change to Stancl.Tenancy.ResourceSyncing.Listeners can't break Stancl.Tenancy.Events.
- Position
- Below the diagonal: Stancl.Tenancy.ResourceSyncing.Listeners uses a module listed above it, which is the healthy direction.
34→33 Stancl.Tenancy.ResourceSyncing.Listeners uses Stancl.Tenancy.Listeners✕
- Connections
- 7 pairs of types, where a type in Stancl.Tenancy.ResourceSyncing.Listeners uses a type in Stancl.Tenancy.Listeners.
- The types involved
Stancl.Tenancy.ResourceSyncing.Listeners.CreateTenantResource→Stancl.Tenancy.Listeners.QueueableListenerStancl.Tenancy.ResourceSyncing.Listeners.DeleteAllTenantMappings→Stancl.Tenancy.Listeners.QueueableListenerStancl.Tenancy.ResourceSyncing.Listeners.DeleteResourceInTenant→Stancl.Tenancy.Listeners.QueueableListenerStancl.Tenancy.ResourceSyncing.Listeners.DeleteResourceMapping→Stancl.Tenancy.Listeners.QueueableListenerStancl.Tenancy.ResourceSyncing.Listeners.DeleteResourcesInTenants→Stancl.Tenancy.Listeners.QueueableListenerStancl.Tenancy.ResourceSyncing.Listeners.RestoreResourcesInTenants→Stancl.Tenancy.Listeners.QueueableListenerStancl.Tenancy.ResourceSyncing.Listeners.UpdateOrCreateSyncedResource→Stancl.Tenancy.Listeners.QueueableListener
- Direction
- Stancl.Tenancy.ResourceSyncing.Listeners uses Stancl.Tenancy.Listeners, so a change to Stancl.Tenancy.Listeners can break Stancl.Tenancy.ResourceSyncing.Listeners, while a change to Stancl.Tenancy.ResourceSyncing.Listeners can't break Stancl.Tenancy.Listeners.
- Position
- Below the diagonal: Stancl.Tenancy.ResourceSyncing.Listeners uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A02:2025 — Security Misconfiguration | 15 | High / Critical |
Roadmap
Top priorities: Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run; Resolve the 1 finding(s) in DR & Backup; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run. | +7.2 pts | Medium | Observability |
| Resolve the 1 finding(s) in DR & Backup. | +7.2 pts | Medium | DR & Backup |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.2 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.8 pts | Medium | Documentation (README) |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.5 pts | Medium | Release Hygiene |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with composer.json. | +0.7 pts | Low | Project Cohesion |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Commands/Migrate.php | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/Bootstrappers/PersistentQueueTenancyBootstrapper.php | 7.2 | Mixed | Code Duplication: Edited copy of a member (24 corresponding lines) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| tests/SessionSeparationTest.php | 7.3 | Mixed | Explicit Debt: TodoComment |
| tests/RLS/PolicyTest.php | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/Database/Concerns/BelongsToPrimaryModel.php | 7.4 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
| src/Middleware/CheckTenantForMaintenanceMode.php | 7.8 | Mixed | Cyclomatic Complexity: CheckTenantForMaintenanceMode.handle (cyclomatic 16) |
| src/Bootstrappers/BroadcastChannelPrefixBootstrapper.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (29 corresponding lines) |
| src/Bootstrappers/CacheTenancyBootstrapper.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
| src/Database/TenantDatabaseManagers/PermissionControlledMicrosoftSQLServerDatabaseManager.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (17 corresponding lines) |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| src/TenancyServiceProvider.php | 8.0 | Near-clean | Coupling: Circular dependency |
| assets/config.php | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: config.php ↔ TenancyUrlGenerator.php |
| tests/CommandsTest.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| tests/Bootstrappers/DatabaseTenancyBootstrapperTest.php | 8.2 | Near-clean | 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 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 40 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, 77 of 89 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 — 7 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 (77 contributor(s) across 1480 commit(s) sampled, automation and bot accounts excluded). One of them holds 81% of the history; the other 76 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (composer.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Commands/TenantList.php`, `src/Concerns/ParallelCommand.php`, `src/Concerns/TenantAwareCommand.php`, `src/Database/Concerns/HasPending.php`, `src/Database/Concerns/InvalidatesResolverCache.php`, … (+24 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.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's PHP, c, lua 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, c, lua 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.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — 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 Java, Kotlin, Scala, Go, Swift, Python and Ruby source only, and no C# was loaded, no Java, Kotlin, Scala, Go, Swift, Python or Ruby was found, and this repository's C, Lua 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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 CheckTenantForMaintenanceMode.handle at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with CheckTenantForMaintenanceMode.handle (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.9 to about 10.0/10.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was CheckTenantForMaintenanceMode.handle at 26.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with CheckTenantForMaintenanceMode.handle (cognitive 26), ParallelCommand.runConcurrently (cognitive 19), CreateUserWithRLSPolicies.createTablePolicies (cognitive 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
10 duplicated block group(s) detected. 3.0 % of the production lines (366 of 12,065) are in a reported copy. A further 9 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (42 corresponding lines) finding(s) in Code Duplication — start with Migrate.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (29 corresponding lines) finding(s) in Code Duplication — start with BroadcastChannelPrefixBootstrapper.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (24 corresponding lines) finding(s) in Code Duplication — start with PersistentQueueTenancyBootstrapper.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
24 production modules (source-import), 1 dependency cycle(s), 2 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; 2 module(s) off the main sequence, with abstractness counted on 22 of the 24 (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 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Circular dependency finding(s) in Coupling — start with TenancyServiceProvider.php. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Unstable project src/Jobs finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 41 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
9 deducted task-comment markers across 12065 LoC (0.1/KLoC) → score 9.9. 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 9 TodoComment finding(s) in Explicit Debt — start with SessionSeparationTest.php (2), PolicyTest.php (2), CommandsTest.php. — One of this dimension's main actionable groups (9 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 2 unit(s).
D26 · Project Cohesion
1 of 2 build units (Composer) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
22 % of calls cross a namespace and 7 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 14 high, 1 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 29 file(s) — `src/Commands/TenantList.php` (line 38), `src/Concerns/ParallelCommand.php` (line 18, line 166), `src/Concerns/TenantAwareCommand.php` (line 22), `src/Database/Concerns/HasPending.php` (line 62, line 87), `src/Database/Concerns/InvalidatesResolverCache.php` (line 13, line 14), … (+24 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 10 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (10 issue-level, 0 of them charged here).
D31 · IaC & Container Security
15 finding(s): 0 critical, 5 high, 9 medium, 1 low.
What to do
- Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 9 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (3). — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
3 of 57 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Concerns/UsableWithEarlyIdentification.php. Counted over 57 of the 264 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: Migrate.php↔Rollback.php 62%; config.php↔TenancyUrlGenerator.php 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with config.php. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with Migrate.php. — One of this dimension's main actionable groups (1 warning-level).
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 7 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
- The projects src → src/Bootstrappers → src (one cycle inside a mutually-dependent group of 14 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — src/TenancyServiceProvider.php:15
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — Gate abilities and policy classes (Gate::define, a UserPolicy), spatie/laravel-permission roles and permissions, or a Symfony Voter — and consult them where access is checked ($this->authorize, a can: middleware, #[IsGranted]), so the rule set is reviewable and testable on its own.
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
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
- `vendor/bin/php-cs-fixer fix --config=.php-cs-fixer.php` invokes php-cs-fixer in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--dry-run` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:141
What to do
- Add `--dry-run` to the php-cs-fixer step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
P2 · Observability
- No logging call was found in the 265 PHP production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (PHP: PSR-3 loggers (Monolog), Laravel's Log facade, error_log()) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run.
- Add a health-check endpoint (Laravel's /up health route or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/Database/TenantDatabaseManagers/SQLiteDatabaseManager.php:119
- `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. — src/Database/TenantDatabaseManagers/SQLiteDatabaseManager.php:123
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81.6 | Strong | Strongest area. |
| Architecture | 83.0 | Adequate — gated by D5, D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 59.2 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 34.4 | Weak — gated by P2, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 74.5 | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 3 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not included — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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) — c apt-get install -y gnupg2 && curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor -o /usr/share/keyrings/microsoft-prod.gpg && curl https://packages.microsoft.com/config/debian/12/prod.list > /etc/apt/sources.list.d/mssql-release.list && apt-get update && ACCEPT_EULA=Y apt-get install -y unixodbc-dev msodbcsql18" did not complete successfully: exit code: 2; likely cause (the repository): a RUN step of the repository's REDACTED exited with code 2 (`/bin/bash -c apt-get install -y gnupg2 && curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearm…`): 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 2 (`/bin/bash -c apt-get install -y gnupg2 && curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearm…`): 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.
- 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.
- D10 Test Quality — ~15220 lines of test source are present (.php) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 7 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Database), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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) — 29 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 3 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 9 domain event(s); its 3 aggregate(s) are ORM models only — persistence, not behaviour: a CRUD model, measured, not claimed as DDD; its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
- 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. 2 claim(s) of kinds M4 does not check were not checked (path 2); M4 checks only links and versions and artefact counts.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the PHP source (service entry point: src/Overrides/TenancyUrlGenerator.php:39 (Route::get())
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 22 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Project dependency cycle src/TenancyServiceProvider.php:15
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: config.php ↔ TenancyUrlGenerator.php assets/config.php:1
- Circular dependency src/TenancyServiceProvider.php:15
Serious — 57 finding(s)
- TodoComment tests/CommandsTest.php:670
- TodoComment tests/SessionSeparationTest.php:29
- TodoComment tests/SessionSeparationTest.php:308
- TodoComment tests/RLS/PolicyTest.php:367
- TodoComment tests/Bootstrappers/DatabaseTenancyBootstrapperTest.php:304
- TodoComment tests/RLS/PolicyTest.php:595
- TodoComment src/ResourceSyncing/ModelNotSyncMasterException.php:9
- TodoComment src/Features/TenantConfig.php:16
- TodoComment src/Commands/Migrate.php:112
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: typedefs
- Off the main sequence: src/Events
- CheckTenantForMaintenanceMode.handle (cyclomatic 16) src/Middleware/CheckTenantForMaintenanceMode.php:16
- CheckTenantForMaintenanceMode.handle (cognitive 26) src/Middleware/CheckTenantForMaintenanceMode.php:16
- ParallelCommand.runConcurrently (cognitive 19) src/Concerns/ParallelCommand.php:166
- CreateUserWithRLSPolicies.createTablePolicies (cognitive 17) src/Commands/CreateUserWithRLSPolicies.php:141
- Install.askForSupport (cognitive 16) src/Commands/Install.php:129
- REDACTED
- Change coupling: Migrate.php ↔ Rollback.php src/Commands/Migrate.php:1
- REDACTED
- Edited copy of a member (42 corresponding lines) src/Commands/Migrate.php:86
- Edited copy of a member (29 corresponding lines) src/Bootstrappers/BroadcastChannelPrefixBootstrapper.php:85
- Edited copy of a member (24 corresponding lines) src/Bootstrappers/PersistentQueueTenancyBootstrapper.php:47
- Edited copy of a member (16 corresponding lines) src/Bootstrappers/CacheTenancyBootstrapper.php:45
- Edited copy of a member (17 corresponding lines) src/Database/TenantDatabaseManagers/PermissionControlledMicrosoftSQLServerDatabaseManager.php:23
- Edited copy of a member (10 corresponding lines) src/Database/Concerns/BelongsToPrimaryModel.php:27
- Edited copy of a member (14 corresponding lines) src/Bootstrappers/BroadcastingConfigBootstrapper.php:145
- Edited copy of a member (8 corresponding lines) src/Actions/CreateStorageSymlinksAction.php:24
- Edited copy of a member (7 corresponding lines) src/Database/Concerns/BelongsToPrimaryModel.php:16
- Duplicated block (19–20 lines × 2) src/Commands/Migrate.php:95
- Duplicated block (18 lines × 2) src/Bootstrappers/TenantConfigBootstrapper.php:28
- Duplicated block (16 lines × 2) src/Bootstrappers/BroadcastChannelPrefixBootstrapper.php:92
- Duplicated block (11–15 lines × 2) src/Database/TenantDatabaseManagers/PermissionControlledMicrosoftSQLServerDatabaseManager.php:23
- Duplicated block (13 lines × 2) src/Bootstrappers/PersistentQueueTenancyBootstrapper.php:47
- Duplicated block (8 lines × 2) src/Database/Concerns/BelongsToPrimaryModel.php:27
- Duplicated block (6 lines × 2) src/Bootstrappers/CacheTenancyBootstrapper.php:52
- Duplicated block (19 lines × 3) src/Database/TenantDatabaseManagers/MicrosoftSQLDatabaseManager.php:13
- Duplicated block (7 lines × 2) src/Bootstrappers/PersistentQueueTenancyBootstrapper.php:120
- Duplicated block (11 lines × 2) src/Bootstrappers/PersistentQueueTenancyBootstrapper.php:131
- Unstable project src/Jobs
- Unstable project src/ResourceSyncing
- CI formatting step cannot fail REDACTED:141
- Coverage collected but not gated
- No structured logging
- No DR/backup evidence
- Swallowed exception (empty catch) src/Database/TenantDatabaseManagers/SQLiteDatabaseManager.php:119
- Swallowed exception (caught, then discarded) src/Database/TenantDatabaseManagers/SQLiteDatabaseManager.php:123
Minor — 10 finding(s)
- Orphaned file src/Concerns/UsableWithEarlyIdentification.php:1
- Orphaned file .php-cs-fixer.php:1
- Orphaned file src/Middleware/PreventAccessFromUnwantedDomains.php:1
- No named authorization policies
- Projects may be oversized for their cohesion composer.json:1
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No changelog
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-e4da8a023fec4c729105e45619f060b6/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-e4da8a023fec4c729105e45619f060b6/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=507" --report-format json --report-path /tmp/watchdog-gitleaks-e4da8a023fec4c729105e45619f060b6/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e4da8a023fec4c729105e45619f060b6/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 15 | 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 . | 15 | 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 29 file(s) — `src/Commands/TenantList.php`, `src/Concerns/ParallelCommand.php`, `src/Concerns/TenantAwareCommand.php`, `src/Database/Concerns/HasPending.php`, `src/Database/Concerns/InvalidatesResolverCache.php`, … (+24 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 | — |