Executive summary
buraksenyurt/project-lighthouse-social falls short of our standard for production because eight passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 42 out of 100 and is rated Weak, and 29 of its 40 critical findings are security problems.
Production Readiness, at 31, is the weakest lens and counts most in the score. The best first step is replacing the eight exposed passwords or keys and switching the old ones off, worth about 9 points. Replacing the three deprecated dependencies comes next, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 51.
Ten settings leave the servers or containers unsafe. Eight passwords or keys in the code and eight in the code's history are open to anyone who can read the repository, and two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Correcting the unsafe settings, replacing each exposed password or key and pinning each tool to an exact version would close these risks. Updating the vulnerable packages would fix the package with a known security hole. Saving the change and the message together would take care of the five places where data is saved and a message sent separately.
The product code is 6,288 lines, about €19,000 to rebuild.
If Production Readiness rose from 31 to 70, the lowest score rated Strong, the score would rise from 42 to about 51.
New since the last survey: 2 findings
- Outbox / dual-write · Dual write (no outbox): PhotoUploadSaga.ExecuteAsync src/LighthouseSocial.Application/Features/Photo/Saga/PhotoUploadSaga.cs
- Rich vs anemic model · Anemic entity: Photo src/LighthouseSocial.Domain/Entities/Photo.cs
Fixed since the last survey: 40 findings
- Dependency Hygiene · Vulnerable: SixLabors.ImageSharp
- Static Analysis (SAST) · Medium: watchdog-eol-dotnet-runtime-in-workflow REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net9.0 src/RabbitMqConsumer/RabbitMqConsumer.csproj
- Cancellation propagation · Async method without CancellationToken: GetDatabaseConnectionStringAsync src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs
- Cancellation propagation · Async method without CancellationToken: GetMinioCredentialsAsync src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs
- Cancellation propagation · Async method without CancellationToken: GetRabbitMqSettingsAsync src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs
- Cancellation propagation · Async method without CancellationToken: GetKeycloakSettingsAsync src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs
- Cancellation propagation · Async method without CancellationToken: GetCachedValueAsync src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs
- Cancellation propagation · Async method without CancellationToken: GetFromDistributedCacheAsync src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs
- Cancellation propagation · Async method without CancellationToken: WarmUpCacheAsync src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs
- Cancellation propagation · Async method without CancellationToken: InvalidateCacheAsync src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs
- Cancellation propagation · Async method without CancellationToken: GetLighthousesAsync src/LighthouseSocial.Data/Repositories/LighthouseODataRepository.cs
- Cancellation propagation · Async method without CancellationToken: Update REDACTED
- Cancellation propagation · Async method without CancellationToken: Delete REDACTED
- Cancellation propagation · Async method without CancellationToken: GetRawPhotoAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: GetByUserIdAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: GetByLighthouseIdAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: GetByIdAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: DeleteAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: UploadAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: Get src/LighthouseSocial.ODataApi/Controllers/LighthousesController.cs
- Cancellation propagation · Async method without CancellationToken: OnGet REDACTED
- Cancellation propagation · Async method without CancellationToken: LoadCountriesAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: OnPostAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: OnGetAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: OnPostDeleteAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/LighthouseSocial.Backoffice/Services/CountryServiceClient.cs
- Cancellation propagation · Async method without CancellationToken: CreateAsync src/LighthouseSocial.Backoffice/Services/LigthouseServiceClient.cs
- Cancellation propagation · Async method without CancellationToken: GetPagedAsync src/LighthouseSocial.Backoffice/Services/LigthouseServiceClient.cs
- Cancellation propagation · Async method without CancellationToken: DeleteByIdAsync src/LighthouseSocial.Backoffice/Services/LigthouseServiceClient.cs
- Cancellation propagation · Async method without CancellationToken: DeleteByIdAsync src/LighthouseSocial.Backoffice/Services/PhotoServiceClient.cs
- Cancellation propagation · Async method without CancellationToken: UploadPhotoAsync src/LighthouseSocial.Backoffice/Services/PhotoUploadServiceClient.cs
- Cancellation propagation · Async endpoint handler without CancellationToken: /moderate src/JudgeDredd/Program.cs
- Cancellation propagation · Async method without CancellationToken: IsFlagged src/JudgeDredd/Services/OpenApiCommentAuditService.cs
- Cancellation propagation · Async method drops its CancellationToken: IsTextCleanAsync src/LighthouseSocial.Infrastructure/Auditors/ExternalCommentAuditor.cs
- Cancellation propagation · Async method drops its CancellationToken: DeleteAsync src/LighthouseSocial.Infrastructure/Storage/PhotoStorageService.cs
- Cancellation propagation · Async method drops its CancellationToken: GetAsync src/LighthouseSocial.Infrastructure/Storage/PhotoStorageService.cs
- Cancellation propagation · Async method drops its CancellationToken: SaveAsync src/LighthouseSocial.Infrastructure/Storage/PhotoStorageService.cs
- Cancellation propagation · Async method drops its CancellationToken: GetAllAsync src/LighthouseSocial.Data/Repositories/CachedCountryDataReader.cs
- Cancellation propagation · Async method drops its CancellationToken: GetByIdAsync src/LighthouseSocial.Data/Repositories/CachedCountryDataReader.cs
Rebuild cost: about €19,000 · Estimate
| Cost to rebuild | €6,200 to €32,000, for 104 to 336 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 42. 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: 6,288 lines of product code, of which 37% is declarations and boilerplate, 16% straight logic and 47% logic with branches |
| Comment lines | The estimate prices 6,259 lines. Comment lines count towards the size of 6,288 lines but aren't priced as work. |
| 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 LighthouseSocial.Application.Common | 2 LighthouseSocial.Application.Common.Pipeline | 3 LighthouseSocial.Application.Dtos | 4 LighthouseSocial.Backoffice.Models | 5 LighthouseSocial.Data | 6 LighthouseSocial.Domain.Common | 7 LighthouseSocial.Domain.ValueObjects | 8 LightHouseSocial.Domain.Enumerations | 9 LighthouseSocial.Application.Common.DistribtedTransaction.Saga | 10 LighthouseSocial.Application.Common.Pipeline.Behaviors | 11 LighthouseSocial.Application.Contracts | 12 LighthouseSocial.Application.Contracts.ExternalServices | 13 LighthouseSocial.Backoffice.Services | 14 LighthouseSocial.Domain.Entities | 15 LighthouseSocial.Domain.Enumerations | 16 LighthouseSocial.Domain.Events.Comment | 17 LighthouseSocial.Domain.Events.Lighthouse | 18 LighthouseSocial.Domain.Events.Photo | 19 LighthouseSocial.EventWorker.Strategies | 20 LighthouseSocial.Infrastructure.Caching | 21 LighthouseSocial.Application.Contracts.Repositories | 22 LighthouseSocial.Backoffice.Pages.Lighthouse | 23 LighthouseSocial.Infrastructure.Auditors | 24 LighthouseSocial.Infrastructure.Configuration | 25 LighthouseSocial.Infrastructure.SecretManager | 26 LighthouseSocial.WebApi.Controllers | 27 LighthouseSocial.Application.Features.Comment | 28 LighthouseSocial.Application.Features.Country | 29 LighthouseSocial.Application.Features.Lighthouse | 30 LighthouseSocial.Application.Features.Photo | 31 LighthouseSocial.Application.Features.Photo.Saga.Steps | 32 LighthouseSocial.Application.Features.User | 33 LighthouseSocial.Data.Repositories | 34 LighthouseSocial.EventWorker.Services | 35 LighthouseSocial.Infrastructure.Messaging | 36 LighthouseSocial.Infrastructure.Storage | 37 LighthouseSocial.ODataApi.Controllers | 38 TerminalApp.UseCases | 39 LighthouseSocial.Application.Features.Photo.Saga | 40 LighthouseSocial.Application.Services |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 LighthouseSocial.Application.Common | ||||||||||||||||||||||||||||||||||||||||
| 2 LighthouseSocial.Application.Common.Pipeline | ||||||||||||||||||||||||||||||||||||||||
| 3 LighthouseSocial.Application.Dtos | ||||||||||||||||||||||||||||||||||||||||
| 4 LighthouseSocial.Backoffice.Models | ||||||||||||||||||||||||||||||||||||||||
| 5 LighthouseSocial.Data | ||||||||||||||||||||||||||||||||||||||||
| 6 LighthouseSocial.Domain.Common | ||||||||||||||||||||||||||||||||||||||||
| 7 LighthouseSocial.Domain.ValueObjects | ||||||||||||||||||||||||||||||||||||||||
| 8 LightHouseSocial.Domain.Enumerations | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 LighthouseSocial.Application.Common.DistribtedTransaction.Saga | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 LighthouseSocial.Application.Common.Pipeline.Behaviors | 4 | |||||||||||||||||||||||||||||||||||||||
| 11 LighthouseSocial.Application.Contracts | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 LighthouseSocial.Application.Contracts.ExternalServices | 6 | 10 | ||||||||||||||||||||||||||||||||||||||
| 13 LighthouseSocial.Backoffice.Services | 18 | |||||||||||||||||||||||||||||||||||||||
| 14 LighthouseSocial.Domain.Entities | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 15 LighthouseSocial.Domain.Enumerations | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 LighthouseSocial.Domain.Events.Comment | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 LighthouseSocial.Domain.Events.Lighthouse | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 LighthouseSocial.Domain.Events.Photo | 9 | |||||||||||||||||||||||||||||||||||||||
| 19 LighthouseSocial.EventWorker.Strategies | 3 | |||||||||||||||||||||||||||||||||||||||
| 20 LighthouseSocial.Infrastructure.Caching | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 LighthouseSocial.Application.Contracts.Repositories | 6 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 22 LighthouseSocial.Backoffice.Pages.Lighthouse | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 23 LighthouseSocial.Infrastructure.Auditors | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 LighthouseSocial.Infrastructure.Configuration | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 LighthouseSocial.Infrastructure.SecretManager | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 LighthouseSocial.WebApi.Controllers | 1 | 5 | 4 | |||||||||||||||||||||||||||||||||||||
| 27 LighthouseSocial.Application.Features.Comment | 3 | 3 | 3 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 28 LighthouseSocial.Application.Features.Country | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 LighthouseSocial.Application.Features.Lighthouse | 7 | 6 | 7 | 1 | 7 | |||||||||||||||||||||||||||||||||||
| 30 LighthouseSocial.Application.Features.Photo | 6 | 6 | 5 | 1 | 3 | 5 | ||||||||||||||||||||||||||||||||||
| 31 LighthouseSocial.Application.Features.Photo.Saga.Steps | 2 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 32 LighthouseSocial.Application.Features.User | 4 | 4 | 5 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 33 LighthouseSocial.Data.Repositories | 7 | 1 | 6 | 1 | 6 | 1 | 7 | |||||||||||||||||||||||||||||||||
| 34 LighthouseSocial.EventWorker.Services | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 LighthouseSocial.Infrastructure.Messaging | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 LighthouseSocial.Infrastructure.Storage | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 LighthouseSocial.ODataApi.Controllers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 TerminalApp.UseCases | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 LighthouseSocial.Application.Features.Photo.Saga | 1 | 1 | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 40 LighthouseSocial.Application.Services | 6 | 4 | 10 | 5 | 1 |
8→6 LightHouseSocial.Domain.Enumerations uses LighthouseSocial.Domain.Common✕
- Connections
- 1 pair of types, where a type in LightHouseSocial.Domain.Enumerations uses a type in LighthouseSocial.Domain.Common.
- The types involved
LightHouseSocial.Domain.Enumerations.PhotoCategory→LighthouseSocial.Domain.Common.EnumerationBase
- Direction
- LightHouseSocial.Domain.Enumerations uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LightHouseSocial.Domain.Enumerations, while a change to LightHouseSocial.Domain.Enumerations can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LightHouseSocial.Domain.Enumerations uses a module listed above it, which is the healthy direction.
9→1 LighthouseSocial.Application.Common.DistribtedTransaction.Saga uses LighthouseSocial.Application.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Common.DistribtedTransaction.Saga uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Common.DistribtedTransaction.Saga.ISagaStep→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Common.DistribtedTransaction.Saga uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Common.DistribtedTransaction.Saga, while a change to LighthouseSocial.Application.Common.DistribtedTransaction.Saga can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Common.DistribtedTransaction.Saga uses a module listed above it, which is the healthy direction.
10→2 LighthouseSocial.Application.Common.Pipeline.Behaviors uses LighthouseSocial.Application.Common.Pipeline✕
- Connections
- 4 pairs of types, where a type in LighthouseSocial.Application.Common.Pipeline.Behaviors uses a type in LighthouseSocial.Application.Common.Pipeline.
- The types involved
LighthouseSocial.Application.Common.Pipeline.Behaviors.CancellationBehavior→LighthouseSocial.Application.Common.Pipeline.IPipelineBehaviorLighthouseSocial.Application.Common.Pipeline.Behaviors.ExceptionHandlingBehavior→LighthouseSocial.Application.Common.Pipeline.IPipelineBehaviorLighthouseSocial.Application.Common.Pipeline.Behaviors.LoggingBehavior→LighthouseSocial.Application.Common.Pipeline.IPipelineBehaviorLighthouseSocial.Application.Common.Pipeline.Behaviors.PerformanceBehavior→LighthouseSocial.Application.Common.Pipeline.IPipelineBehavior
- Direction
- LighthouseSocial.Application.Common.Pipeline.Behaviors uses LighthouseSocial.Application.Common.Pipeline, so a change to LighthouseSocial.Application.Common.Pipeline can break LighthouseSocial.Application.Common.Pipeline.Behaviors, while a change to LighthouseSocial.Application.Common.Pipeline.Behaviors can't break LighthouseSocial.Application.Common.Pipeline.
- Position
- Below the diagonal: LighthouseSocial.Application.Common.Pipeline.Behaviors uses a module listed above it, which is the healthy direction.
11→1 LighthouseSocial.Application.Contracts uses LighthouseSocial.Application.Common✕
- Connections
- 3 pairs of types, where a type in LighthouseSocial.Application.Contracts uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Contracts.ICommentAuditor→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.IPhotoStorageService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.ISecretManager→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Contracts uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Contracts, while a change to LighthouseSocial.Application.Contracts can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Contracts uses a module listed above it, which is the healthy direction.
12→1 LighthouseSocial.Application.Contracts.ExternalServices uses LighthouseSocial.Application.Common✕
- Connections
- 6 pairs of types, where a type in LighthouseSocial.Application.Contracts.ExternalServices uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Contracts.ExternalServices.ICountryService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.ExternalServices.ILighthouseService→LighthouseSocial.Application.Common.PagedResultLighthouseSocial.Application.Contracts.ExternalServices.ILighthouseService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.ExternalServices.IPhotoService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.ExternalServices.IPhotoUploadService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.ExternalServices.IUserService→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Contracts.ExternalServices uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Contracts.ExternalServices, while a change to LighthouseSocial.Application.Contracts.ExternalServices can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Contracts.ExternalServices uses a module listed above it, which is the healthy direction.
12→3 LighthouseSocial.Application.Contracts.ExternalServices uses LighthouseSocial.Application.Dtos✕
- Connections
- 10 pairs of types, where a type in LighthouseSocial.Application.Contracts.ExternalServices uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.Application.Contracts.ExternalServices.ICountryService→LighthouseSocial.Application.Dtos.CountryDtoLighthouseSocial.Application.Contracts.ExternalServices.ILighthouseService→LighthouseSocial.Application.Dtos.LighthouseDtoLighthouseSocial.Application.Contracts.ExternalServices.ILighthouseService→LighthouseSocial.Application.Dtos.LighthouseTopDtoLighthouseSocial.Application.Contracts.ExternalServices.ILighthouseService→LighthouseSocial.Application.Dtos.LighthouseUpsertDtoLighthouseSocial.Application.Contracts.ExternalServices.ILighthouseService→LighthouseSocial.Application.Dtos.PagingDtoLighthouseSocial.Application.Contracts.ExternalServices.ILighthouseService→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.Application.Contracts.ExternalServices.ILighthouseService→LighthouseSocial.Application.Dtos.TopDtoLighthouseSocial.Application.Contracts.ExternalServices.IPhotoService→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.Application.Contracts.ExternalServices.IPhotoUploadService→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.Application.Contracts.ExternalServices.IUserService→LighthouseSocial.Application.Dtos.UserDto
- Direction
- LighthouseSocial.Application.Contracts.ExternalServices uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.Application.Contracts.ExternalServices, while a change to LighthouseSocial.Application.Contracts.ExternalServices can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.Application.Contracts.ExternalServices uses a module listed above it, which is the healthy direction.
13→4 LighthouseSocial.Backoffice.Services uses LighthouseSocial.Backoffice.Models✕
- Connections
- 18 pairs of types, where a type in LighthouseSocial.Backoffice.Services uses a type in LighthouseSocial.Backoffice.Models.
- The types involved
LighthouseSocial.Backoffice.Services.CountryServiceClient→LighthouseSocial.Backoffice.Models.ApiResponseLighthouseSocial.Backoffice.Services.CountryServiceClient→LighthouseSocial.Backoffice.Models.CountryDtoLighthouseSocial.Backoffice.Services.ICountryServiceClient→LighthouseSocial.Backoffice.Models.ApiResponseLighthouseSocial.Backoffice.Services.ICountryServiceClient→LighthouseSocial.Backoffice.Models.CountryDtoLighthouseSocial.Backoffice.Services.ILigthouseServiceClient→LighthouseSocial.Backoffice.Models.ApiResponseLighthouseSocial.Backoffice.Services.ILigthouseServiceClient→LighthouseSocial.Backoffice.Models.CreateLighthouseRequestLighthouseSocial.Backoffice.Services.ILigthouseServiceClient→LighthouseSocial.Backoffice.Models.LighthouseDtoLighthouseSocial.Backoffice.Services.ILigthouseServiceClient→LighthouseSocial.Backoffice.Models.PagedResultLighthouseSocial.Backoffice.Services.IPhotoServiceClient→LighthouseSocial.Backoffice.Models.ApiResponseLighthouseSocial.Backoffice.Services.IPhotoUploadServiceClient→LighthouseSocial.Backoffice.Models.ApiResponseLighthouseSocial.Backoffice.Services.IPhotoUploadServiceClient→LighthouseSocial.Backoffice.Models.PhotoUploadRequestLighthouseSocial.Backoffice.Services.LigthouseServiceClient→LighthouseSocial.Backoffice.Models.ApiResponseLighthouseSocial.Backoffice.Services.LigthouseServiceClient→LighthouseSocial.Backoffice.Models.CreateLighthouseRequestLighthouseSocial.Backoffice.Services.LigthouseServiceClient→LighthouseSocial.Backoffice.Models.LighthouseDtoLighthouseSocial.Backoffice.Services.LigthouseServiceClient→LighthouseSocial.Backoffice.Models.PagedResultLighthouseSocial.Backoffice.Services.PhotoServiceClient→LighthouseSocial.Backoffice.Models.ApiResponseLighthouseSocial.Backoffice.Services.PhotoUploadServiceClient→LighthouseSocial.Backoffice.Models.ApiResponseLighthouseSocial.Backoffice.Services.PhotoUploadServiceClient→LighthouseSocial.Backoffice.Models.PhotoUploadRequest
- Direction
- LighthouseSocial.Backoffice.Services uses LighthouseSocial.Backoffice.Models, so a change to LighthouseSocial.Backoffice.Models can break LighthouseSocial.Backoffice.Services, while a change to LighthouseSocial.Backoffice.Services can't break LighthouseSocial.Backoffice.Models.
- Position
- Below the diagonal: LighthouseSocial.Backoffice.Services uses a module listed above it, which is the healthy direction.
14→6 LighthouseSocial.Domain.Entities uses LighthouseSocial.Domain.Common✕
- Connections
- 4 pairs of types, where a type in LighthouseSocial.Domain.Entities uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Domain.Entities.Comment→LighthouseSocial.Domain.Common.EntityBaseLighthouseSocial.Domain.Entities.Lighthouse→LighthouseSocial.Domain.Common.EntityBaseLighthouseSocial.Domain.Entities.Photo→LighthouseSocial.Domain.Common.EntityBaseLighthouseSocial.Domain.Entities.User→LighthouseSocial.Domain.Common.EntityBase
- Direction
- LighthouseSocial.Domain.Entities uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Domain.Entities, while a change to LighthouseSocial.Domain.Entities can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Domain.Entities uses a module listed above it, which is the healthy direction.
14→7 LighthouseSocial.Domain.Entities uses LighthouseSocial.Domain.ValueObjects✕
- Connections
- 3 pairs of types, where a type in LighthouseSocial.Domain.Entities uses a type in LighthouseSocial.Domain.ValueObjects.
- The types involved
LighthouseSocial.Domain.Entities.Comment→LighthouseSocial.Domain.ValueObjects.RatingLighthouseSocial.Domain.Entities.Lighthouse→LighthouseSocial.Domain.ValueObjects.CoordinatesLighthouseSocial.Domain.Entities.Photo→LighthouseSocial.Domain.ValueObjects.PhotoMetadata
- Direction
- LighthouseSocial.Domain.Entities uses LighthouseSocial.Domain.ValueObjects, so a change to LighthouseSocial.Domain.ValueObjects can break LighthouseSocial.Domain.Entities, while a change to LighthouseSocial.Domain.Entities can't break LighthouseSocial.Domain.ValueObjects.
- Position
- Below the diagonal: LighthouseSocial.Domain.Entities uses a module listed above it, which is the healthy direction.
15→6 LighthouseSocial.Domain.Enumerations uses LighthouseSocial.Domain.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Domain.Enumerations uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Domain.Enumerations.CameraType→LighthouseSocial.Domain.Common.EnumerationBase
- Direction
- LighthouseSocial.Domain.Enumerations uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Domain.Enumerations, while a change to LighthouseSocial.Domain.Enumerations can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Domain.Enumerations uses a module listed above it, which is the healthy direction.
16→6 LighthouseSocial.Domain.Events.Comment uses LighthouseSocial.Domain.Common✕
- Connections
- 3 pairs of types, where a type in LighthouseSocial.Domain.Events.Comment uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Domain.Events.Comment.CommentCreated→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Comment.CommentCreationFailed→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Comment.CommentCreationRequested→LighthouseSocial.Domain.Common.EventBase
- Direction
- LighthouseSocial.Domain.Events.Comment uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Domain.Events.Comment, while a change to LighthouseSocial.Domain.Events.Comment can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Domain.Events.Comment uses a module listed above it, which is the healthy direction.
17→6 LighthouseSocial.Domain.Events.Lighthouse uses LighthouseSocial.Domain.Common✕
- Connections
- 3 pairs of types, where a type in LighthouseSocial.Domain.Events.Lighthouse uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Domain.Events.Lighthouse.LighthouseCreated→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Lighthouse.LighthouseCreationFailed→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Lighthouse.LighthouseCreationRequested→LighthouseSocial.Domain.Common.EventBase
- Direction
- LighthouseSocial.Domain.Events.Lighthouse uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Domain.Events.Lighthouse, while a change to LighthouseSocial.Domain.Events.Lighthouse can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Domain.Events.Lighthouse uses a module listed above it, which is the healthy direction.
18→6 LighthouseSocial.Domain.Events.Photo uses LighthouseSocial.Domain.Common✕
- Connections
- 9 pairs of types, where a type in LighthouseSocial.Domain.Events.Photo uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Domain.Events.Photo.PhotoSavedToRepository→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Photo.PhotoUploadFailed→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Photo.PhotoUploadRequested→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Photo.PhotoUploadSagaCompensationCompleted→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Photo.PhotoUploadSagaCompensationStarted→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Photo.PhotoUploadSagaCompleted→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Photo.PhotoUploadSagaFailed→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Photo.PhotoUploadSagaStarted→LighthouseSocial.Domain.Common.EventBaseLighthouseSocial.Domain.Events.Photo.PhotoUploaded→LighthouseSocial.Domain.Common.EventBase
- Direction
- LighthouseSocial.Domain.Events.Photo uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Domain.Events.Photo, while a change to LighthouseSocial.Domain.Events.Photo can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Domain.Events.Photo uses a module listed above it, which is the healthy direction.
19→34 LighthouseSocial.EventWorker.Strategies uses LighthouseSocial.EventWorker.Services part of a loop✕
- Connections
- 3 pairs of types, where a type in LighthouseSocial.EventWorker.Strategies uses a type in LighthouseSocial.EventWorker.Services.
- The types involved
LighthouseSocial.EventWorker.Strategies.EventDispatcher→LighthouseSocial.EventWorker.Services.EventMessageLighthouseSocial.EventWorker.Strategies.HandlePhotoUploadedStrategy→LighthouseSocial.EventWorker.Services.EventMessageLighthouseSocial.EventWorker.Strategies.IEventStrategy→LighthouseSocial.EventWorker.Services.EventMessage
- Direction
- LighthouseSocial.EventWorker.Strategies uses LighthouseSocial.EventWorker.Services, so a change to LighthouseSocial.EventWorker.Services can break LighthouseSocial.EventWorker.Strategies, while a change to LighthouseSocial.EventWorker.Strategies can't break LighthouseSocial.EventWorker.Services.
- 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.
20→1 LighthouseSocial.Infrastructure.Caching uses LighthouseSocial.Application.Common✕
- Connections
- 3 pairs of types, where a type in LighthouseSocial.Infrastructure.Caching uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Infrastructure.Caching.ICacheService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Infrastructure.Caching.MemoryCacheService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Infrastructure.Caching.RedisCacheService→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Infrastructure.Caching uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Infrastructure.Caching, while a change to LighthouseSocial.Infrastructure.Caching can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.Caching uses a module listed above it, which is the healthy direction.
21→1 LighthouseSocial.Application.Contracts.Repositories uses LighthouseSocial.Application.Common✕
- Connections
- 6 pairs of types, where a type in LighthouseSocial.Application.Contracts.Repositories uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Contracts.Repositories.ICommentRepository→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.Repositories.ICountryDataReader→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.Repositories.ILighthouseODataRepository→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.Repositories.ILighthouseRepository→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.Repositories.IPhotoRepository→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Contracts.Repositories.IUserRepository→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Contracts.Repositories uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Contracts.Repositories, while a change to LighthouseSocial.Application.Contracts.Repositories can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Contracts.Repositories uses a module listed above it, which is the healthy direction.
21→3 LighthouseSocial.Application.Contracts.Repositories uses LighthouseSocial.Application.Dtos✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Contracts.Repositories uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.Application.Contracts.Repositories.ILighthouseODataRepository→LighthouseSocial.Application.Dtos.QueryableLighthouseDto
- Direction
- LighthouseSocial.Application.Contracts.Repositories uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.Application.Contracts.Repositories, while a change to LighthouseSocial.Application.Contracts.Repositories can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.Application.Contracts.Repositories uses a module listed above it, which is the healthy direction.
21→7 LighthouseSocial.Application.Contracts.Repositories uses LighthouseSocial.Domain.ValueObjects✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Contracts.Repositories uses a type in LighthouseSocial.Domain.ValueObjects.
- The types involved
LighthouseSocial.Application.Contracts.Repositories.ILighthouseRepository→LighthouseSocial.Domain.ValueObjects.LighthouseWithStats
- Direction
- LighthouseSocial.Application.Contracts.Repositories uses LighthouseSocial.Domain.ValueObjects, so a change to LighthouseSocial.Domain.ValueObjects can break LighthouseSocial.Application.Contracts.Repositories, while a change to LighthouseSocial.Application.Contracts.Repositories can't break LighthouseSocial.Domain.ValueObjects.
- Position
- Below the diagonal: LighthouseSocial.Application.Contracts.Repositories uses a module listed above it, which is the healthy direction.
21→14 LighthouseSocial.Application.Contracts.Repositories uses LighthouseSocial.Domain.Entities✕
- Connections
- 5 pairs of types, where a type in LighthouseSocial.Application.Contracts.Repositories uses a type in LighthouseSocial.Domain.Entities.
- The types involved
LighthouseSocial.Application.Contracts.Repositories.ICommentRepository→LighthouseSocial.Domain.Entities.CommentLighthouseSocial.Application.Contracts.Repositories.ICountryDataReader→LighthouseSocial.Domain.Entities.CountryLighthouseSocial.Application.Contracts.Repositories.ILighthouseRepository→LighthouseSocial.Domain.Entities.LighthouseLighthouseSocial.Application.Contracts.Repositories.IPhotoRepository→LighthouseSocial.Domain.Entities.PhotoLighthouseSocial.Application.Contracts.Repositories.IUserRepository→LighthouseSocial.Domain.Entities.User
- Direction
- LighthouseSocial.Application.Contracts.Repositories uses LighthouseSocial.Domain.Entities, so a change to LighthouseSocial.Domain.Entities can break LighthouseSocial.Application.Contracts.Repositories, while a change to LighthouseSocial.Application.Contracts.Repositories can't break LighthouseSocial.Domain.Entities.
- Position
- Below the diagonal: LighthouseSocial.Application.Contracts.Repositories uses a module listed above it, which is the healthy direction.
22→4 LighthouseSocial.Backoffice.Pages.Lighthouse uses LighthouseSocial.Backoffice.Models✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Backoffice.Pages.Lighthouse uses a type in LighthouseSocial.Backoffice.Models.
- The types involved
LighthouseSocial.Backoffice.Pages.Lighthouse.ListModel→LighthouseSocial.Backoffice.Models.LighthouseDto
- Direction
- LighthouseSocial.Backoffice.Pages.Lighthouse uses LighthouseSocial.Backoffice.Models, so a change to LighthouseSocial.Backoffice.Models can break LighthouseSocial.Backoffice.Pages.Lighthouse, while a change to LighthouseSocial.Backoffice.Pages.Lighthouse can't break LighthouseSocial.Backoffice.Models.
- Position
- Below the diagonal: LighthouseSocial.Backoffice.Pages.Lighthouse uses a module listed above it, which is the healthy direction.
22→13 LighthouseSocial.Backoffice.Pages.Lighthouse uses LighthouseSocial.Backoffice.Services✕
- Connections
- 5 pairs of types, where a type in LighthouseSocial.Backoffice.Pages.Lighthouse uses a type in LighthouseSocial.Backoffice.Services.
- The types involved
LighthouseSocial.Backoffice.Pages.Lighthouse.CreateModel→LighthouseSocial.Backoffice.Services.ICountryServiceClientLighthouseSocial.Backoffice.Pages.Lighthouse.CreateModel→LighthouseSocial.Backoffice.Services.ILigthouseServiceClientLighthouseSocial.Backoffice.Pages.Lighthouse.CreateModel→LighthouseSocial.Backoffice.Services.IPhotoUploadServiceClientLighthouseSocial.Backoffice.Pages.Lighthouse.ListModel→LighthouseSocial.Backoffice.Services.ILigthouseServiceClientLighthouseSocial.Backoffice.Pages.Lighthouse.ListModel→LighthouseSocial.Backoffice.Services.IPhotoServiceClient
- Direction
- LighthouseSocial.Backoffice.Pages.Lighthouse uses LighthouseSocial.Backoffice.Services, so a change to LighthouseSocial.Backoffice.Services can break LighthouseSocial.Backoffice.Pages.Lighthouse, while a change to LighthouseSocial.Backoffice.Pages.Lighthouse can't break LighthouseSocial.Backoffice.Services.
- Position
- Below the diagonal: LighthouseSocial.Backoffice.Pages.Lighthouse uses a module listed above it, which is the healthy direction.
23→1 LighthouseSocial.Infrastructure.Auditors uses LighthouseSocial.Application.Common✕
- Connections
- 2 pairs of types, where a type in LighthouseSocial.Infrastructure.Auditors uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Infrastructure.Auditors.DefaultCommentAuditor→LighthouseSocial.Application.Common.ResultLighthouseSocial.Infrastructure.Auditors.ExternalCommentAuditor→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Infrastructure.Auditors uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Infrastructure.Auditors, while a change to LighthouseSocial.Infrastructure.Auditors can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.Auditors uses a module listed above it, which is the healthy direction.
23→11 LighthouseSocial.Infrastructure.Auditors uses LighthouseSocial.Application.Contracts✕
- Connections
- 2 pairs of types, where a type in LighthouseSocial.Infrastructure.Auditors uses a type in LighthouseSocial.Application.Contracts.
- The types involved
LighthouseSocial.Infrastructure.Auditors.DefaultCommentAuditor→LighthouseSocial.Application.Contracts.ICommentAuditorLighthouseSocial.Infrastructure.Auditors.ExternalCommentAuditor→LighthouseSocial.Application.Contracts.ICommentAuditor
- Direction
- LighthouseSocial.Infrastructure.Auditors uses LighthouseSocial.Application.Contracts, so a change to LighthouseSocial.Application.Contracts can break LighthouseSocial.Infrastructure.Auditors, while a change to LighthouseSocial.Infrastructure.Auditors can't break LighthouseSocial.Application.Contracts.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.Auditors uses a module listed above it, which is the healthy direction.
24→11 LighthouseSocial.Infrastructure.Configuration uses LighthouseSocial.Application.Contracts✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Infrastructure.Configuration uses a type in LighthouseSocial.Application.Contracts.
- The types involved
LighthouseSocial.Infrastructure.Configuration.CachedConfigurationService→LighthouseSocial.Application.Contracts.ISecretManager
- Direction
- LighthouseSocial.Infrastructure.Configuration uses LighthouseSocial.Application.Contracts, so a change to LighthouseSocial.Application.Contracts can break LighthouseSocial.Infrastructure.Configuration, while a change to LighthouseSocial.Infrastructure.Configuration can't break LighthouseSocial.Application.Contracts.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.Configuration uses a module listed above it, which is the healthy direction.
24→20 LighthouseSocial.Infrastructure.Configuration uses LighthouseSocial.Infrastructure.Caching✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Infrastructure.Configuration uses a type in LighthouseSocial.Infrastructure.Caching.
- The types involved
LighthouseSocial.Infrastructure.Configuration.CachedConfigurationService→LighthouseSocial.Infrastructure.Caching.ICacheService
- Direction
- LighthouseSocial.Infrastructure.Configuration uses LighthouseSocial.Infrastructure.Caching, so a change to LighthouseSocial.Infrastructure.Caching can break LighthouseSocial.Infrastructure.Configuration, while a change to LighthouseSocial.Infrastructure.Configuration can't break LighthouseSocial.Infrastructure.Caching.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.Configuration uses a module listed above it, which is the healthy direction.
25→1 LighthouseSocial.Infrastructure.SecretManager uses LighthouseSocial.Application.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Infrastructure.SecretManager uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Infrastructure.SecretManager.VaultSecretManager→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Infrastructure.SecretManager uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Infrastructure.SecretManager, while a change to LighthouseSocial.Infrastructure.SecretManager can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.SecretManager uses a module listed above it, which is the healthy direction.
25→11 LighthouseSocial.Infrastructure.SecretManager uses LighthouseSocial.Application.Contracts✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Infrastructure.SecretManager uses a type in LighthouseSocial.Application.Contracts.
- The types involved
LighthouseSocial.Infrastructure.SecretManager.VaultSecretManager→LighthouseSocial.Application.Contracts.ISecretManager
- Direction
- LighthouseSocial.Infrastructure.SecretManager uses LighthouseSocial.Application.Contracts, so a change to LighthouseSocial.Application.Contracts can break LighthouseSocial.Infrastructure.SecretManager, while a change to LighthouseSocial.Infrastructure.SecretManager can't break LighthouseSocial.Application.Contracts.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.SecretManager uses a module listed above it, which is the healthy direction.
26→1 LighthouseSocial.WebApi.Controllers uses LighthouseSocial.Application.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.WebApi.Controllers uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.WebApi.Controllers.LighthouseController→LighthouseSocial.Application.Common.PagedResult
- Direction
- LighthouseSocial.WebApi.Controllers uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.WebApi.Controllers, while a change to LighthouseSocial.WebApi.Controllers can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.WebApi.Controllers uses a module listed above it, which is the healthy direction.
26→3 LighthouseSocial.WebApi.Controllers uses LighthouseSocial.Application.Dtos✕
- Connections
- 5 pairs of types, where a type in LighthouseSocial.WebApi.Controllers uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.WebApi.Controllers.CountryController→LighthouseSocial.Application.Dtos.CountryDtoLighthouseSocial.WebApi.Controllers.LighthouseController→LighthouseSocial.Application.Dtos.LighthouseDtoLighthouseSocial.WebApi.Controllers.LighthouseController→LighthouseSocial.Application.Dtos.LighthouseTopDtoLighthouseSocial.WebApi.Controllers.LighthouseController→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.WebApi.Controllers.PhotoController→LighthouseSocial.Application.Dtos.PhotoDto
- Direction
- LighthouseSocial.WebApi.Controllers uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.WebApi.Controllers, while a change to LighthouseSocial.WebApi.Controllers can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.WebApi.Controllers uses a module listed above it, which is the healthy direction.
26→12 LighthouseSocial.WebApi.Controllers uses LighthouseSocial.Application.Contracts.ExternalServices✕
- Connections
- 4 pairs of types, where a type in LighthouseSocial.WebApi.Controllers uses a type in LighthouseSocial.Application.Contracts.ExternalServices.
- The types involved
LighthouseSocial.WebApi.Controllers.CountryController→LighthouseSocial.Application.Contracts.ExternalServices.ICountryServiceLighthouseSocial.WebApi.Controllers.LighthouseController→LighthouseSocial.Application.Contracts.ExternalServices.ILighthouseServiceLighthouseSocial.WebApi.Controllers.PhotoController→LighthouseSocial.Application.Contracts.ExternalServices.IPhotoServiceLighthouseSocial.WebApi.Controllers.PhotoUploadController→LighthouseSocial.Application.Contracts.ExternalServices.IPhotoUploadService
- Direction
- LighthouseSocial.WebApi.Controllers uses LighthouseSocial.Application.Contracts.ExternalServices, so a change to LighthouseSocial.Application.Contracts.ExternalServices can break LighthouseSocial.WebApi.Controllers, while a change to LighthouseSocial.WebApi.Controllers can't break LighthouseSocial.Application.Contracts.ExternalServices.
- Position
- Below the diagonal: LighthouseSocial.WebApi.Controllers uses a module listed above it, which is the healthy direction.
27→1 LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Application.Common✕
- Connections
- 3 pairs of types, where a type in LighthouseSocial.Application.Features.Comment uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Features.Comment.AddCommentHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Comment.DeleteCommentHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Comment.GetCommentsByPhotoHandler→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Features.Comment, while a change to LighthouseSocial.Application.Features.Comment can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Comment uses a module listed above it, which is the healthy direction.
27→2 LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Application.Common.Pipeline✕
- Connections
- 3 pairs of types, where a type in LighthouseSocial.Application.Features.Comment uses a type in LighthouseSocial.Application.Common.Pipeline.
- The types involved
LighthouseSocial.Application.Features.Comment.AddCommentHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Comment.DeleteCommentHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Comment.GetCommentsByPhotoHandler→LighthouseSocial.Application.Common.Pipeline.IHandler
- Direction
- LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Application.Common.Pipeline, so a change to LighthouseSocial.Application.Common.Pipeline can break LighthouseSocial.Application.Features.Comment, while a change to LighthouseSocial.Application.Features.Comment can't break LighthouseSocial.Application.Common.Pipeline.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Comment uses a module listed above it, which is the healthy direction.
27→3 LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Application.Dtos✕
- Connections
- 3 pairs of types, where a type in LighthouseSocial.Application.Features.Comment uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.Application.Features.Comment.AddCommentHandler→LighthouseSocial.Application.Dtos.CommentDtoLighthouseSocial.Application.Features.Comment.AddCommentRequest→LighthouseSocial.Application.Dtos.CommentDtoLighthouseSocial.Application.Features.Comment.GetCommentsByPhotoHandler→LighthouseSocial.Application.Dtos.CommentDto
- Direction
- LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.Application.Features.Comment, while a change to LighthouseSocial.Application.Features.Comment can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Comment uses a module listed above it, which is the healthy direction.
27→6 LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Domain.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Comment uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Application.Features.Comment.AddCommentHandler→LighthouseSocial.Domain.Common.IEventPublisher
- Direction
- LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Application.Features.Comment, while a change to LighthouseSocial.Application.Features.Comment can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Comment uses a module listed above it, which is the healthy direction.
27→11 LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Application.Contracts✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Comment uses a type in LighthouseSocial.Application.Contracts.
- The types involved
LighthouseSocial.Application.Features.Comment.AddCommentHandler→LighthouseSocial.Application.Contracts.ICommentAuditor
- Direction
- LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Application.Contracts, so a change to LighthouseSocial.Application.Contracts can break LighthouseSocial.Application.Features.Comment, while a change to LighthouseSocial.Application.Features.Comment can't break LighthouseSocial.Application.Contracts.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Comment uses a module listed above it, which is the healthy direction.
27→21 LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Application.Contracts.Repositories✕
- Connections
- 5 pairs of types, where a type in LighthouseSocial.Application.Features.Comment uses a type in LighthouseSocial.Application.Contracts.Repositories.
- The types involved
LighthouseSocial.Application.Features.Comment.AddCommentHandler→LighthouseSocial.Application.Contracts.Repositories.ICommentRepositoryLighthouseSocial.Application.Features.Comment.AddCommentHandler→LighthouseSocial.Application.Contracts.Repositories.IPhotoRepositoryLighthouseSocial.Application.Features.Comment.AddCommentHandler→LighthouseSocial.Application.Contracts.Repositories.IUserRepositoryLighthouseSocial.Application.Features.Comment.DeleteCommentHandler→LighthouseSocial.Application.Contracts.Repositories.ICommentRepositoryLighthouseSocial.Application.Features.Comment.GetCommentsByPhotoHandler→LighthouseSocial.Application.Contracts.Repositories.ICommentRepository
- Direction
- LighthouseSocial.Application.Features.Comment uses LighthouseSocial.Application.Contracts.Repositories, so a change to LighthouseSocial.Application.Contracts.Repositories can break LighthouseSocial.Application.Features.Comment, while a change to LighthouseSocial.Application.Features.Comment can't break LighthouseSocial.Application.Contracts.Repositories.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Comment uses a module listed above it, which is the healthy direction.
28→1 LighthouseSocial.Application.Features.Country uses LighthouseSocial.Application.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Country uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Features.Country.GetAllCountriesHandler→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Features.Country uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Features.Country, while a change to LighthouseSocial.Application.Features.Country can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Country uses a module listed above it, which is the healthy direction.
28→2 LighthouseSocial.Application.Features.Country uses LighthouseSocial.Application.Common.Pipeline✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Country uses a type in LighthouseSocial.Application.Common.Pipeline.
- The types involved
LighthouseSocial.Application.Features.Country.GetAllCountriesHandler→LighthouseSocial.Application.Common.Pipeline.IHandler
- Direction
- LighthouseSocial.Application.Features.Country uses LighthouseSocial.Application.Common.Pipeline, so a change to LighthouseSocial.Application.Common.Pipeline can break LighthouseSocial.Application.Features.Country, while a change to LighthouseSocial.Application.Features.Country can't break LighthouseSocial.Application.Common.Pipeline.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Country uses a module listed above it, which is the healthy direction.
28→3 LighthouseSocial.Application.Features.Country uses LighthouseSocial.Application.Dtos✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Country uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.Application.Features.Country.GetAllCountriesHandler→LighthouseSocial.Application.Dtos.CountryDto
- Direction
- LighthouseSocial.Application.Features.Country uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.Application.Features.Country, while a change to LighthouseSocial.Application.Features.Country can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Country uses a module listed above it, which is the healthy direction.
28→21 LighthouseSocial.Application.Features.Country uses LighthouseSocial.Application.Contracts.Repositories✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Country uses a type in LighthouseSocial.Application.Contracts.Repositories.
- The types involved
LighthouseSocial.Application.Features.Country.GetAllCountriesHandler→LighthouseSocial.Application.Contracts.Repositories.ICountryDataReader
- Direction
- LighthouseSocial.Application.Features.Country uses LighthouseSocial.Application.Contracts.Repositories, so a change to LighthouseSocial.Application.Contracts.Repositories can break LighthouseSocial.Application.Features.Country, while a change to LighthouseSocial.Application.Features.Country can't break LighthouseSocial.Application.Contracts.Repositories.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Country uses a module listed above it, which is the healthy direction.
29→1 LighthouseSocial.Application.Features.Lighthouse uses LighthouseSocial.Application.Common✕
- Connections
- 7 pairs of types, where a type in LighthouseSocial.Application.Features.Lighthouse uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Features.Lighthouse.CreateLighthouseHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Lighthouse.DeleteLighthouseHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Lighthouse.GetLighthouseByIdHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Lighthouse.GetPagedLighthouseHandler→LighthouseSocial.Application.Common.PagedResultLighthouseSocial.Application.Features.Lighthouse.GetPagedLighthouseHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Lighthouse.GetTopLighthousesHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Lighthouse.UpdateLighthouseHandler→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Features.Lighthouse uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Features.Lighthouse, while a change to LighthouseSocial.Application.Features.Lighthouse can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Lighthouse uses a module listed above it, which is the healthy direction.
29→2 LighthouseSocial.Application.Features.Lighthouse uses LighthouseSocial.Application.Common.Pipeline✕
- Connections
- 6 pairs of types, where a type in LighthouseSocial.Application.Features.Lighthouse uses a type in LighthouseSocial.Application.Common.Pipeline.
- The types involved
LighthouseSocial.Application.Features.Lighthouse.CreateLighthouseHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Lighthouse.DeleteLighthouseHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Lighthouse.GetLighthouseByIdHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Lighthouse.GetPagedLighthouseHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Lighthouse.GetTopLighthousesHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Lighthouse.UpdateLighthouseHandler→LighthouseSocial.Application.Common.Pipeline.IHandler
- Direction
- LighthouseSocial.Application.Features.Lighthouse uses LighthouseSocial.Application.Common.Pipeline, so a change to LighthouseSocial.Application.Common.Pipeline can break LighthouseSocial.Application.Features.Lighthouse, while a change to LighthouseSocial.Application.Features.Lighthouse can't break LighthouseSocial.Application.Common.Pipeline.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Lighthouse uses a module listed above it, which is the healthy direction.
29→3 LighthouseSocial.Application.Features.Lighthouse uses LighthouseSocial.Application.Dtos✕
- Connections
- 7 pairs of types, where a type in LighthouseSocial.Application.Features.Lighthouse uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.Application.Features.Lighthouse.CreateLighthouseHandler→LighthouseSocial.Application.Dtos.LighthouseUpsertDtoLighthouseSocial.Application.Features.Lighthouse.CreateLighthouseRequest→LighthouseSocial.Application.Dtos.LighthouseUpsertDtoLighthouseSocial.Application.Features.Lighthouse.GetLighthouseByIdHandler→LighthouseSocial.Application.Dtos.LighthouseDtoLighthouseSocial.Application.Features.Lighthouse.GetPagedLighthouseHandler→LighthouseSocial.Application.Dtos.LighthouseDtoLighthouseSocial.Application.Features.Lighthouse.GetPagedLighthouseRequest→LighthouseSocial.Application.Dtos.PagingDtoLighthouseSocial.Application.Features.Lighthouse.GetTopLighthousesHandler→LighthouseSocial.Application.Dtos.LighthouseTopDtoLighthouseSocial.Application.Features.Lighthouse.UpdateLighthouseRequest→LighthouseSocial.Application.Dtos.LighthouseUpsertDto
- Direction
- LighthouseSocial.Application.Features.Lighthouse uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.Application.Features.Lighthouse, while a change to LighthouseSocial.Application.Features.Lighthouse can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Lighthouse uses a module listed above it, which is the healthy direction.
29→6 LighthouseSocial.Application.Features.Lighthouse uses LighthouseSocial.Domain.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Lighthouse uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Application.Features.Lighthouse.CreateLighthouseHandler→LighthouseSocial.Domain.Common.IEventPublisher
- Direction
- LighthouseSocial.Application.Features.Lighthouse uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Application.Features.Lighthouse, while a change to LighthouseSocial.Application.Features.Lighthouse can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Lighthouse uses a module listed above it, which is the healthy direction.
29→21 LighthouseSocial.Application.Features.Lighthouse uses LighthouseSocial.Application.Contracts.Repositories✕
- Connections
- 7 pairs of types, where a type in LighthouseSocial.Application.Features.Lighthouse uses a type in LighthouseSocial.Application.Contracts.Repositories.
- The types involved
LighthouseSocial.Application.Features.Lighthouse.CreateLighthouseHandler→LighthouseSocial.Application.Contracts.Repositories.ICountryDataReaderLighthouseSocial.Application.Features.Lighthouse.CreateLighthouseHandler→LighthouseSocial.Application.Contracts.Repositories.ILighthouseRepositoryLighthouseSocial.Application.Features.Lighthouse.DeleteLighthouseHandler→LighthouseSocial.Application.Contracts.Repositories.ILighthouseRepositoryLighthouseSocial.Application.Features.Lighthouse.GetLighthouseByIdHandler→LighthouseSocial.Application.Contracts.Repositories.ILighthouseRepositoryLighthouseSocial.Application.Features.Lighthouse.GetPagedLighthouseHandler→LighthouseSocial.Application.Contracts.Repositories.ILighthouseRepositoryLighthouseSocial.Application.Features.Lighthouse.GetTopLighthousesHandler→LighthouseSocial.Application.Contracts.Repositories.ILighthouseRepositoryLighthouseSocial.Application.Features.Lighthouse.UpdateLighthouseHandler→LighthouseSocial.Application.Contracts.Repositories.ILighthouseRepository
- Direction
- LighthouseSocial.Application.Features.Lighthouse uses LighthouseSocial.Application.Contracts.Repositories, so a change to LighthouseSocial.Application.Contracts.Repositories can break LighthouseSocial.Application.Features.Lighthouse, while a change to LighthouseSocial.Application.Features.Lighthouse can't break LighthouseSocial.Application.Contracts.Repositories.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Lighthouse uses a module listed above it, which is the healthy direction.
30→1 LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Application.Common✕
- Connections
- 6 pairs of types, where a type in LighthouseSocial.Application.Features.Photo uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Features.Photo.DeletePhotoHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Photo.GetPhotoByIdHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Photo.GetPhotosByLighthouseHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Photo.GetPhotosByUserHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Photo.GetRawPhotoHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Photo.UploadPhotoHandler→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Features.Photo, while a change to LighthouseSocial.Application.Features.Photo can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo uses a module listed above it, which is the healthy direction.
30→2 LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Application.Common.Pipeline✕
- Connections
- 6 pairs of types, where a type in LighthouseSocial.Application.Features.Photo uses a type in LighthouseSocial.Application.Common.Pipeline.
- The types involved
LighthouseSocial.Application.Features.Photo.DeletePhotoHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Photo.GetPhotoByIdHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Photo.GetPhotosByLighthouseHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Photo.GetPhotosByUserHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Photo.GetRawPhotoHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.Photo.UploadPhotoHandler→LighthouseSocial.Application.Common.Pipeline.IHandler
- Direction
- LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Application.Common.Pipeline, so a change to LighthouseSocial.Application.Common.Pipeline can break LighthouseSocial.Application.Features.Photo, while a change to LighthouseSocial.Application.Features.Photo can't break LighthouseSocial.Application.Common.Pipeline.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo uses a module listed above it, which is the healthy direction.
30→3 LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Application.Dtos✕
- Connections
- 5 pairs of types, where a type in LighthouseSocial.Application.Features.Photo uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.Application.Features.Photo.GetPhotoByIdHandler→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.Application.Features.Photo.GetPhotosByLighthouseHandler→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.Application.Features.Photo.GetPhotosByUserHandler→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.Application.Features.Photo.UploadPhotoHandler→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.Application.Features.Photo.UploadPhotoRequest→LighthouseSocial.Application.Dtos.PhotoDto
- Direction
- LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.Application.Features.Photo, while a change to LighthouseSocial.Application.Features.Photo can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo uses a module listed above it, which is the healthy direction.
30→6 LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Domain.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Photo uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Application.Features.Photo.UploadPhotoHandler→LighthouseSocial.Domain.Common.IEventPublisher
- Direction
- LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Application.Features.Photo, while a change to LighthouseSocial.Application.Features.Photo can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo uses a module listed above it, which is the healthy direction.
30→11 LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Application.Contracts✕
- Connections
- 3 pairs of types, where a type in LighthouseSocial.Application.Features.Photo uses a type in LighthouseSocial.Application.Contracts.
- The types involved
LighthouseSocial.Application.Features.Photo.DeletePhotoHandler→LighthouseSocial.Application.Contracts.IPhotoStorageServiceLighthouseSocial.Application.Features.Photo.GetRawPhotoHandler→LighthouseSocial.Application.Contracts.IPhotoStorageServiceLighthouseSocial.Application.Features.Photo.UploadPhotoHandler→LighthouseSocial.Application.Contracts.IPhotoStorageService
- Direction
- LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Application.Contracts, so a change to LighthouseSocial.Application.Contracts can break LighthouseSocial.Application.Features.Photo, while a change to LighthouseSocial.Application.Features.Photo can't break LighthouseSocial.Application.Contracts.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo uses a module listed above it, which is the healthy direction.
30→21 LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Application.Contracts.Repositories✕
- Connections
- 5 pairs of types, where a type in LighthouseSocial.Application.Features.Photo uses a type in LighthouseSocial.Application.Contracts.Repositories.
- The types involved
LighthouseSocial.Application.Features.Photo.DeletePhotoHandler→LighthouseSocial.Application.Contracts.Repositories.IPhotoRepositoryLighthouseSocial.Application.Features.Photo.GetPhotoByIdHandler→LighthouseSocial.Application.Contracts.Repositories.IPhotoRepositoryLighthouseSocial.Application.Features.Photo.GetPhotosByLighthouseHandler→LighthouseSocial.Application.Contracts.Repositories.IPhotoRepositoryLighthouseSocial.Application.Features.Photo.GetPhotosByUserHandler→LighthouseSocial.Application.Contracts.Repositories.IPhotoRepositoryLighthouseSocial.Application.Features.Photo.UploadPhotoHandler→LighthouseSocial.Application.Contracts.Repositories.IPhotoRepository
- Direction
- LighthouseSocial.Application.Features.Photo uses LighthouseSocial.Application.Contracts.Repositories, so a change to LighthouseSocial.Application.Contracts.Repositories can break LighthouseSocial.Application.Features.Photo, while a change to LighthouseSocial.Application.Features.Photo can't break LighthouseSocial.Application.Contracts.Repositories.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo uses a module listed above it, which is the healthy direction.
31→1 LighthouseSocial.Application.Features.Photo.Saga.Steps uses LighthouseSocial.Application.Common✕
- Connections
- 2 pairs of types, where a type in LighthouseSocial.Application.Features.Photo.Saga.Steps uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.Steps.FileUploadStep→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.Photo.Saga.Steps.MetadataSaveStep→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Features.Photo.Saga.Steps uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Features.Photo.Saga.Steps, while a change to LighthouseSocial.Application.Features.Photo.Saga.Steps can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga.Steps uses a module listed above it, which is the healthy direction.
31→9 LighthouseSocial.Application.Features.Photo.Saga.Steps uses LighthouseSocial.Application.Common.DistribtedTransaction.Saga✕
- Connections
- 2 pairs of types, where a type in LighthouseSocial.Application.Features.Photo.Saga.Steps uses a type in LighthouseSocial.Application.Common.DistribtedTransaction.Saga.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.Steps.FileUploadStep→LighthouseSocial.Application.Common.DistribtedTransaction.Saga.ISagaStepLighthouseSocial.Application.Features.Photo.Saga.Steps.MetadataSaveStep→LighthouseSocial.Application.Common.DistribtedTransaction.Saga.ISagaStep
- Direction
- LighthouseSocial.Application.Features.Photo.Saga.Steps uses LighthouseSocial.Application.Common.DistribtedTransaction.Saga, so a change to LighthouseSocial.Application.Common.DistribtedTransaction.Saga can break LighthouseSocial.Application.Features.Photo.Saga.Steps, while a change to LighthouseSocial.Application.Features.Photo.Saga.Steps can't break LighthouseSocial.Application.Common.DistribtedTransaction.Saga.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga.Steps uses a module listed above it, which is the healthy direction.
31→11 LighthouseSocial.Application.Features.Photo.Saga.Steps uses LighthouseSocial.Application.Contracts✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Photo.Saga.Steps uses a type in LighthouseSocial.Application.Contracts.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.Steps.FileUploadStep→LighthouseSocial.Application.Contracts.IPhotoStorageService
- Direction
- LighthouseSocial.Application.Features.Photo.Saga.Steps uses LighthouseSocial.Application.Contracts, so a change to LighthouseSocial.Application.Contracts can break LighthouseSocial.Application.Features.Photo.Saga.Steps, while a change to LighthouseSocial.Application.Features.Photo.Saga.Steps can't break LighthouseSocial.Application.Contracts.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga.Steps uses a module listed above it, which is the healthy direction.
31→21 LighthouseSocial.Application.Features.Photo.Saga.Steps uses LighthouseSocial.Application.Contracts.Repositories✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Photo.Saga.Steps uses a type in LighthouseSocial.Application.Contracts.Repositories.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.Steps.MetadataSaveStep→LighthouseSocial.Application.Contracts.Repositories.IPhotoRepository
- Direction
- LighthouseSocial.Application.Features.Photo.Saga.Steps uses LighthouseSocial.Application.Contracts.Repositories, so a change to LighthouseSocial.Application.Contracts.Repositories can break LighthouseSocial.Application.Features.Photo.Saga.Steps, while a change to LighthouseSocial.Application.Features.Photo.Saga.Steps can't break LighthouseSocial.Application.Contracts.Repositories.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga.Steps uses a module listed above it, which is the healthy direction.
31→39 LighthouseSocial.Application.Features.Photo.Saga.Steps uses LighthouseSocial.Application.Features.Photo.Saga part of a loop✕
- Connections
- 2 pairs of types, where a type in LighthouseSocial.Application.Features.Photo.Saga.Steps uses a type in LighthouseSocial.Application.Features.Photo.Saga.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.Steps.FileUploadStep→LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSagaDataLighthouseSocial.Application.Features.Photo.Saga.Steps.MetadataSaveStep→LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSagaData
- Direction
- LighthouseSocial.Application.Features.Photo.Saga.Steps uses LighthouseSocial.Application.Features.Photo.Saga, so a change to LighthouseSocial.Application.Features.Photo.Saga can break LighthouseSocial.Application.Features.Photo.Saga.Steps, while a change to LighthouseSocial.Application.Features.Photo.Saga.Steps can't break LighthouseSocial.Application.Features.Photo.Saga.
- 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.
32→1 LighthouseSocial.Application.Features.User uses LighthouseSocial.Application.Common✕
- Connections
- 4 pairs of types, where a type in LighthouseSocial.Application.Features.User uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Features.User.CreateUserHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.User.GetUserByEmailHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.User.GetUserByIdHandler→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Features.User.GetUserBySubIdHandler→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Features.User uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Features.User, while a change to LighthouseSocial.Application.Features.User can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.User uses a module listed above it, which is the healthy direction.
32→2 LighthouseSocial.Application.Features.User uses LighthouseSocial.Application.Common.Pipeline✕
- Connections
- 4 pairs of types, where a type in LighthouseSocial.Application.Features.User uses a type in LighthouseSocial.Application.Common.Pipeline.
- The types involved
LighthouseSocial.Application.Features.User.CreateUserHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.User.GetUserByEmailHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.User.GetUserByIdHandler→LighthouseSocial.Application.Common.Pipeline.IHandlerLighthouseSocial.Application.Features.User.GetUserBySubIdHandler→LighthouseSocial.Application.Common.Pipeline.IHandler
- Direction
- LighthouseSocial.Application.Features.User uses LighthouseSocial.Application.Common.Pipeline, so a change to LighthouseSocial.Application.Common.Pipeline can break LighthouseSocial.Application.Features.User, while a change to LighthouseSocial.Application.Features.User can't break LighthouseSocial.Application.Common.Pipeline.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.User uses a module listed above it, which is the healthy direction.
32→3 LighthouseSocial.Application.Features.User uses LighthouseSocial.Application.Dtos✕
- Connections
- 5 pairs of types, where a type in LighthouseSocial.Application.Features.User uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.Application.Features.User.CreateUserHandler→LighthouseSocial.Application.Dtos.UserDtoLighthouseSocial.Application.Features.User.CreateUserRequest→LighthouseSocial.Application.Dtos.UserDtoLighthouseSocial.Application.Features.User.GetUserByEmailHandler→LighthouseSocial.Application.Dtos.UserDtoLighthouseSocial.Application.Features.User.GetUserByIdHandler→LighthouseSocial.Application.Dtos.UserDtoLighthouseSocial.Application.Features.User.GetUserBySubIdHandler→LighthouseSocial.Application.Dtos.UserDto
- Direction
- LighthouseSocial.Application.Features.User uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.Application.Features.User, while a change to LighthouseSocial.Application.Features.User can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.User uses a module listed above it, which is the healthy direction.
32→6 LighthouseSocial.Application.Features.User uses LighthouseSocial.Domain.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.User uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Application.Features.User.CreateUserHandler→LighthouseSocial.Domain.Common.IEventPublisher
- Direction
- LighthouseSocial.Application.Features.User uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Application.Features.User, while a change to LighthouseSocial.Application.Features.User can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.User uses a module listed above it, which is the healthy direction.
32→21 LighthouseSocial.Application.Features.User uses LighthouseSocial.Application.Contracts.Repositories✕
- Connections
- 4 pairs of types, where a type in LighthouseSocial.Application.Features.User uses a type in LighthouseSocial.Application.Contracts.Repositories.
- The types involved
LighthouseSocial.Application.Features.User.CreateUserHandler→LighthouseSocial.Application.Contracts.Repositories.IUserRepositoryLighthouseSocial.Application.Features.User.GetUserByEmailHandler→LighthouseSocial.Application.Contracts.Repositories.IUserRepositoryLighthouseSocial.Application.Features.User.GetUserByIdHandler→LighthouseSocial.Application.Contracts.Repositories.IUserRepositoryLighthouseSocial.Application.Features.User.GetUserBySubIdHandler→LighthouseSocial.Application.Contracts.Repositories.IUserRepository
- Direction
- LighthouseSocial.Application.Features.User uses LighthouseSocial.Application.Contracts.Repositories, so a change to LighthouseSocial.Application.Contracts.Repositories can break LighthouseSocial.Application.Features.User, while a change to LighthouseSocial.Application.Features.User can't break LighthouseSocial.Application.Contracts.Repositories.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.User uses a module listed above it, which is the healthy direction.
33→1 LighthouseSocial.Data.Repositories uses LighthouseSocial.Application.Common✕
- Connections
- 7 pairs of types, where a type in LighthouseSocial.Data.Repositories uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Data.Repositories.CachedCountryDataReader→LighthouseSocial.Application.Common.ResultLighthouseSocial.Data.Repositories.CommentRepository→LighthouseSocial.Application.Common.ResultLighthouseSocial.Data.Repositories.CountryRepository→LighthouseSocial.Application.Common.ResultLighthouseSocial.Data.Repositories.LighthouseODataRepository→LighthouseSocial.Application.Common.ResultLighthouseSocial.Data.Repositories.LighthouseRepository→LighthouseSocial.Application.Common.ResultLighthouseSocial.Data.Repositories.PhotoRepository→LighthouseSocial.Application.Common.ResultLighthouseSocial.Data.Repositories.UserRepository→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Data.Repositories uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Data.Repositories, while a change to LighthouseSocial.Data.Repositories can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Data.Repositories uses a module listed above it, which is the healthy direction.
33→3 LighthouseSocial.Data.Repositories uses LighthouseSocial.Application.Dtos✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Data.Repositories uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.Data.Repositories.LighthouseODataRepository→LighthouseSocial.Application.Dtos.QueryableLighthouseDto
- Direction
- LighthouseSocial.Data.Repositories uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.Data.Repositories, while a change to LighthouseSocial.Data.Repositories can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.Data.Repositories uses a module listed above it, which is the healthy direction.
33→5 LighthouseSocial.Data.Repositories uses LighthouseSocial.Data✕
- Connections
- 6 pairs of types, where a type in LighthouseSocial.Data.Repositories uses a type in LighthouseSocial.Data.
- The types involved
LighthouseSocial.Data.Repositories.CommentRepository→LighthouseSocial.Data.IDbConnectionFactoryLighthouseSocial.Data.Repositories.CountryRepository→LighthouseSocial.Data.IDbConnectionFactoryLighthouseSocial.Data.Repositories.LighthouseODataRepository→LighthouseSocial.Data.IDbConnectionFactoryLighthouseSocial.Data.Repositories.LighthouseRepository→LighthouseSocial.Data.IDbConnectionFactoryLighthouseSocial.Data.Repositories.PhotoRepository→LighthouseSocial.Data.IDbConnectionFactoryLighthouseSocial.Data.Repositories.UserRepository→LighthouseSocial.Data.IDbConnectionFactory
- Direction
- LighthouseSocial.Data.Repositories uses LighthouseSocial.Data, so a change to LighthouseSocial.Data can break LighthouseSocial.Data.Repositories, while a change to LighthouseSocial.Data.Repositories can't break LighthouseSocial.Data.
- Position
- Below the diagonal: LighthouseSocial.Data.Repositories uses a module listed above it, which is the healthy direction.
33→7 LighthouseSocial.Data.Repositories uses LighthouseSocial.Domain.ValueObjects✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Data.Repositories uses a type in LighthouseSocial.Domain.ValueObjects.
- The types involved
LighthouseSocial.Data.Repositories.LighthouseRepository→LighthouseSocial.Domain.ValueObjects.LighthouseWithStats
- Direction
- LighthouseSocial.Data.Repositories uses LighthouseSocial.Domain.ValueObjects, so a change to LighthouseSocial.Domain.ValueObjects can break LighthouseSocial.Data.Repositories, while a change to LighthouseSocial.Data.Repositories can't break LighthouseSocial.Domain.ValueObjects.
- Position
- Below the diagonal: LighthouseSocial.Data.Repositories uses a module listed above it, which is the healthy direction.
33→14 LighthouseSocial.Data.Repositories uses LighthouseSocial.Domain.Entities✕
- Connections
- 6 pairs of types, where a type in LighthouseSocial.Data.Repositories uses a type in LighthouseSocial.Domain.Entities.
- The types involved
LighthouseSocial.Data.Repositories.CachedCountryDataReader→LighthouseSocial.Domain.Entities.CountryLighthouseSocial.Data.Repositories.CommentRepository→LighthouseSocial.Domain.Entities.CommentLighthouseSocial.Data.Repositories.CountryRepository→LighthouseSocial.Domain.Entities.CountryLighthouseSocial.Data.Repositories.LighthouseRepository→LighthouseSocial.Domain.Entities.LighthouseLighthouseSocial.Data.Repositories.PhotoRepository→LighthouseSocial.Domain.Entities.PhotoLighthouseSocial.Data.Repositories.UserRepository→LighthouseSocial.Domain.Entities.User
- Direction
- LighthouseSocial.Data.Repositories uses LighthouseSocial.Domain.Entities, so a change to LighthouseSocial.Domain.Entities can break LighthouseSocial.Data.Repositories, while a change to LighthouseSocial.Data.Repositories can't break LighthouseSocial.Domain.Entities.
- Position
- Below the diagonal: LighthouseSocial.Data.Repositories uses a module listed above it, which is the healthy direction.
33→20 LighthouseSocial.Data.Repositories uses LighthouseSocial.Infrastructure.Caching✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Data.Repositories uses a type in LighthouseSocial.Infrastructure.Caching.
- The types involved
LighthouseSocial.Data.Repositories.CachedCountryDataReader→LighthouseSocial.Infrastructure.Caching.ICacheService
- Direction
- LighthouseSocial.Data.Repositories uses LighthouseSocial.Infrastructure.Caching, so a change to LighthouseSocial.Infrastructure.Caching can break LighthouseSocial.Data.Repositories, while a change to LighthouseSocial.Data.Repositories can't break LighthouseSocial.Infrastructure.Caching.
- Position
- Below the diagonal: LighthouseSocial.Data.Repositories uses a module listed above it, which is the healthy direction.
33→21 LighthouseSocial.Data.Repositories uses LighthouseSocial.Application.Contracts.Repositories✕
- Connections
- 7 pairs of types, where a type in LighthouseSocial.Data.Repositories uses a type in LighthouseSocial.Application.Contracts.Repositories.
- The types involved
LighthouseSocial.Data.Repositories.CachedCountryDataReader→LighthouseSocial.Application.Contracts.Repositories.ICountryDataReaderLighthouseSocial.Data.Repositories.CommentRepository→LighthouseSocial.Application.Contracts.Repositories.ICommentRepositoryLighthouseSocial.Data.Repositories.CountryRepository→LighthouseSocial.Application.Contracts.Repositories.ICountryDataReaderLighthouseSocial.Data.Repositories.LighthouseODataRepository→LighthouseSocial.Application.Contracts.Repositories.ILighthouseODataRepositoryLighthouseSocial.Data.Repositories.LighthouseRepository→LighthouseSocial.Application.Contracts.Repositories.ILighthouseRepositoryLighthouseSocial.Data.Repositories.PhotoRepository→LighthouseSocial.Application.Contracts.Repositories.IPhotoRepositoryLighthouseSocial.Data.Repositories.UserRepository→LighthouseSocial.Application.Contracts.Repositories.IUserRepository
- Direction
- LighthouseSocial.Data.Repositories uses LighthouseSocial.Application.Contracts.Repositories, so a change to LighthouseSocial.Application.Contracts.Repositories can break LighthouseSocial.Data.Repositories, while a change to LighthouseSocial.Data.Repositories can't break LighthouseSocial.Application.Contracts.Repositories.
- Position
- Below the diagonal: LighthouseSocial.Data.Repositories uses a module listed above it, which is the healthy direction.
34→19 LighthouseSocial.EventWorker.Services uses LighthouseSocial.EventWorker.Strategies✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.EventWorker.Services uses a type in LighthouseSocial.EventWorker.Strategies.
- The types involved
LighthouseSocial.EventWorker.Services.RabbitMqEventConsumerService→LighthouseSocial.EventWorker.Strategies.EventDispatcher
- Direction
- LighthouseSocial.EventWorker.Services uses LighthouseSocial.EventWorker.Strategies, so a change to LighthouseSocial.EventWorker.Strategies can break LighthouseSocial.EventWorker.Services, while a change to LighthouseSocial.EventWorker.Services can't break LighthouseSocial.EventWorker.Strategies.
- Position
- Below the diagonal: LighthouseSocial.EventWorker.Services uses a module listed above it, which is the healthy direction.
34→24 LighthouseSocial.EventWorker.Services uses LighthouseSocial.Infrastructure.Configuration✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.EventWorker.Services uses a type in LighthouseSocial.Infrastructure.Configuration.
- The types involved
LighthouseSocial.EventWorker.Services.RabbitMqEventConsumerService→LighthouseSocial.Infrastructure.Configuration.RabbitMqSettings
- Direction
- LighthouseSocial.EventWorker.Services uses LighthouseSocial.Infrastructure.Configuration, so a change to LighthouseSocial.Infrastructure.Configuration can break LighthouseSocial.EventWorker.Services, while a change to LighthouseSocial.EventWorker.Services can't break LighthouseSocial.Infrastructure.Configuration.
- Position
- Below the diagonal: LighthouseSocial.EventWorker.Services uses a module listed above it, which is the healthy direction.
35→6 LighthouseSocial.Infrastructure.Messaging uses LighthouseSocial.Domain.Common✕
- Connections
- 2 pairs of types, where a type in LighthouseSocial.Infrastructure.Messaging uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Infrastructure.Messaging.RabbitMqEventPublisher→LighthouseSocial.Domain.Common.IEventLighthouseSocial.Infrastructure.Messaging.RabbitMqEventPublisher→LighthouseSocial.Domain.Common.IEventPublisher
- Direction
- LighthouseSocial.Infrastructure.Messaging uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Infrastructure.Messaging, while a change to LighthouseSocial.Infrastructure.Messaging can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.Messaging uses a module listed above it, which is the healthy direction.
35→24 LighthouseSocial.Infrastructure.Messaging uses LighthouseSocial.Infrastructure.Configuration✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Infrastructure.Messaging uses a type in LighthouseSocial.Infrastructure.Configuration.
- The types involved
LighthouseSocial.Infrastructure.Messaging.RabbitMqEventPublisher→LighthouseSocial.Infrastructure.Configuration.RabbitMqSettings
- Direction
- LighthouseSocial.Infrastructure.Messaging uses LighthouseSocial.Infrastructure.Configuration, so a change to LighthouseSocial.Infrastructure.Configuration can break LighthouseSocial.Infrastructure.Messaging, while a change to LighthouseSocial.Infrastructure.Messaging can't break LighthouseSocial.Infrastructure.Configuration.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.Messaging uses a module listed above it, which is the healthy direction.
36→1 LighthouseSocial.Infrastructure.Storage uses LighthouseSocial.Application.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Infrastructure.Storage uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Infrastructure.Storage.PhotoStorageService→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Infrastructure.Storage uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Infrastructure.Storage, while a change to LighthouseSocial.Infrastructure.Storage can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.Storage uses a module listed above it, which is the healthy direction.
36→11 LighthouseSocial.Infrastructure.Storage uses LighthouseSocial.Application.Contracts✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Infrastructure.Storage uses a type in LighthouseSocial.Application.Contracts.
- The types involved
LighthouseSocial.Infrastructure.Storage.PhotoStorageService→LighthouseSocial.Application.Contracts.IPhotoStorageService
- Direction
- LighthouseSocial.Infrastructure.Storage uses LighthouseSocial.Application.Contracts, so a change to LighthouseSocial.Application.Contracts can break LighthouseSocial.Infrastructure.Storage, while a change to LighthouseSocial.Infrastructure.Storage can't break LighthouseSocial.Application.Contracts.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.Storage uses a module listed above it, which is the healthy direction.
36→24 LighthouseSocial.Infrastructure.Storage uses LighthouseSocial.Infrastructure.Configuration✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Infrastructure.Storage uses a type in LighthouseSocial.Infrastructure.Configuration.
- The types involved
LighthouseSocial.Infrastructure.Storage.PhotoStorageService→LighthouseSocial.Infrastructure.Configuration.CachedConfigurationService
- Direction
- LighthouseSocial.Infrastructure.Storage uses LighthouseSocial.Infrastructure.Configuration, so a change to LighthouseSocial.Infrastructure.Configuration can break LighthouseSocial.Infrastructure.Storage, while a change to LighthouseSocial.Infrastructure.Storage can't break LighthouseSocial.Infrastructure.Configuration.
- Position
- Below the diagonal: LighthouseSocial.Infrastructure.Storage uses a module listed above it, which is the healthy direction.
37→3 LighthouseSocial.ODataApi.Controllers uses LighthouseSocial.Application.Dtos✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.ODataApi.Controllers uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.ODataApi.Controllers.LighthousesController→LighthouseSocial.Application.Dtos.QueryableLighthouseDto
- Direction
- LighthouseSocial.ODataApi.Controllers uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.ODataApi.Controllers, while a change to LighthouseSocial.ODataApi.Controllers can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.ODataApi.Controllers uses a module listed above it, which is the healthy direction.
37→21 LighthouseSocial.ODataApi.Controllers uses LighthouseSocial.Application.Contracts.Repositories✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.ODataApi.Controllers uses a type in LighthouseSocial.Application.Contracts.Repositories.
- The types involved
LighthouseSocial.ODataApi.Controllers.LighthousesController→LighthouseSocial.Application.Contracts.Repositories.ILighthouseODataRepository
- Direction
- LighthouseSocial.ODataApi.Controllers uses LighthouseSocial.Application.Contracts.Repositories, so a change to LighthouseSocial.Application.Contracts.Repositories can break LighthouseSocial.ODataApi.Controllers, while a change to LighthouseSocial.ODataApi.Controllers can't break LighthouseSocial.Application.Contracts.Repositories.
- Position
- Below the diagonal: LighthouseSocial.ODataApi.Controllers uses a module listed above it, which is the healthy direction.
38→12 TerminalApp.UseCases uses LighthouseSocial.Application.Contracts.ExternalServices✕
- Connections
- 7 pairs of types, where a type in TerminalApp.UseCases uses a type in LighthouseSocial.Application.Contracts.ExternalServices.
- The types involved
TerminalApp.UseCases.Composition→LighthouseSocial.Application.Contracts.ExternalServices.ILighthouseServiceTerminalApp.UseCases.Composition→LighthouseSocial.Application.Contracts.ExternalServices.IPhotoServiceTerminalApp.UseCases.Composition→LighthouseSocial.Application.Contracts.ExternalServices.IPhotoUploadServiceTerminalApp.UseCases.LighthouseManagement→LighthouseSocial.Application.Contracts.ExternalServices.ILighthouseServiceTerminalApp.UseCases.PhotoManagementUseCase→LighthouseSocial.Application.Contracts.ExternalServices.ILighthouseServiceTerminalApp.UseCases.PhotoManagementUseCase→LighthouseSocial.Application.Contracts.ExternalServices.IPhotoServiceTerminalApp.UseCases.PhotoManagementUseCase→LighthouseSocial.Application.Contracts.ExternalServices.IPhotoUploadService
- Direction
- TerminalApp.UseCases uses LighthouseSocial.Application.Contracts.ExternalServices, so a change to LighthouseSocial.Application.Contracts.ExternalServices can break TerminalApp.UseCases, while a change to TerminalApp.UseCases can't break LighthouseSocial.Application.Contracts.ExternalServices.
- Position
- Below the diagonal: TerminalApp.UseCases uses a module listed above it, which is the healthy direction.
38→21 TerminalApp.UseCases uses LighthouseSocial.Application.Contracts.Repositories✕
- Connections
- 1 pair of types, where a type in TerminalApp.UseCases uses a type in LighthouseSocial.Application.Contracts.Repositories.
- The types involved
TerminalApp.UseCases.ViewManagement→LighthouseSocial.Application.Contracts.Repositories.ICountryDataReader
- Direction
- TerminalApp.UseCases uses LighthouseSocial.Application.Contracts.Repositories, so a change to LighthouseSocial.Application.Contracts.Repositories can break TerminalApp.UseCases, while a change to TerminalApp.UseCases can't break LighthouseSocial.Application.Contracts.Repositories.
- Position
- Below the diagonal: TerminalApp.UseCases uses a module listed above it, which is the healthy direction.
39→1 LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Application.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Photo.Saga uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSaga→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Features.Photo.Saga, while a change to LighthouseSocial.Application.Features.Photo.Saga can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga uses a module listed above it, which is the healthy direction.
39→3 LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Application.Dtos✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Photo.Saga uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSaga→LighthouseSocial.Application.Dtos.PhotoDto
- Direction
- LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.Application.Features.Photo.Saga, while a change to LighthouseSocial.Application.Features.Photo.Saga can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga uses a module listed above it, which is the healthy direction.
39→6 LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Domain.Common✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Photo.Saga uses a type in LighthouseSocial.Domain.Common.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSaga→LighthouseSocial.Domain.Common.IEventPublisher
- Direction
- LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Domain.Common, so a change to LighthouseSocial.Domain.Common can break LighthouseSocial.Application.Features.Photo.Saga, while a change to LighthouseSocial.Application.Features.Photo.Saga can't break LighthouseSocial.Domain.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga uses a module listed above it, which is the healthy direction.
39→9 LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Application.Common.DistribtedTransaction.Saga✕
- Connections
- 2 pairs of types, where a type in LighthouseSocial.Application.Features.Photo.Saga uses a type in LighthouseSocial.Application.Common.DistribtedTransaction.Saga.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSaga→LighthouseSocial.Application.Common.DistribtedTransaction.Saga.ISagaLighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSaga→LighthouseSocial.Application.Common.DistribtedTransaction.Saga.ISagaStep
- Direction
- LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Application.Common.DistribtedTransaction.Saga, so a change to LighthouseSocial.Application.Common.DistribtedTransaction.Saga can break LighthouseSocial.Application.Features.Photo.Saga, while a change to LighthouseSocial.Application.Features.Photo.Saga can't break LighthouseSocial.Application.Common.DistribtedTransaction.Saga.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga uses a module listed above it, which is the healthy direction.
39→14 LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Domain.Entities✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Photo.Saga uses a type in LighthouseSocial.Domain.Entities.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSagaData→LighthouseSocial.Domain.Entities.Photo
- Direction
- LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Domain.Entities, so a change to LighthouseSocial.Domain.Entities can break LighthouseSocial.Application.Features.Photo.Saga, while a change to LighthouseSocial.Application.Features.Photo.Saga can't break LighthouseSocial.Domain.Entities.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga uses a module listed above it, which is the healthy direction.
39→30 LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Application.Features.Photo✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Features.Photo.Saga uses a type in LighthouseSocial.Application.Features.Photo.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSaga→LighthouseSocial.Application.Features.Photo.UploadPhotoRequest
- Direction
- LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Application.Features.Photo, so a change to LighthouseSocial.Application.Features.Photo can break LighthouseSocial.Application.Features.Photo.Saga, while a change to LighthouseSocial.Application.Features.Photo.Saga can't break LighthouseSocial.Application.Features.Photo.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga uses a module listed above it, which is the healthy direction.
39→31 LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Application.Features.Photo.Saga.Steps✕
- Connections
- 2 pairs of types, where a type in LighthouseSocial.Application.Features.Photo.Saga uses a type in LighthouseSocial.Application.Features.Photo.Saga.Steps.
- The types involved
LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSaga→LighthouseSocial.Application.Features.Photo.Saga.Steps.FileUploadStepLighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSaga→LighthouseSocial.Application.Features.Photo.Saga.Steps.MetadataSaveStep
- Direction
- LighthouseSocial.Application.Features.Photo.Saga uses LighthouseSocial.Application.Features.Photo.Saga.Steps, so a change to LighthouseSocial.Application.Features.Photo.Saga.Steps can break LighthouseSocial.Application.Features.Photo.Saga, while a change to LighthouseSocial.Application.Features.Photo.Saga can't break LighthouseSocial.Application.Features.Photo.Saga.Steps.
- Position
- Below the diagonal: LighthouseSocial.Application.Features.Photo.Saga uses a module listed above it, which is the healthy direction.
40→1 LighthouseSocial.Application.Services uses LighthouseSocial.Application.Common✕
- Connections
- 6 pairs of types, where a type in LighthouseSocial.Application.Services uses a type in LighthouseSocial.Application.Common.
- The types involved
LighthouseSocial.Application.Services.CountryService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Services.LighthouseService→LighthouseSocial.Application.Common.PagedResultLighthouseSocial.Application.Services.LighthouseService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Services.PhotoService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Services.PhotoUploadService→LighthouseSocial.Application.Common.ResultLighthouseSocial.Application.Services.UserService→LighthouseSocial.Application.Common.Result
- Direction
- LighthouseSocial.Application.Services uses LighthouseSocial.Application.Common, so a change to LighthouseSocial.Application.Common can break LighthouseSocial.Application.Services, while a change to LighthouseSocial.Application.Services can't break LighthouseSocial.Application.Common.
- Position
- Below the diagonal: LighthouseSocial.Application.Services uses a module listed above it, which is the healthy direction.
40→2 LighthouseSocial.Application.Services uses LighthouseSocial.Application.Common.Pipeline✕
- Connections
- 4 pairs of types, where a type in LighthouseSocial.Application.Services uses a type in LighthouseSocial.Application.Common.Pipeline.
- The types involved
LighthouseSocial.Application.Services.CountryService→LighthouseSocial.Application.Common.Pipeline.PipelineDispatcherLighthouseSocial.Application.Services.LighthouseService→LighthouseSocial.Application.Common.Pipeline.PipelineDispatcherLighthouseSocial.Application.Services.PhotoService→LighthouseSocial.Application.Common.Pipeline.PipelineDispatcherLighthouseSocial.Application.Services.UserService→LighthouseSocial.Application.Common.Pipeline.PipelineDispatcher
- Direction
- LighthouseSocial.Application.Services uses LighthouseSocial.Application.Common.Pipeline, so a change to LighthouseSocial.Application.Common.Pipeline can break LighthouseSocial.Application.Services, while a change to LighthouseSocial.Application.Services can't break LighthouseSocial.Application.Common.Pipeline.
- Position
- Below the diagonal: LighthouseSocial.Application.Services uses a module listed above it, which is the healthy direction.
40→3 LighthouseSocial.Application.Services uses LighthouseSocial.Application.Dtos✕
- Connections
- 10 pairs of types, where a type in LighthouseSocial.Application.Services uses a type in LighthouseSocial.Application.Dtos.
- The types involved
LighthouseSocial.Application.Services.CountryService→LighthouseSocial.Application.Dtos.CountryDtoLighthouseSocial.Application.Services.LighthouseService→LighthouseSocial.Application.Dtos.LighthouseDtoLighthouseSocial.Application.Services.LighthouseService→LighthouseSocial.Application.Dtos.LighthouseTopDtoLighthouseSocial.Application.Services.LighthouseService→LighthouseSocial.Application.Dtos.LighthouseUpsertDtoLighthouseSocial.Application.Services.LighthouseService→LighthouseSocial.Application.Dtos.PagingDtoLighthouseSocial.Application.Services.LighthouseService→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.Application.Services.LighthouseService→LighthouseSocial.Application.Dtos.TopDtoLighthouseSocial.Application.Services.PhotoService→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.Application.Services.PhotoUploadService→LighthouseSocial.Application.Dtos.PhotoDtoLighthouseSocial.Application.Services.UserService→LighthouseSocial.Application.Dtos.UserDto
- Direction
- LighthouseSocial.Application.Services uses LighthouseSocial.Application.Dtos, so a change to LighthouseSocial.Application.Dtos can break LighthouseSocial.Application.Services, while a change to LighthouseSocial.Application.Services can't break LighthouseSocial.Application.Dtos.
- Position
- Below the diagonal: LighthouseSocial.Application.Services uses a module listed above it, which is the healthy direction.
40→12 LighthouseSocial.Application.Services uses LighthouseSocial.Application.Contracts.ExternalServices✕
- Connections
- 5 pairs of types, where a type in LighthouseSocial.Application.Services uses a type in LighthouseSocial.Application.Contracts.ExternalServices.
- The types involved
LighthouseSocial.Application.Services.CountryService→LighthouseSocial.Application.Contracts.ExternalServices.ICountryServiceLighthouseSocial.Application.Services.LighthouseService→LighthouseSocial.Application.Contracts.ExternalServices.ILighthouseServiceLighthouseSocial.Application.Services.PhotoService→LighthouseSocial.Application.Contracts.ExternalServices.IPhotoServiceLighthouseSocial.Application.Services.PhotoUploadService→LighthouseSocial.Application.Contracts.ExternalServices.IPhotoUploadServiceLighthouseSocial.Application.Services.UserService→LighthouseSocial.Application.Contracts.ExternalServices.IUserService
- Direction
- LighthouseSocial.Application.Services uses LighthouseSocial.Application.Contracts.ExternalServices, so a change to LighthouseSocial.Application.Contracts.ExternalServices can break LighthouseSocial.Application.Services, while a change to LighthouseSocial.Application.Services can't break LighthouseSocial.Application.Contracts.ExternalServices.
- Position
- Below the diagonal: LighthouseSocial.Application.Services uses a module listed above it, which is the healthy direction.
40→39 LighthouseSocial.Application.Services uses LighthouseSocial.Application.Features.Photo.Saga✕
- Connections
- 1 pair of types, where a type in LighthouseSocial.Application.Services uses a type in LighthouseSocial.Application.Features.Photo.Saga.
- The types involved
LighthouseSocial.Application.Services.PhotoUploadService→LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSaga
- Direction
- LighthouseSocial.Application.Services uses LighthouseSocial.Application.Features.Photo.Saga, so a change to LighthouseSocial.Application.Features.Photo.Saga can break LighthouseSocial.Application.Services, while a change to LighthouseSocial.Application.Services can't break LighthouseSocial.Application.Features.Photo.Saga.
- Position
- Below the diagonal: LighthouseSocial.Application.Services uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 21 | High / Critical |
| A07:2025 — Authentication Failures | 17 | High / Critical |
| A02:2025 — Security Misconfiguration | 17 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (2); Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with LighthouseSocial.Integration.Tests.csproj, LighthouseSocial.Infrastructure.Tests.csproj, LighthouseSocial.Application.Tests.csproj; Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (2). | +9.0 pts | Low | REDACTED Scanning |
| Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with LighthouseSocial.Integration.Tests.csproj, LighthouseSocial.Infrastructure.Tests.csproj, LighthouseSocial.Application.Tests.csproj. | +6.6 pts | Low | Dependency Hygiene |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +5.9 pts | Medium | Security & performance tooling |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +5.9 pts | Medium | DR & Backup |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.5 pts | Low | ADR Quality |
| Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with LighthouseSocial.Application.Tests.csproj. | +2.3 pts | Low | Dependency Hygiene |
| Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down. | +3.2 pts | Medium | Outbound HTTP resilience |
| Resolve the 34 Orphaned file finding(s) in Knowledge Freshness — start with DependencyInjection.cs (3), CachedConfigurationService.cs, PhotoUploadSaga.cs. | +2.6 pts | Medium | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.2 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/Clients/TerminalApp/UseCases/Composition.cs | 4.3 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.5 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/LighthouseSocial.Application/Features/Lighthouse/CreateLighthouseHandler.cs | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/LighthouseSocial.Application/Features/User/CreateUserHandler.cs | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/LighthouseSocial.Application/Features/Comment/AddCommentHandler.cs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/LighthouseSocial.Application/Contracts/ExternalServices/IUserService.cs | 6.9 | Mixed | Explicit Debt: Dead code: CreateUserAsync |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/LighthouseSocial.Infrastructure/Auditors/ExternalCommentAuditor.cs | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/LighthouseSocial.Backoffice/Pages/Index.cshtml.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
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 95 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 95 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, 275 of 322 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: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes, and real coverage will be read. You can widen what we reach: optional: your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes, and the real number is read on the next scan.
- 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 (2 contributor(s) across 256 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- 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/Clients/TerminalApp/UseCases/Composition.cs`, `src/Clients/TerminalApp/UseCases/LighthouseManagement.cs`, `src/Clients/TerminalApp/UseCases/PhotoManagement.cs`, `src/Clients/TerminalApp/UseCases/ViewManagement.cs`, `src/JudgeDredd/Services/OpenApiCommentAuditService.cs`, … (+73 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.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — opensearch Error context canceled graylog Error context canceled keycloak Error context canceled postgres Error context canceled kiwi-store-server Error context canceled pgadmin Error context canceled Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: mongodb Error context canceled opensearch Error context canceled rabbitmq Error context canceled postgres Error context canceled graylog Error context canceled redis Error context canceled Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- ED5 Idempotency — 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 classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 29 further occurrence(s) are not listed individually; the score already reflects all 69.
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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CachedConfigurationService.GetKeycloakSettingsAsync at 28.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with CachedConfigurationService.GetKeycloakSettingsAsync (cyclomatic 28). — Refactoring it lifts Cyclomatic Complexity from 9.3 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was CachedConfigurationService.GetKeycloakSettingsAsync at 24.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with CachedConfigurationService.GetKeycloakSettingsAsync (cognitive 24). — Refactoring it lifts Cognitive Complexity from 9.4 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with PhotoUploadSaga.cs, AddCommentHandler.cs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
13 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (23 lines × 2) finding(s) in Code Duplication — start with LigthouseServiceClient.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (15–16 lines × 3) finding(s) in Code Duplication — start with GetUserByEmailHandler.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with GetPhotosByLighthouseHandler.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
14 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling — start with LighthouseSocial.Domain.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 35 classes have LCOM4 above 3.
D9 · Test Distribution
68 test methods: 66 unit, 2 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 2 mock references across 68 tests.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).
D12 · Dependency Hygiene
31 outdated, 1 vulnerable, 1 deprecated packages.
What to do
- Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with LighthouseSocial.Integration.Tests.csproj, LighthouseSocial.Infrastructure.Tests.csproj, LighthouseSocial.Application.Tests.csproj. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with LighthouseSocial.Application.Tests.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 216 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 34 direct `PackageReference`(s), and 166 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
27 deducted debt markers + 12 dead symbols across 6288 LoC in the .NET projects (1.1/KLoC) → score 7.8.
What to do
- Resolve the 4 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Composition.cs, REDACTED, Index.cshtml.cs. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 23 TodoComment finding(s) in Explicit Debt — start with CreateLighthouseHandler.cs (4), CreateUserHandler.cs (4), REDACTED (2). — One of this dimension's main actionable groups (23 warning-level).
- Resolve the 12 Dead code finding(s) in Explicit Debt — start with IUserService.cs (3), CachedConfigurationService.cs (2), Photo.cs. — One of this dimension's main actionable groups (12 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
14 projects, 191 source files, 8080 hand-written lines of code (6288 production / 1792 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 23 inter-project edges. Measured across 3 solutions loaded as one workspace: `src/LighthouseSocial.sln`, `src/JudgeDredd/JudgeDredd.sln`, `src/RabbitMqConsumer/RabbitMqConsumer.sln`.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 12 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
0 naming inconsistencies among 68 declarations measured against a convention their peers follow.
D26 · Project Cohesion
0 of 14 projects flagged as possibly oversized/incoherent.
D27 · Navigability
97 % of calls cross a namespace and 19 % 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)
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
21 finding(s): 0 critical, 2 high, 19 medium, 0 low. 2 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 78 file(s) — `src/Clients/TerminalApp/UseCases/Composition.cs` (lines 8–11, line 12), `src/Clients/TerminalApp/UseCases/LighthouseManagement.cs` (lines 8–9, line 10), `src/Clients/TerminalApp/UseCases/PhotoManagement.cs` (lines 7–10, line 11), `src/Clients/TerminalApp/UseCases/ViewManagement.cs` (line 6), `src/JudgeDredd/Services/OpenApiCommentAuditService.cs` (line 5), … (+73 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. In 78 of those file(s) — `src/Clients/TerminalApp/UseCases/Composition.cs`, `src/Clients/TerminalApp/UseCases/LighthouseManagement.cs`, `src/Clients/TerminalApp/UseCases/PhotoManagement.cs`, `src/Clients/TerminalApp/UseCases/ViewManagement.cs`, `src/JudgeDredd/Services/OpenApiCommentAuditService.cs`, … (+73 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
What to do
- Resolve the 19 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (5), REDACTED (2). — One of this dimension's main actionable groups (19 warning-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
17 finding(s): 0 critical, 10 high, 6 medium, 1 low.
What to do
- Resolve the 10 High IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED. — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 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
34 of 34 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs. Counted over 34 of the 168 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 34 Orphaned file finding(s) in Knowledge Freshness — start with DependencyInjection.cs (3), CachedConfigurationService.cs, PhotoUploadSaga.cs. — One of this dimension's main actionable groups (34 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 14 platform declaration(s) and 0 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
AC2 · Forms & labels
AC3 · Page structure
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×6) — src/LighthouseSocial.Backoffice/Pages/Index.cshtml:21, src/LighthouseSocial.Backoffice/Pages/Index.cshtml:28, src/LighthouseSocial.Backoffice/Pages/Lighthouse/Create.cshtml:40, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 7 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX2 · Stateful singletons
- `RabbitMqEventConsumerService` is a singleton (one shared instance) but mutates instance state outside any lock (_connection, _channel; e.g. `_connection` at line 56). — src/LighthouseSocial.EventWorker/Services/RabbitMqEventConsumerService.cs:11
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles
- The namespaces LighthouseSocial.Application.Features.Photo.Saga ↔ LighthouseSocial.Application.Features.Photo.Saga.Steps depend on each other. The lightest dependency in the cycle is LighthouseSocial.Application.Features.Photo.Saga → LighthouseSocial.Application.Features.Photo.Saga.Steps (LighthouseSocial.Application.Features.Photo.Saga.PhotoUploadSaga → LighthouseSocial.Application.Features.Photo.Saga.Steps.FileUploadStep, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/LighthouseSocial.Application/Features/Photo/Saga/PhotoUploadSaga.cs:4
- The namespaces LighthouseSocial.EventWorker.Services ↔ LighthouseSocial.EventWorker.Strategies depend on each other. The lightest dependency in the cycle is LighthouseSocial.EventWorker.Services → LighthouseSocial.EventWorker.Strategies (LighthouseSocial.EventWorker.Services.RabbitMqEventConsumerService → LighthouseSocial.EventWorker.Strategies.EventDispatcher, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/LighthouseSocial.EventWorker/Services/RabbitMqEventConsumerService.cs:1
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `Comment`'s public constructor takes `text` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Comment` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/LighthouseSocial.Domain/Entities/Comment.cs:15
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `EventBase.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Common/EventBase.cs:6
- `EventBase.AggregateId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Common/EventBase.cs:9
- `Comment.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Entities/Comment.cs:9
- `Comment.PhotoId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Entities/Comment.cs:10
- `Lighthouse.CountryId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Entities/Lighthouse.cs:9
- `Photo.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Entities/Photo.cs:9
- `Photo.LighthouseId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Entities/Photo.cs:10
- `User.ExternalId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Entities/User.cs:10
- `CommentCreated.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Comment/CommentCreated.cs:8
- `CommentCreated.PhotoId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Comment/CommentCreated.cs:9
- `CommentCreationFailed.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Comment/CommentCreationFailed.cs:8
- `CommentCreationFailed.PhotoId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Comment/CommentCreationFailed.cs:9
- `CommentCreationRequested.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Comment/CommentCreationRequested.cs:8
- `CommentCreationRequested.PhotoId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Comment/CommentCreationRequested.cs:9
- `LighthouseCreated.CountryId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Lighthouse/LighthouseCreated.cs:9
- `LighthouseCreationFailed.CountryId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Lighthouse/LighthouseCreationFailed.cs:9
- `LighthouseCreationRequested.CountryId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Lighthouse/LighthouseCreationRequested.cs:9
- `PhotoSavedToRepository.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoSavedToRepository.cs:9
- `PhotoSavedToRepository.LighthouseId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoSavedToRepository.cs:10
- `PhotoUploaded.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploaded.cs:9
- `PhotoUploaded.LighthouseId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploaded.cs:10
- `PhotoUploadFailed.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadFailed.cs:9
- `PhotoUploadFailed.LighthouseId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadFailed.cs:10
- `PhotoUploadRequested.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadRequested.cs:9
- `PhotoUploadRequested.LighthouseId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadRequested.cs:10
- `PhotoUploadSagaCompensationCompleted.SagaId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaCompensationCompleted.cs:8
- `PhotoUploadSagaCompensationStarted.SagaId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaCompensationStarted.cs:8
- `PhotoUploadSagaCompleted.SagaId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaCompleted.cs:8
- `PhotoUploadSagaCompleted.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaCompleted.cs:10
- `PhotoUploadSagaCompleted.LighthouseId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaCompleted.cs:11
- `PhotoUploadSagaFailed.SagaId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaFailed.cs:8
- `PhotoUploadSagaFailed.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaFailed.cs:10
- `PhotoUploadSagaFailed.LighthouseId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaFailed.cs:11
- `PhotoUploadSagaStarted.SagaId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaStarted.cs:8
- `PhotoUploadSagaStarted.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaStarted.cs:10
- `PhotoUploadSagaStarted.LighthouseId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaStarted.cs:11
- `UserCreated.ExternalId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/User/UserCreated.cs:8
- `UserCreationFailed.ExternalId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/User/UserCreationFailed.cs:8
- `UserCreationRequested.ExternalId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/LighthouseSocial.Domain/Events/User/UserCreationRequested.cs:8
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `Comment` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/LighthouseSocial.Domain/Entities/Comment.cs:6
- `Lighthouse` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/LighthouseSocial.Domain/Entities/Lighthouse.cs:6
- `Photo` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/LighthouseSocial.Domain/Entities/Photo.cs:6
- `User` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/LighthouseSocial.Domain/Entities/User.cs:5
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `Lighthouse` exposes its own state through a mutable collection (Photos) — a caller can add to or remove from it directly, without passing through the methods that enforce the invariants. — src/LighthouseSocial.Domain/Entities/Lighthouse.cs:6
- `Photo` exposes its own state through a mutable collection (Comments) — a caller can add to or remove from it directly, without passing through the methods that enforce the invariants. — src/LighthouseSocial.Domain/Entities/Photo.cs:6
- `User` exposes publicly writable state (Fullname, Email, ExternalId). — src/LighthouseSocial.Domain/Entities/User.cs:5
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
- `ICommentRepository` is a repository over `Comment`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Comment` through its owning aggregate instead. — src/LighthouseSocial.Application/Contracts/Repositories/ICommentRepository.cs:6
What to do
- Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED3 · Event naming
ED4 · Outbox / dual-write
- `AddCommentHandler.HandleAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/LighthouseSocial.Application/Features/Comment/AddCommentHandler.cs:30
- `CreateLighthouseHandler.HandleAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/LighthouseSocial.Application/Features/Lighthouse/CreateLighthouseHandler.cs:21
- `UploadPhotoHandler.HandleAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/LighthouseSocial.Application/Features/Photo/UploadPhotoHandler.cs:26
- `CreateUserHandler.HandleAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/LighthouseSocial.Application/Features/User/CreateUserHandler.cs:16
- `PhotoUploadSaga.ExecuteAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/LighthouseSocial.Application/Features/Photo/Saga/PhotoUploadSaga.cs:13
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a README to the 11 of 11 project(s) that lack one — worth up to 2 pts.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- Only 8/9 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 9, 5 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 741 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9
- `src/Clients/TerminalApp/TerminalApp.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/Clients/TerminalApp/TerminalApp.csproj:11
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
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.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P7 · Outbound HTTP resilience
- `builder.Services.AddHttpClient("LighthouseServiceClient", client => { client....` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/LighthouseSocial.Backoffice/Program.cs:8
- `builder.Services.AddHttpClient<ICommentAuditor, ExternalCommentAuditor>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/LighthouseSocial.WebApi/Program.cs:30
What to do
- Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
PF3 · Async & latency hygiene
- 4 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×4) — src/LighthouseSocial.Infrastructure/DependencyInjection.cs:102, src/LighthouseSocial.Infrastructure/Messaging/RabbitMqEventPublisher.cs:171, src/LighthouseSocial.Infrastructure/Storage/PhotoStorageService.cs:20, …
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×4) — src/JudgeDredd/Program.cs:3, src/LighthouseSocial.Backoffice/Program.cs:3, src/LighthouseSocial.ODataApi/Program.cs:10, …
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×4) — src/LighthouseSocial.Infrastructure/DependencyInjection.cs:102, src/LighthouseSocial.Infrastructure/Messaging/RabbitMqEventPublisher.cs:171, src/LighthouseSocial.Infrastructure/Storage/PhotoStorageService.cs:20, …
What to do
- Sync-over-async (deadlock risk)
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 73/134 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×33) — src/LighthouseSocial.Application/Services/LighthouseService.cs:15, src/LighthouseSocial.Application/Services/LighthouseService.cs:20, src/LighthouseSocial.Application/Services/LighthouseService.cs:25, …
- Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. (×6) — REDACTED:43, REDACTED:110, REDACTED:119, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- This method contradicts itself about `text`: line 34 writes `text?.Length`, which says `text` can be null, but line 29 then dereferences it directly as `text.Length` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `text` truly cannot be null here, the `?.` is misleading. Settle it one way — test `text` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/LighthouseSocial.Infrastructure/Auditors/ExternalCommentAuditor.cs:29
- ~1.8 `!` suppressions per 1k syntax nodes — 64 suppression(s) across the 35737 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80% | Strong | Strongest area. |
| Architecture | 78% | Strong | Solid. |
| Maturity | 46% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 31% | Weak — gated by D13, P3, P5, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58% | Adequate — gated by D28, D29, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 47% | Weak — gated by DM2, DM4, DM5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 75% | Strong | Solid. |
| Accessibility | 68% | Adequate | Acceptable, with room to improve. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 4 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). 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.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 31 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 18 — an image could not be pulled) — opensearch Error context canceled graylog Error context canceled keycloak Error context canceled postgres Error context canceled kiwi-store-server Error context canceled pgadmin Error context canceled Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: mongodb Error context canceled opensearch Error context canceled rabbitmq Error context canceled postgres Error context canceled graylog Error context canceled redis Error context canceled Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (6,288 production LoC in the .NET projects) — bounded contexts are not needed at this size 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 (LighthouseSocial.Domain), 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 — Too few judgeable comments (6 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 78 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.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — analyzer environment
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
- ED5 Idempotency — not scored — 7 of 8 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- 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.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 40 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dual write (no outbox): AddCommentHandler.HandleAsync src/LighthouseSocial.Application/Features/Comment/AddCommentHandler.cs:30
- Dual write (no outbox): CreateLighthouseHandler.HandleAsync src/LighthouseSocial.Application/Features/Lighthouse/CreateLighthouseHandler.cs:21
- Dual write (no outbox): UploadPhotoHandler.HandleAsync src/LighthouseSocial.Application/Features/Photo/UploadPhotoHandler.cs:26
- Dual write (no outbox): CreateUserHandler.HandleAsync src/LighthouseSocial.Application/Features/User/CreateUserHandler.cs:16
- Dual write (no outbox): PhotoUploadSaga.ExecuteAsync src/LighthouseSocial.Application/Features/Photo/Saga/PhotoUploadSaga.cs:13
- WriteOnlyPrivateField src/Clients/TerminalApp/UseCases/Composition.cs:16
- WriteOnlyPrivateField REDACTED:15
- WriteOnlyPrivateField src/LighthouseSocial.Backoffice/Pages/Index.cshtml.cs:8
- WriteOnlyPrivateField src/LighthouseSocial.Backoffice/Pages/Privacy.cshtml.cs:8
- Namespace dependency cycle src/LighthouseSocial.Application/Features/Photo/Saga/PhotoUploadSaga.cs:4
- Namespace dependency cycle src/LighthouseSocial.EventWorker/Services/RabbitMqEventConsumerService.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 153 finding(s)
- Async method without CancellationToken: CreateAsync src/LighthouseSocial.Application/Services/LighthouseService.cs:15
- Async method without CancellationToken: DeleteAsync src/LighthouseSocial.Application/Services/LighthouseService.cs:20
- Async method without CancellationToken: GetByIdAsync src/LighthouseSocial.Application/Services/LighthouseService.cs:25
- Async method without CancellationToken: GetPagedAsync src/LighthouseSocial.Application/Services/LighthouseService.cs:30
- Async method without CancellationToken: GetPhotosByIdAsync src/LighthouseSocial.Application/Services/LighthouseService.cs:35
- Async method without CancellationToken: GetTopAsync src/LighthouseSocial.Application/Services/LighthouseService.cs:40
- Async method without CancellationToken: UpdateAsync src/LighthouseSocial.Application/Services/LighthouseService.cs:45
- Async method without CancellationToken: DeleteAsync src/LighthouseSocial.Application/Services/PhotoService.cs:12
- Async method without CancellationToken: GetRawPhotoAsync src/LighthouseSocial.Application/Services/PhotoService.cs:18
- Async method without CancellationToken: GetByIdAsync src/LighthouseSocial.Application/Services/PhotoService.cs:24
- Async method without CancellationToken: GetByUserIdAsync src/LighthouseSocial.Application/Services/PhotoService.cs:30
- Async method without CancellationToken: GetByLighthouseIdAsync src/LighthouseSocial.Application/Services/PhotoService.cs:36
- Async method without CancellationToken: UploadAsync src/LighthouseSocial.Application/Services/PhotoUploadService.cs:13
- Async method without CancellationToken: CreateUserAsync src/LighthouseSocial.Application/Services/UserService.cs:12
- Async method without CancellationToken: GetUserByIdAsync src/LighthouseSocial.Application/Services/UserService.cs:18
- Async method without CancellationToken: GetUserBySubIdAsync src/LighthouseSocial.Application/Services/UserService.cs:24
- Async method without CancellationToken: GetUserByEmailAsync src/LighthouseSocial.Application/Services/UserService.cs:30
- Async method without CancellationToken: ExecuteFullWorkflowAsync src/Clients/TerminalApp/UseCases/Composition.cs:19
- Async method without CancellationToken: CreateLighthouseAsync src/Clients/TerminalApp/UseCases/Composition.cs:47
- Async method without CancellationToken: UploadPhotoAsync src/Clients/TerminalApp/UseCases/Composition.cs:79
- Async method without CancellationToken: AddCommentsToPhotoAsync src/Clients/TerminalApp/UseCases/Composition.cs:128
- Async method without CancellationToken: ListLighthouseDetailsAsync src/Clients/TerminalApp/UseCases/Composition.cs:153
- Async method without CancellationToken: UpdateLighthouseAsync src/Clients/TerminalApp/UseCases/Composition.cs:192
- Async method without CancellationToken: CreateAndTestLighthouseAsync src/Clients/TerminalApp/UseCases/LighthouseManagement.cs:15
- Async method without CancellationToken: GetOrCreateSampleLighthouseAsync src/Clients/TerminalApp/UseCases/LighthouseManagement.cs:79
- TodoComment src/Clients/TerminalApp/UseCases/Composition.cs:136
- TodoComment src/JudgeDredd/Services/OpenApiCommentAuditService.cs:19
- TodoComment src/LighthouseSocial.Application/Common/Pipeline/Behaviors/PerformanceBehavior.cs:19
- TodoComment src/LighthouseSocial.Application/Features/Comment/AddCommentHandler.cs:22
- TodoComment src/LighthouseSocial.Application/Features/Lighthouse/CreateLighthouseHandler.cs:29
- TodoComment src/LighthouseSocial.Application/Features/Lighthouse/CreateLighthouseHandler.cs:47
- TodoComment src/LighthouseSocial.Application/Features/Lighthouse/CreateLighthouseHandler.cs:65
- TodoComment src/LighthouseSocial.Application/Features/Lighthouse/CreateLighthouseHandler.cs:87
- TodoComment src/LighthouseSocial.Application/Features/User/CreateUserHandler.cs:25
- TodoComment src/LighthouseSocial.Application/Features/User/CreateUserHandler.cs:41
- TodoComment src/LighthouseSocial.Application/Features/User/CreateUserHandler.cs:58
- TodoComment src/LighthouseSocial.Application/Features/User/CreateUserHandler.cs:76
- TodoComment src/LighthouseSocial.Application/Validators/LighthouseDtoValidator.cs:17
- TodoComment REDACTED:115
- TodoComment REDACTED:70
- TodoComment REDACTED:75
- TodoComment src/LighthouseSocial.Data/Repositories/CachedCountryDataReader.cs:74
- TodoComment src/LighthouseSocial.Data/Repositories/PhotoRepository.cs:151
- TodoComment src/LighthouseSocial.Domain/Common/EntityBase.cs:6
- TodoComment src/LighthouseSocial.EventWorker/EventHandlers/PhotoUploadedEventHandler.cs:22
- TodoComment src/LighthouseSocial.Infrastructure/Auditors/ExternalCommentAuditor.cs:15
- TodoComment src/LighthouseSocial.Infrastructure/Auditors/ExternalCommentAuditor.cs:16
- TodoComment src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs:242
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dead code: SetIsPrimary src/LighthouseSocial.Domain/Entities/Photo.cs:35
- Dead code: FromId src/LighthouseSocial.Domain/Enumerations/CameraType.cs:14
- Dead code: FromId src/LighthouseSocial.Domain/Enumerations/PhotoCategory.cs:17
- Dead code: Common src/LighthouseSocial.Application/Common/Constants.cs:7
- Dead code: ServiceResponse src/LighthouseSocial.Application/Common/ServiceResponse.cs:3
- Dead code: CreateUserAsync src/LighthouseSocial.Application/Contracts/ExternalServices/IUserService.cs:8
- Dead code: GetUserByIdAsync src/LighthouseSocial.Application/Contracts/ExternalServices/IUserService.cs:9
- Dead code: GetUserByEmailAsync src/LighthouseSocial.Application/Contracts/ExternalServices/IUserService.cs:10
- Dead code: GetSecretsAsync src/LighthouseSocial.Application/Contracts/ISecretManager.cs:8
- Dead code: GetUserBySubIdAsync src/LighthouseSocial.Application/Services/UserService.cs:24
- Dead code: GetRabbitMqSettingsAsync src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs:78
- Dead code: InvalidateCacheAsync src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs:265
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Async local function without CancellationToken: RunInteractiveCliAsync REDACTED:43
- Async local function without CancellationToken: ExecuteLighthouseManagementAsync REDACTED:110
- Async local function without CancellationToken: ExecutePhotoManagementAsync REDACTED:119
- Async local function without CancellationToken: ExecuteComprehensiveFlowAsync REDACTED:131
- Async local function without CancellationToken: ExecuteCountryCacheTestAsync REDACTED:140
- Async local function without CancellationToken: ExecuteListPhotosForLighthouseTestAsync REDACTED:149
- Sync-over-async blocking
- Sync-over-async blocking src/LighthouseSocial.Infrastructure/DependencyInjection.cs:102
- Sync-over-async blocking src/LighthouseSocial.Infrastructure/Messaging/RabbitMqEventPublisher.cs:171
- Sync-over-async blocking src/LighthouseSocial.Infrastructure/Storage/PhotoStorageService.cs:20
- Sync-over-async blocking src/LighthouseSocial.Data/DependencyInjection.cs:59
- Anemic entity: Comment src/LighthouseSocial.Domain/Entities/Comment.cs:6
- Anemic entity: Lighthouse src/LighthouseSocial.Domain/Entities/Lighthouse.cs:6
- Anemic entity: Photo src/LighthouseSocial.Domain/Entities/Photo.cs:6
- Anemic entity: User src/LighthouseSocial.Domain/Entities/User.cs:5
- Sync-over-async (deadlock risk) src/LighthouseSocial.Infrastructure/DependencyInjection.cs:102
- Sync-over-async (deadlock risk) src/LighthouseSocial.Infrastructure/Messaging/RabbitMqEventPublisher.cs:171
- Sync-over-async (deadlock risk) src/LighthouseSocial.Infrastructure/Storage/PhotoStorageService.cs:20
- Sync-over-async (deadlock risk) src/LighthouseSocial.Data/DependencyInjection.cs:59
- Deprecated: xunit src/Tests/LighthouseSocial.Integration.Tests/LighthouseSocial.Integration.Tests.csproj:13
- Deprecated: xunit src/Tests/LighthouseSocial.Infrastructure.Tests/LighthouseSocial.Infrastructure.Tests.csproj:14
- Deprecated: xunit src/Tests/LighthouseSocial.Application.Tests/LighthouseSocial.Application.Tests.csproj:15
- Mutable entity: Lighthouse src/LighthouseSocial.Domain/Entities/Lighthouse.cs:6
- Mutable entity: Photo src/LighthouseSocial.Domain/Entities/Photo.cs:6
- Mutable entity: User src/LighthouseSocial.Domain/Entities/User.cs:5
- Heading level jumps from h1 to h3 src/LighthouseSocial.Backoffice/Pages/Index.cshtml:21
- Heading level jumps from h1 to h3 src/LighthouseSocial.Backoffice/Pages/Privacy.cshtml:25
- Heading level jumps from h3 to h5 src/LighthouseSocial.Backoffice/Pages/Index.cshtml:28
- Heading level jumps from h3 to h5 src/LighthouseSocial.Backoffice/Pages/Privacy.cshtml:36
- MethodTooLong: PhotoUploadSaga.ExecuteAsync src/LighthouseSocial.Application/Features/Photo/Saga/PhotoUploadSaga.cs:13
- MethodTooLong: AddCommentHandler.HandleAsync src/LighthouseSocial.Application/Features/Comment/AddCommentHandler.cs:30
- Outbound HTTP without resilience src/LighthouseSocial.Backoffice/Program.cs:8
- Outbound HTTP without resilience src/LighthouseSocial.WebApi/Program.cs:30
- Heading level jumps from h1 to h5 src/LighthouseSocial.Backoffice/Pages/Lighthouse/Create.cshtml:40
- Heading level jumps from h1 to h4 src/LighthouseSocial.Backoffice/Pages/Lighthouse/List.cshtml:39
- Accessibility enforcement below the top rung
- Stateful singleton: RabbitMqEventConsumerService src/LighthouseSocial.EventWorker/Services/RabbitMqEventConsumerService.cs:11
- No data-protection/encryption
- CachedConfigurationService.GetKeycloakSettingsAsync (cyclomatic 28) src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs:105
- CachedConfigurationService.GetKeycloakSettingsAsync (cognitive 24) src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs:105
- REDACTED
- Duplicated block (23 lines × 2) src/LighthouseSocial.Backoffice/Services/LigthouseServiceClient.cs:40
- Duplicated block (15–16 lines × 3) src/LighthouseSocial.Application/Features/User/GetUserByEmailHandler.cs:19
- Duplicated block (15 lines × 2) src/LighthouseSocial.Application/Features/Photo/GetPhotosByLighthouseHandler.cs:27
- Duplicated block (13 lines × 2) src/LighthouseSocial.Data/Repositories/LighthouseRepository.cs:23
- Duplicated block (3–13 lines × 3) src/LighthouseSocial.Data/Repositories/LighthouseRepository.cs:117
- Duplicated block (9 lines × 3) src/LighthouseSocial.Data/Repositories/UserRepository.cs:49
- Duplicated block (8 lines × 2) src/LighthouseSocial.Application/Features/Photo/Saga/PhotoUploadSaga.cs:60
- Duplicated block (9 lines × 2) src/Clients/TerminalApp/UseCases/Composition.cs:96
- Duplicated block (7 lines × 3) src/LighthouseSocial.Domain/Events/Photo/PhotoUploadSagaCompleted.cs:6
- Duplicated block (6 lines × 2) src/LighthouseSocial.Domain/Events/Lighthouse/LighthouseCreationFailed.cs:6
- Duplicated block (6 lines × 4) src/LighthouseSocial.Domain/Events/Photo/PhotoSavedToRepository.cs:6
- Duplicated block (5 lines × 2) src/LighthouseSocial.Domain/Events/User/UserCreationFailed.cs:6
- Duplicated block (6 lines × 7) src/LighthouseSocial.Domain/Events/Photo/PhotoSavedToRepository.cs:8
- Off the main sequence: LighthouseSocial.Domain src/LighthouseSocial.Domain/LighthouseSocial.Domain.csproj:1
- Constructible in an invalid state: Comment src/LighthouseSocial.Domain/Entities/Comment.cs:15
- Repository for a non-root entity: ICommentRepository → Comment src/LighthouseSocial.Application/Contracts/Repositories/ICommentRepository.cs:6
- No DR/backup evidence
- NuGet dependencies are not locked
- Symbol treated as nullable, then dereferenced unguarded src/LighthouseSocial.Infrastructure/Auditors/ExternalCommentAuditor.cs:29
Minor — 97 finding(s)
- Primitive id on a domain type: EventBase.EventId src/LighthouseSocial.Domain/Common/EventBase.cs:6
- Primitive id on a domain type: EventBase.AggregateId src/LighthouseSocial.Domain/Common/EventBase.cs:9
- Primitive id on a domain type: Comment.UserId src/LighthouseSocial.Domain/Entities/Comment.cs:9
- Primitive id on a domain type: Comment.PhotoId src/LighthouseSocial.Domain/Entities/Comment.cs:10
- Primitive id on a domain type: Lighthouse.CountryId src/LighthouseSocial.Domain/Entities/Lighthouse.cs:9
- Primitive id on a domain type: Photo.UserId src/LighthouseSocial.Domain/Entities/Photo.cs:9
- Primitive id on a domain type: Photo.LighthouseId src/LighthouseSocial.Domain/Entities/Photo.cs:10
- Primitive id on a domain type: User.ExternalId src/LighthouseSocial.Domain/Entities/User.cs:10
- Primitive id on a domain type: CommentCreated.UserId src/LighthouseSocial.Domain/Events/Comment/CommentCreated.cs:8
- Primitive id on a domain type: CommentCreated.PhotoId src/LighthouseSocial.Domain/Events/Comment/CommentCreated.cs:9
- Primitive id on a domain type: CommentCreationFailed.UserId src/LighthouseSocial.Domain/Events/Comment/CommentCreationFailed.cs:8
- Primitive id on a domain type: CommentCreationFailed.PhotoId src/LighthouseSocial.Domain/Events/Comment/CommentCreationFailed.cs:9
- Primitive id on a domain type: CommentCreationRequested.UserId src/LighthouseSocial.Domain/Events/Comment/CommentCreationRequested.cs:8
- Primitive id on a domain type: CommentCreationRequested.PhotoId src/LighthouseSocial.Domain/Events/Comment/CommentCreationRequested.cs:9
- Primitive id on a domain type: LighthouseCreated.CountryId src/LighthouseSocial.Domain/Events/Lighthouse/LighthouseCreated.cs:9
- Primitive id on a domain type: LighthouseCreationFailed.CountryId src/LighthouseSocial.Domain/Events/Lighthouse/LighthouseCreationFailed.cs:9
- Primitive id on a domain type: LighthouseCreationRequested.CountryId src/LighthouseSocial.Domain/Events/Lighthouse/LighthouseCreationRequested.cs:9
- Primitive id on a domain type: PhotoSavedToRepository.UserId src/LighthouseSocial.Domain/Events/Photo/PhotoSavedToRepository.cs:9
- Primitive id on a domain type: PhotoSavedToRepository.LighthouseId src/LighthouseSocial.Domain/Events/Photo/PhotoSavedToRepository.cs:10
- Primitive id on a domain type: PhotoUploaded.UserId src/LighthouseSocial.Domain/Events/Photo/PhotoUploaded.cs:9
- Primitive id on a domain type: PhotoUploaded.LighthouseId src/LighthouseSocial.Domain/Events/Photo/PhotoUploaded.cs:10
- Primitive id on a domain type: PhotoUploadFailed.UserId src/LighthouseSocial.Domain/Events/Photo/PhotoUploadFailed.cs:9
- Primitive id on a domain type: PhotoUploadFailed.LighthouseId src/LighthouseSocial.Domain/Events/Photo/PhotoUploadFailed.cs:10
- Primitive id on a domain type: PhotoUploadRequested.UserId src/LighthouseSocial.Domain/Events/Photo/PhotoUploadRequested.cs:9
- Primitive id on a domain type: PhotoUploadRequested.LighthouseId src/LighthouseSocial.Domain/Events/Photo/PhotoUploadRequested.cs:10
- Orphaned file src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs:1
- Orphaned file src/LighthouseSocial.Application/Features/Photo/Saga/PhotoUploadSaga.cs:1
- Orphaned file src/Clients/TerminalApp/UseCases/Composition.cs:1
- Orphaned file src/LighthouseSocial.Data/Repositories/LighthouseRepository.cs:1
- Orphaned file src/LighthouseSocial.Application/Features/Comment/AddCommentHandler.cs:1
- Orphaned file src/LighthouseSocial.Infrastructure/DependencyInjection.cs:1
- Orphaned file src/LighthouseSocial.EventWorker/Services/RabbitMqEventConsumerService.cs:1
- Orphaned file src/LighthouseSocial.Data/Repositories/PhotoRepository.cs:1
- Orphaned file src/LighthouseSocial.Infrastructure/Messaging/RabbitMqEventPublisher.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/Clients/TerminalApp/UseCases/PhotoManagement.cs:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file src/LighthouseSocial.Infrastructure/Storage/PhotoStorageService.cs:1
- Orphaned file src/LighthouseSocial.Backoffice/Services/LigthouseServiceClient.cs:1
- Orphaned file src/LighthouseSocial.Data/Repositories/CommentRepository.cs:1
- Orphaned file src/LighthouseSocial.Application/Features/Lighthouse/CreateLighthouseHandler.cs:1
- Orphaned file src/LighthouseSocial.Application/Features/Photo/UploadPhotoHandler.cs:1
- Orphaned file src/LighthouseSocial.Data/Repositories/UserRepository.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/LighthouseSocial.Application/DependencyInjection.cs:1
- Orphaned file src/LighthouseSocial.Application/Features/User/CreateUserHandler.cs:1
- Orphaned file src/Clients/TerminalApp/UseCases/LighthouseManagement.cs:1
- Orphaned file src/LighthouseSocial.Infrastructure/SecretManager/VaultSecretManager.cs:1
- Orphaned file src/LighthouseSocial.Application/Common/Constants.cs:1
- No security response headers detected
- No security response headers detected src/JudgeDredd/Program.cs:3
- No security response headers detected src/LighthouseSocial.Backoffice/Program.cs:3
- No security response headers detected src/LighthouseSocial.ODataApi/Program.cs:10
- No security response headers detected src/LighthouseSocial.WebApi/Program.cs:9
- Silent fallback default in catch src/LighthouseSocial.Application/Validators/PhotoDtoValidator.cs:43
- Silent fallback default in catch src/Clients/TerminalApp/UseCases/Composition.cs:72
- Silent fallback default in catch src/Clients/TerminalApp/UseCases/Composition.cs:121
- Duplicated predicate src/LighthouseSocial.Infrastructure/Configuration/CachedConfigurationService.cs:200
- Duplicated predicate src/LighthouseSocial.Application/Common/Pipeline/Behaviors/CancellationBehavior.cs:23
- Outdated: coverlet.collector src/Tests/LighthouseSocial.Application.Tests/LighthouseSocial.Application.Tests.csproj:11
- No ADRs found
- REDACTED
- REDACTED
- Dormant codebase
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST REDACTED:9
- No dependency-update automation src/Clients/TerminalApp/TerminalApp.csproj:11
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
- Silent fallback default on configuration miss src/LighthouseSocial.Infrastructure/DependencyInjection.cs:66
Minor — 32 finding(s)
- Outdated: FluentValidation
- Outdated: Microsoft.Extensions.DependencyInjection
- Outdated: Microsoft.Extensions.Logging
- Outdated: Microsoft.Extensions.Logging.Abstractions
- Outdated: Keycloak.AuthServices.Authentication
- Outdated: Keycloak.AuthServices.Authorization
- Outdated: Microsoft.Extensions.Caching.Memory
- Outdated: Microsoft.Extensions.Caching.StackExchangeRedis
- Outdated: Microsoft.Extensions.Configuration.Abstractions
- Outdated: Microsoft.Extensions.Configuration.Binder
- Outdated: Minio
- Outdated: RabbitMQ.Client
- Outdated: Serilog
- Outdated: Serilog.Extensions.Hosting
- Outdated: Serilog.Sinks.Console
- Outdated: Dapper
- Outdated: Npgsql
- Outdated: Microsoft.Extensions.Configuration
- Outdated: Microsoft.Extensions.Configuration.Json
- Outdated: Microsoft.Extensions.Logging.Console
- Outdated: Microsoft.AspNetCore.OData
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: xunit
- Outdated: xunit.runner.visualstudio
- Outdated: Moq
- Mock framework: Moq
- Mock framework: Moq
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9fbd3e308b9f4b418ce6027676b9ef5d/history.json --exit-code 0 --source . | 11 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9fbd3e308b9f4b418ce6027676b9ef5d/tree.json --exit-code 0 --source . | 7 | 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 . | 21 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/LighthouseSocial.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 17 | 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 78 file(s) — `src/Clients/TerminalApp/UseCases/Composition.cs`, `src/Clients/TerminalApp/UseCases/LighthouseManagement.cs`, `src/Clients/TerminalApp/UseCases/PhotoManagement.cs`, `src/Clients/TerminalApp/UseCases/ViewManagement.cs`, `src/JudgeDredd/Services/OpenApiCommentAuditService.cs`, … (+73 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-ac335e232cc04af9af0cc020d40d0e03 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 6 field(s)
- UserDto.Email src/LighthouseSocial.Application/Dtos/UserDto.cs:3
- GetUserByEmailRequest.Email src/LighthouseSocial.Application/Features/User/GetUserByEmailHandler.cs:8
- User.Email src/LighthouseSocial.Domain/Entities/User.cs:9
- UserCreated.Email src/LighthouseSocial.Domain/Events/User/UserCreated.cs:10
- UserCreationFailed.Email src/LighthouseSocial.Domain/Events/User/UserCreationFailed.cs:10
- UserCreationRequested.Email src/LighthouseSocial.Domain/Events/User/UserCreationRequested.cs:10
Name — 5 field(s)
- UserDto.Fullname src/LighthouseSocial.Application/Dtos/UserDto.cs:3
- User.Fullname src/LighthouseSocial.Domain/Entities/User.cs:8
- UserCreated.Fullname src/LighthouseSocial.Domain/Events/User/UserCreated.cs:9
- UserCreationFailed.Fullname src/LighthouseSocial.Domain/Events/User/UserCreationFailed.cs:9
- UserCreationRequested.Fullname src/LighthouseSocial.Domain/Events/User/UserCreationRequested.cs:9