Executive summary
mbraceproject/FsPickler falls short of our standard for production because 40 files are no longer known to anyone active in the project and we found no recorded design decisions and no architecture document or diagram. It scores 55 out of 100 and is rated Adequate, and both of its critical findings are security problems in its servers and containers.
Maturity, at 43, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 40 files no active contributor knows, worth about 11 points. Updating the outdated dependencies comes next, worth about 8 points. Raising Maturity to 70 would lift the score to about 63.
Two settings leave the servers or containers unsafe. Correcting the unsafe settings would close this risk.
The product code is 8,523 lines, about €11,000 to rebuild. The check for malicious packages couldn't finish, so that result is missing, not a clean pass.
If Maturity rose from 43 to 70, the lowest score rated Strong, the score would rise from 55 to about 63.
New since the last survey: 1 finding
- Code Duplication · Edited copy of a member (28 corresponding lines) src/FsPickler/FsPickler/BinarySerializer.fs
Fixed since the last survey: 5 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Dependency Hygiene · Vulnerable: Newtonsoft.Json
- Dependency Hygiene · Vulnerable: System.Drawing.Common
- Dependency Hygiene · Vulnerable: System.Security.Cryptography.Xml
- Dependency Hygiene · Vulnerable: Wire
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,700 to €19,000, for 62 to 197 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 55. 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,523 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 MBrace.FsPickler.CSharpProxy | 2 MBrace.FsPickler.Emit | 3 MBrace.FsPickler.Emit.DynamicMethod | 4 MBrace.FsPickler.Hashing | 5 MBrace.FsPickler.Hashing.MurMur3Utils | 6 MBrace.FsPickler.Json.Common.Enum | 7 MBrace.FsPickler.PicklerEmit.ReflectedPicklerAPI | 8 MBrace.FsPickler.PicklerGenerator | 9 MBrace.FsPickler.TypeShapeExtensions | 10 MBrace.FsPickler.Utils | 11 TypeShape | 12 MBrace.FsPickler.ReflectionCache | 13 MBrace.FsPickler.TypeShapeExtensions.Shape | 14 MBrace.FsPickler.Utils.Exn | 15 TypeShape.MemberUtils | 16 TypeShape.MemberUtils2 | 17 TypeShape.Shape | 18 TypeShape.TypeShapeImpl | 19 MBrace.FsPickler | 20 MBrace.FsPickler.ArrayPicklerUtils | 21 MBrace.FsPickler.BinaryFormatUtils | 22 MBrace.FsPickler.Combinators.Binary | 23 MBrace.FsPickler.Combinators.Pickler.ProductInternals | 24 MBrace.FsPickler.Combinators.Pickler.SumInternals | 25 MBrace.FsPickler.Combinators.Xml | 26 MBrace.FsPickler.ExtensionMethods | 27 MBrace.FsPickler.ISerializableUtils | 28 MBrace.FsPickler.Json | 29 MBrace.FsPickler.Json.Common | 30 MBrace.FsPickler.KindModule | 31 MBrace.FsPickler.PicklerEmit | 32 MBrace.FsPickler.PicklerResolution | 33 MBrace.FsPickler.PrimitivePicklers | 34 MBrace.FsPickler.RootSerialization | 35 MBrace.FsPickler.SequenceUtils | 36 MBrace.FsPickler.TypeNameConverter | 37 MBrace.FsPickler.XmlUtils | 38 MBrace.FsPickler.Combinators.Bson | 39 MBrace.FsPickler.Combinators.Json | 40 MBrace.FsPickler.Combinators.Pickler |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 MBrace.FsPickler.CSharpProxy | ||||||||||||||||||||||||||||||||||||||||
| 2 MBrace.FsPickler.Emit | ||||||||||||||||||||||||||||||||||||||||
| 3 MBrace.FsPickler.Emit.DynamicMethod | ||||||||||||||||||||||||||||||||||||||||
| 4 MBrace.FsPickler.Hashing | ||||||||||||||||||||||||||||||||||||||||
| 5 MBrace.FsPickler.Hashing.MurMur3Utils | ||||||||||||||||||||||||||||||||||||||||
| 6 MBrace.FsPickler.Json.Common.Enum | ||||||||||||||||||||||||||||||||||||||||
| 7 MBrace.FsPickler.PicklerEmit.ReflectedPicklerAPI | ||||||||||||||||||||||||||||||||||||||||
| 8 MBrace.FsPickler.PicklerGenerator | ||||||||||||||||||||||||||||||||||||||||
| 9 MBrace.FsPickler.TypeShapeExtensions | ||||||||||||||||||||||||||||||||||||||||
| 10 MBrace.FsPickler.Utils | ||||||||||||||||||||||||||||||||||||||||
| 11 TypeShape | ||||||||||||||||||||||||||||||||||||||||
| 12 MBrace.FsPickler.ReflectionCache | 3 | |||||||||||||||||||||||||||||||||||||||
| 13 MBrace.FsPickler.TypeShapeExtensions.Shape | 14 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 MBrace.FsPickler.Utils.Exn | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 TypeShape.MemberUtils | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 TypeShape.MemberUtils2 | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 TypeShape.Shape | 30 | |||||||||||||||||||||||||||||||||||||||
| 18 TypeShape.TypeShapeImpl | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 MBrace.FsPickler | 1 | 4 | 4 | |||||||||||||||||||||||||||||||||||||
| 20 MBrace.FsPickler.ArrayPicklerUtils | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 MBrace.FsPickler.BinaryFormatUtils | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 MBrace.FsPickler.Combinators.Binary | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 MBrace.FsPickler.Combinators.Pickler.ProductInternals | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 MBrace.FsPickler.Combinators.Pickler.SumInternals | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 MBrace.FsPickler.Combinators.Xml | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 MBrace.FsPickler.ExtensionMethods | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 MBrace.FsPickler.ISerializableUtils | 6 | |||||||||||||||||||||||||||||||||||||||
| 28 MBrace.FsPickler.Json | 18 | |||||||||||||||||||||||||||||||||||||||
| 29 MBrace.FsPickler.Json.Common | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 MBrace.FsPickler.KindModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 MBrace.FsPickler.PicklerEmit | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 32 MBrace.FsPickler.PicklerResolution | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 33 MBrace.FsPickler.PrimitivePicklers | 47 | |||||||||||||||||||||||||||||||||||||||
| 34 MBrace.FsPickler.RootSerialization | 1 | 9 | ||||||||||||||||||||||||||||||||||||||
| 35 MBrace.FsPickler.SequenceUtils | 8 | |||||||||||||||||||||||||||||||||||||||
| 36 MBrace.FsPickler.TypeNameConverter | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 MBrace.FsPickler.XmlUtils | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 MBrace.FsPickler.Combinators.Bson | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 MBrace.FsPickler.Combinators.Json | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 MBrace.FsPickler.Combinators.Pickler | 2 | 1 | 2 |
12→19 MBrace.FsPickler.ReflectionCache uses MBrace.FsPickler part of a loop✕
- Connections
- 3 pairs of types, where a type in MBrace.FsPickler.ReflectionCache uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.ReflectionCache.CompositeMemberInfo→MBrace.FsPickler.AssemblyInfoMBrace.FsPickler.ReflectionCache.ReflectionCache→MBrace.FsPickler.AssemblyInfoMBrace.FsPickler.ReflectionCache.ReflectionCache→MBrace.FsPickler.ITypeNameConverter
- Direction
- MBrace.FsPickler.ReflectionCache uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.ReflectionCache, while a change to MBrace.FsPickler.ReflectionCache can't break MBrace.FsPickler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→9 MBrace.FsPickler.TypeShapeExtensions.Shape uses MBrace.FsPickler.TypeShapeExtensions✕
- Connections
- 14 pairs of types, where a type in MBrace.FsPickler.TypeShapeExtensions.Shape uses a type in MBrace.FsPickler.TypeShapeExtensions.
- The types involved
MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeFSharpChoice2MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeFSharpChoice3MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeFSharpChoice4MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeFSharpChoice5MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeFSharpChoice6MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeFSharpChoice7MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeTuple1MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeTuple2MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeTuple3MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeTuple4MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeTuple5MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeTuple6MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeTuple7MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→MBrace.FsPickler.TypeShapeExtensions.IShapeTuple8
- Direction
- MBrace.FsPickler.TypeShapeExtensions.Shape uses MBrace.FsPickler.TypeShapeExtensions, so a change to MBrace.FsPickler.TypeShapeExtensions can break MBrace.FsPickler.TypeShapeExtensions.Shape, while a change to MBrace.FsPickler.TypeShapeExtensions.Shape can't break MBrace.FsPickler.TypeShapeExtensions.
- Position
- Below the diagonal: MBrace.FsPickler.TypeShapeExtensions.Shape uses a module listed above it, which is the healthy direction.
13→11 MBrace.FsPickler.TypeShapeExtensions.Shape uses TypeShape✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.TypeShapeExtensions.Shape uses a type in TypeShape.
- The types involved
MBrace.FsPickler.TypeShapeExtensions.Shape.Shape→TypeShape.TypeShape
- Direction
- MBrace.FsPickler.TypeShapeExtensions.Shape uses TypeShape, so a change to TypeShape can break MBrace.FsPickler.TypeShapeExtensions.Shape, while a change to MBrace.FsPickler.TypeShapeExtensions.Shape can't break TypeShape.
- Position
- Below the diagonal: MBrace.FsPickler.TypeShapeExtensions.Shape uses a module listed above it, which is the healthy direction.
14→10 MBrace.FsPickler.Utils.Exn uses MBrace.FsPickler.Utils✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.Utils.Exn uses a type in MBrace.FsPickler.Utils.
- The types involved
MBrace.FsPickler.Utils.Exn.Exn→MBrace.FsPickler.Utils.Exn`1
- Direction
- MBrace.FsPickler.Utils.Exn uses MBrace.FsPickler.Utils, so a change to MBrace.FsPickler.Utils can break MBrace.FsPickler.Utils.Exn, while a change to MBrace.FsPickler.Utils.Exn can't break MBrace.FsPickler.Utils.
- Position
- Below the diagonal: MBrace.FsPickler.Utils.Exn uses a module listed above it, which is the healthy direction.
15→11 TypeShape.MemberUtils uses TypeShape✕
- Connections
- 1 pair of types, where a type in TypeShape.MemberUtils uses a type in TypeShape.
- The types involved
TypeShape.MemberUtils.MemberUtils→TypeShape.ITypeVisitor`1
- Direction
- TypeShape.MemberUtils uses TypeShape, so a change to TypeShape can break TypeShape.MemberUtils, while a change to TypeShape.MemberUtils can't break TypeShape.
- Position
- Below the diagonal: TypeShape.MemberUtils uses a module listed above it, which is the healthy direction.
16→11 TypeShape.MemberUtils2 uses TypeShape✕
- Connections
- 3 pairs of types, where a type in TypeShape.MemberUtils2 uses a type in TypeShape.
- The types involved
TypeShape.MemberUtils2.MemberUtils2→TypeShape.IShapeConstructor`1TypeShape.MemberUtils2.MemberUtils2→TypeShape.IShapeMember`1TypeShape.MemberUtils2.MemberUtils2→TypeShape.IShapeReadOnlyMember`1
- Direction
- TypeShape.MemberUtils2 uses TypeShape, so a change to TypeShape can break TypeShape.MemberUtils2, while a change to TypeShape.MemberUtils2 can't break TypeShape.
- Position
- Below the diagonal: TypeShape.MemberUtils2 uses a module listed above it, which is the healthy direction.
17→11 TypeShape.Shape uses TypeShape✕
- Connections
- 30 pairs of types, where a type in TypeShape.Shape uses a type in TypeShape. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
TypeShape.Shape.Shape→TypeShape.IShapeArrayTypeShape.Shape.Shape→TypeShape.IShapeCliMutableTypeShape.Shape.Shape→TypeShape.IShapeCollectionTypeShape.Shape.Shape→TypeShape.IShapeComparisonTypeShape.Shape.Shape→TypeShape.IShapeDefaultConstructorTypeShape.Shape.Shape→TypeShape.IShapeDelegateTypeShape.Shape.Shape→TypeShape.IShapeDictionaryTypeShape.Shape.Shape→TypeShape.IShapeEnumTypeShape.Shape.Shape→TypeShape.IShapeEnumerableTypeShape.Shape.Shape→TypeShape.IShapeEqualityTypeShape.Shape.Shape→TypeShape.IShapeExceptionTypeShape.Shape.Shape→TypeShape.IShapeFSharpFuncTypeShape.Shape.Shape→TypeShape.IShapeFSharpListTypeShape.Shape.Shape→TypeShape.IShapeFSharpMapTypeShape.Shape.Shape→TypeShape.IShapeFSharpOptionTypeShape.Shape.Shape→TypeShape.IShapeFSharpRecordTypeShape.Shape.Shape→TypeShape.IShapeFSharpRefTypeShape.Shape.Shape→TypeShape.IShapeFSharpSetTypeShape.Shape.Shape→TypeShape.IShapeFSharpUnionTypeShape.Shape.Shape→TypeShape.IShapeHashSetTypeShape.Shape.Shape→TypeShape.IShapeISerializableTypeShape.Shape.Shape→TypeShape.IShapeKeyValuePairTypeShape.Shape.Shape→TypeShape.IShapeNotStructTypeShape.Shape.Shape→TypeShape.IShapeNullableTypeShape.Shape.Shape→TypeShape.IShapePoco
- Direction
- TypeShape.Shape uses TypeShape, so a change to TypeShape can break TypeShape.Shape, while a change to TypeShape.Shape can't break TypeShape.
- Position
- Below the diagonal: TypeShape.Shape uses a module listed above it, which is the healthy direction.
18→11 TypeShape.TypeShapeImpl uses TypeShape✕
- Connections
- 1 pair of types, where a type in TypeShape.TypeShapeImpl uses a type in TypeShape.
- The types involved
TypeShape.TypeShapeImpl.TypeShapeImpl→TypeShape.TypeShape
- Direction
- TypeShape.TypeShapeImpl uses TypeShape, so a change to TypeShape can break TypeShape.TypeShapeImpl, while a change to TypeShape.TypeShapeImpl can't break TypeShape.
- Position
- Below the diagonal: TypeShape.TypeShapeImpl uses a module listed above it, which is the healthy direction.
19→2 MBrace.FsPickler uses MBrace.FsPickler.Emit✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler uses a type in MBrace.FsPickler.Emit.
- The types involved
MBrace.FsPickler.UnionCaseSerializationHelper→MBrace.FsPickler.Emit.EnvItem`1
- Direction
- MBrace.FsPickler uses MBrace.FsPickler.Emit, so a change to MBrace.FsPickler.Emit can break MBrace.FsPickler, while a change to MBrace.FsPickler can't break MBrace.FsPickler.Emit.
- Position
- Below the diagonal: MBrace.FsPickler uses a module listed above it, which is the healthy direction.
19→4 MBrace.FsPickler uses MBrace.FsPickler.Hashing✕
- Connections
- 4 pairs of types, where a type in MBrace.FsPickler uses a type in MBrace.FsPickler.Hashing.
- The types involved
MBrace.FsPickler.FsPickler→MBrace.FsPickler.Hashing.HashResultMBrace.FsPickler.FsPickler→MBrace.FsPickler.Hashing.IHashStreamFactoryMBrace.FsPickler.FsPicklerSerializer→MBrace.FsPickler.Hashing.HashResultMBrace.FsPickler.FsPicklerSerializer→MBrace.FsPickler.Hashing.IHashStreamFactory
- Direction
- MBrace.FsPickler uses MBrace.FsPickler.Hashing, so a change to MBrace.FsPickler.Hashing can break MBrace.FsPickler, while a change to MBrace.FsPickler can't break MBrace.FsPickler.Hashing.
- Position
- Below the diagonal: MBrace.FsPickler uses a module listed above it, which is the healthy direction.
19→12 MBrace.FsPickler uses MBrace.FsPickler.ReflectionCache✕
- Connections
- 4 pairs of types, where a type in MBrace.FsPickler uses a type in MBrace.FsPickler.ReflectionCache.
- The types involved
MBrace.FsPickler.FsPicklerSerializer→MBrace.FsPickler.ReflectionCache.ReflectionCacheMBrace.FsPickler.ObjectSizeCounter→MBrace.FsPickler.ReflectionCache.ReflectionCacheMBrace.FsPickler.ReadState→MBrace.FsPickler.ReflectionCache.ReflectionCacheMBrace.FsPickler.WriteState→MBrace.FsPickler.ReflectionCache.ReflectionCache
- Direction
- MBrace.FsPickler uses MBrace.FsPickler.ReflectionCache, so a change to MBrace.FsPickler.ReflectionCache can break MBrace.FsPickler, while a change to MBrace.FsPickler can't break MBrace.FsPickler.ReflectionCache.
- Position
- Below the diagonal: MBrace.FsPickler uses a module listed above it, which is the healthy direction.
20→19 MBrace.FsPickler.ArrayPicklerUtils uses MBrace.FsPickler✕
- Connections
- 3 pairs of types, where a type in MBrace.FsPickler.ArrayPicklerUtils uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.ArrayPicklerUtils.ArrayPicklerUtils→MBrace.FsPickler.IPickleFormatReaderMBrace.FsPickler.ArrayPicklerUtils.ArrayPicklerUtils→MBrace.FsPickler.IPickleFormatWriterMBrace.FsPickler.ArrayPicklerUtils.ArrayPicklerUtils→MBrace.FsPickler.Pickler
- Direction
- MBrace.FsPickler.ArrayPicklerUtils uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.ArrayPicklerUtils, while a change to MBrace.FsPickler.ArrayPicklerUtils can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.ArrayPicklerUtils uses a module listed above it, which is the healthy direction.
21→19 MBrace.FsPickler.BinaryFormatUtils uses MBrace.FsPickler✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.BinaryFormatUtils uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.BinaryFormatUtils.BinaryFormatUtils→MBrace.FsPickler.ObjectFlags
- Direction
- MBrace.FsPickler.BinaryFormatUtils uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.BinaryFormatUtils, while a change to MBrace.FsPickler.BinaryFormatUtils can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.BinaryFormatUtils uses a module listed above it, which is the healthy direction.
22→19 MBrace.FsPickler.Combinators.Binary uses MBrace.FsPickler✕
- Connections
- 2 pairs of types, where a type in MBrace.FsPickler.Combinators.Binary uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.Combinators.Binary.Binary→MBrace.FsPickler.BinarySerializerMBrace.FsPickler.Combinators.Binary.Binary→MBrace.FsPickler.Pickler`1
- Direction
- MBrace.FsPickler.Combinators.Binary uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.Combinators.Binary, while a change to MBrace.FsPickler.Combinators.Binary can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Binary uses a module listed above it, which is the healthy direction.
23→19 MBrace.FsPickler.Combinators.Pickler.ProductInternals uses MBrace.FsPickler✕
- Connections
- 2 pairs of types, where a type in MBrace.FsPickler.Combinators.Pickler.ProductInternals uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.Combinators.Pickler.ProductInternals.Part`3→MBrace.FsPickler.Pickler`1MBrace.FsPickler.Combinators.Pickler.ProductInternals.ProductInternals→MBrace.FsPickler.Pickler`1
- Direction
- MBrace.FsPickler.Combinators.Pickler.ProductInternals uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.Combinators.Pickler.ProductInternals, while a change to MBrace.FsPickler.Combinators.Pickler.ProductInternals can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Pickler.ProductInternals uses a module listed above it, which is the healthy direction.
24→19 MBrace.FsPickler.Combinators.Pickler.SumInternals uses MBrace.FsPickler✕
- Connections
- 2 pairs of types, where a type in MBrace.FsPickler.Combinators.Pickler.SumInternals uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.Combinators.Pickler.SumInternals.Part`4→MBrace.FsPickler.Pickler`1MBrace.FsPickler.Combinators.Pickler.SumInternals.SumInternals→MBrace.FsPickler.Pickler`1
- Direction
- MBrace.FsPickler.Combinators.Pickler.SumInternals uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.Combinators.Pickler.SumInternals, while a change to MBrace.FsPickler.Combinators.Pickler.SumInternals can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Pickler.SumInternals uses a module listed above it, which is the healthy direction.
25→19 MBrace.FsPickler.Combinators.Xml uses MBrace.FsPickler✕
- Connections
- 2 pairs of types, where a type in MBrace.FsPickler.Combinators.Xml uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.Combinators.Xml.Xml→MBrace.FsPickler.Pickler`1MBrace.FsPickler.Combinators.Xml.Xml→MBrace.FsPickler.XmlSerializer
- Direction
- MBrace.FsPickler.Combinators.Xml uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.Combinators.Xml, while a change to MBrace.FsPickler.Combinators.Xml can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Xml uses a module listed above it, which is the healthy direction.
26→4 MBrace.FsPickler.ExtensionMethods uses MBrace.FsPickler.Hashing✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.ExtensionMethods uses a type in MBrace.FsPickler.Hashing.
- The types involved
MBrace.FsPickler.ExtensionMethods.ExtensionMethods→MBrace.FsPickler.Hashing.HashResult
- Direction
- MBrace.FsPickler.ExtensionMethods uses MBrace.FsPickler.Hashing, so a change to MBrace.FsPickler.Hashing can break MBrace.FsPickler.ExtensionMethods, while a change to MBrace.FsPickler.ExtensionMethods can't break MBrace.FsPickler.Hashing.
- Position
- Below the diagonal: MBrace.FsPickler.ExtensionMethods uses a module listed above it, which is the healthy direction.
26→19 MBrace.FsPickler.ExtensionMethods uses MBrace.FsPickler✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.ExtensionMethods uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.ExtensionMethods.ExtensionMethods→MBrace.FsPickler.Pickler`1
- Direction
- MBrace.FsPickler.ExtensionMethods uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.ExtensionMethods, while a change to MBrace.FsPickler.ExtensionMethods can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.ExtensionMethods uses a module listed above it, which is the healthy direction.
27→19 MBrace.FsPickler.ISerializableUtils uses MBrace.FsPickler✕
- Connections
- 6 pairs of types, where a type in MBrace.FsPickler.ISerializableUtils uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.ISerializableUtils.ISerializableUtils→MBrace.FsPickler.CloneStateMBrace.FsPickler.ISerializableUtils.ISerializableUtils→MBrace.FsPickler.IPicklerResolverMBrace.FsPickler.ISerializableUtils.ISerializableUtils→MBrace.FsPickler.PicklerMBrace.FsPickler.ISerializableUtils.ISerializableUtils→MBrace.FsPickler.ReadStateMBrace.FsPickler.ISerializableUtils.ISerializableUtils→MBrace.FsPickler.VisitStateMBrace.FsPickler.ISerializableUtils.ISerializableUtils→MBrace.FsPickler.WriteState
- Direction
- MBrace.FsPickler.ISerializableUtils uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.ISerializableUtils, while a change to MBrace.FsPickler.ISerializableUtils can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.ISerializableUtils uses a module listed above it, which is the healthy direction.
28→19 MBrace.FsPickler.Json uses MBrace.FsPickler✕
- Connections
- 18 pairs of types, where a type in MBrace.FsPickler.Json uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.Json.BsonPickleFormatProvider→MBrace.FsPickler.IPickleFormatProviderMBrace.FsPickler.Json.BsonPickleFormatProvider→MBrace.FsPickler.IPickleFormatReaderMBrace.FsPickler.Json.BsonPickleFormatProvider→MBrace.FsPickler.IPickleFormatWriterMBrace.FsPickler.Json.BsonSerializer→MBrace.FsPickler.FsPicklerSerializerMBrace.FsPickler.Json.BsonSerializer→MBrace.FsPickler.IPicklerResolverMBrace.FsPickler.Json.BsonSerializer→MBrace.FsPickler.ITypeNameConverterMBrace.FsPickler.Json.FsPickler→MBrace.FsPickler.IPicklerResolverMBrace.FsPickler.Json.FsPickler→MBrace.FsPickler.ITypeNameConverterMBrace.FsPickler.Json.JsonPickleFormatProvider→MBrace.FsPickler.IPickleFormatReaderMBrace.FsPickler.Json.JsonPickleFormatProvider→MBrace.FsPickler.IPickleFormatWriterMBrace.FsPickler.Json.JsonPickleFormatProvider→MBrace.FsPickler.ITextPickleFormatProviderMBrace.FsPickler.Json.JsonPickleReader→MBrace.FsPickler.IPickleFormatReaderMBrace.FsPickler.Json.JsonPickleReader→MBrace.FsPickler.ObjectFlagsMBrace.FsPickler.Json.JsonPickleWriter→MBrace.FsPickler.IPickleFormatWriterMBrace.FsPickler.Json.JsonPickleWriter→MBrace.FsPickler.ObjectFlagsMBrace.FsPickler.Json.JsonSerializer→MBrace.FsPickler.FsPicklerTextSerializerMBrace.FsPickler.Json.JsonSerializer→MBrace.FsPickler.IPicklerResolverMBrace.FsPickler.Json.JsonSerializer→MBrace.FsPickler.ITypeNameConverter
- Direction
- MBrace.FsPickler.Json uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.Json, while a change to MBrace.FsPickler.Json can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.Json uses a module listed above it, which is the healthy direction.
29→19 MBrace.FsPickler.Json.Common uses MBrace.FsPickler✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.Json.Common uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.Json.Common.Common→MBrace.FsPickler.ObjectFlags
- Direction
- MBrace.FsPickler.Json.Common uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.Json.Common, while a change to MBrace.FsPickler.Json.Common can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.Json.Common uses a module listed above it, which is the healthy direction.
30→19 MBrace.FsPickler.KindModule uses MBrace.FsPickler✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.KindModule uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.KindModule.KindModule→MBrace.FsPickler.Kind
- Direction
- MBrace.FsPickler.KindModule uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.KindModule, while a change to MBrace.FsPickler.KindModule can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.KindModule uses a module listed above it, which is the healthy direction.
31→2 MBrace.FsPickler.PicklerEmit uses MBrace.FsPickler.Emit✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.PicklerEmit uses a type in MBrace.FsPickler.Emit.
- The types involved
MBrace.FsPickler.PicklerEmit.PicklerEmit→MBrace.FsPickler.Emit.EnvItem`1
- Direction
- MBrace.FsPickler.PicklerEmit uses MBrace.FsPickler.Emit, so a change to MBrace.FsPickler.Emit can break MBrace.FsPickler.PicklerEmit, while a change to MBrace.FsPickler.PicklerEmit can't break MBrace.FsPickler.Emit.
- Position
- Below the diagonal: MBrace.FsPickler.PicklerEmit uses a module listed above it, which is the healthy direction.
31→19 MBrace.FsPickler.PicklerEmit uses MBrace.FsPickler✕
- Connections
- 5 pairs of types, where a type in MBrace.FsPickler.PicklerEmit uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.PicklerEmit.PicklerEmit→MBrace.FsPickler.CloneStateMBrace.FsPickler.PicklerEmit.PicklerEmit→MBrace.FsPickler.PicklerMBrace.FsPickler.PicklerEmit.PicklerEmit→MBrace.FsPickler.ReadStateMBrace.FsPickler.PicklerEmit.PicklerEmit→MBrace.FsPickler.VisitStateMBrace.FsPickler.PicklerEmit.PicklerEmit→MBrace.FsPickler.WriteState
- Direction
- MBrace.FsPickler.PicklerEmit uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.PicklerEmit, while a change to MBrace.FsPickler.PicklerEmit can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.PicklerEmit uses a module listed above it, which is the healthy direction.
32→10 MBrace.FsPickler.PicklerResolution uses MBrace.FsPickler.Utils✕
- Connections
- 2 pairs of types, where a type in MBrace.FsPickler.PicklerResolution uses a type in MBrace.FsPickler.Utils.
- The types involved
MBrace.FsPickler.PicklerResolution.PicklerResolution→MBrace.FsPickler.Utils.Exn`1MBrace.FsPickler.PicklerResolution.PicklerResolution→MBrace.FsPickler.Utils.ICache`2
- Direction
- MBrace.FsPickler.PicklerResolution uses MBrace.FsPickler.Utils, so a change to MBrace.FsPickler.Utils can break MBrace.FsPickler.PicklerResolution, while a change to MBrace.FsPickler.PicklerResolution can't break MBrace.FsPickler.Utils.
- Position
- Below the diagonal: MBrace.FsPickler.PicklerResolution uses a module listed above it, which is the healthy direction.
32→19 MBrace.FsPickler.PicklerResolution uses MBrace.FsPickler✕
- Connections
- 3 pairs of types, where a type in MBrace.FsPickler.PicklerResolution uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.PicklerResolution.PicklerResolution→MBrace.FsPickler.ICustomPicklerRegistryMBrace.FsPickler.PicklerResolution.PicklerResolution→MBrace.FsPickler.IPicklerResolverMBrace.FsPickler.PicklerResolution.PicklerResolution→MBrace.FsPickler.Pickler
- Direction
- MBrace.FsPickler.PicklerResolution uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.PicklerResolution, while a change to MBrace.FsPickler.PicklerResolution can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.PicklerResolution uses a module listed above it, which is the healthy direction.
33→19 MBrace.FsPickler.PrimitivePicklers uses MBrace.FsPickler✕
- Connections
- 47 pairs of types, where a type in MBrace.FsPickler.PrimitivePicklers uses a type in MBrace.FsPickler. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
MBrace.FsPickler.PrimitivePicklers.BigIntPickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.BigIntPickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.BooleanPickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.BooleanPickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.BytePickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.BytePickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.CharPickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.CharPickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.DBNullPickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.DBNullPickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.DateTimeOffsetPickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.DateTimeOffsetPickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.DateTimePickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.DateTimePickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.DecimalPickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.DecimalPickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.DoublePickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.DoublePickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.GuidPickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.GuidPickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.Int16Pickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.Int16Pickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.Int32Pickler→MBrace.FsPickler.ReadStateMBrace.FsPickler.PrimitivePicklers.Int32Pickler→MBrace.FsPickler.WriteStateMBrace.FsPickler.PrimitivePicklers.Int64Pickler→MBrace.FsPickler.ReadState
- Direction
- MBrace.FsPickler.PrimitivePicklers uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.PrimitivePicklers, while a change to MBrace.FsPickler.PrimitivePicklers can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.PrimitivePicklers uses a module listed above it, which is the healthy direction.
34→12 MBrace.FsPickler.RootSerialization uses MBrace.FsPickler.ReflectionCache✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.RootSerialization uses a type in MBrace.FsPickler.ReflectionCache.
- The types involved
MBrace.FsPickler.RootSerialization.RootSerialization→MBrace.FsPickler.ReflectionCache.ReflectionCache
- Direction
- MBrace.FsPickler.RootSerialization uses MBrace.FsPickler.ReflectionCache, so a change to MBrace.FsPickler.ReflectionCache can break MBrace.FsPickler.RootSerialization, while a change to MBrace.FsPickler.RootSerialization can't break MBrace.FsPickler.ReflectionCache.
- Position
- Below the diagonal: MBrace.FsPickler.RootSerialization uses a module listed above it, which is the healthy direction.
34→19 MBrace.FsPickler.RootSerialization uses MBrace.FsPickler✕
- Connections
- 9 pairs of types, where a type in MBrace.FsPickler.RootSerialization uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.RootSerialization.RootSerialization→MBrace.FsPickler.IObjectSifterMBrace.FsPickler.RootSerialization.RootSerialization→MBrace.FsPickler.IPickleFormatProviderMBrace.FsPickler.RootSerialization.RootSerialization→MBrace.FsPickler.IPickleFormatReaderMBrace.FsPickler.RootSerialization.RootSerialization→MBrace.FsPickler.IPickleFormatWriterMBrace.FsPickler.RootSerialization.RootSerialization→MBrace.FsPickler.IPicklerResolverMBrace.FsPickler.RootSerialization.RootSerialization→MBrace.FsPickler.ITextPickleFormatProviderMBrace.FsPickler.RootSerialization.RootSerialization→MBrace.FsPickler.PicklerMBrace.FsPickler.RootSerialization.RootSerialization→MBrace.FsPickler.Pickler`1MBrace.FsPickler.RootSerialization.RootSerialization→MBrace.FsPickler.WriteState
- Direction
- MBrace.FsPickler.RootSerialization uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.RootSerialization, while a change to MBrace.FsPickler.RootSerialization can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.RootSerialization uses a module listed above it, which is the healthy direction.
35→19 MBrace.FsPickler.SequenceUtils uses MBrace.FsPickler✕
- Connections
- 8 pairs of types, where a type in MBrace.FsPickler.SequenceUtils uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.SequenceUtils.SequenceDeserializerEnumerable`1→MBrace.FsPickler.Pickler`1MBrace.FsPickler.SequenceUtils.SequenceDeserializerEnumerable`1→MBrace.FsPickler.ReadStateMBrace.FsPickler.SequenceUtils.SequenceDeserializerEnumerator`1→MBrace.FsPickler.Pickler`1MBrace.FsPickler.SequenceUtils.SequenceDeserializerEnumerator`1→MBrace.FsPickler.ReadStateMBrace.FsPickler.SequenceUtils.SequenceUtils→MBrace.FsPickler.IPickleFormatReaderMBrace.FsPickler.SequenceUtils.SequenceUtils→MBrace.FsPickler.Pickler`1MBrace.FsPickler.SequenceUtils.SequenceUtils→MBrace.FsPickler.ReadStateMBrace.FsPickler.SequenceUtils.SequenceUtils→MBrace.FsPickler.WriteState
- Direction
- MBrace.FsPickler.SequenceUtils uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.SequenceUtils, while a change to MBrace.FsPickler.SequenceUtils can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.SequenceUtils uses a module listed above it, which is the healthy direction.
36→19 MBrace.FsPickler.TypeNameConverter uses MBrace.FsPickler✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.TypeNameConverter uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.TypeNameConverter.TypeNameConverter→MBrace.FsPickler.ITypeNameConverter
- Direction
- MBrace.FsPickler.TypeNameConverter uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.TypeNameConverter, while a change to MBrace.FsPickler.TypeNameConverter can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.TypeNameConverter uses a module listed above it, which is the healthy direction.
37→19 MBrace.FsPickler.XmlUtils uses MBrace.FsPickler✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.XmlUtils uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.XmlUtils.XmlUtils→MBrace.FsPickler.ObjectFlags
- Direction
- MBrace.FsPickler.XmlUtils uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.XmlUtils, while a change to MBrace.FsPickler.XmlUtils can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.XmlUtils uses a module listed above it, which is the healthy direction.
38→19 MBrace.FsPickler.Combinators.Bson uses MBrace.FsPickler✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.Combinators.Bson uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.Combinators.Bson.Bson→MBrace.FsPickler.Pickler`1
- Direction
- MBrace.FsPickler.Combinators.Bson uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.Combinators.Bson, while a change to MBrace.FsPickler.Combinators.Bson can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Bson uses a module listed above it, which is the healthy direction.
38→28 MBrace.FsPickler.Combinators.Bson uses MBrace.FsPickler.Json✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.Combinators.Bson uses a type in MBrace.FsPickler.Json.
- The types involved
MBrace.FsPickler.Combinators.Bson.Bson→MBrace.FsPickler.Json.BsonSerializer
- Direction
- MBrace.FsPickler.Combinators.Bson uses MBrace.FsPickler.Json, so a change to MBrace.FsPickler.Json can break MBrace.FsPickler.Combinators.Bson, while a change to MBrace.FsPickler.Combinators.Bson can't break MBrace.FsPickler.Json.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Bson uses a module listed above it, which is the healthy direction.
39→19 MBrace.FsPickler.Combinators.Json uses MBrace.FsPickler✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.Combinators.Json uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.Combinators.Json.Json→MBrace.FsPickler.Pickler`1
- Direction
- MBrace.FsPickler.Combinators.Json uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.Combinators.Json, while a change to MBrace.FsPickler.Combinators.Json can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Json uses a module listed above it, which is the healthy direction.
39→28 MBrace.FsPickler.Combinators.Json uses MBrace.FsPickler.Json✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.Combinators.Json uses a type in MBrace.FsPickler.Json.
- The types involved
MBrace.FsPickler.Combinators.Json.Json→MBrace.FsPickler.Json.JsonSerializer
- Direction
- MBrace.FsPickler.Combinators.Json uses MBrace.FsPickler.Json, so a change to MBrace.FsPickler.Json can break MBrace.FsPickler.Combinators.Json, while a change to MBrace.FsPickler.Combinators.Json can't break MBrace.FsPickler.Json.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Json uses a module listed above it, which is the healthy direction.
40→19 MBrace.FsPickler.Combinators.Pickler uses MBrace.FsPickler✕
- Connections
- 2 pairs of types, where a type in MBrace.FsPickler.Combinators.Pickler uses a type in MBrace.FsPickler.
- The types involved
MBrace.FsPickler.Combinators.Pickler.Pickler→MBrace.FsPickler.PicklerMBrace.FsPickler.Combinators.Pickler.Pickler→MBrace.FsPickler.Pickler`1
- Direction
- MBrace.FsPickler.Combinators.Pickler uses MBrace.FsPickler, so a change to MBrace.FsPickler can break MBrace.FsPickler.Combinators.Pickler, while a change to MBrace.FsPickler.Combinators.Pickler can't break MBrace.FsPickler.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Pickler uses a module listed above it, which is the healthy direction.
40→23 MBrace.FsPickler.Combinators.Pickler uses MBrace.FsPickler.Combinators.Pickler.ProductInternals✕
- Connections
- 1 pair of types, where a type in MBrace.FsPickler.Combinators.Pickler uses a type in MBrace.FsPickler.Combinators.Pickler.ProductInternals.
- The types involved
MBrace.FsPickler.Combinators.Pickler.Pickler→MBrace.FsPickler.Combinators.Pickler.ProductInternals.Wrap`1
- Direction
- MBrace.FsPickler.Combinators.Pickler uses MBrace.FsPickler.Combinators.Pickler.ProductInternals, so a change to MBrace.FsPickler.Combinators.Pickler.ProductInternals can break MBrace.FsPickler.Combinators.Pickler, while a change to MBrace.FsPickler.Combinators.Pickler can't break MBrace.FsPickler.Combinators.Pickler.ProductInternals.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Pickler uses a module listed above it, which is the healthy direction.
40→24 MBrace.FsPickler.Combinators.Pickler uses MBrace.FsPickler.Combinators.Pickler.SumInternals✕
- Connections
- 2 pairs of types, where a type in MBrace.FsPickler.Combinators.Pickler uses a type in MBrace.FsPickler.Combinators.Pickler.SumInternals.
- The types involved
MBrace.FsPickler.Combinators.Pickler.Pickler→MBrace.FsPickler.Combinators.Pickler.SumInternals.Case`2MBrace.FsPickler.Combinators.Pickler.Pickler→MBrace.FsPickler.Combinators.Pickler.SumInternals.Wrap`1
- Direction
- MBrace.FsPickler.Combinators.Pickler uses MBrace.FsPickler.Combinators.Pickler.SumInternals, so a change to MBrace.FsPickler.Combinators.Pickler.SumInternals can break MBrace.FsPickler.Combinators.Pickler, while a change to MBrace.FsPickler.Combinators.Pickler can't break MBrace.FsPickler.Combinators.Pickler.SumInternals.
- Position
- Below the diagonal: MBrace.FsPickler.Combinators.Pickler 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 |
|---|---|---|
| A02:2025 — Security Misconfiguration | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 40 Orphaned file finding(s) in Knowledge Freshness — start with FSharpTypeGen.fs, PicklerEmit.fs, TextSerializer.fs; Resolve the 23 Outdated finding(s) in Dependency 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 40 Orphaned file finding(s) in Knowledge Freshness — start with FSharpTypeGen.fs, PicklerEmit.fs, TextSerializer.fs. | +11.2 pts | Medium | Knowledge Freshness |
| Resolve the 23 Outdated finding(s) in Dependency Hygiene. | +8.5 pts | Medium | Dependency 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. | +8.5 pts | Medium | Architecture documentation |
| Resolve the 4 Deprecated finding(s) in Dependency Hygiene. | +1.5 pts | Low | Dependency Hygiene |
| 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. | +2.6 pts | Medium | Documentation (README) |
| Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with CompositePickler.fs, Serializer.fs. | +1.1 pts | Low | Knowledge Freshness |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.0 pts | Medium | Deployment & Rollback |
| Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. | +0.5 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| src/FsPickler/Combinators/Array.fs | 7.0 | Mixed | Cyclomatic Complexity: ArrayPickler.Create4D (cyclomatic 20) |
| src/FsPickler/Pickler/CompositePickler.fs | 7.0 | Mixed | Cyclomatic Complexity: CompositePickler`1.Clone (cyclomatic 28) |
| src/FsPickler/Combinators/Tuple.fs | 7.0 | Mixed | Code Duplication: Duplicated block (8 lines × 2) |
| src/FsPickler/Pickler/ReflectionCache.fs | 7.2 | Mixed | Cyclomatic Complexity: ReflectionCache.loadMemberInfo (cyclomatic 32) |
| src/FsPickler/PicklerGeneration/DataContractPickler.fs | 7.2 | Mixed | Cyclomatic Complexity: DataContractPickler.Create (cyclomatic 22) |
| src/FsPickler/Format/BinaryFormat.fs | 7.4 | Mixed | Cognitive Complexity: BinaryPickleReader.MBrace.FsPickler.IPickleFormatReader.BeginReadRoot (cognitive 17) |
| src/FsPickler/PicklerGeneration/FieldPicklers.fs | 7.8 | Mixed | Cyclomatic Complexity: ClassFieldPickler.Create (cyclomatic 23) |
| src/FsPickler/Utils/Hashing.fs | 7.8 | Mixed | Cognitive Complexity: MurMur3Stream.Write (cognitive 23) |
| src/FsPickler/Utils/Reflection.fs | 7.8 | Mixed | Cognitive Complexity: Reflection.isPolymorphicRecursive (cognitive 20) |
| src/FsPickler.Json/JsonReader.fs | 7.8 | Mixed | Cognitive Complexity: JsonPickleReader.MBrace.FsPickler.IPickleFormatReader.BeginReadRoot (cognitive 17) |
| src/FsPickler/Format/XmlFormat.fs | 7.8 | Mixed | God Classes: TooManyMethods: XmlPickleWriter |
| src/FsPickler/PicklerGeneration/ISerializablePickler.fs | 7.8 | Mixed | Code Duplication: Duplicated block (8–10 lines × 2) |
| src/FsPickler/PicklerGeneration/PicklerGenerator.fs | 8.5 | Near-clean | Cyclomatic Complexity: PicklerGenerator.Create (cyclomatic 79) |
| src/FsPickler/Combinators/DotNetTypes.fs | 8.5 | Near-clean | Cognitive Complexity: DelegatePickler.Create (cognitive 25) |
| src/FsPickler/PicklerGeneration/PicklerEmit.fs | 8.5 | Near-clean | Cognitive Complexity: PicklerEmit.emitCloneMembers (cognitive 19) |
| src/FsPickler/Combinators/FSharpList.fs | 8.5 | Near-clean | Cognitive Complexity: ListPickler.Create (cognitive 17) |
| src/FsPickler/PicklerGeneration/FSharpTypeGen.fs | 8.5 | Near-clean | Cognitive Complexity: FsUnionPickler.Create (cognitive 16) |
| src/FsPickler.Json/JsonWriter.fs | 8.5 | Near-clean | God Classes: TooManyMethods: JsonPickleWriter |
| src/FsPickler/FsPickler/BinarySerializer.fs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (28 corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 30 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 30 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 105 of 170 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's projects are MSBuild/NuGet projects, whose package licenses are exactly what this dimension reads, but no license could be resolved for them (the .NET license collector did not run, or restore failed). A gap in the analysis run, NOT a finding that the repository's licenses are compliant.
- D15 Churn × Complexity Hotspots — 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/FsPickler/Pickler/ReflectionCache.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 (19 contributor(s) across 1113 commit(s) sampled, automation and bot accounts excluded). One of them holds 94% of the history; the other 18 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — 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.
- 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- 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.
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PicklerGenerator.Create at 79. 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 ReflectionPicklers.CreateMemberInfoPickler at 30 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/FsPickler/Pickler/ReflectionPicklers.fs (ReflectionPicklers.CreateMemberInfoPickler at 30), src/FsPickler/Combinators/FSharpTypes.fs (ChoicePickler.Create at 29). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with PicklerGenerator.Create (cyclomatic 79), ReflectionCache.loadMemberInfo (cyclomatic 32). — 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 Cyclomatic Complexity from 7.4 to about 8.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
21 method(s) exceeded the cognitive complexity threshold of 15; the worst was CompositePickler`1.Clone at 66.
What to do
- Bring the 21 bodies over 15 down to 15 or less in Cognitive Complexity — start with CompositePickler`1.Clone (cognitive 66), ArrayPickler.Create4D (cognitive 58), CompositePickler`1.Accept (cognitive 49). — 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 21 together lifts Cognitive Complexity from 6.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 6 TooManyMethods finding(s) in God Classes — start with BinaryFormat.fs (2), XmlFormat.fs (2), JsonWriter.fs. — One of this dimension's main actionable groups (6 warning-level).
D4 · Code Duplication
18 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 2 Duplicated block (7–8 lines × 2) finding(s) in Code Duplication — start with DataContractPickler.fs, Hashing.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (6 lines × 4) finding(s) in Code Duplication — start with Tuple.fs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Pickler.fs, ISerializablePickler.fs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
4 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 22 classes have LCOM4 above 3.
D12 · Dependency Hygiene
52 outdated, 4 vulnerable, 4 deprecated, 1 prerelease packages.
What to do
- Resolve the 23 Outdated finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (23 recommendation-level).
- Resolve the 4 Deprecated finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: src/FsPickler/Pickler/ReflectionCache.fs (3×32=96)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with ReflectionCache.fs. — One of this dimension's main actionable groups (1 warning-level).
D26 · Project Cohesion
1 of 2 build units (MSBuild) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
90 % of calls cross a namespace and 6 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D31 · IaC & Container Security
3 finding(s): 0 critical, 2 high, 1 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
42 of 42 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/FsPickler/Pickler/CompositePickler.fs. Counted over 42 of the 52 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 40 Orphaned file finding(s) in Knowledge Freshness — start with FSharpTypeGen.fs, PicklerEmit.fs, TextSerializer.fs. — One of this dimension's main actionable groups (40 recommendation-level).
- Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with CompositePickler.fs, Serializer.fs. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 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
AX3 · Project dependency cycles
AX4 · Dependency direction
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
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.
- `docs/tools/packages.config` 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`. — docs/tools/packages.config:3
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
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
- A F#/VB BenchmarkDotNet suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — tests/FsPickler.Benchmarks/Serializers.fs
What to do
- Add [<MemoryDiagnoser>] to the benchmarks so allocation regressions are visible, not just time.
X27 · Collection changed while being enumerated
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 78% | Checked 4 of 11 | Solid. |
| Architecture | 93% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 43% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47% | Weak — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 98% | Checked 5 of 11 | Strongest area. |
| Performance | 85% | Strong | 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 — 82 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads.
- 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
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) 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 — ~2637 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D14 License Compliance — Package licences not resolved for an MSBuild/NuGet repository
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- 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
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan; nuget packages.config: the scanner produced no output at all, so no dependency was actually scanned
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — osv: the scanner produced no output at all, so no dependency was actually scanned
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (30 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'.
- P2 Observability — This repository's F# source (2 module(s), 52 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — 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.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 2 finding(s)
- REDACTED
- REDACTED
Serious — 65 finding(s)
- TooManyMethods: JsonPickleWriter src/FsPickler.Json/JsonWriter.fs:16
- TooManyMethods: BinaryPickleWriter src/FsPickler/Format/BinaryFormat.fs:110
- TooManyMethods: XmlPickleWriter src/FsPickler/Format/XmlFormat.fs:114
- TooManyMethods: JsonPickleReader src/FsPickler.Json/JsonReader.fs:19
- TooManyMethods: BinaryPickleReader src/FsPickler/Format/BinaryFormat.fs:206
- TooManyMethods: XmlPickleReader src/FsPickler/Format/XmlFormat.fs:210
- Deprecated: Microsoft.DotNet.InternalAbstractions
- Deprecated: NuGet.Frameworks
- Deprecated: System.Collections.Immutable
- Deprecated: Wire
- Duplicated block (7–8 lines × 2) src/FsPickler/PicklerGeneration/DataContractPickler.fs:186
- Duplicated block (7–8 lines × 2) src/FsPickler/Utils/Hashing.fs:36
- Duplicated block (6 lines × 4) src/FsPickler/Combinators/Tuple.fs:119
- Duplicated block (6 lines × 4) src/FsPickler/Combinators/Tuple.fs:143
- Duplicated block (5 lines × 2) src/FsPickler/Pickler/Pickler.fs:98
- Duplicated block (5 lines × 2) src/FsPickler/PicklerGeneration/ISerializablePickler.fs:129
- PicklerGenerator.Create (cyclomatic 79) src/FsPickler/PicklerGeneration/PicklerGenerator.fs:29
- ReflectionCache.loadMemberInfo (cyclomatic 32) src/FsPickler/Pickler/ReflectionCache.fs:181
- CompositePickler`1.Clone (cyclomatic 28) src/FsPickler/Pickler/CompositePickler.fs:324
- ReflectionCache.getMemberInfo (cyclomatic 26) src/FsPickler/Pickler/ReflectionCache.fs:86
- ClassFieldPickler.Create (cyclomatic 23) src/FsPickler/PicklerGeneration/FieldPicklers.fs:115
- DataContractPickler.Create (cyclomatic 22) src/FsPickler/PicklerGeneration/DataContractPickler.fs:20
- CompositePickler`1.Accept (cyclomatic 21) src/FsPickler/Pickler/CompositePickler.fs:423
- CompositePickler`1.Write (cyclomatic 21) src/FsPickler/Pickler/CompositePickler.fs:163
- ArrayPickler.Create4D (cyclomatic 20) src/FsPickler/Combinators/Array.fs:262
- ArrayPickler.Create3D (cyclomatic 16) src/FsPickler/Combinators/Array.fs:195
- CompositePickler`1.Read (cyclomatic 16) src/FsPickler/Pickler/CompositePickler.fs:244
- Prerelease dependency: FsCheck
- Hotspot: src/FsPickler/Pickler/ReflectionCache.fs src/FsPickler/Pickler/ReflectionCache.fs:181
- CompositePickler`1.Clone (cognitive 66) src/FsPickler/Pickler/CompositePickler.fs:324
- ArrayPickler.Create4D (cognitive 58) src/FsPickler/Combinators/Array.fs:262
- CompositePickler`1.Accept (cognitive 49) src/FsPickler/Pickler/CompositePickler.fs:423
- CompositePickler`1.Write (cognitive 48) src/FsPickler/Pickler/CompositePickler.fs:163
- DataContractPickler.Create (cognitive 43) src/FsPickler/PicklerGeneration/DataContractPickler.fs:20
- ArrayPickler.Create3D (cognitive 39) src/FsPickler/Combinators/Array.fs:195
- ReflectionCache.getMemberInfo (cognitive 37) src/FsPickler/Pickler/ReflectionCache.fs:86
- CompositePickler`1.Read (cognitive 34) src/FsPickler/Pickler/CompositePickler.fs:244
- DelegatePickler.Create (cognitive 25) src/FsPickler/Combinators/DotNetTypes.fs:83
- ArrayPickler.Create2D (cognitive 24) src/FsPickler/Combinators/Array.fs:133
- MurMur3Stream.Write (cognitive 23) src/FsPickler/Utils/Hashing.fs:233
- ClassFieldPickler.Create (cognitive 21) src/FsPickler/PicklerGeneration/FieldPicklers.fs:115
- ArrayPickler.Create (cognitive 21) src/FsPickler/Combinators/Array.fs:46
- Reflection.isPolymorphicRecursive (cognitive 20) src/FsPickler/Utils/Reflection.fs:184
- PicklerEmit.emitCloneMembers (cognitive 19) src/FsPickler/PicklerGeneration/PicklerEmit.fs:159
- ReflectionCache.loadMemberInfo (cognitive 19) src/FsPickler/Pickler/ReflectionCache.fs:181
- JsonPickleReader.MBrace.FsPickler.IPickleFormatReader.BeginReadRoot (cognitive 17) src/FsPickler.Json/JsonReader.fs:45
- BinaryPickleReader.MBrace.FsPickler.IPickleFormatReader.BeginReadRoot (cognitive 17) src/FsPickler/Format/BinaryFormat.fs:216
- ListPickler.Create (cognitive 17) src/FsPickler/Combinators/FSharpList.fs:9
- FsUnionPickler.Create (cognitive 16) src/FsPickler/PicklerGeneration/FSharpTypeGen.fs:25
- Reflection.isRecursiveType (cognitive 16) src/FsPickler/Utils/Reflection.fs:228
- REDACTED
- Edited copy of a member (28 corresponding lines) src/FsPickler/FsPickler/BinarySerializer.fs:1
- Duplicated block (13 lines × 2) src/FsPickler/Combinators/Array.fs:216
- Duplicated block (12 lines × 2) src/FsPickler/Pickler/CompositePickler.fs:306
- Duplicated block (10–11 lines × 2) src/FsPickler/Combinators/Array.fs:198
- Duplicated block (9–10 lines × 3) src/FsPickler/Combinators/Array.fs:136
- Duplicated block (8–10 lines × 2) src/FsPickler/PicklerGeneration/ISerializablePickler.fs:187
- Duplicated block (9 lines × 3) src/FsPickler/Combinators/Array.fs:156
- Duplicated block (8 lines × 2) src/FsPickler/Combinators/Tuple.fs:209
- Duplicated block (7 lines × 3) src/FsPickler/Combinators/Tuple.fs:161
- Duplicated block (7 lines × 2) src/FsPickler/PicklerGeneration/DataContractPickler.fs:190
- Duplicated block (6 lines × 2) src/FsPickler/Combinators/Tuple.fs:198
- Duplicated block (5 lines × 3) src/FsPickler/Combinators/Tuple.fs:152
- Duplicated block (5 lines × 4) src/FsPickler/Combinators/Tuple.fs:170
- NuGet dependencies are not locked
Minor — 74 finding(s)
- Orphaned file src/FsPickler/PicklerGeneration/FSharpTypeGen.fs:1
- Orphaned file src/FsPickler/PicklerGeneration/PicklerEmit.fs:1
- Orphaned file src/FsPickler/FsPickler/TextSerializer.fs:1
- Orphaned file src/FsPickler/Combinators/FSharpTypes.fs:1
- Orphaned file src/FsPickler/Format/XmlFormat.fs:1
- Orphaned file src/FsPickler/Pickler/ReflectionCache.fs:1
- Orphaned file src/FsPickler/PicklerGeneration/ISerializablePickler.fs:1
- Orphaned file src/FsPickler/PicklerGeneration/PicklerGenerator.fs:1
- Orphaned file src/FsPickler/Combinators/Tuple.fs:1
- Orphaned file src/FsPickler/Combinators/Array.fs:1
- Orphaned file src/FsPickler/PicklerGeneration/FieldPicklers.fs:1
- Orphaned file src/FsPickler/FsPickler/FsPickler.fs:1
- Orphaned file src/FsPickler/Format/BinaryFormat.fs:1
- Orphaned file src/FsPickler/Pickler/Types.fs:1
- Orphaned file src/FsPickler/Pickler/ReflectionPicklers.fs:1
- Orphaned file src/FsPickler/PicklerGeneration/DataContractPickler.fs:1
- Orphaned file src/FsPickler/FsPickler/Combinators.fs:1
- Orphaned file src/FsPickler.Json/JsonReader.fs:1
- Orphaned file src/FsPickler/Utils/Reflection.fs:1
- Orphaned file src/FsPickler/Pickler/Pickler.fs:1
- Orphaned file src/FsPickler/Utils/TypeShapeExtensions.fs:1
- Orphaned file src/FsPickler/Utils/Hashing.fs:1
- Orphaned file src/FsPickler/FsPickler/ExtensionMethods.fs:1
- Orphaned file src/FsPickler/Pickler/PrimitivePicklers.fs:1
- Orphaned file src/FsPickler/Utils/Utils.fs:1
- Outdated: FSharp.Core
- Outdated: FsUnit
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: Microsoft.NETCore.Platforms
- Outdated: NuGet.Frameworks
- Outdated: NUnit3TestAdapter
- Outdated: Microsoft.Build.Tasks.Git
- Outdated: Microsoft.SourceLink.Common
- Outdated: Microsoft.SourceLink.GitHub
- Outdated: System.Runtime.Serialization.Formatters
- Outdated: Microsoft.CodeAnalysis.Analyzers
- Outdated: Microsoft.Win32.SystemEvents
- Outdated: System.CodeDom
- Outdated: System.Collections.Immutable
- Outdated: System.Drawing.Common
- Outdated: System.Management
- Outdated: System.Reflection.Metadata
- Outdated: System.Security.Cryptography.Pkcs
- Outdated: System.Security.Cryptography.Xml
- Outdated: System.Security.Permissions
- Outdated: System.ServiceModel.Primitives
- Outdated: System.Text.Encoding.CodePages
- Outdated: System.Windows.Extensions
- Most significant orphaned file src/FsPickler/Pickler/CompositePickler.fs:1
- Most significant orphaned file src/FsPickler/FsPickler/Serializer.fs:1
- Projects may be oversized for their cohesion
- Dormant codebase
- REDACTED
- No ADRs
- No architecture diagram/doc
- CI test execution not evidenced
- No SAST
- No dependency-update automation docs/tools/packages.config:3
- Benchmarks don't track allocations tests/FsPickler.Benchmarks/Serializers.fs
Minor — 29 finding(s)
- Outdated: FsCheck
- Outdated: Microsoft.CodeCoverage
- Outdated: Microsoft.NETCore.Targets
- Outdated: Microsoft.TestPlatform.ObjectModel
- Outdated: Microsoft.TestPlatform.TestHost
- Outdated: Microsoft.Win32.Registry
- Outdated: Newtonsoft.Json
- Outdated: NUnit
- Outdated: System.Runtime.CompilerServices.Unsafe
- Outdated: System.Security.AccessControl
- Outdated: System.Security.Principal.Windows
- Outdated: System.Threading.Tasks.Extensions
- Outdated: System.ValueTuple
- Outdated: System.Xml.XPath.XmlDocument
- Outdated: System.Reflection.Emit.Lightweight
- Outdated: BenchmarkDotNet
- Outdated: BenchmarkDotNet.Annotations
- Outdated: CommandLineParser
- Outdated: Microsoft.CodeAnalysis.Common
- Outdated: Microsoft.CodeAnalysis.CSharp
- Outdated: Microsoft.DotNet.PlatformAbstractions
- Outdated: protobuf-net
- Outdated: System.Memory
- Outdated: System.Private.ServiceModel
- Outdated: System.Reflection.DispatchProxy
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-cedf49af15bc4f999e798b7a19bd1ea7/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-cedf49af15bc4f999e798b7a19bd1ea7/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 .paket/load . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan; nuget packages.config: the scanner produced no output at all, so no dependency was actually scanned | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |