Executive summary
serde-fs/Serde.FS falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 56 out of 100 and is rated Adequate, and all ten of its critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 38, is the weakest lens and counts most in the score. The best first step is logging through a logging library, worth about 8 points. Recording design decisions comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 70.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks.
The product code is 8,053 lines, about €13,000 to rebuild.
If Production Readiness rose from 38 to 70, the lowest score rated Strong, the score would rise from 56 to about 70.
New since the last survey: 2 findings
- Code Duplication · Edited copy of a member (6 corresponding lines) src/Serde.FS/SerdeCodecException.fs
- Code Duplication · Edited copy of a member (5 corresponding lines) src/Serde.FS/SerdeCodecNotFoundException.fs
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,200 to €21,000, for 70 to 221 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. 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: 8,053 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 FSharp.SourceDjinn | 2 FSharp.SourceDjinn.TypeModel.Types | 3 SampleRpc.Shared | 4 Serde.FS.AspNet | 5 Serde.FS.Json.Codec | 6 FSharp.SourceDjinn.AstParser | 7 FSharp.SourceDjinn.CallTypeArgExtractor | 8 FSharp.SourceDjinn.EntryPointDetector | 9 FSharp.SourceDjinn.EntryPointEmitter | 10 FSharp.SourceDjinn.TypeKindExtractor | 11 FSharp.SourceDjinn.TypeModel.Types.TypeInfoModule | 12 SampleRpc.Server.InventoryApi | 13 Serde.FS | 14 Serde.FS.AspNet.RpcEndpointCore | 15 Serde.FS.AspNet.RpcEndpointExtensions | 16 Serde.FS.Json.Codec.CodecRegistryModule | 17 Serde.FS.Json.Codec.CodecResolver | 18 Serde.FS.Json.Codec.CollectionCodecs | 19 Serde.FS.Json.Codec.CollectionCodecs.ArrayCodecFactory | 20 Serde.FS.Json.Codec.CollectionCodecs.ListCodecFactory | 21 Serde.FS.Json.Codec.CollectionCodecs.MapCodecFactory | 22 Serde.FS.Json.Codec.CollectionCodecs.OptionCodecFactory | 23 Serde.FS.SourceGen | 24 Serde.FS.AspNet.Helpers | 25 Serde.FS.Fable.SourceGen.FableClientEmitter | 26 Serde.FS.Json | 27 Serde.FS.Json.SourceGen.JsonCodeEmitterImpl | 28 Serde.FS.SerdeMetadataBuilder | 29 Serde.FS.SourceGen.CollectionDiscovery | 30 Serde.FS.SourceGen.CollectionTypes | 31 Serde.FS.SourceGen.DiscoveryRoots | 32 Serde.FS.SourceGen.FieldTypeResolver | 33 Serde.FS.SourceGen.GenericDiscovery | 34 Serde.FS.SourceGen.NestedTypeValidator | 35 Serde.FS.SourceGen.OptionDiscovery | 36 Serde.FS.SourceGen.RootGenericDiagnostics | 37 Serde.FS.SourceGen.RpcApiDiscovery | 38 Serde.FS.SourceGen.SerdeAstParser | 39 Serde.FS.SourceGen.TupleDiscovery | 40 Serde.FS.Json.SerdeJson |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 FSharp.SourceDjinn | ||||||||||||||||||||||||||||||||||||||||
| 2 FSharp.SourceDjinn.TypeModel.Types | ||||||||||||||||||||||||||||||||||||||||
| 3 SampleRpc.Shared | ||||||||||||||||||||||||||||||||||||||||
| 4 Serde.FS.AspNet | ||||||||||||||||||||||||||||||||||||||||
| 5 Serde.FS.Json.Codec | ||||||||||||||||||||||||||||||||||||||||
| 6 FSharp.SourceDjinn.AstParser | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 FSharp.SourceDjinn.CallTypeArgExtractor | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 FSharp.SourceDjinn.EntryPointDetector | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 FSharp.SourceDjinn.EntryPointEmitter | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 FSharp.SourceDjinn.TypeKindExtractor | 7 | |||||||||||||||||||||||||||||||||||||||
| 11 FSharp.SourceDjinn.TypeModel.Types.TypeInfoModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 SampleRpc.Server.InventoryApi | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 Serde.FS | 5 | |||||||||||||||||||||||||||||||||||||||
| 14 Serde.FS.AspNet.RpcEndpointCore | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Serde.FS.AspNet.RpcEndpointExtensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Serde.FS.Json.Codec.CodecRegistryModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 Serde.FS.Json.Codec.CodecResolver | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 Serde.FS.Json.Codec.CollectionCodecs | 3 | |||||||||||||||||||||||||||||||||||||||
| 19 Serde.FS.Json.Codec.CollectionCodecs.ArrayCodecFactory | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 Serde.FS.Json.Codec.CollectionCodecs.ListCodecFactory | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 Serde.FS.Json.Codec.CollectionCodecs.MapCodecFactory | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 Serde.FS.Json.Codec.CollectionCodecs.OptionCodecFactory | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Serde.FS.SourceGen | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Serde.FS.AspNet.Helpers | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Serde.FS.Fable.SourceGen.FableClientEmitter | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 Serde.FS.Json | 3 | |||||||||||||||||||||||||||||||||||||||
| 27 Serde.FS.Json.SourceGen.JsonCodeEmitterImpl | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 Serde.FS.SerdeMetadataBuilder | 5 | 5 | ||||||||||||||||||||||||||||||||||||||
| 29 Serde.FS.SourceGen.CollectionDiscovery | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Serde.FS.SourceGen.CollectionTypes | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 Serde.FS.SourceGen.DiscoveryRoots | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Serde.FS.SourceGen.FieldTypeResolver | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Serde.FS.SourceGen.GenericDiscovery | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 Serde.FS.SourceGen.NestedTypeValidator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 Serde.FS.SourceGen.OptionDiscovery | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Serde.FS.SourceGen.RootGenericDiagnostics | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Serde.FS.SourceGen.RpcApiDiscovery | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 38 Serde.FS.SourceGen.SerdeAstParser | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 Serde.FS.SourceGen.TupleDiscovery | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 Serde.FS.Json.SerdeJson | 1 | 1 |
6→2 FSharp.SourceDjinn.AstParser uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in FSharp.SourceDjinn.AstParser uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
FSharp.SourceDjinn.AstParser.AstParser→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- FSharp.SourceDjinn.AstParser uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break FSharp.SourceDjinn.AstParser, while a change to FSharp.SourceDjinn.AstParser can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: FSharp.SourceDjinn.AstParser uses a module listed above it, which is the healthy direction.
7→2 FSharp.SourceDjinn.CallTypeArgExtractor uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in FSharp.SourceDjinn.CallTypeArgExtractor uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
FSharp.SourceDjinn.CallTypeArgExtractor.CallTypeArgExtractor→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- FSharp.SourceDjinn.CallTypeArgExtractor uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break FSharp.SourceDjinn.CallTypeArgExtractor, while a change to FSharp.SourceDjinn.CallTypeArgExtractor can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: FSharp.SourceDjinn.CallTypeArgExtractor uses a module listed above it, which is the healthy direction.
8→1 FSharp.SourceDjinn.EntryPointDetector uses FSharp.SourceDjinn✕
- Connections
- 1 pair of types, where a type in FSharp.SourceDjinn.EntryPointDetector uses a type in FSharp.SourceDjinn.
- The types involved
FSharp.SourceDjinn.EntryPointDetector.EntryPointDetector→FSharp.SourceDjinn.EntryPointInfo
- Direction
- FSharp.SourceDjinn.EntryPointDetector uses FSharp.SourceDjinn, so a change to FSharp.SourceDjinn can break FSharp.SourceDjinn.EntryPointDetector, while a change to FSharp.SourceDjinn.EntryPointDetector can't break FSharp.SourceDjinn.
- Position
- Below the diagonal: FSharp.SourceDjinn.EntryPointDetector uses a module listed above it, which is the healthy direction.
9→1 FSharp.SourceDjinn.EntryPointEmitter uses FSharp.SourceDjinn✕
- Connections
- 1 pair of types, where a type in FSharp.SourceDjinn.EntryPointEmitter uses a type in FSharp.SourceDjinn.
- The types involved
FSharp.SourceDjinn.EntryPointEmitter.EntryPointEmitter→FSharp.SourceDjinn.EntryPointInfo
- Direction
- FSharp.SourceDjinn.EntryPointEmitter uses FSharp.SourceDjinn, so a change to FSharp.SourceDjinn can break FSharp.SourceDjinn.EntryPointEmitter, while a change to FSharp.SourceDjinn.EntryPointEmitter can't break FSharp.SourceDjinn.
- Position
- Below the diagonal: FSharp.SourceDjinn.EntryPointEmitter uses a module listed above it, which is the healthy direction.
10→2 FSharp.SourceDjinn.TypeKindExtractor uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 7 pairs of types, where a type in FSharp.SourceDjinn.TypeKindExtractor uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
FSharp.SourceDjinn.TypeKindExtractor.TypeKindExtractor→FSharp.SourceDjinn.TypeModel.Types.AttributeInfoFSharp.SourceDjinn.TypeKindExtractor.TypeKindExtractor→FSharp.SourceDjinn.TypeModel.Types.EnumCaseFSharp.SourceDjinn.TypeKindExtractor.TypeKindExtractor→FSharp.SourceDjinn.TypeModel.Types.FieldInfoFSharp.SourceDjinn.TypeKindExtractor.TypeKindExtractor→FSharp.SourceDjinn.TypeModel.Types.GenericParameterInfoFSharp.SourceDjinn.TypeKindExtractor.TypeKindExtractor→FSharp.SourceDjinn.TypeModel.Types.PrimitiveKindFSharp.SourceDjinn.TypeKindExtractor.TypeKindExtractor→FSharp.SourceDjinn.TypeModel.Types.TypeInfoFSharp.SourceDjinn.TypeKindExtractor.TypeKindExtractor→FSharp.SourceDjinn.TypeModel.Types.UnionCase
- Direction
- FSharp.SourceDjinn.TypeKindExtractor uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break FSharp.SourceDjinn.TypeKindExtractor, while a change to FSharp.SourceDjinn.TypeKindExtractor can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: FSharp.SourceDjinn.TypeKindExtractor uses a module listed above it, which is the healthy direction.
11→2 FSharp.SourceDjinn.TypeModel.Types.TypeInfoModule uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 2 pairs of types, where a type in FSharp.SourceDjinn.TypeModel.Types.TypeInfoModule uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
FSharp.SourceDjinn.TypeModel.Types.TypeInfoModule.TypeInfoModule→FSharp.SourceDjinn.TypeModel.Types.FieldInfoFSharp.SourceDjinn.TypeModel.Types.TypeInfoModule.TypeInfoModule→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- FSharp.SourceDjinn.TypeModel.Types.TypeInfoModule uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break FSharp.SourceDjinn.TypeModel.Types.TypeInfoModule, while a change to FSharp.SourceDjinn.TypeModel.Types.TypeInfoModule can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: FSharp.SourceDjinn.TypeModel.Types.TypeInfoModule uses a module listed above it, which is the healthy direction.
12→3 SampleRpc.Server.InventoryApi uses SampleRpc.Shared✕
- Connections
- 2 pairs of types, where a type in SampleRpc.Server.InventoryApi uses a type in SampleRpc.Shared.
- The types involved
SampleRpc.Server.InventoryApi.IStockRepository→SampleRpc.Shared.ProductIdSampleRpc.Server.InventoryApi.IStockRepository→SampleRpc.Shared.StockLevel
- Direction
- SampleRpc.Server.InventoryApi uses SampleRpc.Shared, so a change to SampleRpc.Shared can break SampleRpc.Server.InventoryApi, while a change to SampleRpc.Server.InventoryApi can't break SampleRpc.Shared.
- Position
- Below the diagonal: SampleRpc.Server.InventoryApi uses a module listed above it, which is the healthy direction.
13→2 Serde.FS uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 5 pairs of types, where a type in Serde.FS uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.RpcMethodInfo→FSharp.SourceDjinn.TypeModel.Types.TypeInfoSerde.FS.SerdeFieldInfo→FSharp.SourceDjinn.TypeModel.Types.TypeInfoSerde.FS.SerdeGenericContext→FSharp.SourceDjinn.TypeModel.Types.GenericParameterInfoSerde.FS.SerdeGenericContext→FSharp.SourceDjinn.TypeModel.Types.TypeInfoSerde.FS.SerdeTypeInfo→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS, while a change to Serde.FS can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS uses a module listed above it, which is the healthy direction.
14→4 Serde.FS.AspNet.RpcEndpointCore uses Serde.FS.AspNet✕
- Connections
- 1 pair of types, where a type in Serde.FS.AspNet.RpcEndpointCore uses a type in Serde.FS.AspNet.
- The types involved
Serde.FS.AspNet.RpcEndpointCore.RpcEndpointCore→Serde.FS.AspNet.RpcApiBuilder
- Direction
- Serde.FS.AspNet.RpcEndpointCore uses Serde.FS.AspNet, so a change to Serde.FS.AspNet can break Serde.FS.AspNet.RpcEndpointCore, while a change to Serde.FS.AspNet.RpcEndpointCore can't break Serde.FS.AspNet.
- Position
- Below the diagonal: Serde.FS.AspNet.RpcEndpointCore uses a module listed above it, which is the healthy direction.
15→4 Serde.FS.AspNet.RpcEndpointExtensions uses Serde.FS.AspNet✕
- Connections
- 1 pair of types, where a type in Serde.FS.AspNet.RpcEndpointExtensions uses a type in Serde.FS.AspNet.
- The types involved
Serde.FS.AspNet.RpcEndpointExtensions.RpcEndpointExtensions→Serde.FS.AspNet.RpcApiBuilder
- Direction
- Serde.FS.AspNet.RpcEndpointExtensions uses Serde.FS.AspNet, so a change to Serde.FS.AspNet can break Serde.FS.AspNet.RpcEndpointExtensions, while a change to Serde.FS.AspNet.RpcEndpointExtensions can't break Serde.FS.AspNet.
- Position
- Below the diagonal: Serde.FS.AspNet.RpcEndpointExtensions uses a module listed above it, which is the healthy direction.
16→5 Serde.FS.Json.Codec.CodecRegistryModule uses Serde.FS.Json.Codec✕
- Connections
- 2 pairs of types, where a type in Serde.FS.Json.Codec.CodecRegistryModule uses a type in Serde.FS.Json.Codec.
- The types involved
Serde.FS.Json.Codec.CodecRegistryModule.CodecRegistryModule→Serde.FS.Json.Codec.CodecRegistrySerde.FS.Json.Codec.CodecRegistryModule.CodecRegistryModule→Serde.FS.Json.Codec.IJsonCodec
- Direction
- Serde.FS.Json.Codec.CodecRegistryModule uses Serde.FS.Json.Codec, so a change to Serde.FS.Json.Codec can break Serde.FS.Json.Codec.CodecRegistryModule, while a change to Serde.FS.Json.Codec.CodecRegistryModule can't break Serde.FS.Json.Codec.
- Position
- Below the diagonal: Serde.FS.Json.Codec.CodecRegistryModule uses a module listed above it, which is the healthy direction.
17→5 Serde.FS.Json.Codec.CodecResolver uses Serde.FS.Json.Codec✕
- Connections
- 2 pairs of types, where a type in Serde.FS.Json.Codec.CodecResolver uses a type in Serde.FS.Json.Codec.
- The types involved
Serde.FS.Json.Codec.CodecResolver.CodecResolver→Serde.FS.Json.Codec.CodecRegistrySerde.FS.Json.Codec.CodecResolver.CodecResolver→Serde.FS.Json.Codec.IJsonCodec
- Direction
- Serde.FS.Json.Codec.CodecResolver uses Serde.FS.Json.Codec, so a change to Serde.FS.Json.Codec can break Serde.FS.Json.Codec.CodecResolver, while a change to Serde.FS.Json.Codec.CodecResolver can't break Serde.FS.Json.Codec.
- Position
- Below the diagonal: Serde.FS.Json.Codec.CodecResolver uses a module listed above it, which is the healthy direction.
18→5 Serde.FS.Json.Codec.CollectionCodecs uses Serde.FS.Json.Codec✕
- Connections
- 3 pairs of types, where a type in Serde.FS.Json.Codec.CollectionCodecs uses a type in Serde.FS.Json.Codec.
- The types involved
Serde.FS.Json.Codec.CollectionCodecs.CollectionCodecs→Serde.FS.Json.Codec.CodecRegistrySerde.FS.Json.Codec.CollectionCodecs.CollectionCodecs→Serde.FS.Json.Codec.IJsonCodecSerde.FS.Json.Codec.CollectionCodecs.CollectionCodecs→Serde.FS.Json.Codec.IJsonCodec`1
- Direction
- Serde.FS.Json.Codec.CollectionCodecs uses Serde.FS.Json.Codec, so a change to Serde.FS.Json.Codec can break Serde.FS.Json.Codec.CollectionCodecs, while a change to Serde.FS.Json.Codec.CollectionCodecs can't break Serde.FS.Json.Codec.
- Position
- Below the diagonal: Serde.FS.Json.Codec.CollectionCodecs uses a module listed above it, which is the healthy direction.
19→5 Serde.FS.Json.Codec.CollectionCodecs.ArrayCodecFactory uses Serde.FS.Json.Codec✕
- Connections
- 2 pairs of types, where a type in Serde.FS.Json.Codec.CollectionCodecs.ArrayCodecFactory uses a type in Serde.FS.Json.Codec.
- The types involved
Serde.FS.Json.Codec.CollectionCodecs.ArrayCodecFactory.ArrayCodecFactory→Serde.FS.Json.Codec.CodecRegistrySerde.FS.Json.Codec.CollectionCodecs.ArrayCodecFactory.ArrayCodecFactory→Serde.FS.Json.Codec.IJsonCodec
- Direction
- Serde.FS.Json.Codec.CollectionCodecs.ArrayCodecFactory uses Serde.FS.Json.Codec, so a change to Serde.FS.Json.Codec can break Serde.FS.Json.Codec.CollectionCodecs.ArrayCodecFactory, while a change to Serde.FS.Json.Codec.CollectionCodecs.ArrayCodecFactory can't break Serde.FS.Json.Codec.
- Position
- Below the diagonal: Serde.FS.Json.Codec.CollectionCodecs.ArrayCodecFactory uses a module listed above it, which is the healthy direction.
20→5 Serde.FS.Json.Codec.CollectionCodecs.ListCodecFactory uses Serde.FS.Json.Codec✕
- Connections
- 2 pairs of types, where a type in Serde.FS.Json.Codec.CollectionCodecs.ListCodecFactory uses a type in Serde.FS.Json.Codec.
- The types involved
Serde.FS.Json.Codec.CollectionCodecs.ListCodecFactory.ListCodecFactory→Serde.FS.Json.Codec.CodecRegistrySerde.FS.Json.Codec.CollectionCodecs.ListCodecFactory.ListCodecFactory→Serde.FS.Json.Codec.IJsonCodec
- Direction
- Serde.FS.Json.Codec.CollectionCodecs.ListCodecFactory uses Serde.FS.Json.Codec, so a change to Serde.FS.Json.Codec can break Serde.FS.Json.Codec.CollectionCodecs.ListCodecFactory, while a change to Serde.FS.Json.Codec.CollectionCodecs.ListCodecFactory can't break Serde.FS.Json.Codec.
- Position
- Below the diagonal: Serde.FS.Json.Codec.CollectionCodecs.ListCodecFactory uses a module listed above it, which is the healthy direction.
21→5 Serde.FS.Json.Codec.CollectionCodecs.MapCodecFactory uses Serde.FS.Json.Codec✕
- Connections
- 2 pairs of types, where a type in Serde.FS.Json.Codec.CollectionCodecs.MapCodecFactory uses a type in Serde.FS.Json.Codec.
- The types involved
Serde.FS.Json.Codec.CollectionCodecs.MapCodecFactory.MapCodecFactory→Serde.FS.Json.Codec.CodecRegistrySerde.FS.Json.Codec.CollectionCodecs.MapCodecFactory.MapCodecFactory→Serde.FS.Json.Codec.IJsonCodec
- Direction
- Serde.FS.Json.Codec.CollectionCodecs.MapCodecFactory uses Serde.FS.Json.Codec, so a change to Serde.FS.Json.Codec can break Serde.FS.Json.Codec.CollectionCodecs.MapCodecFactory, while a change to Serde.FS.Json.Codec.CollectionCodecs.MapCodecFactory can't break Serde.FS.Json.Codec.
- Position
- Below the diagonal: Serde.FS.Json.Codec.CollectionCodecs.MapCodecFactory uses a module listed above it, which is the healthy direction.
22→5 Serde.FS.Json.Codec.CollectionCodecs.OptionCodecFactory uses Serde.FS.Json.Codec✕
- Connections
- 2 pairs of types, where a type in Serde.FS.Json.Codec.CollectionCodecs.OptionCodecFactory uses a type in Serde.FS.Json.Codec.
- The types involved
Serde.FS.Json.Codec.CollectionCodecs.OptionCodecFactory.OptionCodecFactory→Serde.FS.Json.Codec.CodecRegistrySerde.FS.Json.Codec.CollectionCodecs.OptionCodecFactory.OptionCodecFactory→Serde.FS.Json.Codec.IJsonCodec
- Direction
- Serde.FS.Json.Codec.CollectionCodecs.OptionCodecFactory uses Serde.FS.Json.Codec, so a change to Serde.FS.Json.Codec can break Serde.FS.Json.Codec.CollectionCodecs.OptionCodecFactory, while a change to Serde.FS.Json.Codec.CollectionCodecs.OptionCodecFactory can't break Serde.FS.Json.Codec.
- Position
- Below the diagonal: Serde.FS.Json.Codec.CollectionCodecs.OptionCodecFactory uses a module listed above it, which is the healthy direction.
23→2 Serde.FS.SourceGen uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.CollectionShape→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen, while a change to Serde.FS.SourceGen can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen uses a module listed above it, which is the healthy direction.
24→13 Serde.FS.AspNet.Helpers uses Serde.FS✕
- Connections
- 1 pair of types, where a type in Serde.FS.AspNet.Helpers uses a type in Serde.FS.
- The types involved
Serde.FS.AspNet.Helpers.Helpers→Serde.FS.UrlCase
- Direction
- Serde.FS.AspNet.Helpers uses Serde.FS, so a change to Serde.FS can break Serde.FS.AspNet.Helpers, while a change to Serde.FS.AspNet.Helpers can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.AspNet.Helpers uses a module listed above it, which is the healthy direction.
25→2 Serde.FS.Fable.SourceGen.FableClientEmitter uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 2 pairs of types, where a type in Serde.FS.Fable.SourceGen.FableClientEmitter uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.Fable.SourceGen.FableClientEmitter.FableClientEmitter→FSharp.SourceDjinn.TypeModel.Types.PrimitiveKindSerde.FS.Fable.SourceGen.FableClientEmitter.FableClientEmitter→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.Fable.SourceGen.FableClientEmitter uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.Fable.SourceGen.FableClientEmitter, while a change to Serde.FS.Fable.SourceGen.FableClientEmitter can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.Fable.SourceGen.FableClientEmitter uses a module listed above it, which is the healthy direction.
25→13 Serde.FS.Fable.SourceGen.FableClientEmitter uses Serde.FS✕
- Connections
- 2 pairs of types, where a type in Serde.FS.Fable.SourceGen.FableClientEmitter uses a type in Serde.FS.
- The types involved
Serde.FS.Fable.SourceGen.FableClientEmitter.FableClientEmitter→Serde.FS.RpcInterfaceInfoSerde.FS.Fable.SourceGen.FableClientEmitter.FableClientEmitter→Serde.FS.SerdeTypeInfo
- Direction
- Serde.FS.Fable.SourceGen.FableClientEmitter uses Serde.FS, so a change to Serde.FS can break Serde.FS.Fable.SourceGen.FableClientEmitter, while a change to Serde.FS.Fable.SourceGen.FableClientEmitter can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.Fable.SourceGen.FableClientEmitter uses a module listed above it, which is the healthy direction.
26→13 Serde.FS.Json uses Serde.FS✕
- Connections
- 3 pairs of types, where a type in Serde.FS.Json uses a type in Serde.FS.
- The types involved
Serde.FS.Json.JsonBackend→Serde.FS.ISerdeBackendSerde.FS.Json.JsonBackend→Serde.FS.ISerdeOptionsSerde.FS.Json.SerdeJsonOptions→Serde.FS.ISerdeOptions
- Direction
- Serde.FS.Json uses Serde.FS, so a change to Serde.FS can break Serde.FS.Json, while a change to Serde.FS.Json can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.Json uses a module listed above it, which is the healthy direction.
27→2 Serde.FS.Json.SourceGen.JsonCodeEmitterImpl uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.Json.SourceGen.JsonCodeEmitterImpl uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.Json.SourceGen.JsonCodeEmitterImpl.JsonCodeEmitterImpl→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.Json.SourceGen.JsonCodeEmitterImpl uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.Json.SourceGen.JsonCodeEmitterImpl, while a change to Serde.FS.Json.SourceGen.JsonCodeEmitterImpl can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.Json.SourceGen.JsonCodeEmitterImpl uses a module listed above it, which is the healthy direction.
27→13 Serde.FS.Json.SourceGen.JsonCodeEmitterImpl uses Serde.FS✕
- Connections
- 2 pairs of types, where a type in Serde.FS.Json.SourceGen.JsonCodeEmitterImpl uses a type in Serde.FS.
- The types involved
Serde.FS.Json.SourceGen.JsonCodeEmitterImpl.JsonCodeEmitterImpl→Serde.FS.SerdeTypeInfoSerde.FS.Json.SourceGen.JsonCodeEmitterImpl.JsonCodeEmitterImpl→Serde.FS.SerdeUnionCaseInfo
- Direction
- Serde.FS.Json.SourceGen.JsonCodeEmitterImpl uses Serde.FS, so a change to Serde.FS can break Serde.FS.Json.SourceGen.JsonCodeEmitterImpl, while a change to Serde.FS.Json.SourceGen.JsonCodeEmitterImpl can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.Json.SourceGen.JsonCodeEmitterImpl uses a module listed above it, which is the healthy direction.
28→2 Serde.FS.SerdeMetadataBuilder uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 5 pairs of types, where a type in Serde.FS.SerdeMetadataBuilder uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SerdeMetadataBuilder.SerdeMetadataBuilder→FSharp.SourceDjinn.TypeModel.Types.AttributeInfoSerde.FS.SerdeMetadataBuilder.SerdeMetadataBuilder→FSharp.SourceDjinn.TypeModel.Types.EnumCaseSerde.FS.SerdeMetadataBuilder.SerdeMetadataBuilder→FSharp.SourceDjinn.TypeModel.Types.FieldInfoSerde.FS.SerdeMetadataBuilder.SerdeMetadataBuilder→FSharp.SourceDjinn.TypeModel.Types.TypeInfoSerde.FS.SerdeMetadataBuilder.SerdeMetadataBuilder→FSharp.SourceDjinn.TypeModel.Types.UnionCase
- Direction
- Serde.FS.SerdeMetadataBuilder uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SerdeMetadataBuilder, while a change to Serde.FS.SerdeMetadataBuilder can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SerdeMetadataBuilder uses a module listed above it, which is the healthy direction.
28→13 Serde.FS.SerdeMetadataBuilder uses Serde.FS✕
- Connections
- 5 pairs of types, where a type in Serde.FS.SerdeMetadataBuilder uses a type in Serde.FS.
- The types involved
Serde.FS.SerdeMetadataBuilder.SerdeMetadataBuilder→Serde.FS.SerdeAttributesSerde.FS.SerdeMetadataBuilder.SerdeMetadataBuilder→Serde.FS.SerdeEnumCaseInfoSerde.FS.SerdeMetadataBuilder.SerdeMetadataBuilder→Serde.FS.SerdeFieldInfoSerde.FS.SerdeMetadataBuilder.SerdeMetadataBuilder→Serde.FS.SerdeTypeInfoSerde.FS.SerdeMetadataBuilder.SerdeMetadataBuilder→Serde.FS.SerdeUnionCaseInfo
- Direction
- Serde.FS.SerdeMetadataBuilder uses Serde.FS, so a change to Serde.FS can break Serde.FS.SerdeMetadataBuilder, while a change to Serde.FS.SerdeMetadataBuilder can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SerdeMetadataBuilder uses a module listed above it, which is the healthy direction.
29→2 Serde.FS.SourceGen.CollectionDiscovery uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.CollectionDiscovery uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.CollectionDiscovery.CollectionDiscovery→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen.CollectionDiscovery uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.CollectionDiscovery, while a change to Serde.FS.SourceGen.CollectionDiscovery can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.CollectionDiscovery uses a module listed above it, which is the healthy direction.
29→13 Serde.FS.SourceGen.CollectionDiscovery uses Serde.FS✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.CollectionDiscovery uses a type in Serde.FS.
- The types involved
Serde.FS.SourceGen.CollectionDiscovery.CollectionDiscovery→Serde.FS.SerdeTypeInfo
- Direction
- Serde.FS.SourceGen.CollectionDiscovery uses Serde.FS, so a change to Serde.FS can break Serde.FS.SourceGen.CollectionDiscovery, while a change to Serde.FS.SourceGen.CollectionDiscovery can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SourceGen.CollectionDiscovery uses a module listed above it, which is the healthy direction.
30→2 Serde.FS.SourceGen.CollectionTypes uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.CollectionTypes uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.CollectionTypes.CollectionTypes→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen.CollectionTypes uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.CollectionTypes, while a change to Serde.FS.SourceGen.CollectionTypes can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.CollectionTypes uses a module listed above it, which is the healthy direction.
30→23 Serde.FS.SourceGen.CollectionTypes uses Serde.FS.SourceGen✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.CollectionTypes uses a type in Serde.FS.SourceGen.
- The types involved
Serde.FS.SourceGen.CollectionTypes.CollectionTypes→Serde.FS.SourceGen.CollectionShape
- Direction
- Serde.FS.SourceGen.CollectionTypes uses Serde.FS.SourceGen, so a change to Serde.FS.SourceGen can break Serde.FS.SourceGen.CollectionTypes, while a change to Serde.FS.SourceGen.CollectionTypes can't break Serde.FS.SourceGen.
- Position
- Below the diagonal: Serde.FS.SourceGen.CollectionTypes uses a module listed above it, which is the healthy direction.
31→2 Serde.FS.SourceGen.DiscoveryRoots uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.DiscoveryRoots uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.DiscoveryRoots.DiscoveryRoots→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen.DiscoveryRoots uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.DiscoveryRoots, while a change to Serde.FS.SourceGen.DiscoveryRoots can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.DiscoveryRoots uses a module listed above it, which is the healthy direction.
31→13 Serde.FS.SourceGen.DiscoveryRoots uses Serde.FS✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.DiscoveryRoots uses a type in Serde.FS.
- The types involved
Serde.FS.SourceGen.DiscoveryRoots.DiscoveryRoots→Serde.FS.SerdeTypeInfo
- Direction
- Serde.FS.SourceGen.DiscoveryRoots uses Serde.FS, so a change to Serde.FS can break Serde.FS.SourceGen.DiscoveryRoots, while a change to Serde.FS.SourceGen.DiscoveryRoots can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SourceGen.DiscoveryRoots uses a module listed above it, which is the healthy direction.
32→2 Serde.FS.SourceGen.FieldTypeResolver uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.FieldTypeResolver uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.FieldTypeResolver.FieldTypeResolver→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen.FieldTypeResolver uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.FieldTypeResolver, while a change to Serde.FS.SourceGen.FieldTypeResolver can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.FieldTypeResolver uses a module listed above it, which is the healthy direction.
32→13 Serde.FS.SourceGen.FieldTypeResolver uses Serde.FS✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.FieldTypeResolver uses a type in Serde.FS.
- The types involved
Serde.FS.SourceGen.FieldTypeResolver.FieldTypeResolver→Serde.FS.SerdeTypeInfo
- Direction
- Serde.FS.SourceGen.FieldTypeResolver uses Serde.FS, so a change to Serde.FS can break Serde.FS.SourceGen.FieldTypeResolver, while a change to Serde.FS.SourceGen.FieldTypeResolver can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SourceGen.FieldTypeResolver uses a module listed above it, which is the healthy direction.
33→2 Serde.FS.SourceGen.GenericDiscovery uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.GenericDiscovery uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.GenericDiscovery.GenericDiscovery→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen.GenericDiscovery uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.GenericDiscovery, while a change to Serde.FS.SourceGen.GenericDiscovery can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.GenericDiscovery uses a module listed above it, which is the healthy direction.
33→13 Serde.FS.SourceGen.GenericDiscovery uses Serde.FS✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.GenericDiscovery uses a type in Serde.FS.
- The types involved
Serde.FS.SourceGen.GenericDiscovery.GenericDiscovery→Serde.FS.SerdeTypeInfo
- Direction
- Serde.FS.SourceGen.GenericDiscovery uses Serde.FS, so a change to Serde.FS can break Serde.FS.SourceGen.GenericDiscovery, while a change to Serde.FS.SourceGen.GenericDiscovery can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SourceGen.GenericDiscovery uses a module listed above it, which is the healthy direction.
34→2 Serde.FS.SourceGen.NestedTypeValidator uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.NestedTypeValidator uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.NestedTypeValidator.NestedTypeValidator→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen.NestedTypeValidator uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.NestedTypeValidator, while a change to Serde.FS.SourceGen.NestedTypeValidator can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.NestedTypeValidator uses a module listed above it, which is the healthy direction.
34→13 Serde.FS.SourceGen.NestedTypeValidator uses Serde.FS✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.NestedTypeValidator uses a type in Serde.FS.
- The types involved
Serde.FS.SourceGen.NestedTypeValidator.NestedTypeValidator→Serde.FS.SerdeTypeInfo
- Direction
- Serde.FS.SourceGen.NestedTypeValidator uses Serde.FS, so a change to Serde.FS can break Serde.FS.SourceGen.NestedTypeValidator, while a change to Serde.FS.SourceGen.NestedTypeValidator can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SourceGen.NestedTypeValidator uses a module listed above it, which is the healthy direction.
35→2 Serde.FS.SourceGen.OptionDiscovery uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.OptionDiscovery uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.OptionDiscovery.OptionDiscovery→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen.OptionDiscovery uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.OptionDiscovery, while a change to Serde.FS.SourceGen.OptionDiscovery can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.OptionDiscovery uses a module listed above it, which is the healthy direction.
35→13 Serde.FS.SourceGen.OptionDiscovery uses Serde.FS✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.OptionDiscovery uses a type in Serde.FS.
- The types involved
Serde.FS.SourceGen.OptionDiscovery.OptionDiscovery→Serde.FS.SerdeTypeInfo
- Direction
- Serde.FS.SourceGen.OptionDiscovery uses Serde.FS, so a change to Serde.FS can break Serde.FS.SourceGen.OptionDiscovery, while a change to Serde.FS.SourceGen.OptionDiscovery can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SourceGen.OptionDiscovery uses a module listed above it, which is the healthy direction.
36→2 Serde.FS.SourceGen.RootGenericDiagnostics uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 2 pairs of types, where a type in Serde.FS.SourceGen.RootGenericDiagnostics uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.RootGenericDiagnostics.Ctx→FSharp.SourceDjinn.TypeModel.Types.TypeInfoSerde.FS.SourceGen.RootGenericDiagnostics.RootGenericDiagnostics→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen.RootGenericDiagnostics uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.RootGenericDiagnostics, while a change to Serde.FS.SourceGen.RootGenericDiagnostics can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.RootGenericDiagnostics uses a module listed above it, which is the healthy direction.
36→13 Serde.FS.SourceGen.RootGenericDiagnostics uses Serde.FS✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.RootGenericDiagnostics uses a type in Serde.FS.
- The types involved
Serde.FS.SourceGen.RootGenericDiagnostics.RootGenericDiagnostics→Serde.FS.SerdeTypeInfo
- Direction
- Serde.FS.SourceGen.RootGenericDiagnostics uses Serde.FS, so a change to Serde.FS can break Serde.FS.SourceGen.RootGenericDiagnostics, while a change to Serde.FS.SourceGen.RootGenericDiagnostics can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SourceGen.RootGenericDiagnostics uses a module listed above it, which is the healthy direction.
37→2 Serde.FS.SourceGen.RpcApiDiscovery uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 4 pairs of types, where a type in Serde.FS.SourceGen.RpcApiDiscovery uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.RpcApiDiscovery.RpcApiCollected→FSharp.SourceDjinn.TypeModel.Types.TypeInfoSerde.FS.SourceGen.RpcApiDiscovery.RpcApiDiscovery→FSharp.SourceDjinn.TypeModel.Types.PrimitiveKindSerde.FS.SourceGen.RpcApiDiscovery.RpcApiDiscovery→FSharp.SourceDjinn.TypeModel.Types.TypeInfoSerde.FS.SourceGen.RpcApiDiscovery.RpcApiDiscovery→FSharp.SourceDjinn.TypeModel.Types.TypeKind
- Direction
- Serde.FS.SourceGen.RpcApiDiscovery uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.RpcApiDiscovery, while a change to Serde.FS.SourceGen.RpcApiDiscovery can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.RpcApiDiscovery uses a module listed above it, which is the healthy direction.
37→13 Serde.FS.SourceGen.RpcApiDiscovery uses Serde.FS✕
- Connections
- 3 pairs of types, where a type in Serde.FS.SourceGen.RpcApiDiscovery uses a type in Serde.FS.
- The types involved
Serde.FS.SourceGen.RpcApiDiscovery.RpcApiCollected→Serde.FS.RpcInterfaceInfoSerde.FS.SourceGen.RpcApiDiscovery.RpcApiDiscovery→Serde.FS.RpcDiscoveryResultSerde.FS.SourceGen.RpcApiDiscovery.RpcApiDiscovery→Serde.FS.RpcMethodInfo
- Direction
- Serde.FS.SourceGen.RpcApiDiscovery uses Serde.FS, so a change to Serde.FS can break Serde.FS.SourceGen.RpcApiDiscovery, while a change to Serde.FS.SourceGen.RpcApiDiscovery can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SourceGen.RpcApiDiscovery uses a module listed above it, which is the healthy direction.
38→2 Serde.FS.SourceGen.SerdeAstParser uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.SerdeAstParser uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.SerdeAstParser.SerdeAstParser→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen.SerdeAstParser uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.SerdeAstParser, while a change to Serde.FS.SourceGen.SerdeAstParser can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.SerdeAstParser uses a module listed above it, which is the healthy direction.
38→13 Serde.FS.SourceGen.SerdeAstParser uses Serde.FS✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.SerdeAstParser uses a type in Serde.FS.
- The types involved
Serde.FS.SourceGen.SerdeAstParser.SerdeAstParser→Serde.FS.SerdeTypeInfo
- Direction
- Serde.FS.SourceGen.SerdeAstParser uses Serde.FS, so a change to Serde.FS can break Serde.FS.SourceGen.SerdeAstParser, while a change to Serde.FS.SourceGen.SerdeAstParser can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SourceGen.SerdeAstParser uses a module listed above it, which is the healthy direction.
39→2 Serde.FS.SourceGen.TupleDiscovery uses FSharp.SourceDjinn.TypeModel.Types✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.TupleDiscovery uses a type in FSharp.SourceDjinn.TypeModel.Types.
- The types involved
Serde.FS.SourceGen.TupleDiscovery.TupleDiscovery→FSharp.SourceDjinn.TypeModel.Types.TypeInfo
- Direction
- Serde.FS.SourceGen.TupleDiscovery uses FSharp.SourceDjinn.TypeModel.Types, so a change to FSharp.SourceDjinn.TypeModel.Types can break Serde.FS.SourceGen.TupleDiscovery, while a change to Serde.FS.SourceGen.TupleDiscovery can't break FSharp.SourceDjinn.TypeModel.Types.
- Position
- Below the diagonal: Serde.FS.SourceGen.TupleDiscovery uses a module listed above it, which is the healthy direction.
39→13 Serde.FS.SourceGen.TupleDiscovery uses Serde.FS✕
- Connections
- 1 pair of types, where a type in Serde.FS.SourceGen.TupleDiscovery uses a type in Serde.FS.
- The types involved
Serde.FS.SourceGen.TupleDiscovery.TupleDiscovery→Serde.FS.SerdeTypeInfo
- Direction
- Serde.FS.SourceGen.TupleDiscovery uses Serde.FS, so a change to Serde.FS can break Serde.FS.SourceGen.TupleDiscovery, while a change to Serde.FS.SourceGen.TupleDiscovery can't break Serde.FS.
- Position
- Below the diagonal: Serde.FS.SourceGen.TupleDiscovery uses a module listed above it, which is the healthy direction.
40→5 Serde.FS.Json.SerdeJson uses Serde.FS.Json.Codec✕
- Connections
- 1 pair of types, where a type in Serde.FS.Json.SerdeJson uses a type in Serde.FS.Json.Codec.
- The types involved
Serde.FS.Json.SerdeJson.SerdeJson→Serde.FS.Json.Codec.JsonValue
- Direction
- Serde.FS.Json.SerdeJson uses Serde.FS.Json.Codec, so a change to Serde.FS.Json.Codec can break Serde.FS.Json.SerdeJson, while a change to Serde.FS.Json.SerdeJson can't break Serde.FS.Json.Codec.
- Position
- Below the diagonal: Serde.FS.Json.SerdeJson uses a module listed above it, which is the healthy direction.
40→26 Serde.FS.Json.SerdeJson uses Serde.FS.Json✕
- Connections
- 1 pair of types, where a type in Serde.FS.Json.SerdeJson uses a type in Serde.FS.Json.
- The types involved
Serde.FS.Json.SerdeJson.SerdeJson→Serde.FS.Json.SerdeJsonOptions
- Direction
- Serde.FS.Json.SerdeJson uses Serde.FS.Json, so a change to Serde.FS.Json can break Serde.FS.Json.SerdeJson, while a change to Serde.FS.Json.SerdeJson can't break Serde.FS.Json.
- Position
- Below the diagonal: Serde.FS.Json.SerdeJson uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 11 | High / Critical |
| A05:2025 — Injection | 7 | High / Critical |
Roadmap
Top priorities: Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Serde.FS.Fable.GeneratorHost.fsproj.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run. | +8.2 pts | Medium | Observability |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Serde.FS.Fable.GeneratorHost.fsproj. | +2.8 pts | Low | ADR Quality |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.2 pts | Medium | Release Hygiene |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.5 pts | Medium | Architecture documentation |
| Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with SerdeGeneratorEngine.generate (cognitive 177), Program.main (cognitive 63). | +1.0 pts | Medium | Cognitive Complexity |
| Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with SerdeGeneratorEngine.generate (cyclomatic 93). | +0.4 pts | Medium | Cyclomatic Complexity |
| Resolve the 3 FileTooLong finding(s) in God Classes — start with JsonCodeEmitter.fs, RpcApiDiscovery.fs, SerdeGeneratorEngine.fs. | +0.7 pts | High | God Classes |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.2 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Serde.FS.SourceGen/RootGenericDiagnostics.fs | 5.9 | Mixed | Cyclomatic Complexity: RootGenericDiagnostics.walkExpr (cyclomatic 33) |
| src/Serde.FS/SerdeCodecException.fs | 7.0 | Mixed | Code Duplication: Edited copy of a member (6 corresponding lines) |
| src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs | 7.0 | Mixed | Cyclomatic Complexity: JsonCodeEmitterImpl.emitUnion (cyclomatic 22) |
| src/Serde.FS.SourceGen/RpcApiDiscovery.fs | 7.0 | Mixed | Cyclomatic Complexity: RpcApiDiscovery.synTypeToTypeInfo (cyclomatic 24) |
| src/Serde.FS.Fable.SourceGen/FableClientEmitter.fs | 7.1 | Mixed | Cyclomatic Complexity: FableClientEmitter.emit (cyclomatic 22) |
| src/FSharp.SourceDjinn/TypeKindExtractor.fs | 7.2 | Mixed | Cyclomatic Complexity: TypeKindExtractor.synTypeToTypeInfo (cyclomatic 23) |
| src/Serde.FS.Json/Codec/SerdeJsonReader.fs | 7.2 | Mixed | Cyclomatic Complexity: SerdeJsonReader.parseValue (cyclomatic 23) |
| src/Serde.FS.Json/Codec/CollectionCodecs.fs | 7.2 | Mixed | Code Duplication: Duplicated block (15–17 lines × 2) |
| src/Serde.FS.SourceGen/SerdeGeneratorEngine.fs | 7.4 | Mixed | Cyclomatic Complexity: SerdeGeneratorEngine.generate (cyclomatic 93) |
| src/FSharp.SourceDjinn/CallTypeArgExtractor.fs | 7.8 | Mixed | Cyclomatic Complexity: CallTypeArgExtractor.walkExpr (cyclomatic 32) |
| src/Serde.FS.Json.GeneratorHost/Program.fs | 7.8 | Mixed | Cyclomatic Complexity: Program.main (cyclomatic 27) |
| src/Serde.FS.Fable.GeneratorHost/Program.fs | 7.8 | Mixed | Cyclomatic Complexity: Program.main (cyclomatic 20) |
| src/Serde.FS.Json/Codec/SerdeJsonWriter.fs | 7.8 | Mixed | Cyclomatic Complexity: SerdeJsonWriter.writeValue (cyclomatic 18) |
| src/Serde.FS.Fable.GeneratorHost/Serde.FS.Fable.GeneratorHost.fsproj | 8.0 | Near-clean | Code Coverage: No test project references Serde.FS.Fable.GeneratorHost |
| src/Serde.FS/SerdeCodecNotFoundException.fs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (5 corresponding lines) |
| src/FSharp.SourceDjinn/EntryPointDetector.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (12 lines × 2) |
| src/Serde.FS.Json/Codec/PrimitiveCodecs.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
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 39 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 39 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, 93 of 102 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
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D15 Churn × Complexity Hotspots — 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. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/Serde.FS.Fable.SourceGen/FableClientEmitter.fs, src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs, src/Serde.FS.SourceGen/RpcApiDiscovery.fs, src/Serde.FS.SourceGen/SerdeGeneratorEngine.fs, src/Serde.FS.Json/Codec/SerdeJsonWriter.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- 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 412 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — evaluation did not complete — Naming Consistency not included (check did not complete) — excluded from the score.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- 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.
- D27 Navigability — evaluation did not complete — Navigability not included (check did not complete) — excluded from the score.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Microsoft.Extensions.DependencyInjection registered from F#, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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.
- 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.
- 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.
- 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 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").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SerdeGeneratorEngine.generate at 93. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being FableClientEmitter.decodeExpr at 36 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with SerdeGeneratorEngine.generate (cyclomatic 93). — Refactoring it lifts Cyclomatic Complexity from 6.1 to about 6.8/10.
D2 · Cognitive Complexity
17 method(s) exceeded the cognitive complexity threshold of 15; the worst was SerdeGeneratorEngine.generate at 177.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with SerdeGeneratorEngine.generate (cognitive 177), Program.main (cognitive 63). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 3.6 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with JsonCodeEmitter.fs, RpcApiDiscovery.fs, SerdeGeneratorEngine.fs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
16 duplicated block group(s) detected. 3.7 % of the production lines (300 of 8,053) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with FableClientEmitter.fs, PrimitiveCodecs.fs, JsonCodeEmitter.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with FableClientEmitter.fs, CollectionCodecs.fs, TypeKindExtractor.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with EntryPointDetector.fs, RootGenericDiagnostics.fs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
21 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 80.7% — 10 file(s) below 50%.
What to do
- Resolve the 10 Low coverage finding(s) in Code Coverage — start with RootGenericDiagnostics.fs, ISerdeCodeEmitter.fs, EntryPointAttribute.fs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 1 No test project references Serde.FS.Json.SampleRpc.Server finding(s) in Code Coverage — start with Serde.FS.Json.SampleRpc.Server.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references Serde.FS.AspNet finding(s) in Code Coverage — start with Serde.FS.AspNet.fsproj. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 119 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 15 direct `PackageReference`(s), and 102 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
Top hotspots: src/Serde.FS.SourceGen/SerdeGeneratorEngine.fs (2×93=186); src/Serde.FS.Fable.SourceGen/FableClientEmitter.fs (7×22=154); src/Serde.FS.SourceGen/RpcApiDiscovery.fs (3×24=72)
What to do
- Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with SerdeGeneratorEngine.fs, FableClientEmitter.fs, RpcApiDiscovery.fs. — One of this dimension's main actionable groups (5 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Serde.FS.Fable.GeneratorHost.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 18 build units (MSBuild, npm) 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)
7 finding(s): 0 critical, 6 high, 1 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 4 high, 1 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 34 of the 66 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 21 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- No logging call was found in the 66 F# production file(s) this check read across 18 module(s). Each was searched for its ecosystem's logging libraries (F#: Microsoft.Extensions.Logging (ILogger), Serilog, NLog, log4net, Logary) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run.
- Add a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) so orchestrators and load balancers can probe liveness/readiness.
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) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:10
- `src/FSharp.SourceDjinn.TypeModel/FSharp.SourceDjinn.TypeModel.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/FSharp.SourceDjinn.TypeModel/FSharp.SourceDjinn.TypeModel.fsproj:22
What to do
- Add a SAST step to CI running 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) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
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
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 67% | Checked 4 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 68% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 38% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 74% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 4 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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.
- D10 Test Quality — ~4350 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.
- D12 Dependency Hygiene — Dependency hygiene not 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.
- D21 Naming Consistency — Naming Consistency not included (check did not complete)
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed F# surface was not measured.
- 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 — Navigability not included (check did not complete)
- 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (43 value object(s))
- 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: the 2 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 44 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — 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)
Critical — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 83 finding(s)
- Low coverage: src/Serde.FS.SourceGen/RootGenericDiagnostics.fs src/Serde.FS.SourceGen/RootGenericDiagnostics.fs:1
- Low coverage: src/Serde.FS.SourceGen/ISerdeCodeEmitter.fs src/Serde.FS.SourceGen/ISerdeCodeEmitter.fs:1
- Low coverage: src/FSharp.SourceDjinn.TypeModel/EntryPointAttribute.fs src/FSharp.SourceDjinn.TypeModel/EntryPointAttribute.fs:1
- Low coverage: src/FSharp.SourceDjinn/EntryPointEmitter.fs src/FSharp.SourceDjinn/EntryPointEmitter.fs:1
- Low coverage: src/Serde.FS.Json/JsonExtensions.fs src/Serde.FS.Json/JsonExtensions.fs:1
- Low coverage: src/Serde.FS.Json/RpcClient.fs src/Serde.FS.Json/RpcClient.fs:1
- Low coverage: src/Serde.FS.Json/Codec/CodecResolver.fs src/Serde.FS.Json/Codec/CodecResolver.fs:1
- Low coverage: src/Serde.FS/Attributes.fs src/Serde.FS/Attributes.fs:1
- Low coverage: src/Serde.FS/JsonCodecAttribute.fs src/Serde.FS/JsonCodecAttribute.fs:1
- Low coverage: src/Serde.FS/SerdeCodecException.fs src/Serde.FS/SerdeCodecException.fs:1
- Hotspot: src/Serde.FS.SourceGen/SerdeGeneratorEngine.fs src/Serde.FS.SourceGen/SerdeGeneratorEngine.fs:350
- Hotspot: src/Serde.FS.Fable.SourceGen/FableClientEmitter.fs src/Serde.FS.Fable.SourceGen/FableClientEmitter.fs:447
- Hotspot: src/Serde.FS.SourceGen/RpcApiDiscovery.fs src/Serde.FS.SourceGen/RpcApiDiscovery.fs:274
- Hotspot: src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs:352
- Hotspot: src/Serde.FS.Json/Codec/SerdeJsonWriter.fs src/Serde.FS.Json/Codec/SerdeJsonWriter.fs:35
- FileTooLong: Serde.FS.Json.SourceGen/JsonCodeEmitter.fs src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs
- FileTooLong: Serde.FS.SourceGen/RpcApiDiscovery.fs src/Serde.FS.SourceGen/RpcApiDiscovery.fs
- FileTooLong: Serde.FS.SourceGen/SerdeGeneratorEngine.fs src/Serde.FS.SourceGen/SerdeGeneratorEngine.fs
- Duplicated block (9 lines × 2) src/Serde.FS.Fable.SourceGen/FableClientEmitter.fs:63
- Duplicated block (9 lines × 2) src/Serde.FS.Json/Codec/PrimitiveCodecs.fs:92
- Duplicated block (9 lines × 2) src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs:428
- Duplicated block (5 lines × 2) src/Serde.FS.Fable.SourceGen/FableClientEmitter.fs:303
- Duplicated block (5 lines × 2) src/Serde.FS.Json/Codec/CollectionCodecs.fs:408
- Duplicated block (5 lines × 2) src/FSharp.SourceDjinn/TypeKindExtractor.fs:256
- Duplicated block (12 lines × 2) src/FSharp.SourceDjinn/EntryPointDetector.fs:66
- Duplicated block (12 lines × 2) src/Serde.FS.SourceGen/RootGenericDiagnostics.fs:203
- SerdeGeneratorEngine.generate (cyclomatic 93) src/Serde.FS.SourceGen/SerdeGeneratorEngine.fs:350
- RootGenericDiagnostics.walkExpr (cyclomatic 33) src/Serde.FS.SourceGen/RootGenericDiagnostics.fs:167
- CallTypeArgExtractor.walkExpr (cyclomatic 32) src/FSharp.SourceDjinn/CallTypeArgExtractor.fs:23
- Program.main (cyclomatic 27) src/Serde.FS.Json.GeneratorHost/Program.fs:8
- RpcApiDiscovery.synTypeToTypeInfo (cyclomatic 24) src/Serde.FS.SourceGen/RpcApiDiscovery.fs:274
- TypeKindExtractor.synTypeToTypeInfo (cyclomatic 23) src/FSharp.SourceDjinn/TypeKindExtractor.fs:138
- SerdeJsonReader.parseValue (cyclomatic 23) src/Serde.FS.Json/Codec/SerdeJsonReader.fs:102
- JsonCodeEmitterImpl.emitUnion (cyclomatic 22) src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs:352
- RpcApiDiscovery.findRpcApis (cyclomatic 22) src/Serde.FS.SourceGen/RpcApiDiscovery.fs:620
- FableClientEmitter.emit (cyclomatic 22) src/Serde.FS.Fable.SourceGen/FableClientEmitter.fs:447
- Program.main (cyclomatic 20) src/Serde.FS.Fable.GeneratorHost/Program.fs:126
- SerdeJsonReader.parseString (cyclomatic 18) src/Serde.FS.Json/Codec/SerdeJsonReader.fs:35
- SerdeJsonWriter.writeValue (cyclomatic 18) src/Serde.FS.Json/Codec/SerdeJsonWriter.fs:35
- SerdeGeneratorEngine.generate (cognitive 177) src/Serde.FS.SourceGen/SerdeGeneratorEngine.fs:350
- Program.main (cognitive 63) src/Serde.FS.Json.GeneratorHost/Program.fs:8
- Program.main (cognitive 51) src/Serde.FS.Fable.GeneratorHost/Program.fs:126
- JsonCodeEmitterImpl.emitUnion (cognitive 40) src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs:352
- RootGenericDiagnostics.walkExpr (cognitive 39) src/Serde.FS.SourceGen/RootGenericDiagnostics.fs:167
- SerdeJsonReader.parseValue (cognitive 37) src/Serde.FS.Json/Codec/SerdeJsonReader.fs:102
- TypeKindExtractor.synTypeToTypeInfo (cognitive 33) src/FSharp.SourceDjinn/TypeKindExtractor.fs:138
- RpcApiDiscovery.findRpcApis (cognitive 32) src/Serde.FS.SourceGen/RpcApiDiscovery.fs:620
- FableClientEmitter.emit (cognitive 24) src/Serde.FS.Fable.SourceGen/FableClientEmitter.fs:447
- FableClientEmitter.validateInterfaceTypes (cognitive 22) src/Serde.FS.Fable.SourceGen/FableClientEmitter.fs:704
- SerdeJsonReader.parseString (cognitive 20) src/Serde.FS.Json/Codec/SerdeJsonReader.fs:35
- JsonCodeEmitterImpl.emitConsolidatedFile (cognitive 20) src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs:679
- RpcApiDiscovery.discover (cognitive 19) src/Serde.FS.SourceGen/RpcApiDiscovery.fs:900
- CallTypeArgExtractor.walkExpr (cognitive 18) src/FSharp.SourceDjinn/CallTypeArgExtractor.fs:23
- SerdeJsonWriter.writeValue (cognitive 17) src/Serde.FS.Json/Codec/SerdeJsonWriter.fs:35
- RpcDispatchEmitter.emit (cognitive 17) src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs:799
- RpcApiDiscovery.synTypeToTypeInfo (cognitive 16) src/Serde.FS.SourceGen/RpcApiDiscovery.fs:274
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (6 corresponding lines) src/Serde.FS/SerdeCodecException.fs:1
- Edited copy of a member (5 corresponding lines) src/Serde.FS/SerdeCodecNotFoundException.fs:1
- Duplicated block (15–17 lines × 2) src/Serde.FS.Json/Codec/CollectionCodecs.fs:308
- Duplicated block (14 lines × 3) src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs:201
- Duplicated block (11 lines × 2) src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs:320
- Duplicated block (10–11 lines × 2) src/Serde.FS.Json/Codec/CollectionCodecs.fs:101
- Duplicated block (8–9 lines × 2) src/Serde.FS.Json/Codec/CollectionCodecs.fs:287
- Duplicated block (7 lines × 4) src/FSharp.SourceDjinn/TypeKindExtractor.fs:166
- Duplicated block (7 lines × 2) src/Serde.FS.SourceGen/RpcApiDiscovery.fs:181
- Duplicated block (6 lines × 2) src/Serde.FS.Json.SourceGen/JsonCodeEmitter.fs:483
- No test project references Serde.FS.Json.SampleRpc.Server src/Serde.FS.Json.SampleRpc.Server/Serde.FS.Json.SampleRpc.Server.fsproj
- No test project references Serde.FS.AspNet src/Serde.FS.AspNet/Serde.FS.AspNet.fsproj
- No test project references Serde.FS.Json.RoundTrip.Net src/Serde.FS.Json.RoundTrip.Net/Serde.FS.Json.RoundTrip.Net.fsproj
- No test project references Serde.FS.Json.RoundTrip.Shared src/Serde.FS.Json.RoundTrip.Shared/Serde.FS.Json.RoundTrip.Shared.fsproj
- No test project references Serde.FS.Fable.GeneratorHost src/Serde.FS.Fable.GeneratorHost/Serde.FS.Fable.GeneratorHost.fsproj
- No test project references Serde.FS.Json.GeneratorHost src/Serde.FS.Json.GeneratorHost/Serde.FS.Json.GeneratorHost.fsproj
- No test project references Serde.FS.Json.RoundTrip.Fable src/Serde.FS.Json.RoundTrip.Fable/Serde.FS.Json.RoundTrip.Fable.fsproj
- No test project references Serde.FS.Json.SampleApp src/Serde.FS.Json.SampleApp/Serde.FS.Json.SampleApp.fsproj
- No test project references Serde.FS.Json.SampleRpc.Client src/Serde.FS.Json.SampleRpc.Client/Serde.FS.Json.SampleRpc.Client.fsproj
- No test project references Serde.FS.Json.SampleRpc.FableClient src/Serde.FS.Json.SampleRpc.FableClient/Serde.FS.Json.SampleRpc.FableClient.fsproj
- No test project references Serde.FS.Json.SampleRpc.Shared src/Serde.FS.Json.SampleRpc.Shared/Serde.FS.Json.SampleRpc.Shared.fsproj
- No structured logging
- NuGet dependencies are not locked
Minor — 9 finding(s)
- No ADRs found src/Serde.FS.Fable.GeneratorHost/Serde.FS.Fable.GeneratorHost.fsproj:3
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:10
- No dependency-update automation src/FSharp.SourceDjinn.TypeModel/FSharp.SourceDjinn.TypeModel.fsproj:22
- 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-25d56b6f4a6f4a97ab3001fea3668fee/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-25d56b6f4a6f4a97ab3001fea3668fee/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 --exclude src/Serde.FS.SourceGen.Tests/Fable/Snapshots . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 5 | artifacts/raw/trivy-fs.json |
| 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 | — |
| 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |