Executive summary
rommsen/EventSourcing-DIY falls short of our standard for production because 28 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 34 out of 100 and is rated Weak, and it has no critical findings.
Maturity, at 12, is the weakest lens and counts most in the score. The best first steps are recording design decisions and having someone learn and document the 28 files no active contributor knows, each worth about 19 points. Raising Maturity to 70 would lift the score to about 49.
Most of the 63 serious findings are in Code Health.
The product code is 4,864 lines, about €5,700 to rebuild.
If Maturity rose from 12 to 70, the lowest score rated Strong, the score would rise from 34 to about 49.
Fixed since the last survey: 1 finding
- Documentation accuracy · No README
Rebuild cost: about €5,700 · Estimate
| Cost to rebuild | €1,900 to €9,500, for 31 to 100 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.7 at a score of 34. 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: 4,864 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Agent | 2 Application.PersistentReadmodels | 3 Application.QueryHandlers | 4 Domain | 5 Domain.Behaviour | 6 Infrastructure | 7 Application.API | 8 Application.InMemoryReadmodels | 9 Infrastructure.CommandHandler | 10 Infrastructure.EventSourced | 11 Infrastructure.EventStorage.FileStorage | 12 Infrastructure.EventStorage.InMemoryStorage | 13 Infrastructure.EventStorage.PostgresStorage | 14 Infrastructure.EventStore | 15 Step2.Program | 16 Step3.Program | 17 Step4.Program | 18 Step6.Application.API | 19 Step6.Application.Readmodels | 20 Step6.Infrastructure | 21 Step6.Infrastructure.EventStore | 22 Step7.Application.API | 23 Step7.Application.Readmodels | 24 Step7.Infrastructure | 25 Step7.Infrastructure.EventStore | 26 Step8.Application.API | 27 Step8.Application.Readmodels | 28 Step8.Infrastructure | 29 Step9.Application.API | 30 Step9.Application.InMemoryReadmodels | 31 Step9.Infrastructure | 32 Step7.Infrastructure.CommandHandler | 33 Step8.Infrastructure.CommandHandler | 34 Step8.Infrastructure.EventStorage.FileStorage | 35 Step8.Infrastructure.EventStorage.InMemory | 36 Step8.Infrastructure.EventStore | 37 Step9.Infrastructure.CommandHandler | 38 Step9.Infrastructure.EventStorage.FileStorage | 39 Step9.Infrastructure.EventStorage.InMemory | 40 Step9.Infrastructure.EventStore |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Agent | ||||||||||||||||||||||||||||||||||||||||
| 2 Application.PersistentReadmodels | ||||||||||||||||||||||||||||||||||||||||
| 3 Application.QueryHandlers | ||||||||||||||||||||||||||||||||||||||||
| 4 Domain | ||||||||||||||||||||||||||||||||||||||||
| 5 Domain.Behaviour | ||||||||||||||||||||||||||||||||||||||||
| 6 Infrastructure | ||||||||||||||||||||||||||||||||||||||||
| 7 Application.API | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 Application.InMemoryReadmodels | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Infrastructure.CommandHandler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 Infrastructure.EventSourced | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Infrastructure.EventStorage.FileStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Infrastructure.EventStorage.InMemoryStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Infrastructure.EventStorage.PostgresStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Infrastructure.EventStore | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Step2.Program | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Step3.Program | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Step4.Program | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Step6.Application.API | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 Step6.Application.Readmodels | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Step6.Infrastructure | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 Step6.Infrastructure.EventStore | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Step7.Application.API | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Step7.Application.Readmodels | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Step7.Infrastructure | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 Step7.Infrastructure.EventStore | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Step8.Application.API | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 Step8.Application.Readmodels | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Step8.Infrastructure | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 Step9.Application.API | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 Step9.Application.InMemoryReadmodels | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 Step9.Infrastructure | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 Step7.Infrastructure.CommandHandler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Step8.Infrastructure.CommandHandler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 Step8.Infrastructure.EventStorage.FileStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 Step8.Infrastructure.EventStorage.InMemory | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 Step8.Infrastructure.EventStore | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Step9.Infrastructure.CommandHandler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 Step9.Infrastructure.EventStorage.FileStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 Step9.Infrastructure.EventStorage.InMemory | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 Step9.Infrastructure.EventStore | 1 | 1 |
7→4 Application.API uses Domain✕
- Connections
- 2 pairs of types, where a type in Application.API uses a type in Domain.
- The types involved
Application.API.Query→Domain.FlavourApplication.API.Query→Domain.Truck
- Direction
- Application.API uses Domain, so a change to Domain can break Application.API, while a change to Application.API can't break Domain.
- Position
- Below the diagonal: Application.API uses a module listed above it, which is the healthy direction.
8→6 Application.InMemoryReadmodels uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Application.InMemoryReadmodels uses a type in Infrastructure.
- The types involved
Application.InMemoryReadmodels.InMemoryReadmodels→Infrastructure.ReadModel
- Direction
- Application.InMemoryReadmodels uses Infrastructure, so a change to Infrastructure can break Application.InMemoryReadmodels, while a change to Application.InMemoryReadmodels can't break Infrastructure.
- Position
- Below the diagonal: Application.InMemoryReadmodels uses a module listed above it, which is the healthy direction.
9→5 Infrastructure.CommandHandler uses Domain.Behaviour✕
- Connections
- 1 pair of types, where a type in Infrastructure.CommandHandler uses a type in Domain.Behaviour.
- The types involved
Infrastructure.CommandHandler.CommandHandler→Domain.Behaviour.Behaviour
- Direction
- Infrastructure.CommandHandler uses Domain.Behaviour, so a change to Domain.Behaviour can break Infrastructure.CommandHandler, while a change to Infrastructure.CommandHandler can't break Domain.Behaviour.
- Position
- Below the diagonal: Infrastructure.CommandHandler uses a module listed above it, which is the healthy direction.
9→6 Infrastructure.CommandHandler uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Infrastructure.CommandHandler uses a type in Infrastructure.
- The types involved
Infrastructure.CommandHandler.CommandHandler→Infrastructure.EventStore
- Direction
- Infrastructure.CommandHandler uses Infrastructure, so a change to Infrastructure can break Infrastructure.CommandHandler, while a change to Infrastructure.CommandHandler can't break Infrastructure.
- Position
- Below the diagonal: Infrastructure.CommandHandler uses a module listed above it, which is the healthy direction.
10→6 Infrastructure.EventSourced uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Infrastructure.EventSourced uses a type in Infrastructure.
- The types involved
Infrastructure.EventSourced.EventSourcedConfig→Infrastructure.QueryHandler
- Direction
- Infrastructure.EventSourced uses Infrastructure, so a change to Infrastructure can break Infrastructure.EventSourced, while a change to Infrastructure.EventSourced can't break Infrastructure.
- Position
- Below the diagonal: Infrastructure.EventSourced uses a module listed above it, which is the healthy direction.
11→6 Infrastructure.EventStorage.FileStorage uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Infrastructure.EventStorage.FileStorage uses a type in Infrastructure.
- The types involved
Infrastructure.EventStorage.FileStorage.FileStorage→Infrastructure.EventStorage
- Direction
- Infrastructure.EventStorage.FileStorage uses Infrastructure, so a change to Infrastructure can break Infrastructure.EventStorage.FileStorage, while a change to Infrastructure.EventStorage.FileStorage can't break Infrastructure.
- Position
- Below the diagonal: Infrastructure.EventStorage.FileStorage uses a module listed above it, which is the healthy direction.
12→6 Infrastructure.EventStorage.InMemoryStorage uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Infrastructure.EventStorage.InMemoryStorage uses a type in Infrastructure.
- The types involved
Infrastructure.EventStorage.InMemoryStorage.InMemoryStorage→Infrastructure.EventStorage
- Direction
- Infrastructure.EventStorage.InMemoryStorage uses Infrastructure, so a change to Infrastructure can break Infrastructure.EventStorage.InMemoryStorage, while a change to Infrastructure.EventStorage.InMemoryStorage can't break Infrastructure.
- Position
- Below the diagonal: Infrastructure.EventStorage.InMemoryStorage uses a module listed above it, which is the healthy direction.
13→6 Infrastructure.EventStorage.PostgresStorage uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Infrastructure.EventStorage.PostgresStorage uses a type in Infrastructure.
- The types involved
Infrastructure.EventStorage.PostgresStorage.PostgresStorage→Infrastructure.EventStorage
- Direction
- Infrastructure.EventStorage.PostgresStorage uses Infrastructure, so a change to Infrastructure can break Infrastructure.EventStorage.PostgresStorage, while a change to Infrastructure.EventStorage.PostgresStorage can't break Infrastructure.
- Position
- Below the diagonal: Infrastructure.EventStorage.PostgresStorage uses a module listed above it, which is the healthy direction.
14→6 Infrastructure.EventStore uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Infrastructure.EventStore uses a type in Infrastructure.
- The types involved
Infrastructure.EventStore.EventStore→Infrastructure.EventStorage
- Direction
- Infrastructure.EventStore uses Infrastructure, so a change to Infrastructure can break Infrastructure.EventStore, while a change to Infrastructure.EventStore can't break Infrastructure.
- Position
- Below the diagonal: Infrastructure.EventStore uses a module listed above it, which is the healthy direction.
15→4 Step2.Program uses Domain✕
- Connections
- 1 pair of types, where a type in Step2.Program uses a type in Domain.
- The types involved
Step2.Program.Msg→Domain.Flavour
- Direction
- Step2.Program uses Domain, so a change to Domain can break Step2.Program, while a change to Step2.Program can't break Domain.
- Position
- Below the diagonal: Step2.Program uses a module listed above it, which is the healthy direction.
16→4 Step3.Program uses Domain✕
- Connections
- 1 pair of types, where a type in Step3.Program uses a type in Domain.
- The types involved
Step3.Program.Msg→Domain.Flavour
- Direction
- Step3.Program uses Domain, so a change to Domain can break Step3.Program, while a change to Step3.Program can't break Domain.
- Position
- Below the diagonal: Step3.Program uses a module listed above it, which is the healthy direction.
17→4 Step4.Program uses Domain✕
- Connections
- 1 pair of types, where a type in Step4.Program uses a type in Domain.
- The types involved
Step4.Program.Msg→Domain.Flavour
- Direction
- Step4.Program uses Domain, so a change to Domain can break Step4.Program, while a change to Step4.Program can't break Domain.
- Position
- Below the diagonal: Step4.Program uses a module listed above it, which is the healthy direction.
18→4 Step6.Application.API uses Domain✕
- Connections
- 2 pairs of types, where a type in Step6.Application.API uses a type in Domain.
- The types involved
Step6.Application.API.Query→Domain.FlavourStep6.Application.API.Query→Domain.Truck
- Direction
- Step6.Application.API uses Domain, so a change to Domain can break Step6.Application.API, while a change to Step6.Application.API can't break Domain.
- Position
- Below the diagonal: Step6.Application.API uses a module listed above it, which is the healthy direction.
19→6 Step6.Application.Readmodels uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Step6.Application.Readmodels uses a type in Infrastructure.
- The types involved
Step6.Application.Readmodels.Msg→Infrastructure.EventEnvelope
- Direction
- Step6.Application.Readmodels uses Infrastructure, so a change to Infrastructure can break Step6.Application.Readmodels, while a change to Step6.Application.Readmodels can't break Infrastructure.
- Position
- Below the diagonal: Step6.Application.Readmodels uses a module listed above it, which is the healthy direction.
20→6 Step6.Infrastructure uses Infrastructure✕
- Connections
- 2 pairs of types, where a type in Step6.Infrastructure uses a type in Infrastructure.
- The types involved
Step6.Infrastructure.ReadModel→Infrastructure.EventListenerStep6.Infrastructure.ReadModel→Infrastructure.QueryHandler
- Direction
- Step6.Infrastructure uses Infrastructure, so a change to Infrastructure can break Step6.Infrastructure, while a change to Step6.Infrastructure can't break Infrastructure.
- Position
- Below the diagonal: Step6.Infrastructure uses a module listed above it, which is the healthy direction.
21→6 Step6.Infrastructure.EventStore uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Step6.Infrastructure.EventStore uses a type in Infrastructure.
- The types involved
Step6.Infrastructure.EventStore.Msg→Infrastructure.EventListener
- Direction
- Step6.Infrastructure.EventStore uses Infrastructure, so a change to Infrastructure can break Step6.Infrastructure.EventStore, while a change to Step6.Infrastructure.EventStore can't break Infrastructure.
- Position
- Below the diagonal: Step6.Infrastructure.EventStore uses a module listed above it, which is the healthy direction.
22→4 Step7.Application.API uses Domain✕
- Connections
- 2 pairs of types, where a type in Step7.Application.API uses a type in Domain.
- The types involved
Step7.Application.API.Query→Domain.FlavourStep7.Application.API.Query→Domain.Truck
- Direction
- Step7.Application.API uses Domain, so a change to Domain can break Step7.Application.API, while a change to Step7.Application.API can't break Domain.
- Position
- Below the diagonal: Step7.Application.API uses a module listed above it, which is the healthy direction.
23→6 Step7.Application.Readmodels uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Step7.Application.Readmodels uses a type in Infrastructure.
- The types involved
Step7.Application.Readmodels.Msg→Infrastructure.EventEnvelope
- Direction
- Step7.Application.Readmodels uses Infrastructure, so a change to Infrastructure can break Step7.Application.Readmodels, while a change to Step7.Application.Readmodels can't break Infrastructure.
- Position
- Below the diagonal: Step7.Application.Readmodels uses a module listed above it, which is the healthy direction.
24→6 Step7.Infrastructure uses Infrastructure✕
- Connections
- 2 pairs of types, where a type in Step7.Infrastructure uses a type in Infrastructure.
- The types involved
Step7.Infrastructure.ReadModel→Infrastructure.EventListenerStep7.Infrastructure.ReadModel→Infrastructure.QueryHandler
- Direction
- Step7.Infrastructure uses Infrastructure, so a change to Infrastructure can break Step7.Infrastructure, while a change to Step7.Infrastructure can't break Infrastructure.
- Position
- Below the diagonal: Step7.Infrastructure uses a module listed above it, which is the healthy direction.
25→6 Step7.Infrastructure.EventStore uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Step7.Infrastructure.EventStore uses a type in Infrastructure.
- The types involved
Step7.Infrastructure.EventStore.Msg→Infrastructure.EventListener
- Direction
- Step7.Infrastructure.EventStore uses Infrastructure, so a change to Infrastructure can break Step7.Infrastructure.EventStore, while a change to Step7.Infrastructure.EventStore can't break Infrastructure.
- Position
- Below the diagonal: Step7.Infrastructure.EventStore uses a module listed above it, which is the healthy direction.
26→4 Step8.Application.API uses Domain✕
- Connections
- 2 pairs of types, where a type in Step8.Application.API uses a type in Domain.
- The types involved
Step8.Application.API.Query→Domain.FlavourStep8.Application.API.Query→Domain.Truck
- Direction
- Step8.Application.API uses Domain, so a change to Domain can break Step8.Application.API, while a change to Step8.Application.API can't break Domain.
- Position
- Below the diagonal: Step8.Application.API uses a module listed above it, which is the healthy direction.
27→6 Step8.Application.Readmodels uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Step8.Application.Readmodels uses a type in Infrastructure.
- The types involved
Step8.Application.Readmodels.Msg→Infrastructure.EventEnvelope
- Direction
- Step8.Application.Readmodels uses Infrastructure, so a change to Infrastructure can break Step8.Application.Readmodels, while a change to Step8.Application.Readmodels can't break Infrastructure.
- Position
- Below the diagonal: Step8.Application.Readmodels uses a module listed above it, which is the healthy direction.
28→6 Step8.Infrastructure uses Infrastructure✕
- Connections
- 2 pairs of types, where a type in Step8.Infrastructure uses a type in Infrastructure.
- The types involved
Step8.Infrastructure.ReadModel→Infrastructure.EventListenerStep8.Infrastructure.ReadModel→Infrastructure.QueryHandler
- Direction
- Step8.Infrastructure uses Infrastructure, so a change to Infrastructure can break Step8.Infrastructure, while a change to Step8.Infrastructure can't break Infrastructure.
- Position
- Below the diagonal: Step8.Infrastructure uses a module listed above it, which is the healthy direction.
29→4 Step9.Application.API uses Domain✕
- Connections
- 2 pairs of types, where a type in Step9.Application.API uses a type in Domain.
- The types involved
Step9.Application.API.Query→Domain.FlavourStep9.Application.API.Query→Domain.Truck
- Direction
- Step9.Application.API uses Domain, so a change to Domain can break Step9.Application.API, while a change to Step9.Application.API can't break Domain.
- Position
- Below the diagonal: Step9.Application.API uses a module listed above it, which is the healthy direction.
30→6 Step9.Application.InMemoryReadmodels uses Infrastructure✕
- Connections
- 2 pairs of types, where a type in Step9.Application.InMemoryReadmodels uses a type in Infrastructure.
- The types involved
Step9.Application.InMemoryReadmodels.InMemoryReadmodels→Infrastructure.ReadModelStep9.Application.InMemoryReadmodels.Msg→Infrastructure.EventEnvelope
- Direction
- Step9.Application.InMemoryReadmodels uses Infrastructure, so a change to Infrastructure can break Step9.Application.InMemoryReadmodels, while a change to Step9.Application.InMemoryReadmodels can't break Infrastructure.
- Position
- Below the diagonal: Step9.Application.InMemoryReadmodels uses a module listed above it, which is the healthy direction.
31→6 Step9.Infrastructure uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Step9.Infrastructure uses a type in Infrastructure.
- The types involved
Step9.Infrastructure.ReadModel→Infrastructure.EventListener
- Direction
- Step9.Infrastructure uses Infrastructure, so a change to Infrastructure can break Step9.Infrastructure, while a change to Step9.Infrastructure can't break Infrastructure.
- Position
- Below the diagonal: Step9.Infrastructure uses a module listed above it, which is the healthy direction.
32→5 Step7.Infrastructure.CommandHandler uses Domain.Behaviour✕
- Connections
- 1 pair of types, where a type in Step7.Infrastructure.CommandHandler uses a type in Domain.Behaviour.
- The types involved
Step7.Infrastructure.CommandHandler.CommandHandler→Domain.Behaviour.Behaviour
- Direction
- Step7.Infrastructure.CommandHandler uses Domain.Behaviour, so a change to Domain.Behaviour can break Step7.Infrastructure.CommandHandler, while a change to Step7.Infrastructure.CommandHandler can't break Domain.Behaviour.
- Position
- Below the diagonal: Step7.Infrastructure.CommandHandler uses a module listed above it, which is the healthy direction.
32→24 Step7.Infrastructure.CommandHandler uses Step7.Infrastructure✕
- Connections
- 1 pair of types, where a type in Step7.Infrastructure.CommandHandler uses a type in Step7.Infrastructure.
- The types involved
Step7.Infrastructure.CommandHandler.CommandHandler→Step7.Infrastructure.EventStore
- Direction
- Step7.Infrastructure.CommandHandler uses Step7.Infrastructure, so a change to Step7.Infrastructure can break Step7.Infrastructure.CommandHandler, while a change to Step7.Infrastructure.CommandHandler can't break Step7.Infrastructure.
- Position
- Below the diagonal: Step7.Infrastructure.CommandHandler uses a module listed above it, which is the healthy direction.
33→5 Step8.Infrastructure.CommandHandler uses Domain.Behaviour✕
- Connections
- 1 pair of types, where a type in Step8.Infrastructure.CommandHandler uses a type in Domain.Behaviour.
- The types involved
Step8.Infrastructure.CommandHandler.CommandHandler→Domain.Behaviour.Behaviour
- Direction
- Step8.Infrastructure.CommandHandler uses Domain.Behaviour, so a change to Domain.Behaviour can break Step8.Infrastructure.CommandHandler, while a change to Step8.Infrastructure.CommandHandler can't break Domain.Behaviour.
- Position
- Below the diagonal: Step8.Infrastructure.CommandHandler uses a module listed above it, which is the healthy direction.
33→28 Step8.Infrastructure.CommandHandler uses Step8.Infrastructure✕
- Connections
- 1 pair of types, where a type in Step8.Infrastructure.CommandHandler uses a type in Step8.Infrastructure.
- The types involved
Step8.Infrastructure.CommandHandler.CommandHandler→Step8.Infrastructure.EventStore
- Direction
- Step8.Infrastructure.CommandHandler uses Step8.Infrastructure, so a change to Step8.Infrastructure can break Step8.Infrastructure.CommandHandler, while a change to Step8.Infrastructure.CommandHandler can't break Step8.Infrastructure.
- Position
- Below the diagonal: Step8.Infrastructure.CommandHandler uses a module listed above it, which is the healthy direction.
34→28 Step8.Infrastructure.EventStorage.FileStorage uses Step8.Infrastructure✕
- Connections
- 1 pair of types, where a type in Step8.Infrastructure.EventStorage.FileStorage uses a type in Step8.Infrastructure.
- The types involved
Step8.Infrastructure.EventStorage.FileStorage.FileStorage→Step8.Infrastructure.EventStorage
- Direction
- Step8.Infrastructure.EventStorage.FileStorage uses Step8.Infrastructure, so a change to Step8.Infrastructure can break Step8.Infrastructure.EventStorage.FileStorage, while a change to Step8.Infrastructure.EventStorage.FileStorage can't break Step8.Infrastructure.
- Position
- Below the diagonal: Step8.Infrastructure.EventStorage.FileStorage uses a module listed above it, which is the healthy direction.
35→28 Step8.Infrastructure.EventStorage.InMemory uses Step8.Infrastructure✕
- Connections
- 1 pair of types, where a type in Step8.Infrastructure.EventStorage.InMemory uses a type in Step8.Infrastructure.
- The types involved
Step8.Infrastructure.EventStorage.InMemory.InMemory→Step8.Infrastructure.EventStorage
- Direction
- Step8.Infrastructure.EventStorage.InMemory uses Step8.Infrastructure, so a change to Step8.Infrastructure can break Step8.Infrastructure.EventStorage.InMemory, while a change to Step8.Infrastructure.EventStorage.InMemory can't break Step8.Infrastructure.
- Position
- Below the diagonal: Step8.Infrastructure.EventStorage.InMemory uses a module listed above it, which is the healthy direction.
36→6 Step8.Infrastructure.EventStore uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Step8.Infrastructure.EventStore uses a type in Infrastructure.
- The types involved
Step8.Infrastructure.EventStore.Msg→Infrastructure.EventListener
- Direction
- Step8.Infrastructure.EventStore uses Infrastructure, so a change to Infrastructure can break Step8.Infrastructure.EventStore, while a change to Step8.Infrastructure.EventStore can't break Infrastructure.
- Position
- Below the diagonal: Step8.Infrastructure.EventStore uses a module listed above it, which is the healthy direction.
36→28 Step8.Infrastructure.EventStore uses Step8.Infrastructure✕
- Connections
- 1 pair of types, where a type in Step8.Infrastructure.EventStore uses a type in Step8.Infrastructure.
- The types involved
Step8.Infrastructure.EventStore.EventStore→Step8.Infrastructure.EventStorage
- Direction
- Step8.Infrastructure.EventStore uses Step8.Infrastructure, so a change to Step8.Infrastructure can break Step8.Infrastructure.EventStore, while a change to Step8.Infrastructure.EventStore can't break Step8.Infrastructure.
- Position
- Below the diagonal: Step8.Infrastructure.EventStore uses a module listed above it, which is the healthy direction.
37→5 Step9.Infrastructure.CommandHandler uses Domain.Behaviour✕
- Connections
- 1 pair of types, where a type in Step9.Infrastructure.CommandHandler uses a type in Domain.Behaviour.
- The types involved
Step9.Infrastructure.CommandHandler.CommandHandler→Domain.Behaviour.Behaviour
- Direction
- Step9.Infrastructure.CommandHandler uses Domain.Behaviour, so a change to Domain.Behaviour can break Step9.Infrastructure.CommandHandler, while a change to Step9.Infrastructure.CommandHandler can't break Domain.Behaviour.
- Position
- Below the diagonal: Step9.Infrastructure.CommandHandler uses a module listed above it, which is the healthy direction.
37→31 Step9.Infrastructure.CommandHandler uses Step9.Infrastructure✕
- Connections
- 1 pair of types, where a type in Step9.Infrastructure.CommandHandler uses a type in Step9.Infrastructure.
- The types involved
Step9.Infrastructure.CommandHandler.CommandHandler→Step9.Infrastructure.EventStore
- Direction
- Step9.Infrastructure.CommandHandler uses Step9.Infrastructure, so a change to Step9.Infrastructure can break Step9.Infrastructure.CommandHandler, while a change to Step9.Infrastructure.CommandHandler can't break Step9.Infrastructure.
- Position
- Below the diagonal: Step9.Infrastructure.CommandHandler uses a module listed above it, which is the healthy direction.
38→31 Step9.Infrastructure.EventStorage.FileStorage uses Step9.Infrastructure✕
- Connections
- 1 pair of types, where a type in Step9.Infrastructure.EventStorage.FileStorage uses a type in Step9.Infrastructure.
- The types involved
Step9.Infrastructure.EventStorage.FileStorage.FileStorage→Step9.Infrastructure.EventStorage
- Direction
- Step9.Infrastructure.EventStorage.FileStorage uses Step9.Infrastructure, so a change to Step9.Infrastructure can break Step9.Infrastructure.EventStorage.FileStorage, while a change to Step9.Infrastructure.EventStorage.FileStorage can't break Step9.Infrastructure.
- Position
- Below the diagonal: Step9.Infrastructure.EventStorage.FileStorage uses a module listed above it, which is the healthy direction.
39→31 Step9.Infrastructure.EventStorage.InMemory uses Step9.Infrastructure✕
- Connections
- 1 pair of types, where a type in Step9.Infrastructure.EventStorage.InMemory uses a type in Step9.Infrastructure.
- The types involved
Step9.Infrastructure.EventStorage.InMemory.InMemory→Step9.Infrastructure.EventStorage
- Direction
- Step9.Infrastructure.EventStorage.InMemory uses Step9.Infrastructure, so a change to Step9.Infrastructure can break Step9.Infrastructure.EventStorage.InMemory, while a change to Step9.Infrastructure.EventStorage.InMemory can't break Step9.Infrastructure.
- Position
- Below the diagonal: Step9.Infrastructure.EventStorage.InMemory uses a module listed above it, which is the healthy direction.
40→6 Step9.Infrastructure.EventStore uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Step9.Infrastructure.EventStore uses a type in Infrastructure.
- The types involved
Step9.Infrastructure.EventStore.Msg→Infrastructure.EventListener
- Direction
- Step9.Infrastructure.EventStore uses Infrastructure, so a change to Infrastructure can break Step9.Infrastructure.EventStore, while a change to Step9.Infrastructure.EventStore can't break Infrastructure.
- Position
- Below the diagonal: Step9.Infrastructure.EventStore uses a module listed above it, which is the healthy direction.
40→31 Step9.Infrastructure.EventStore uses Step9.Infrastructure✕
- Connections
- 1 pair of types, where a type in Step9.Infrastructure.EventStore uses a type in Step9.Infrastructure.
- The types involved
Step9.Infrastructure.EventStore.EventStore→Step9.Infrastructure.EventStorage
- Direction
- Step9.Infrastructure.EventStore uses Step9.Infrastructure, so a change to Step9.Infrastructure can break Step9.Infrastructure.EventStore, while a change to Step9.Infrastructure.EventStore can't break Step9.Infrastructure.
- Position
- Below the diagonal: Step9.Infrastructure.EventStore 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 — Performance
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 28 Orphaned file finding(s) in Knowledge Freshness — start with Program.fs (4), Domain.fs (2), Infrastructure9.fs; Add a root README: what the system is, how to build/run it, and a map of the projects.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +18.8 pts | Low | ADR Quality |
| Resolve the 28 Orphaned file finding(s) in Knowledge Freshness — start with Program.fs (4), Domain.fs (2), Infrastructure9.fs. | +18.8 pts | Medium | Knowledge Freshness |
| Add a root README: what the system is, how to build/run it, and a map of the projects. | +5.9 pts | Medium | Documentation (README) |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.9 pts | Medium | Architecture documentation |
| Resolve the 3 End-of-life runtime finding(s) in Platform End-of-Life — start with Talk.fsproj, Videos.fsproj, EventSourced.fsproj. | +2.4 pts | Low | Platform End-of-Life |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +4.1 pts | Medium | CI/CD gates |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +4.1 pts | Medium | Observability |
| Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. | +1.6 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| EventSourced/Domain.fs | 7.1 | Mixed | Code Duplication: Near-duplicate member family (5 members, 65 shared lines) |
| Videos/Step6/Infrastructure6.fs | 7.1 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| Talk/Step2/Domain2.fs | 7.1 | Mixed | Code Duplication: Duplicated block (33 lines × 3) |
| Videos/Step8/Infrastructure8.fs | 7.2 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
| Talk/Step1/Program1.fs | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| Videos/Step6/Application6.fs | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| Videos/Step7/Infrastructure7.fs | 7.4 | Mixed | Code Duplication: Duplicated block (68 lines × 2) |
| Videos/Step3.fs | 7.4 | Mixed | Code Duplication: Duplicated block (48–59 lines × 3) |
| Talk/Step1/Infrastructure1.fs | 7.4 | Mixed | Code Duplication: Duplicated block (26 lines × 3) |
| Talk/Step2/Tests2.fs | 7.8 | Mixed | Code Duplication: Members sharing a duplicated core (5 members, 50+ identical tokens) |
| Videos/Step6/Tests6.fs | 7.8 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| Talk/Step2/Program2.fs | 7.8 | Mixed | Code Duplication: Duplicated block (75 lines × 2) |
| Talk/Step4/Infrastructure4.fs | 7.8 | Mixed | Code Duplication: Duplicated block (74 lines × 2) |
| Videos/Step1.fs | 7.8 | Mixed | Code Duplication: Duplicated block (46–47 lines × 2) |
| EventSourced/Infrastructure/EventStorage/FileStorage.fs | 7.8 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| Talk/Talk.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp2.0 |
| Videos/Videos.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp2.1 |
| EventSourced/EventSourced.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp2.2 |
| Talk/Step3/Domain3.fs | 8.5 | Near-clean | Code Duplication: Near-duplicate member family (5 members, 37 shared lines) |
| Talk/Step2/Infrastructure2.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (40 lines × 4) |
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 30 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.6, the weighted average across measured dimensions.
What we checked — 30 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, 89 of 99 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.fs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.fs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D6 Cohesion (LCOM4) — 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. 5 of 5 class(es) with two or more methods were found, but the language model this pass loaded exposed none of their method bodies, so which method touches which field could not be seen.
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.fs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, 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. You can widen what we reach: optional: 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 — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.fs) and it is .NET, which this analyzer re-runs through `dotnet test` — but the .NET workspace loaded none of this repository's test projects, so there was no suite to re-run and flakiness couldn't be assessed. The repository commits a project or solution file, so the load had something to read and still produced nothing: the remedy is the restore, the SDK band or the target resolution, not a new runner. Not scored — this is a gap on our side, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: .paket/Paket.Restore.targets(118,5): error MSB3073: The command "mono --runtime=v4.0.30319 ".paket/paket.exe" restore" exited with code 127. [….
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's projects are MSBuild/NuGet projects, whose package licenses are exactly what this dimension reads, but no license could be resolved for them (the .NET license collector did not run, or restore failed). A gap in the analysis run, NOT a finding that the repository's licenses are compliant.
- D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (21 line(s) across the 90-day window), but no complexity could be computed for .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- 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 83 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- AX2 Stateful singletons — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection singletons in C#, Spring/JSR-330/CDI singletons in Java and Kotlin, module state in Python request handlers, handler state in Go and Swift, Play controllers, Cask routes, Scalatra servlets, Finatra controllers, Akka/Pekko HTTP routes and JSR-330 singletons in Scala, Rails, Sinatra, Grape, Roda and Hanami handlers and Rack apps in Ruby, and module state in F# request handlers (Giraffe, Saturn, Falco, Oxpecker and Suave handlers and ASP.NET Core controllers) only, and this repository's product is written in F#, which was left unread, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for Talk/Talk.fsproj, Videos/Videos.fsproj, EventSourced/EventSourced.fsproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
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
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- 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.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (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.
- 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.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
50 duplicated block group(s) detected. A further 7 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 4 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with Program1.fs, Application6.fs, Infrastructure6.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Duplicated block (12 lines × 3) finding(s) in Code Duplication — start with Infrastructure1.fs, Program1.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with List.fs, Step1.fs. — One of this dimension's main actionable groups (2 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
3 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
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).
D26 · Project Cohesion
0 of 3 build units (MSBuild) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D34 · Knowledge Freshness
28 of 28 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Videos/Step9/Infrastructure9.fs. Counted over 28 of the 60 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 28 Orphaned file finding(s) in Knowledge Freshness — start with Program.fs (4), Domain.fs (2), Infrastructure9.fs. — One of this dimension's main actionable groups (28 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.
D44 · Platform End-of-Life
3 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 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.
What to do
- Resolve the 3 End-of-life runtime finding(s) in Platform End-of-Life — start with Talk.fsproj, Videos.fsproj, EventSourced.fsproj. — One of this dimension's main actionable groups (3 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
- No README at the repository root — newcomers have no entry point.
What to do
- Add a root README: what the system is, how to build/run it, and a map of the projects.
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
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
- `paket.dependencies` 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`. — paket.dependencies:3
What to do
- Run what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Checked 2 of 12 | Solid. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 12% | Critical — gated by D34, M1, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 17% | Critical — gated by P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73% | Checked 3 of 9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 94 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.
- AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .fs exposed no member bodies
- D10 Test Quality — ~77 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .NET workspace loaded no .fs test project
- D12 Dependency Hygiene — Dependency hygiene not measured
- D14 License Compliance — Package licences not resolved for an MSBuild/NuGet repository
- D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D2 Cognitive Complexity — cognitive complexity not measured — .fs exposed no member bodies
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D6 Cohesion (LCOM4) — cohesion (LCOM4) not measured — the code model exposed no member bodies
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: there are no current-state documents to check (a README, docs/, a contributor or build guide). Whether a README exists is M1's question.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Serious — 63 finding(s)
- Members sharing a duplicated core (4 members, 50+ identical tokens) Talk/Step1/Program1.fs:1
- Members sharing a duplicated core (4 members, 50+ identical tokens) Videos/Step6/Application6.fs:1
- Members sharing a duplicated core (4 members, 50+ identical tokens) Videos/Step6/Infrastructure6.fs:1
- Members sharing a duplicated core (4 members, 50+ identical tokens) Videos/Step6/Tests6.fs:1
- End-of-life runtime: .NET netcoreapp2.0 Talk/Talk.fsproj:5
- End-of-life runtime: .NET netcoreapp2.1 Videos/Videos.fsproj:4
- End-of-life runtime: .NET netcoreapp2.2 EventSourced/EventSourced.fsproj:4
- Duplicated block (12 lines × 3) Talk/Step1/Infrastructure1.fs:12
- Duplicated block (12 lines × 3) Talk/Step1/Program1.fs:14
- Duplicated block (12 lines × 2) EventSourced/Utils/List.fs:5
- Duplicated block (12 lines × 2) Videos/Step1.fs:76
- Duplicated block (11 lines × 2) EventSourced/Infrastructure/EventStorage/FileStorage.fs:22
- Duplicated block (11 lines × 2) Talk/Step4/Infrastructure4.fs:3
- Near-duplicate member family (5 members, 65 shared lines) EventSourced/Domain.fs:1
- Near-duplicate member family (5 members, 37 shared lines) Talk/Step3/Domain3.fs:1
- Members sharing a duplicated core (5 members, 50+ identical tokens) Talk/Step2/Tests2.fs:1
- Duplicated block (87–88 lines × 3) Videos/Step6/Application6.fs:50
- Duplicated block (82 lines × 4) Videos/Step6/Tests6.fs:5
- Duplicated block (75 lines × 2) Talk/Step2/Program2.fs:9
- Duplicated block (74 lines × 2) Talk/Step4/Infrastructure4.fs:26
- Duplicated block (68 lines × 2) Videos/Step7/Infrastructure7.fs:107
- Duplicated block (48–59 lines × 3) Videos/Step3.fs:55
- Duplicated block (52 lines × 5) EventSourced/Domain.fs:47
- Duplicated block (46–47 lines × 2) Videos/Step1.fs:13
- Duplicated block (46 lines × 3) Videos/Step6/Infrastructure6.fs:164
- Duplicated block (41–43 lines × 5) Talk/Step2/Tests2.fs:9
- Duplicated block (40 lines × 4) Talk/Step2/Infrastructure2.fs:28
- Duplicated block (34 lines × 3) Videos/Step3.fs:119
- Duplicated block (33 lines × 3) Talk/Step2/Domain2.fs:53
- Duplicated block (30 lines × 2) EventSourced/Infrastructure/Agent.fs:8
- Duplicated block (28–29 lines × 2) Talk/Step2/Domain2.fs:29
- Duplicated block (15–28 lines × 2) Videos/Step6/Infrastructure6.fs:111
- Duplicated block (26 lines × 3) Talk/Step1/Infrastructure1.fs:28
- Duplicated block (24–26 lines × 2) Videos/Step6/Infrastructure6.fs:71
- Duplicated block (24–25 lines × 4) Videos/Step2.fs:45
- Duplicated block (22–24 lines × 2) Videos/Step3.fs:159
- Duplicated block (23 lines × 3) Videos/Step7/Domain7.fs:94
- Duplicated block (19–21 lines × 6) Talk/Step2/Domain2.fs:44
- Duplicated block (21 lines × 3) Talk/Step2/Domain2.fs:18
- Duplicated block (20 lines × 3) Videos/Step6/Infrastructure6.fs:3
- Duplicated block (18–19 lines × 10) Talk/Step2/Domain2.fs:50
- Duplicated block (17–19 lines × 3) Videos/Step6/Infrastructure6.fs:28
- Duplicated block (17 lines × 8) EventSourced/Domain.fs:64
- Duplicated block (16 lines × 7) Talk/Step1/Infrastructure1.fs:25
- Duplicated block (13–16 lines × 6) Talk/Step2/Domain2.fs:72
- Duplicated block (16 lines × 3) Talk/Step1/Program1.fs:36
- Duplicated block (15 lines × 11) EventSourced/Domain.fs:85
- Duplicated block (14–15 lines × 5) Talk/Step1/Domain1.fs:18
- Duplicated block (15 lines × 3) Videos/Step7/Infrastructure7.fs:130
- Duplicated block (15 lines × 2) EventSourced/Infrastructure/QueryHandler.fs:5
- Duplicated block (14 lines × 10) EventSourced/Domain.fs:62
- Duplicated block (13–14 lines × 4) Videos/Step6/Application6.fs:58
- Duplicated block (14 lines × 2) Videos/Step8/Infrastructure8.fs:96
- Duplicated block (13 lines × 2) Videos/Step8/Infrastructure8.fs:69
- Duplicated block (12 lines × 5) EventSourced/Domain.fs:126
- Duplicated block (11–12 lines × 2) Videos/Step8/Infrastructure8.fs:113
- Duplicated block (10 lines × 3) Talk/Step2/Program2.fs:17
- Duplicated block (9–10 lines × 2) Videos/Step8/Infrastructure8.fs:178
- Duplicated block (7–9 lines × 2) Videos/Step7/Infrastructure7.fs:56
- Duplicated block (6 lines × 3) EventSourced/Infrastructure/EventStorage/FileStorage.fs:23
- No solution README
- No CI pipeline
- No structured logging
Minor — 36 finding(s)
- Orphaned file Videos/Step9/Infrastructure9.fs:1
- Orphaned file Videos/Step8/Infrastructure8.fs:1
- Orphaned file Videos/Step5.fs:1
- Orphaned file EventSourced/Program.fs:1
- Orphaned file Videos/Step4.fs:1
- Orphaned file EventSourced/Application.fs:1
- Orphaned file Videos/Step6/Infrastructure6.fs:1
- Orphaned file Videos/Step7/Infrastructure7.fs:1
- Orphaned file EventSourced/Infrastructure/Types.fs:1
- Orphaned file Videos/Step3.fs:1
- Orphaned file Talk/Step4/Program4.fs:1
- Orphaned file Brainstorming/Domain.fs:1
- Orphaned file Talk/Program.fs:1
- Orphaned file Videos/Step7/Application7.fs:1
- Orphaned file Videos/Step6/Application6.fs:1
- Orphaned file Videos/Program.fs:1
- Orphaned file EventSourced/Domain.fs:1
- Orphaned file Videos/Step9/Application9.fs:1
- Orphaned file Brainstorming/Program.fs:1
- Orphaned file Videos/Step8/Application8.fs:1
- Orphaned file Videos/Step2.fs:1
- Orphaned file Videos/Step9/Domain9.fs:1
- Orphaned file Videos/Step8/Domain8.fs:1
- Orphaned file Videos/Step7/Domain7.fs:1
- Orphaned file Talk/Step2/Program2.fs:1
- No ADRs found
- Dormant codebase
- No ADRs
- No architecture diagram/doc
- No src/ separation
- No SAST
- No dependency-update automation paket.dependencies:3
- No changelog
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a3f7da5db24d49c7a66de3f508c19d0b/history.json --exit-code 0 --source . | 0 | 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-a3f7da5db24d49c7a66de3f508c19d0b/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |