Executive summary
Gramli/WeatherApi has a provisional result, because the code didn't build. It scores 65 out of 100, and the ratings may change once the code builds. All 13 of its critical findings are security problems. We judged it as a template or a sample, against a lower bar.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first steps are having someone learn and document the five files no active contributor knows and adding automated security scanning, each worth about 5 points.
Four passwords or keys are open to anyone who can read the repository. Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Replacing each exposed password or key and pinning each tool to an exact version would close both risks. Updating the vulnerable packages would fix the two packages with a known security hole, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once.
The product code is 1,441 lines, about €3,600 to rebuild.
If Production Readiness rose from 52 to 52, the lowest score rated Strong, the score would rise from 65 to about 65.
Rebuild cost: about €3,600 · Estimate
| Cost to rebuild | €1,200 to €6,000, for 20 to 63 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. 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 | Very small: 1,441 lines of product code, of which 58% is declarations and boilerplate, 33% straight logic and 9% logic with branches |
| Comment lines | The estimate prices 1,429 lines. Comment lines count towards the size of 1,441 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 (global) | 2 Weather.API.Configuration | 3 Weather.API.EndpointBuilders | 4 Weather.API.Middlewares | 5 Weather.Core.Configuration | 6 Weather.Core.HandlerModel | 7 Weather.Domain.Dtos | 8 Weather.Domain.Extensions | 9 Weather.Domain.Logging | 10 Weather.Infrastructure.Configuration | 11 Weather.Infrastructure.Database.EFContext.Entities | 12 Weather.Infrastructure.Mapping.Profiles | 13 Wheaterbit.Client.Configuration | 14 Wheaterbit.Client.Dtos | 15 Wheaterbit.Client.Options | 16 Weather.Domain.BusinessEntities | 17 Weather.Domain.Commands | 18 Weather.Domain.Queries | 19 Weather.Infrastructure.Database.EFContext | 20 Wheaterbit.Client.Abstractions | 21 Wheaterbit.Client.Validation | 22 Weather.Core.Abstractions | 23 Weather.Infrastructure.Database | 24 Wheaterbit.Client | 25 Wheaterbit.Client.Factories | 26 Weather.API.Extensions | 27 Weather.Core.Commands | 28 Weather.Core.Queries | 29 Weather.Core.Validation | 30 Weather.Infrastructure.Database.Repositories | 31 Weather.Infrastructure.Services |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | |||||||||||||||||||||||||||||||
| 2 Weather.API.Configuration | |||||||||||||||||||||||||||||||
| 3 Weather.API.EndpointBuilders | |||||||||||||||||||||||||||||||
| 4 Weather.API.Middlewares | |||||||||||||||||||||||||||||||
| 5 Weather.Core.Configuration | |||||||||||||||||||||||||||||||
| 6 Weather.Core.HandlerModel | |||||||||||||||||||||||||||||||
| 7 Weather.Domain.Dtos | |||||||||||||||||||||||||||||||
| 8 Weather.Domain.Extensions | |||||||||||||||||||||||||||||||
| 9 Weather.Domain.Logging | |||||||||||||||||||||||||||||||
| 10 Weather.Infrastructure.Configuration | |||||||||||||||||||||||||||||||
| 11 Weather.Infrastructure.Database.EFContext.Entities | |||||||||||||||||||||||||||||||
| 12 Weather.Infrastructure.Mapping.Profiles | |||||||||||||||||||||||||||||||
| 13 Wheaterbit.Client.Configuration | |||||||||||||||||||||||||||||||
| 14 Wheaterbit.Client.Dtos | |||||||||||||||||||||||||||||||
| 15 Wheaterbit.Client.Options | |||||||||||||||||||||||||||||||
| 16 Weather.Domain.BusinessEntities | 1 | ||||||||||||||||||||||||||||||
| 17 Weather.Domain.Commands | 1 | ||||||||||||||||||||||||||||||
| 18 Weather.Domain.Queries | 2 | ||||||||||||||||||||||||||||||
| 19 Weather.Infrastructure.Database.EFContext | 1 | ||||||||||||||||||||||||||||||
| 20 Wheaterbit.Client.Abstractions | 2 | ||||||||||||||||||||||||||||||
| 21 Wheaterbit.Client.Validation | 1 | ||||||||||||||||||||||||||||||
| 22 Weather.Core.Abstractions | 3 | 3 | 1 | 2 | |||||||||||||||||||||||||||
| 23 Weather.Infrastructure.Database | 1 | ||||||||||||||||||||||||||||||
| 24 Wheaterbit.Client | 2 | 1 | 2 | ||||||||||||||||||||||||||||
| 25 Wheaterbit.Client.Factories | 1 | ||||||||||||||||||||||||||||||
| 26 Weather.API.Extensions | 1 | ||||||||||||||||||||||||||||||
| 27 Weather.Core.Commands | 2 | 2 | 6 | ||||||||||||||||||||||||||||
| 28 Weather.Core.Queries | 5 | 5 | 1 | 2 | 10 | ||||||||||||||||||||||||||
| 29 Weather.Core.Validation | 7 | 4 | 2 | 2 | 7 | ||||||||||||||||||||||||||
| 30 Weather.Infrastructure.Database.Repositories | 1 | 2 | 2 | 2 | 2 | ||||||||||||||||||||||||||
| 31 Weather.Infrastructure.Services | 3 | 1 | 1 |
16→7 Weather.Domain.BusinessEntities uses Weather.Domain.Dtos✕
- Connections
- 1 pair of types, where a type in Weather.Domain.BusinessEntities uses a type in Weather.Domain.Dtos.
- The types involved
Weather.Domain.BusinessEntities.FavoriteLocation→Weather.Domain.Dtos.LocationDto
- Direction
- Weather.Domain.BusinessEntities uses Weather.Domain.Dtos, so a change to Weather.Domain.Dtos can break Weather.Domain.BusinessEntities, while a change to Weather.Domain.BusinessEntities can't break Weather.Domain.Dtos.
- Position
- Below the diagonal: Weather.Domain.BusinessEntities uses a module listed above it, which is the healthy direction.
17→7 Weather.Domain.Commands uses Weather.Domain.Dtos✕
- Connections
- 1 pair of types, where a type in Weather.Domain.Commands uses a type in Weather.Domain.Dtos.
- The types involved
Weather.Domain.Commands.AddFavoriteCommand→Weather.Domain.Dtos.LocationDto
- Direction
- Weather.Domain.Commands uses Weather.Domain.Dtos, so a change to Weather.Domain.Dtos can break Weather.Domain.Commands, while a change to Weather.Domain.Commands can't break Weather.Domain.Dtos.
- Position
- Below the diagonal: Weather.Domain.Commands uses a module listed above it, which is the healthy direction.
18→7 Weather.Domain.Queries uses Weather.Domain.Dtos✕
- Connections
- 2 pairs of types, where a type in Weather.Domain.Queries uses a type in Weather.Domain.Dtos.
- The types involved
Weather.Domain.Queries.GetCurrentWeatherQuery→Weather.Domain.Dtos.LocationDtoWeather.Domain.Queries.GetForecastWeatherQuery→Weather.Domain.Dtos.LocationDto
- Direction
- Weather.Domain.Queries uses Weather.Domain.Dtos, so a change to Weather.Domain.Dtos can break Weather.Domain.Queries, while a change to Weather.Domain.Queries can't break Weather.Domain.Dtos.
- Position
- Below the diagonal: Weather.Domain.Queries uses a module listed above it, which is the healthy direction.
19→11 Weather.Infrastructure.Database.EFContext uses Weather.Infrastructure.Database.EFContext.Entities✕
- Connections
- 1 pair of types, where a type in Weather.Infrastructure.Database.EFContext uses a type in Weather.Infrastructure.Database.EFContext.Entities.
- The types involved
Weather.Infrastructure.Database.EFContext.WeatherContext→Weather.Infrastructure.Database.EFContext.Entities.FavoriteLocationEntity
- Direction
- Weather.Infrastructure.Database.EFContext uses Weather.Infrastructure.Database.EFContext.Entities, so a change to Weather.Infrastructure.Database.EFContext.Entities can break Weather.Infrastructure.Database.EFContext, while a change to Weather.Infrastructure.Database.EFContext can't break Weather.Infrastructure.Database.EFContext.Entities.
- Position
- Below the diagonal: Weather.Infrastructure.Database.EFContext uses a module listed above it, which is the healthy direction.
20→14 Wheaterbit.Client.Abstractions uses Wheaterbit.Client.Dtos✕
- Connections
- 2 pairs of types, where a type in Wheaterbit.Client.Abstractions uses a type in Wheaterbit.Client.Dtos.
- The types involved
Wheaterbit.Client.Abstractions.IWeatherbitHttpClient→Wheaterbit.Client.Dtos.CurrentWeatherDataDtoWheaterbit.Client.Abstractions.IWeatherbitHttpClient→Wheaterbit.Client.Dtos.ForecastWeatherDto
- Direction
- Wheaterbit.Client.Abstractions uses Wheaterbit.Client.Dtos, so a change to Wheaterbit.Client.Dtos can break Wheaterbit.Client.Abstractions, while a change to Wheaterbit.Client.Abstractions can't break Wheaterbit.Client.Dtos.
- Position
- Below the diagonal: Wheaterbit.Client.Abstractions uses a module listed above it, which is the healthy direction.
21→15 Wheaterbit.Client.Validation uses Wheaterbit.Client.Options✕
- Connections
- 1 pair of types, where a type in Wheaterbit.Client.Validation uses a type in Wheaterbit.Client.Options.
- The types involved
Wheaterbit.Client.Validation.WeatherbitOptionsSpecificationHolder→Wheaterbit.Client.Options.WeatherbitOptions
- Direction
- Wheaterbit.Client.Validation uses Wheaterbit.Client.Options, so a change to Wheaterbit.Client.Options can break Wheaterbit.Client.Validation, while a change to Wheaterbit.Client.Validation can't break Wheaterbit.Client.Options.
- Position
- Below the diagonal: Wheaterbit.Client.Validation uses a module listed above it, which is the healthy direction.
22→6 Weather.Core.Abstractions uses Weather.Core.HandlerModel✕
- Connections
- 3 pairs of types, where a type in Weather.Core.Abstractions uses a type in Weather.Core.HandlerModel.
- The types involved
Weather.Core.Abstractions.IRequestValidator→Weather.Core.HandlerModel.RequestValidationResultWeather.Core.Abstractions.ValidationStatusRequestHandler→Weather.Core.HandlerModel.HandlerResponseWeather.Core.Abstractions.ValidationStatusRequestHandler→Weather.Core.HandlerModel.RequestValidationResult
- Direction
- Weather.Core.Abstractions uses Weather.Core.HandlerModel, so a change to Weather.Core.HandlerModel can break Weather.Core.Abstractions, while a change to Weather.Core.Abstractions can't break Weather.Core.HandlerModel.
- Position
- Below the diagonal: Weather.Core.Abstractions uses a module listed above it, which is the healthy direction.
22→7 Weather.Core.Abstractions uses Weather.Domain.Dtos✕
- Connections
- 3 pairs of types, where a type in Weather.Core.Abstractions uses a type in Weather.Domain.Dtos.
- The types involved
Weather.Core.Abstractions.IWeatherService→Weather.Domain.Dtos.CurrentWeatherDtoWeather.Core.Abstractions.IWeatherService→Weather.Domain.Dtos.ForecastWeatherDtoWeather.Core.Abstractions.IWeatherService→Weather.Domain.Dtos.LocationDto
- Direction
- Weather.Core.Abstractions uses Weather.Domain.Dtos, so a change to Weather.Domain.Dtos can break Weather.Core.Abstractions, while a change to Weather.Core.Abstractions can't break Weather.Domain.Dtos.
- Position
- Below the diagonal: Weather.Core.Abstractions uses a module listed above it, which is the healthy direction.
22→16 Weather.Core.Abstractions uses Weather.Domain.BusinessEntities✕
- Connections
- 1 pair of types, where a type in Weather.Core.Abstractions uses a type in Weather.Domain.BusinessEntities.
- The types involved
Weather.Core.Abstractions.IWeatherQueriesRepository→Weather.Domain.BusinessEntities.FavoriteLocation
- Direction
- Weather.Core.Abstractions uses Weather.Domain.BusinessEntities, so a change to Weather.Domain.BusinessEntities can break Weather.Core.Abstractions, while a change to Weather.Core.Abstractions can't break Weather.Domain.BusinessEntities.
- Position
- Below the diagonal: Weather.Core.Abstractions uses a module listed above it, which is the healthy direction.
22→17 Weather.Core.Abstractions uses Weather.Domain.Commands✕
- Connections
- 2 pairs of types, where a type in Weather.Core.Abstractions uses a type in Weather.Domain.Commands.
- The types involved
Weather.Core.Abstractions.IWeatherCommandsRepository→Weather.Domain.Commands.AddFavoriteCommandWeather.Core.Abstractions.IWeatherCommandsRepository→Weather.Domain.Commands.DeleteFavoriteCommand
- Direction
- Weather.Core.Abstractions uses Weather.Domain.Commands, so a change to Weather.Domain.Commands can break Weather.Core.Abstractions, while a change to Weather.Core.Abstractions can't break Weather.Domain.Commands.
- Position
- Below the diagonal: Weather.Core.Abstractions uses a module listed above it, which is the healthy direction.
23→19 Weather.Infrastructure.Database uses Weather.Infrastructure.Database.EFContext✕
- Connections
- 1 pair of types, where a type in Weather.Infrastructure.Database uses a type in Weather.Infrastructure.Database.EFContext.
- The types involved
Weather.Infrastructure.Database.RepositoryBase→Weather.Infrastructure.Database.EFContext.WeatherContext
- Direction
- Weather.Infrastructure.Database uses Weather.Infrastructure.Database.EFContext, so a change to Weather.Infrastructure.Database.EFContext can break Weather.Infrastructure.Database, while a change to Weather.Infrastructure.Database can't break Weather.Infrastructure.Database.EFContext.
- Position
- Below the diagonal: Weather.Infrastructure.Database uses a module listed above it, which is the healthy direction.
24→14 Wheaterbit.Client uses Wheaterbit.Client.Dtos✕
- Connections
- 2 pairs of types, where a type in Wheaterbit.Client uses a type in Wheaterbit.Client.Dtos.
- The types involved
Wheaterbit.Client.WeatherbitHttpClient→Wheaterbit.Client.Dtos.CurrentWeatherDataDtoWheaterbit.Client.WeatherbitHttpClient→Wheaterbit.Client.Dtos.ForecastWeatherDto
- Direction
- Wheaterbit.Client uses Wheaterbit.Client.Dtos, so a change to Wheaterbit.Client.Dtos can break Wheaterbit.Client, while a change to Wheaterbit.Client can't break Wheaterbit.Client.Dtos.
- Position
- Below the diagonal: Wheaterbit.Client uses a module listed above it, which is the healthy direction.
24→15 Wheaterbit.Client uses Wheaterbit.Client.Options✕
- Connections
- 1 pair of types, where a type in Wheaterbit.Client uses a type in Wheaterbit.Client.Options.
- The types involved
Wheaterbit.Client.WeatherbitHttpClient→Wheaterbit.Client.Options.WeatherbitOptions
- Direction
- Wheaterbit.Client uses Wheaterbit.Client.Options, so a change to Wheaterbit.Client.Options can break Wheaterbit.Client, while a change to Wheaterbit.Client can't break Wheaterbit.Client.Options.
- Position
- Below the diagonal: Wheaterbit.Client uses a module listed above it, which is the healthy direction.
24→20 Wheaterbit.Client uses Wheaterbit.Client.Abstractions✕
- Connections
- 2 pairs of types, where a type in Wheaterbit.Client uses a type in Wheaterbit.Client.Abstractions.
- The types involved
Wheaterbit.Client.WeatherbitHttpClient→Wheaterbit.Client.Abstractions.IJsonSerializerSettingsFactoryWheaterbit.Client.WeatherbitHttpClient→Wheaterbit.Client.Abstractions.IWeatherbitHttpClient
- Direction
- Wheaterbit.Client uses Wheaterbit.Client.Abstractions, so a change to Wheaterbit.Client.Abstractions can break Wheaterbit.Client, while a change to Wheaterbit.Client can't break Wheaterbit.Client.Abstractions.
- Position
- Below the diagonal: Wheaterbit.Client uses a module listed above it, which is the healthy direction.
25→20 Wheaterbit.Client.Factories uses Wheaterbit.Client.Abstractions✕
- Connections
- 1 pair of types, where a type in Wheaterbit.Client.Factories uses a type in Wheaterbit.Client.Abstractions.
- The types involved
Wheaterbit.Client.Factories.JsonSerializerSettingsFactory→Wheaterbit.Client.Abstractions.IJsonSerializerSettingsFactory
- Direction
- Wheaterbit.Client.Factories uses Wheaterbit.Client.Abstractions, so a change to Wheaterbit.Client.Abstractions can break Wheaterbit.Client.Factories, while a change to Wheaterbit.Client.Factories can't break Wheaterbit.Client.Abstractions.
- Position
- Below the diagonal: Wheaterbit.Client.Factories uses a module listed above it, which is the healthy direction.
26→22 Weather.API.Extensions uses Weather.Core.Abstractions✕
- Connections
- 1 pair of types, where a type in Weather.API.Extensions uses a type in Weather.Core.Abstractions.
- The types involved
Weather.API.Extensions.HandlerExtensions→Weather.Core.Abstractions.IStatusRequestHandler
- Direction
- Weather.API.Extensions uses Weather.Core.Abstractions, so a change to Weather.Core.Abstractions can break Weather.API.Extensions, while a change to Weather.API.Extensions can't break Weather.Core.Abstractions.
- Position
- Below the diagonal: Weather.API.Extensions uses a module listed above it, which is the healthy direction.
27→6 Weather.Core.Commands uses Weather.Core.HandlerModel✕
- Connections
- 2 pairs of types, where a type in Weather.Core.Commands uses a type in Weather.Core.HandlerModel.
- The types involved
Weather.Core.Commands.AddFavoriteHandler→Weather.Core.HandlerModel.HandlerResponseWeather.Core.Commands.DeleteFavoriteHandler→Weather.Core.HandlerModel.HandlerResponse
- Direction
- Weather.Core.Commands uses Weather.Core.HandlerModel, so a change to Weather.Core.HandlerModel can break Weather.Core.Commands, while a change to Weather.Core.Commands can't break Weather.Core.HandlerModel.
- Position
- Below the diagonal: Weather.Core.Commands uses a module listed above it, which is the healthy direction.
27→17 Weather.Core.Commands uses Weather.Domain.Commands✕
- Connections
- 2 pairs of types, where a type in Weather.Core.Commands uses a type in Weather.Domain.Commands.
- The types involved
Weather.Core.Commands.AddFavoriteHandler→Weather.Domain.Commands.AddFavoriteCommandWeather.Core.Commands.DeleteFavoriteHandler→Weather.Domain.Commands.DeleteFavoriteCommand
- Direction
- Weather.Core.Commands uses Weather.Domain.Commands, so a change to Weather.Domain.Commands can break Weather.Core.Commands, while a change to Weather.Core.Commands can't break Weather.Domain.Commands.
- Position
- Below the diagonal: Weather.Core.Commands uses a module listed above it, which is the healthy direction.
27→22 Weather.Core.Commands uses Weather.Core.Abstractions✕
- Connections
- 6 pairs of types, where a type in Weather.Core.Commands uses a type in Weather.Core.Abstractions.
- The types involved
Weather.Core.Commands.AddFavoriteHandler→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Commands.AddFavoriteHandler→Weather.Core.Abstractions.IWeatherCommandsRepositoryWeather.Core.Commands.AddFavoriteHandler→Weather.Core.Abstractions.ValidationStatusRequestHandlerWeather.Core.Commands.DeleteFavoriteHandler→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Commands.DeleteFavoriteHandler→Weather.Core.Abstractions.IWeatherCommandsRepositoryWeather.Core.Commands.DeleteFavoriteHandler→Weather.Core.Abstractions.ValidationStatusRequestHandler
- Direction
- Weather.Core.Commands uses Weather.Core.Abstractions, so a change to Weather.Core.Abstractions can break Weather.Core.Commands, while a change to Weather.Core.Commands can't break Weather.Core.Abstractions.
- Position
- Below the diagonal: Weather.Core.Commands uses a module listed above it, which is the healthy direction.
28→6 Weather.Core.Queries uses Weather.Core.HandlerModel✕
- Connections
- 5 pairs of types, where a type in Weather.Core.Queries uses a type in Weather.Core.HandlerModel.
- The types involved
Weather.Core.Queries.GetCurrentWeatherHandler→Weather.Core.HandlerModel.HandlerResponseWeather.Core.Queries.GetCurrentWeatherHandler→Weather.Core.HandlerModel.RequestValidationResultWeather.Core.Queries.GetFavoritesHandler→Weather.Core.HandlerModel.EmptyRequestWeather.Core.Queries.GetFavoritesHandler→Weather.Core.HandlerModel.HandlerResponseWeather.Core.Queries.GetForecastWeatherHandler→Weather.Core.HandlerModel.HandlerResponse
- Direction
- Weather.Core.Queries uses Weather.Core.HandlerModel, so a change to Weather.Core.HandlerModel can break Weather.Core.Queries, while a change to Weather.Core.Queries can't break Weather.Core.HandlerModel.
- Position
- Below the diagonal: Weather.Core.Queries uses a module listed above it, which is the healthy direction.
28→7 Weather.Core.Queries uses Weather.Domain.Dtos✕
- Connections
- 5 pairs of types, where a type in Weather.Core.Queries uses a type in Weather.Domain.Dtos.
- The types involved
Weather.Core.Queries.GetCurrentWeatherHandler→Weather.Domain.Dtos.CurrentWeatherDtoWeather.Core.Queries.GetFavoritesHandler→Weather.Domain.Dtos.CurrentWeatherDtoWeather.Core.Queries.GetFavoritesHandler→Weather.Domain.Dtos.FavoritesWeatherDtoWeather.Core.Queries.GetFavoritesHandler→Weather.Domain.Dtos.LocationDtoWeather.Core.Queries.GetForecastWeatherHandler→Weather.Domain.Dtos.ForecastWeatherDto
- Direction
- Weather.Core.Queries uses Weather.Domain.Dtos, so a change to Weather.Domain.Dtos can break Weather.Core.Queries, while a change to Weather.Core.Queries can't break Weather.Domain.Dtos.
- Position
- Below the diagonal: Weather.Core.Queries uses a module listed above it, which is the healthy direction.
28→16 Weather.Core.Queries uses Weather.Domain.BusinessEntities✕
- Connections
- 1 pair of types, where a type in Weather.Core.Queries uses a type in Weather.Domain.BusinessEntities.
- The types involved
Weather.Core.Queries.GetFavoritesHandler→Weather.Domain.BusinessEntities.FavoriteLocation
- Direction
- Weather.Core.Queries uses Weather.Domain.BusinessEntities, so a change to Weather.Domain.BusinessEntities can break Weather.Core.Queries, while a change to Weather.Core.Queries can't break Weather.Domain.BusinessEntities.
- Position
- Below the diagonal: Weather.Core.Queries uses a module listed above it, which is the healthy direction.
28→18 Weather.Core.Queries uses Weather.Domain.Queries✕
- Connections
- 2 pairs of types, where a type in Weather.Core.Queries uses a type in Weather.Domain.Queries.
- The types involved
Weather.Core.Queries.GetCurrentWeatherHandler→Weather.Domain.Queries.GetCurrentWeatherQueryWeather.Core.Queries.GetForecastWeatherHandler→Weather.Domain.Queries.GetForecastWeatherQuery
- Direction
- Weather.Core.Queries uses Weather.Domain.Queries, so a change to Weather.Domain.Queries can break Weather.Core.Queries, while a change to Weather.Core.Queries can't break Weather.Domain.Queries.
- Position
- Below the diagonal: Weather.Core.Queries uses a module listed above it, which is the healthy direction.
28→22 Weather.Core.Queries uses Weather.Core.Abstractions✕
- Connections
- 10 pairs of types, where a type in Weather.Core.Queries uses a type in Weather.Core.Abstractions.
- The types involved
Weather.Core.Queries.GetCurrentWeatherHandler→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Queries.GetCurrentWeatherHandler→Weather.Core.Abstractions.IWeatherServiceWeather.Core.Queries.GetCurrentWeatherHandler→Weather.Core.Abstractions.ValidationStatusRequestHandlerWeather.Core.Queries.GetFavoritesHandler→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Queries.GetFavoritesHandler→Weather.Core.Abstractions.IStatusRequestHandlerWeather.Core.Queries.GetFavoritesHandler→Weather.Core.Abstractions.IWeatherQueriesRepositoryWeather.Core.Queries.GetFavoritesHandler→Weather.Core.Abstractions.IWeatherServiceWeather.Core.Queries.GetForecastWeatherHandler→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Queries.GetForecastWeatherHandler→Weather.Core.Abstractions.IWeatherServiceWeather.Core.Queries.GetForecastWeatherHandler→Weather.Core.Abstractions.ValidationStatusRequestHandler
- Direction
- Weather.Core.Queries uses Weather.Core.Abstractions, so a change to Weather.Core.Abstractions can break Weather.Core.Queries, while a change to Weather.Core.Queries can't break Weather.Core.Abstractions.
- Position
- Below the diagonal: Weather.Core.Queries uses a module listed above it, which is the healthy direction.
29→6 Weather.Core.Validation uses Weather.Core.HandlerModel✕
- Connections
- 7 pairs of types, where a type in Weather.Core.Validation uses a type in Weather.Core.HandlerModel.
- The types involved
Weather.Core.Validation.AddFavoriteCommandValidator→Weather.Core.HandlerModel.RequestValidationResultWeather.Core.Validation.CurrentWeatherDtoValidator→Weather.Core.HandlerModel.RequestValidationResultWeather.Core.Validation.DeleteFavoriteCommandValidator→Weather.Core.HandlerModel.RequestValidationResultWeather.Core.Validation.ForecastWeatherDtoValidator→Weather.Core.HandlerModel.RequestValidationResultWeather.Core.Validation.GetCurrentWeatherQueryValidator→Weather.Core.HandlerModel.RequestValidationResultWeather.Core.Validation.GetForecastWeatherValidator→Weather.Core.HandlerModel.RequestValidationResultWeather.Core.Validation.LocationDtoValidator→Weather.Core.HandlerModel.RequestValidationResult
- Direction
- Weather.Core.Validation uses Weather.Core.HandlerModel, so a change to Weather.Core.HandlerModel can break Weather.Core.Validation, while a change to Weather.Core.Validation can't break Weather.Core.HandlerModel.
- Position
- Below the diagonal: Weather.Core.Validation uses a module listed above it, which is the healthy direction.
29→7 Weather.Core.Validation uses Weather.Domain.Dtos✕
- Connections
- 4 pairs of types, where a type in Weather.Core.Validation uses a type in Weather.Domain.Dtos.
- The types involved
Weather.Core.Validation.CurrentWeatherDtoValidator→Weather.Domain.Dtos.CurrentWeatherDtoWeather.Core.Validation.ForecastWeatherDtoValidator→Weather.Domain.Dtos.ForecastWeatherDtoWeather.Core.Validation.GeneralPredicates→Weather.Domain.Dtos.LocationDtoWeather.Core.Validation.LocationDtoValidator→Weather.Domain.Dtos.LocationDto
- Direction
- Weather.Core.Validation uses Weather.Domain.Dtos, so a change to Weather.Domain.Dtos can break Weather.Core.Validation, while a change to Weather.Core.Validation can't break Weather.Domain.Dtos.
- Position
- Below the diagonal: Weather.Core.Validation uses a module listed above it, which is the healthy direction.
29→17 Weather.Core.Validation uses Weather.Domain.Commands✕
- Connections
- 2 pairs of types, where a type in Weather.Core.Validation uses a type in Weather.Domain.Commands.
- The types involved
Weather.Core.Validation.AddFavoriteCommandValidator→Weather.Domain.Commands.AddFavoriteCommandWeather.Core.Validation.DeleteFavoriteCommandValidator→Weather.Domain.Commands.DeleteFavoriteCommand
- Direction
- Weather.Core.Validation uses Weather.Domain.Commands, so a change to Weather.Domain.Commands can break Weather.Core.Validation, while a change to Weather.Core.Validation can't break Weather.Domain.Commands.
- Position
- Below the diagonal: Weather.Core.Validation uses a module listed above it, which is the healthy direction.
29→18 Weather.Core.Validation uses Weather.Domain.Queries✕
- Connections
- 2 pairs of types, where a type in Weather.Core.Validation uses a type in Weather.Domain.Queries.
- The types involved
Weather.Core.Validation.GetCurrentWeatherQueryValidator→Weather.Domain.Queries.GetCurrentWeatherQueryWeather.Core.Validation.GetForecastWeatherValidator→Weather.Domain.Queries.GetForecastWeatherQuery
- Direction
- Weather.Core.Validation uses Weather.Domain.Queries, so a change to Weather.Domain.Queries can break Weather.Core.Validation, while a change to Weather.Core.Validation can't break Weather.Domain.Queries.
- Position
- Below the diagonal: Weather.Core.Validation uses a module listed above it, which is the healthy direction.
29→22 Weather.Core.Validation uses Weather.Core.Abstractions✕
- Connections
- 7 pairs of types, where a type in Weather.Core.Validation uses a type in Weather.Core.Abstractions.
- The types involved
Weather.Core.Validation.AddFavoriteCommandValidator→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Validation.CurrentWeatherDtoValidator→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Validation.DeleteFavoriteCommandValidator→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Validation.ForecastWeatherDtoValidator→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Validation.GetCurrentWeatherQueryValidator→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Validation.GetForecastWeatherValidator→Weather.Core.Abstractions.IRequestValidatorWeather.Core.Validation.LocationDtoValidator→Weather.Core.Abstractions.IRequestValidator
- Direction
- Weather.Core.Validation uses Weather.Core.Abstractions, so a change to Weather.Core.Abstractions can break Weather.Core.Validation, while a change to Weather.Core.Validation can't break Weather.Core.Abstractions.
- Position
- Below the diagonal: Weather.Core.Validation uses a module listed above it, which is the healthy direction.
30→16 Weather.Infrastructure.Database.Repositories uses Weather.Domain.BusinessEntities✕
- Connections
- 1 pair of types, where a type in Weather.Infrastructure.Database.Repositories uses a type in Weather.Domain.BusinessEntities.
- The types involved
Weather.Infrastructure.Database.Repositories.WeatherQueriesRepository→Weather.Domain.BusinessEntities.FavoriteLocation
- Direction
- Weather.Infrastructure.Database.Repositories uses Weather.Domain.BusinessEntities, so a change to Weather.Domain.BusinessEntities can break Weather.Infrastructure.Database.Repositories, while a change to Weather.Infrastructure.Database.Repositories can't break Weather.Domain.BusinessEntities.
- Position
- Below the diagonal: Weather.Infrastructure.Database.Repositories uses a module listed above it, which is the healthy direction.
30→17 Weather.Infrastructure.Database.Repositories uses Weather.Domain.Commands✕
- Connections
- 2 pairs of types, where a type in Weather.Infrastructure.Database.Repositories uses a type in Weather.Domain.Commands.
- The types involved
Weather.Infrastructure.Database.Repositories.WeatherCommandsRepository→Weather.Domain.Commands.AddFavoriteCommandWeather.Infrastructure.Database.Repositories.WeatherCommandsRepository→Weather.Domain.Commands.DeleteFavoriteCommand
- Direction
- Weather.Infrastructure.Database.Repositories uses Weather.Domain.Commands, so a change to Weather.Domain.Commands can break Weather.Infrastructure.Database.Repositories, while a change to Weather.Infrastructure.Database.Repositories can't break Weather.Domain.Commands.
- Position
- Below the diagonal: Weather.Infrastructure.Database.Repositories uses a module listed above it, which is the healthy direction.
30→19 Weather.Infrastructure.Database.Repositories uses Weather.Infrastructure.Database.EFContext✕
- Connections
- 2 pairs of types, where a type in Weather.Infrastructure.Database.Repositories uses a type in Weather.Infrastructure.Database.EFContext.
- The types involved
Weather.Infrastructure.Database.Repositories.WeatherCommandsRepository→Weather.Infrastructure.Database.EFContext.WeatherContextWeather.Infrastructure.Database.Repositories.WeatherQueriesRepository→Weather.Infrastructure.Database.EFContext.WeatherContext
- Direction
- Weather.Infrastructure.Database.Repositories uses Weather.Infrastructure.Database.EFContext, so a change to Weather.Infrastructure.Database.EFContext can break Weather.Infrastructure.Database.Repositories, while a change to Weather.Infrastructure.Database.Repositories can't break Weather.Infrastructure.Database.EFContext.
- Position
- Below the diagonal: Weather.Infrastructure.Database.Repositories uses a module listed above it, which is the healthy direction.
30→22 Weather.Infrastructure.Database.Repositories uses Weather.Core.Abstractions✕
- Connections
- 2 pairs of types, where a type in Weather.Infrastructure.Database.Repositories uses a type in Weather.Core.Abstractions.
- The types involved
Weather.Infrastructure.Database.Repositories.WeatherCommandsRepository→Weather.Core.Abstractions.IWeatherCommandsRepositoryWeather.Infrastructure.Database.Repositories.WeatherQueriesRepository→Weather.Core.Abstractions.IWeatherQueriesRepository
- Direction
- Weather.Infrastructure.Database.Repositories uses Weather.Core.Abstractions, so a change to Weather.Core.Abstractions can break Weather.Infrastructure.Database.Repositories, while a change to Weather.Infrastructure.Database.Repositories can't break Weather.Core.Abstractions.
- Position
- Below the diagonal: Weather.Infrastructure.Database.Repositories uses a module listed above it, which is the healthy direction.
30→23 Weather.Infrastructure.Database.Repositories uses Weather.Infrastructure.Database✕
- Connections
- 2 pairs of types, where a type in Weather.Infrastructure.Database.Repositories uses a type in Weather.Infrastructure.Database.
- The types involved
Weather.Infrastructure.Database.Repositories.WeatherCommandsRepository→Weather.Infrastructure.Database.RepositoryBaseWeather.Infrastructure.Database.Repositories.WeatherQueriesRepository→Weather.Infrastructure.Database.RepositoryBase
- Direction
- Weather.Infrastructure.Database.Repositories uses Weather.Infrastructure.Database, so a change to Weather.Infrastructure.Database can break Weather.Infrastructure.Database.Repositories, while a change to Weather.Infrastructure.Database.Repositories can't break Weather.Infrastructure.Database.
- Position
- Below the diagonal: Weather.Infrastructure.Database.Repositories uses a module listed above it, which is the healthy direction.
31→7 Weather.Infrastructure.Services uses Weather.Domain.Dtos✕
- Connections
- 3 pairs of types, where a type in Weather.Infrastructure.Services uses a type in Weather.Domain.Dtos.
- The types involved
Weather.Infrastructure.Services.WeatherService→Weather.Domain.Dtos.CurrentWeatherDtoWeather.Infrastructure.Services.WeatherService→Weather.Domain.Dtos.ForecastWeatherDtoWeather.Infrastructure.Services.WeatherService→Weather.Domain.Dtos.LocationDto
- Direction
- Weather.Infrastructure.Services uses Weather.Domain.Dtos, so a change to Weather.Domain.Dtos can break Weather.Infrastructure.Services, while a change to Weather.Infrastructure.Services can't break Weather.Domain.Dtos.
- Position
- Below the diagonal: Weather.Infrastructure.Services uses a module listed above it, which is the healthy direction.
31→20 Weather.Infrastructure.Services uses Wheaterbit.Client.Abstractions✕
- Connections
- 1 pair of types, where a type in Weather.Infrastructure.Services uses a type in Wheaterbit.Client.Abstractions.
- The types involved
Weather.Infrastructure.Services.WeatherService→Wheaterbit.Client.Abstractions.IWeatherbitHttpClient
- Direction
- Weather.Infrastructure.Services uses Wheaterbit.Client.Abstractions, so a change to Wheaterbit.Client.Abstractions can break Weather.Infrastructure.Services, while a change to Weather.Infrastructure.Services can't break Wheaterbit.Client.Abstractions.
- Position
- Below the diagonal: Weather.Infrastructure.Services uses a module listed above it, which is the healthy direction.
31→22 Weather.Infrastructure.Services uses Weather.Core.Abstractions✕
- Connections
- 1 pair of types, where a type in Weather.Infrastructure.Services uses a type in Weather.Core.Abstractions.
- The types involved
Weather.Infrastructure.Services.WeatherService→Weather.Core.Abstractions.IWeatherService
- Direction
- Weather.Infrastructure.Services uses Weather.Core.Abstractions, so a change to Weather.Core.Abstractions can break Weather.Infrastructure.Services, while a change to Weather.Infrastructure.Services can't break Weather.Core.Abstractions.
- Position
- Below the diagonal: Weather.Infrastructure.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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 9 | High / Critical |
| A07:2025 — Authentication Failures | 5 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with GetFavoritesHandler.cs, WeatherbitHttpClient.cs, WeatherBuilder.cs; 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; Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with GetFavoritesHandler.cs, WeatherbitHttpClient.cs, WeatherBuilder.cs. | +5.4 pts | Low | Knowledge Freshness |
| 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.0 pts | Medium | Security & performance tooling |
| Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down. | +5.0 pts | Medium | Outbound HTTP resilience |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +2.1 pts | Low | Knowledge Freshness |
| Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically. | +3.0 pts | Medium | Deployment & Rollback |
| 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. | +2.7 pts | Medium | Architecture documentation |
| Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability. | +2.1 pts | Medium | Observability |
| Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (4). | +0.7 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| src/Weather.Domain/Extensions/EnumerableExtensions.cs | 8.2 | Near-clean | Explicit Debt: Dead code: ForEach |
| src/Weather.Domain/Weather.Domain.csproj | 8.5 | Near-clean | Coupling: Off the main sequence: Weather.Domain |
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 72 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 — 72 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, 32 of 45 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.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- 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 (3 contributor(s) across 160 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 2 hold 0.5% 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/Weather.API/Middlewares/ExceptionMiddleware.cs` 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 REDACTED (REDACTED). docker build failed (exit 1) — 9 | WORKDIR 10 | >>> COPY ["REDACTED", "Weather.API/"] 11 | RUN dotnet restore "REDACTED" 12 | COPY . . -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref a4d3489d-5a90-4a49-806f-e98acb1bd6e7::2exrsbcfl3cd6182id90v1cd2: "/Weather.API/Weather.API.csproj": not found; runtime evidence skipped.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P8 Schema migrations — 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. Every other migration runner — DbUp, FluentMigrator, Evolve, Flyway, Liquibase, RoundhousE, a hand-rolled versioned-SQL runner — is invisible to the detector, so an absence here is our blind spot rather than a missing migration strategy in the repository. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool other than EF Core migrations, naming it lets us teach the detector to read it.
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.
- 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.
- 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.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D5 · Coupling
13 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 Weather.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 7 classes have LCOM4 above 3.
D9 · Test Distribution
54 test methods: 54 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 4 mock references across 54 tests.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 101 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 22 direct `PackageReference`(s), and 96 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
0 deducted debt markers + 1 dead symbols across 1441 LoC in the .NET projects (0.1/KLoC) → score 9.9.
What to do
- Resolve the 1 Dead code finding(s) in Explicit Debt — start with EnumerableExtensions.cs. — One of this dimension's main actionable groups (1 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
13 projects, 95 source files, 2747 hand-written lines of code (1441 production / 1306 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), plus 245 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 16 inter-project edges (build failed).
What to do
- Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 6 unit(s).
D26 · Project Cohesion
0 of 13 projects flagged as possibly oversized/incoherent.
D27 · Navigability
94 % of calls cross a namespace and 17 % 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)
4 finding(s): 0 critical, 4 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (4). — One of this dimension's main actionable groups (4 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)
9 finding(s): 0 critical, 6 high, 3 medium, 0 low. 4 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 1 file(s) — `src/Weather.API/Middlewares/ExceptionMiddleware.cs` (lines 7–8, line 56) — 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 1 of those file(s) — `src/Weather.API/Middlewares/ExceptionMiddleware.cs` — 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 1 high, 2 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 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
5 of 5 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Weather.Core/Queries/GetFavoritesHandler.cs. Counted over 5 of the 68 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 5 Orphaned file finding(s) in Knowledge Freshness — start with GetFavoritesHandler.cs, WeatherbitHttpClient.cs, WeatherBuilder.cs. — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
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
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 5 of 5 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.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- 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 1184 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
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- 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.
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P7 · Outbound HTTP resilience
- The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.
What to do
- Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.
PF3 · Async & latency hygiene
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. — src/Weather.API/Program.cs:8
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
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 23/24 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, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. — src/Weather.API/Middlewares/ExceptionMiddleware.cs:28
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
- ~0.1 `!` suppressions per 1k syntax nodes — 1 suppression(s) across the 7076 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
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 95% | Adequate — gated by D18 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 90% | Exemplary | Solid. |
| Maturity | 66% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 79% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 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.
Not evidenced — 2 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 45 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- 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 — docker build failed (exit 1) — 9 | WORKDIR 10 | >>> COPY ["REDACTED", "Weather.API/"] 11 | RUN dotnet restore "REDACTED" 12 | COPY . . -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref a4d3489d-5a90-4a49-806f-e98acb1bd6e7::2exrsbcfl3cd6182id90v1cd2: "/Weather.API/Weather.API.csproj": not found; 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.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (358 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (1,441 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. 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 (0 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 1 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
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 CQRS handler(s))
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P8 Schema migrations — EF Core is used, but the schema-migration mechanism could not be identified — this check only recognises EF migrations, so any other migration runner reads as an absence. Our limit, not a verdict on this repository.
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dead code: ForEach src/Weather.Domain/Extensions/EnumerableExtensions.cs:5
- Build failed
- Off the main sequence: Weather.Domain src/Weather.Domain/Weather.Domain.csproj:1
- Outbound HTTP without resilience
- Async method without CancellationToken: WriteResponseAsync src/Weather.API/Middlewares/ExceptionMiddleware.cs:28
Minor — 16 finding(s)
- Orphaned file src/Weather.Core/Queries/GetFavoritesHandler.cs:1
- Orphaned file src/Wheaterbit.Client/WeatherbitHttpClient.cs:1
- Orphaned file src/Weather.API/EndpointBuilders/WeatherBuilder.cs:1
- Orphaned file src/Weather.Core/Queries/GetCurrentWeatherHandler.cs:1
- Orphaned file src/Weather.Infrastructure/Services/WeatherService.cs:1
- No security response headers detected
- No security response headers detected src/Weather.API/Program.cs:8
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- No ADRs
- No SAST REDACTED:9
- Dependabot does not watch github-actions REDACTED:2
- No rollback/health safety
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 4 finding(s)
- Mock framework: Moq
- Mock framework: 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-19492942c1ae4506a679161336b6ce4d/history.json --exit-code 0 --source . | 4 | 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-19492942c1ae4506a679161336b6ce4d/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/Weather.API.slnx package --vulnerable --include-transitive --format json | 2 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | 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 1 file(s) — `src/Weather.API/Middlewares/ExceptionMiddleware.cs` — 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-326b7726359944668611cc11fbafd774 | 0 | artifacts/raw/osv-scanner.json |