Executive summary
krauthaufen/Adaptify falls short of our standard for production because 13 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 58 out of 100 and is rated Adequate, and 14 of its 17 critical findings are security problems in the build pipeline and in the packages it uses.
Maturity, at 44, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 13 points. Having someone learn and document the 13 files no active contributor knows comes next, worth about 10 points. Raising Maturity to 70 would lift the score to about 69.
Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five known security holes in the packages the code depends on can be used by attackers, and three parts of the code are no longer understood by anyone working on it. Having someone learn the forgotten files, pinning each tool to an exact version and updating the vulnerable packages would close these risks.
The product code is 6,949 lines, about €6,400 to rebuild.
If Maturity rose from 44 to 70, the lowest score rated Strong, the score would rise from 58 to about 69.
New since the last survey: 6 findings
- Code Coverage · Low coverage: src/Adaptify.Compiler/Process.fs src/Adaptify.Compiler/Process.fs
- Code Coverage · Low coverage: src/Adaptify.Compiler/Server.fs src/Adaptify.Compiler/Server.fs
- Code Coverage · Low coverage: src/Adaptify.Compiler/Cache.fs src/Adaptify.Compiler/Cache.fs
- Code Coverage · Low coverage: src/Adaptify.Compiler/ProjectInfo.fs src/Adaptify.Compiler/ProjectInfo.fs
- Code Coverage · Low coverage: src/Adaptify.Compiler/CoreTypes.fs src/Adaptify.Compiler/CoreTypes.fs
- Code Coverage · Low coverage: src/Adaptify.Compiler/Scope.fs src/Adaptify.Compiler/Scope.fs
Fixed since the last survey: 1 finding
- Code Duplication · Duplicated block (4–6 lines × 3) src/Adaptify.Compiler/Adaptor.fs
Rebuild cost: about €6,400 · Estimate
| Cost to rebuild | €2,100 to €11,000, for 35 to 111 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, 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 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,949 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 Aardvark.Compiler | 2 Adaptify | 3 Adaptify.Compiler | 4 Aardvark.Compiler.CacheFileModule | 5 Aardvark.Compiler.WarningModule | 6 Adaptify.Compiler.Adaptify | 7 Adaptify.Compiler.AdaptifyModeModule | 8 Adaptify.Compiler.AdaptiveTypes | 9 Adaptify.Compiler.AdaptiveTypes.AList | 10 Adaptify.Compiler.AdaptiveTypes.AMap | 11 Adaptify.Compiler.AdaptiveTypes.ASet | 12 Adaptify.Compiler.AdaptiveTypes.AVal | 13 Adaptify.Compiler.AdaptiveTypes.AbstractAdaptiveValue | 14 Adaptify.Compiler.AdaptiveTypes.AdaptiveObject | 15 Adaptify.Compiler.AdaptiveTypes.AdaptiveToken | 16 Adaptify.Compiler.AdaptiveTypes.Adaptor | 17 Adaptify.Compiler.AdaptiveTypes.CList | 18 Adaptify.Compiler.AdaptiveTypes.CMap | 19 Adaptify.Compiler.AdaptiveTypes.CSet | 20 Adaptify.Compiler.AdaptiveTypes.CVal | 21 Adaptify.Compiler.AdaptiveTypes.CValCustomEquality | 22 Adaptify.Compiler.AdaptiveTypes.ChangeableListArray | 23 Adaptify.Compiler.AdaptiveTypes.ChangeableListList | 24 Adaptify.Compiler.AdaptiveTypes.ChangeableModelList | 25 Adaptify.Compiler.AdaptiveTypes.ChangeableModelListArray | 26 Adaptify.Compiler.AdaptiveTypes.ChangeableModelListList | 27 Adaptify.Compiler.AdaptiveTypes.ChangeableModelMap | 28 Adaptify.Compiler.AdaptiveTypes.HashMap | 29 Adaptify.Compiler.AdaptiveTypes.HashSet | 30 Adaptify.Compiler.AdaptiveTypes.IndexList | 31 Adaptify.Compiler.AdaptiveTypes.Lazy | 32 Adaptify.Compiler.AdaptiveTypes.List | 33 Adaptify.Compiler.AdaptiveTypes.Object | 34 Adaptify.Compiler.AdaptiveTypes.Option | 35 Adaptify.Compiler.AdaptiveTypes.Transaction | 36 Adaptify.Compiler.AdaptorModule | 37 Adaptify.Compiler.Client | 38 Adaptify.Compiler.IPC | 39 Adaptify.FSharp.Core | 40 Adaptify.Compiler.Server |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Aardvark.Compiler | ||||||||||||||||||||||||||||||||||||||||
| 2 Adaptify | ||||||||||||||||||||||||||||||||||||||||
| 3 Adaptify.Compiler | ||||||||||||||||||||||||||||||||||||||||
| 4 Aardvark.Compiler.CacheFileModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 5 Aardvark.Compiler.WarningModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 Adaptify.Compiler.Adaptify | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 Adaptify.Compiler.AdaptifyModeModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 Adaptify.Compiler.AdaptiveTypes | 3 | |||||||||||||||||||||||||||||||||||||||
| 9 Adaptify.Compiler.AdaptiveTypes.AList | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Adaptify.Compiler.AdaptiveTypes.AMap | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Adaptify.Compiler.AdaptiveTypes.ASet | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Adaptify.Compiler.AdaptiveTypes.AVal | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 Adaptify.Compiler.AdaptiveTypes.AbstractAdaptiveValue | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Adaptify.Compiler.AdaptiveTypes.AdaptiveObject | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 Adaptify.Compiler.AdaptiveTypes.AdaptiveToken | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Adaptify.Compiler.AdaptiveTypes.Adaptor | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 Adaptify.Compiler.AdaptiveTypes.CList | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 Adaptify.Compiler.AdaptiveTypes.CMap | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 Adaptify.Compiler.AdaptiveTypes.CSet | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 Adaptify.Compiler.AdaptiveTypes.CVal | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 Adaptify.Compiler.AdaptiveTypes.CValCustomEquality | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 Adaptify.Compiler.AdaptiveTypes.ChangeableListArray | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Adaptify.Compiler.AdaptiveTypes.ChangeableListList | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 Adaptify.Compiler.AdaptiveTypes.ChangeableModelList | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 Adaptify.Compiler.AdaptiveTypes.ChangeableModelListArray | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 Adaptify.Compiler.AdaptiveTypes.ChangeableModelListList | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 Adaptify.Compiler.AdaptiveTypes.ChangeableModelMap | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 Adaptify.Compiler.AdaptiveTypes.HashMap | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 Adaptify.Compiler.AdaptiveTypes.HashSet | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 Adaptify.Compiler.AdaptiveTypes.IndexList | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 Adaptify.Compiler.AdaptiveTypes.Lazy | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 Adaptify.Compiler.AdaptiveTypes.List | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 Adaptify.Compiler.AdaptiveTypes.Object | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 Adaptify.Compiler.AdaptiveTypes.Option | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 Adaptify.Compiler.AdaptiveTypes.Transaction | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 Adaptify.Compiler.AdaptorModule | 6 | |||||||||||||||||||||||||||||||||||||||
| 37 Adaptify.Compiler.Client | 2 | |||||||||||||||||||||||||||||||||||||||
| 38 Adaptify.Compiler.IPC | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 Adaptify.FSharp.Core | 5 | |||||||||||||||||||||||||||||||||||||||
| 40 Adaptify.Compiler.Server | 2 | 1 |
4→1 Aardvark.Compiler.CacheFileModule uses Aardvark.Compiler✕
- Connections
- 1 pair of types, where a type in Aardvark.Compiler.CacheFileModule uses a type in Aardvark.Compiler.
- The types involved
Aardvark.Compiler.CacheFileModule.CacheFileModule→Aardvark.Compiler.CacheFile
- Direction
- Aardvark.Compiler.CacheFileModule uses Aardvark.Compiler, so a change to Aardvark.Compiler can break Aardvark.Compiler.CacheFileModule, while a change to Aardvark.Compiler.CacheFileModule can't break Aardvark.Compiler.
- Position
- Below the diagonal: Aardvark.Compiler.CacheFileModule uses a module listed above it, which is the healthy direction.
4→3 Aardvark.Compiler.CacheFileModule uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Aardvark.Compiler.CacheFileModule uses a type in Adaptify.Compiler.
- The types involved
Aardvark.Compiler.CacheFileModule.CacheFileModule→Adaptify.Compiler.ILog
- Direction
- Aardvark.Compiler.CacheFileModule uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Aardvark.Compiler.CacheFileModule, while a change to Aardvark.Compiler.CacheFileModule can't break Adaptify.Compiler.
- Position
- Below the diagonal: Aardvark.Compiler.CacheFileModule uses a module listed above it, which is the healthy direction.
5→1 Aardvark.Compiler.WarningModule uses Aardvark.Compiler✕
- Connections
- 1 pair of types, where a type in Aardvark.Compiler.WarningModule uses a type in Aardvark.Compiler.
- The types involved
Aardvark.Compiler.WarningModule.WarningModule→Aardvark.Compiler.Warning
- Direction
- Aardvark.Compiler.WarningModule uses Aardvark.Compiler, so a change to Aardvark.Compiler can break Aardvark.Compiler.WarningModule, while a change to Aardvark.Compiler.WarningModule can't break Aardvark.Compiler.
- Position
- Below the diagonal: Aardvark.Compiler.WarningModule uses a module listed above it, which is the healthy direction.
6→3 Adaptify.Compiler.Adaptify uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.Adaptify uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.Adaptify.Adaptify→Adaptify.Compiler.ILogAdaptify.Compiler.Adaptify.Adaptify→Adaptify.Compiler.ProjectInfo
- Direction
- Adaptify.Compiler.Adaptify uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.Adaptify, while a change to Adaptify.Compiler.Adaptify can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.Adaptify uses a module listed above it, which is the healthy direction.
7→3 Adaptify.Compiler.AdaptifyModeModule uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptifyModeModule uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptifyModeModule.AdaptifyModeModule→Adaptify.Compiler.AdaptifyModeAdaptify.Compiler.AdaptifyModeModule.AdaptifyModeModule→Adaptify.Compiler.ILog
- Direction
- Adaptify.Compiler.AdaptifyModeModule uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptifyModeModule, while a change to Adaptify.Compiler.AdaptifyModeModule can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptifyModeModule uses a module listed above it, which is the healthy direction.
8→3 Adaptify.Compiler.AdaptiveTypes uses Adaptify.Compiler✕
- Connections
- 3 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.AdaptiveTypes→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.AdaptiveTypes→Adaptify.Compiler.ScopeAdaptify.Compiler.AdaptiveTypes.AdaptiveTypes→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes, while a change to Adaptify.Compiler.AdaptiveTypes can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes uses a module listed above it, which is the healthy direction.
9→3 Adaptify.Compiler.AdaptiveTypes.AList uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.AdaptiveTypes.AList uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.AList.AList→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.AList uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.AList, while a change to Adaptify.Compiler.AdaptiveTypes.AList can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.AList uses a module listed above it, which is the healthy direction.
10→3 Adaptify.Compiler.AdaptiveTypes.AMap uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.AdaptiveTypes.AMap uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.AMap.AMap→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.AMap uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.AMap, while a change to Adaptify.Compiler.AdaptiveTypes.AMap can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.AMap uses a module listed above it, which is the healthy direction.
11→3 Adaptify.Compiler.AdaptiveTypes.ASet uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.AdaptiveTypes.ASet uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.ASet.ASet→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.ASet uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.ASet, while a change to Adaptify.Compiler.AdaptiveTypes.ASet can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.ASet uses a module listed above it, which is the healthy direction.
12→3 Adaptify.Compiler.AdaptiveTypes.AVal uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.AVal uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.AVal.AVal→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.AVal.AVal→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.AVal uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.AVal, while a change to Adaptify.Compiler.AdaptiveTypes.AVal can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.AVal uses a module listed above it, which is the healthy direction.
13→3 Adaptify.Compiler.AdaptiveTypes.AbstractAdaptiveValue uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.AdaptiveTypes.AbstractAdaptiveValue uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.AbstractAdaptiveValue.AbstractAdaptiveValue→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.AbstractAdaptiveValue uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.AbstractAdaptiveValue, while a change to Adaptify.Compiler.AdaptiveTypes.AbstractAdaptiveValue can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.AbstractAdaptiveValue uses a module listed above it, which is the healthy direction.
14→3 Adaptify.Compiler.AdaptiveTypes.AdaptiveObject uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.AdaptiveObject uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.AdaptiveObject.AdaptiveObject→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.AdaptiveObject.AdaptiveObject→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.AdaptiveObject uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.AdaptiveObject, while a change to Adaptify.Compiler.AdaptiveTypes.AdaptiveObject can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.AdaptiveObject uses a module listed above it, which is the healthy direction.
15→3 Adaptify.Compiler.AdaptiveTypes.AdaptiveToken uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.AdaptiveTypes.AdaptiveToken uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.AdaptiveToken.AdaptiveToken→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.AdaptiveToken uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.AdaptiveToken, while a change to Adaptify.Compiler.AdaptiveTypes.AdaptiveToken can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.AdaptiveToken uses a module listed above it, which is the healthy direction.
16→3 Adaptify.Compiler.AdaptiveTypes.Adaptor uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.Adaptor uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.Adaptor.Adaptor→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.Adaptor.Adaptor→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.Adaptor uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.Adaptor, while a change to Adaptify.Compiler.AdaptiveTypes.Adaptor can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.Adaptor uses a module listed above it, which is the healthy direction.
17→3 Adaptify.Compiler.AdaptiveTypes.CList uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.CList uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.CList.CList→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.CList.CList→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.CList uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.CList, while a change to Adaptify.Compiler.AdaptiveTypes.CList can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.CList uses a module listed above it, which is the healthy direction.
18→3 Adaptify.Compiler.AdaptiveTypes.CMap uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.CMap uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.CMap.CMap→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.CMap.CMap→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.CMap uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.CMap, while a change to Adaptify.Compiler.AdaptiveTypes.CMap can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.CMap uses a module listed above it, which is the healthy direction.
19→3 Adaptify.Compiler.AdaptiveTypes.CSet uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.CSet uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.CSet.CSet→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.CSet.CSet→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.CSet uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.CSet, while a change to Adaptify.Compiler.AdaptiveTypes.CSet can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.CSet uses a module listed above it, which is the healthy direction.
20→3 Adaptify.Compiler.AdaptiveTypes.CVal uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.CVal uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.CVal.CVal→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.CVal.CVal→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.CVal uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.CVal, while a change to Adaptify.Compiler.AdaptiveTypes.CVal can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.CVal uses a module listed above it, which is the healthy direction.
21→3 Adaptify.Compiler.AdaptiveTypes.CValCustomEquality uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.CValCustomEquality uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.CValCustomEquality.CValCustomEquality→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.CValCustomEquality.CValCustomEquality→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.CValCustomEquality uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.CValCustomEquality, while a change to Adaptify.Compiler.AdaptiveTypes.CValCustomEquality can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.CValCustomEquality uses a module listed above it, which is the healthy direction.
22→3 Adaptify.Compiler.AdaptiveTypes.ChangeableListArray uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.ChangeableListArray uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.ChangeableListArray.ChangeableListArray→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.ChangeableListArray.ChangeableListArray→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.ChangeableListArray uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.ChangeableListArray, while a change to Adaptify.Compiler.AdaptiveTypes.ChangeableListArray can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.ChangeableListArray uses a module listed above it, which is the healthy direction.
23→3 Adaptify.Compiler.AdaptiveTypes.ChangeableListList uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.ChangeableListList uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.ChangeableListList.ChangeableListList→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.ChangeableListList.ChangeableListList→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.ChangeableListList uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.ChangeableListList, while a change to Adaptify.Compiler.AdaptiveTypes.ChangeableListList can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.ChangeableListList uses a module listed above it, which is the healthy direction.
24→3 Adaptify.Compiler.AdaptiveTypes.ChangeableModelList uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.ChangeableModelList uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.ChangeableModelList.ChangeableModelList→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.ChangeableModelList.ChangeableModelList→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.ChangeableModelList uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.ChangeableModelList, while a change to Adaptify.Compiler.AdaptiveTypes.ChangeableModelList can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.ChangeableModelList uses a module listed above it, which is the healthy direction.
25→3 Adaptify.Compiler.AdaptiveTypes.ChangeableModelListArray uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.ChangeableModelListArray uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.ChangeableModelListArray.ChangeableModelListArray→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.ChangeableModelListArray.ChangeableModelListArray→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.ChangeableModelListArray uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.ChangeableModelListArray, while a change to Adaptify.Compiler.AdaptiveTypes.ChangeableModelListArray can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.ChangeableModelListArray uses a module listed above it, which is the healthy direction.
26→3 Adaptify.Compiler.AdaptiveTypes.ChangeableModelListList uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.ChangeableModelListList uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.ChangeableModelListList.ChangeableModelListList→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.ChangeableModelListList.ChangeableModelListList→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.ChangeableModelListList uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.ChangeableModelListList, while a change to Adaptify.Compiler.AdaptiveTypes.ChangeableModelListList can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.ChangeableModelListList uses a module listed above it, which is the healthy direction.
27→3 Adaptify.Compiler.AdaptiveTypes.ChangeableModelMap uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.ChangeableModelMap uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.ChangeableModelMap.ChangeableModelMap→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.ChangeableModelMap.ChangeableModelMap→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.ChangeableModelMap uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.ChangeableModelMap, while a change to Adaptify.Compiler.AdaptiveTypes.ChangeableModelMap can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.ChangeableModelMap uses a module listed above it, which is the healthy direction.
28→3 Adaptify.Compiler.AdaptiveTypes.HashMap uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.AdaptiveTypes.HashMap uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.HashMap.HashMap→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.HashMap uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.HashMap, while a change to Adaptify.Compiler.AdaptiveTypes.HashMap can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.HashMap uses a module listed above it, which is the healthy direction.
29→3 Adaptify.Compiler.AdaptiveTypes.HashSet uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.AdaptiveTypes.HashSet uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.HashSet.HashSet→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.HashSet uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.HashSet, while a change to Adaptify.Compiler.AdaptiveTypes.HashSet can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.HashSet uses a module listed above it, which is the healthy direction.
30→3 Adaptify.Compiler.AdaptiveTypes.IndexList uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.AdaptiveTypes.IndexList uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.IndexList.IndexList→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.IndexList uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.IndexList, while a change to Adaptify.Compiler.AdaptiveTypes.IndexList can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.IndexList uses a module listed above it, which is the healthy direction.
31→3 Adaptify.Compiler.AdaptiveTypes.Lazy uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.Lazy uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.Lazy.Lazy→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.Lazy.Lazy→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.Lazy uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.Lazy, while a change to Adaptify.Compiler.AdaptiveTypes.Lazy can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.Lazy uses a module listed above it, which is the healthy direction.
32→3 Adaptify.Compiler.AdaptiveTypes.List uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.AdaptiveTypes.List uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.List.List→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.List uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.List, while a change to Adaptify.Compiler.AdaptiveTypes.List can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.List uses a module listed above it, which is the healthy direction.
33→3 Adaptify.Compiler.AdaptiveTypes.Object uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.AdaptiveTypes.Object uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.Object.Object→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.Object uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.Object, while a change to Adaptify.Compiler.AdaptiveTypes.Object can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.Object uses a module listed above it, which is the healthy direction.
34→3 Adaptify.Compiler.AdaptiveTypes.Option uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.Option uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.Option.Option→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.Option.Option→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.Option uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.Option, while a change to Adaptify.Compiler.AdaptiveTypes.Option can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.Option uses a module listed above it, which is the healthy direction.
35→3 Adaptify.Compiler.AdaptiveTypes.Transaction uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.AdaptiveTypes.Transaction uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptiveTypes.Transaction.Transaction→Adaptify.Compiler.MethodAdaptify.Compiler.AdaptiveTypes.Transaction.Transaction→Adaptify.Compiler.TypeRef
- Direction
- Adaptify.Compiler.AdaptiveTypes.Transaction uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptiveTypes.Transaction, while a change to Adaptify.Compiler.AdaptiveTypes.Transaction can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptiveTypes.Transaction uses a module listed above it, which is the healthy direction.
36→3 Adaptify.Compiler.AdaptorModule uses Adaptify.Compiler✕
- Connections
- 6 pairs of types, where a type in Adaptify.Compiler.AdaptorModule uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.AdaptorModule.AdaptorModule→Adaptify.Compiler.AdaptorAdaptify.Compiler.AdaptorModule.AdaptorModule→Adaptify.Compiler.EqualityModeAdaptify.Compiler.AdaptorModule.AdaptorModule→Adaptify.Compiler.ILogAdaptify.Compiler.AdaptorModule.AdaptorModule→Adaptify.Compiler.ScopeAdaptify.Compiler.AdaptorModule.AdaptorModule→Adaptify.Compiler.TypeRefAdaptify.Compiler.AdaptorModule.AdaptorModule→Adaptify.Compiler.TypeVar
- Direction
- Adaptify.Compiler.AdaptorModule uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.AdaptorModule, while a change to Adaptify.Compiler.AdaptorModule can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.AdaptorModule uses a module listed above it, which is the healthy direction.
37→3 Adaptify.Compiler.Client uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.Client uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.Client.Client→Adaptify.Compiler.ILogAdaptify.Compiler.Client.Client→Adaptify.Compiler.ProjectInfo
- Direction
- Adaptify.Compiler.Client uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.Client, while a change to Adaptify.Compiler.Client can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.Client uses a module listed above it, which is the healthy direction.
38→3 Adaptify.Compiler.IPC uses Adaptify.Compiler✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.IPC uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.IPC.Command→Adaptify.Compiler.ProjectInfo
- Direction
- Adaptify.Compiler.IPC uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.IPC, while a change to Adaptify.Compiler.IPC can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.IPC uses a module listed above it, which is the healthy direction.
39→2 Adaptify.FSharp.Core uses Adaptify✕
- Connections
- 5 pairs of types, where a type in Adaptify.FSharp.Core uses a type in Adaptify.
- The types involved
Adaptify.FSharp.Core.AdaptiveChoice`12→Adaptify.AdaptiveValue`1Adaptify.FSharp.Core.AdaptiveChoice`6→Adaptify.AdaptiveValue`1Adaptify.FSharp.Core.AdaptiveChoice`9→Adaptify.AdaptiveValue`1Adaptify.FSharp.Core.AdaptiveOption`3→Adaptify.AdaptiveValue`1Adaptify.FSharp.Core.AdaptiveResult`6→Adaptify.AdaptiveValue`1
- Direction
- Adaptify.FSharp.Core uses Adaptify, so a change to Adaptify can break Adaptify.FSharp.Core, while a change to Adaptify.FSharp.Core can't break Adaptify.
- Position
- Below the diagonal: Adaptify.FSharp.Core uses a module listed above it, which is the healthy direction.
40→3 Adaptify.Compiler.Server uses Adaptify.Compiler✕
- Connections
- 2 pairs of types, where a type in Adaptify.Compiler.Server uses a type in Adaptify.Compiler.
- The types involved
Adaptify.Compiler.Server.Server→Adaptify.Compiler.ILogAdaptify.Compiler.Server.Server→Adaptify.Compiler.ProjectInfo
- Direction
- Adaptify.Compiler.Server uses Adaptify.Compiler, so a change to Adaptify.Compiler can break Adaptify.Compiler.Server, while a change to Adaptify.Compiler.Server can't break Adaptify.Compiler.
- Position
- Below the diagonal: Adaptify.Compiler.Server uses a module listed above it, which is the healthy direction.
40→38 Adaptify.Compiler.Server uses Adaptify.Compiler.IPC✕
- Connections
- 1 pair of types, where a type in Adaptify.Compiler.Server uses a type in Adaptify.Compiler.IPC.
- The types involved
Adaptify.Compiler.Server.Server→Adaptify.Compiler.IPC.Reply
- Direction
- Adaptify.Compiler.Server uses Adaptify.Compiler.IPC, so a change to Adaptify.Compiler.IPC can break Adaptify.Compiler.Server, while a change to Adaptify.Compiler.Server can't break Adaptify.Compiler.IPC.
- Position
- Below the diagonal: Adaptify.Compiler.Server uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 11 | High / Critical |
| A05:2025 — Injection | 9 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Adaptify.MSBuild.fsproj; 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; Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with Program.fs (2), Process.fs, Utilities.fs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Adaptify.MSBuild.fsproj. | +12.6 pts | Low | ADR Quality |
| Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with Program.fs (2), Process.fs, Utilities.fs. | +10.0 pts | Medium | Knowledge Freshness |
| Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with CoreInstances.fs, Adaptor.fs, Runner.fs. | +3.1 pts | Low | Knowledge Freshness |
| 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. | +11.2 pts | Medium | Architecture documentation |
| Resolve the 6 Low coverage finding(s) in Code Coverage — start with Process.fs, Server.fs, Cache.fs. | +2.0 pts | Low | Code Coverage |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.9 pts | Low | Bus Factor |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +3.8 pts | Medium | Documentation (README) |
| Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with Adaptor.fs, Types.fs. | +0.9 pts | Medium | Churn × Complexity Hotspots |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/Adaptify.Compiler/ProjectInfo.fs | 5.6 | Mixed | Cyclomatic Complexity: ProjectInfoModule.ofFscArgs (cyclomatic 27) |
| src/Adaptify.Compiler/CoreTypes.fs | 6.3 | Mixed | Code Duplication: Duplicated block (13 lines × 2) |
| src/Adaptify.Compiler/Adaptor.fs | 7.0 | Mixed | Cyclomatic Complexity: TypeDefinitionModule.productType (cyclomatic 43) |
| src/Adaptify.Compiler/Server.fs | 7.0 | Mixed | Cognitive Complexity: Client.adaptify (cognitive 21) |
| src/Adaptify.Compiler/Process.fs | 7.0 | Mixed | Cognitive Complexity: ProcessManagement.startAdaptifyServer (cognitive 21) |
| src/Adaptify.Compiler/Scope.fs | 7.0 | Mixed | Cognitive Complexity: ScopeModule.ofFSharpEntity (cognitive 16) |
| src/Adaptify.Core/CoreInstances.fs | 7.0 | Mixed | God Classes: FileTooLong: Adaptify.Core/CoreInstances.fs |
| src/Adaptify.Compiler/Runner.fs | 7.1 | Mixed | Cyclomatic Complexity: Adaptify.runAsync (cyclomatic 84) |
| src/Adaptify.Compiler/Ast.fs | 7.8 | Mixed | Cyclomatic Complexity: ExprModule.toString (cyclomatic 53) |
| src/adaptify/Program.fs | 7.8 | Mixed | Cyclomatic Complexity: Program.main (cyclomatic 29) |
| src/Adaptify.Compiler/Types.fs | 7.8 | Mixed | Cyclomatic Complexity: TypeRefModule.toString (cyclomatic 21) |
| src/Adaptify.Compiler/Utilities.fs | 8.5 | Near-clean | Cognitive Complexity: Process.tryStart (cognitive 17) |
| src/Adaptify.Core/Helpers.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| src/Examples/Net10/Model.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (26 lines × 3) |
| src/Examples/Net10/Program.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (83 lines × 2) |
| src/Adaptify.Compiler/Cache.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Adaptify.Compiler/Cache.fs |
| src/Adaptify.MSBuild/Adaptify.MSBuild.fsproj | 9.5 | Near-clean | ADR Quality: No ADRs found |
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 37 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 37 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, 96 of 108 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/Adaptify.Compiler/Adaptor.fs, src/Adaptify.Compiler/Types.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.
- D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/Adaptify.Compiler/Adaptify.Compiler.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — 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. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (6,936 lines, 100% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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.
- X23 Unguarded diagnostic materialisation — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X28 Index access outside its own emptiness 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Adaptify.runAsync at 84. A further 1 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 ExprModule.substitute at 21 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with Adaptify.runAsync (cyclomatic 84). — Refactoring it lifts Cyclomatic Complexity from 7.3 to about 7.7/10.
D2 · Cognitive Complexity
14 method(s) exceeded the cognitive complexity threshold of 15; the worst was Adaptify.runAsync at 342.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with Adaptify.runAsync (cognitive 342). — Refactoring it lifts Cognitive Complexity from 3.3 to about 5.2/10.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Adaptor.fs, CoreInstances.fs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
29 duplicated block group(s) detected. 15.2 % of the production lines (1,053 of 6,949) are in a reported copy. 2 of the 29 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Adaptor.fs, CoreInstances.fs, ProjectInfo.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (7 lines × 3) finding(s) in Code Duplication — start with CoreInstances.fs (2), CoreTypes.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (8 lines × 3) finding(s) in Code Duplication — start with CoreInstances.fs (2). — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 21 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 47.5% — 6 file(s) below 50%.
What to do
- Resolve the 6 Low coverage finding(s) in Code Coverage — start with Process.fs, Server.fs, Cache.fs. — One of this dimension's main actionable groups (6 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 115 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 4 direct `PackageReference`(s), and 103 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
Top hotspots: src/Adaptify.Compiler/Adaptor.fs (4×43=172); src/Adaptify.Compiler/Types.fs (3×21=63)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with Adaptor.fs, Types.fs. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Adaptify.Compiler/Adaptor.fs.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted debt markers + unmeasured dead symbols across 13 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (100% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Adaptify.MSBuild.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
94 % of calls cross a namespace and 6 % go through an interface, but 98 % 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)
9 finding(s): 0 critical, 9 high, 0 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- No action in Static Analysis (SAST) — all 9 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 5 high, 0 medium, 0 low.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
D34 · Knowledge Freshness
16 of 16 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Adaptify.Core/CoreInstances.fs.
What to do
- Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with Program.fs (2), Process.fs, Utilities.fs. — One of this dimension's main actionable groups (13 recommendation-level).
- Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with CoreInstances.fs, Adaptor.fs, Runner.fs. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Further orphaned files (smaller) 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.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 11 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
AX5 · Architecture & structure
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- 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
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 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `REDACTED` 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`. — REDACTED:26
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `retry` is async and calls .Wait() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs. — src/Adaptify.Compiler/Process.fs:109
What to do
- F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 76% | Adequate — gated by D2, D4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 44% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- 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 — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 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 — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~175 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1141 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (6,949 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one project, `LibraryCSharp` (13 LoC, 1 public types across 1 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (18 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 1 current-state document(s) make no claim of a kind M4 checks.
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage data present for 12 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — X23 reached only 0% of this repository's production lines — fsharp (6,936 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — X28 reached only 0% of this repository's production lines — fsharp (6,936 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X5 Nullable reference types — no NRT-eligible projects
- 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 — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge src/Adaptify.Core/CoreInstances.fs:1
- Orphaned knowledge src/Adaptify.Compiler/Adaptor.fs:1
- Orphaned knowledge src/Adaptify.Compiler/Runner.fs:1
Serious — 67 finding(s)
- Low coverage: src/Adaptify.Compiler/Process.fs src/Adaptify.Compiler/Process.fs:1
- Low coverage: src/Adaptify.Compiler/Server.fs src/Adaptify.Compiler/Server.fs:1
- Low coverage: src/Adaptify.Compiler/Cache.fs src/Adaptify.Compiler/Cache.fs:1
- Low coverage: src/Adaptify.Compiler/ProjectInfo.fs src/Adaptify.Compiler/ProjectInfo.fs:1
- Low coverage: src/Adaptify.Compiler/CoreTypes.fs src/Adaptify.Compiler/CoreTypes.fs:1
- Low coverage: src/Adaptify.Compiler/Scope.fs src/Adaptify.Compiler/Scope.fs:1
- Duplicated block (7 lines × 2) src/Adaptify.Compiler/Adaptor.fs:1313
- Duplicated block (7 lines × 2) src/Adaptify.Core/CoreInstances.fs:264
- Duplicated block (7 lines × 2) src/Adaptify.Compiler/ProjectInfo.fs:207
- Duplicated block (7 lines × 2) src/Adaptify.Core/Helpers.fs:39
- Duplicated block (7 lines × 3) src/Adaptify.Core/CoreInstances.fs:94
- Duplicated block (7 lines × 3) src/Adaptify.Core/CoreInstances.fs:116
- Duplicated block (7 lines × 3) src/Adaptify.Compiler/CoreTypes.fs:342
- Hotspot: src/Adaptify.Compiler/Adaptor.fs src/Adaptify.Compiler/Adaptor.fs:1095
- Hotspot: src/Adaptify.Compiler/Types.fs src/Adaptify.Compiler/Types.fs:231
- FileTooLong: Adaptify.Compiler/Adaptor.fs src/Adaptify.Compiler/Adaptor.fs
- FileTooLong: Adaptify.Core/CoreInstances.fs src/Adaptify.Core/CoreInstances.fs
- Duplicated block (8 lines × 3) src/Adaptify.Core/CoreInstances.fs:125
- Duplicated block (8 lines × 3) src/Adaptify.Core/CoreInstances.fs:798
- Duplicated block (1–7 lines × 4) src/Adaptify.Core/CoreInstances.fs:107
- Duplicated block (1–7 lines × 4) src/Adaptify.Core/CoreInstances.fs:780
- Adaptify.runAsync (cyclomatic 84) src/Adaptify.Compiler/Runner.fs:145
- ExprModule.toString (cyclomatic 53) src/Adaptify.Compiler/Ast.fs:194
- TypeDefinitionModule.productType (cyclomatic 43) src/Adaptify.Compiler/Adaptor.fs:1095
- TypeDefinitionModule.toString (cyclomatic 42) src/Adaptify.Compiler/Adaptor.fs:886
- Program.main (cyclomatic 29) src/adaptify/Program.fs:141
- ProjectInfoModule.ofFscArgs (cyclomatic 27) src/Adaptify.Compiler/ProjectInfo.fs:37
- AdaptorModule.get (cyclomatic 27) src/Adaptify.Compiler/Adaptor.fs:537
- TypeRefModule.toString (cyclomatic 21) src/Adaptify.Compiler/Types.fs:231
- ProjectInfoModule.computeHash (cyclomatic 16) src/Adaptify.Compiler/ProjectInfo.fs:201
- Adaptify.runAsync (cognitive 342) src/Adaptify.Compiler/Runner.fs:145
- TypeDefinitionModule.toString (cognitive 118) src/Adaptify.Compiler/Adaptor.fs:886
- ExprModule.toString (cognitive 72) src/Adaptify.Compiler/Ast.fs:194
- Program.main (cognitive 58) src/adaptify/Program.fs:141
- TypeDefinitionModule.productType (cognitive 40) src/Adaptify.Compiler/Adaptor.fs:1095
- AdaptorModule.get (cognitive 39) src/Adaptify.Compiler/Adaptor.fs:537
- ProjectInfoModule.ofFscArgs (cognitive 29) src/Adaptify.Compiler/ProjectInfo.fs:37
- TypeDefinitionModule.ofTypeDef (cognitive 24) src/Adaptify.Compiler/Adaptor.fs:1435
- Client.adaptify (cognitive 21) src/Adaptify.Compiler/Server.fs:301
- ProcessManagement.startAdaptifyServer (cognitive 21) src/Adaptify.Compiler/Process.fs:496
- Adaptify.waitUntilExisting (cognitive 18) src/Adaptify.Compiler/Runner.fs:14
- TypeRefModule.ofType (cognitive 18) src/Adaptify.Compiler/Types.fs:174
- Process.tryStart (cognitive 17) src/Adaptify.Compiler/Utilities.fs:334
- ScopeModule.ofFSharpEntity (cognitive 16) src/Adaptify.Compiler/Scope.fs:13
- REDACTED
- REDACTED
- Duplicated block (43 lines × 2) src/Adaptify.Compiler/Adaptor.fs:935
- Duplicated block (22 lines × 2) src/Adaptify.Compiler/Adaptor.fs:711
- Duplicated block (28–30 lines × 3) src/Adaptify.Compiler/Adaptor.fs:647
- Duplicated block (19 lines × 2) src/Adaptify.Compiler/Adaptor.fs:350
- Duplicated block (16–17 lines × 2) src/Adaptify.Compiler/Adaptor.fs:627
- Duplicated block (13 lines × 2) src/Adaptify.Compiler/CoreTypes.fs:181
- Duplicated block (10–11 lines × 2) src/Adaptify.Compiler/Runner.fs:66
- Duplicated block (9–10 lines × 2) src/Adaptify.Compiler/Adaptor.fs:524
- Duplicated block (9 lines × 2) src/Adaptify.Compiler/Runner.fs:86
- Duplicated block (8 lines × 32) src/Adaptify.Core/CoreInstances.fs:207
- Duplicated block (7 lines × 4) src/Adaptify.Compiler/Adaptor.fs:317
- Duplicated block (6 lines × 38) src/Adaptify.Core/CoreInstances.fs:108
- Duplicated block (6 lines × 6) src/Adaptify.Core/CoreInstances.fs:781
- Duplicated block (8 lines × 2) src/Adaptify.Compiler/ProjectInfo.fs:98
- Duplicated block (5 lines × 3) src/Adaptify.Core/CoreInstances.fs:36
- Duplicated block (5 lines × 2) src/Adaptify.Compiler/Adaptor.fs:325
- Duplicated block (26 lines × 3) src/Examples/Net10/Model.fs:1
- Duplicated block (83 lines × 2) src/Examples/Net10/Program.fs:1
- Test suite runs only after the merge
- Sync-over-async blocking src/Adaptify.Compiler/Process.fs:109
- NuGet dependencies are not locked
Minor — 24 finding(s)
- Orphaned file src/Adaptify.Compiler/Process.fs:1
- Orphaned file src/Adaptify.Compiler/Utilities.fs:1
- Orphaned file src/Adaptify.Compiler/Ast.fs:1
- Orphaned file src/Adaptify.Compiler/CoreTypes.fs:1
- Orphaned file src/Adaptify.Compiler/Server.fs:1
- Orphaned file src/Adaptify.Compiler/Types.fs:1
- Orphaned file src/Adaptify.Compiler/ProjectInfo.fs:1
- Orphaned file src/adaptify/Program.fs:1
- Orphaned file src/Adaptify.MSBuild/Program.fs:1
- Orphaned file src/Adaptify.Compiler/Cache.fs:1
- Orphaned file src/Adaptify.Compiler/Scope.fs:1
- Orphaned file src/Adaptify.Core/Helpers.fs:1
- Orphaned file src/Adaptify.Core/Attributes.fs:1
- Off-boarding risk: anonymized user #1
- No ADRs found src/Adaptify.MSBuild/Adaptify.MSBuild.fsproj:4
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation REDACTED:26
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-cba078c1d1264b57ab0d46eceb495cf6/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-cba078c1d1264b57ab0d46eceb495cf6/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/Adaptify.sln package --vulnerable --include-transitive --format json | 5 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-24f1e99d24a243f3ace731772d5b7647 | 0 | artifacts/raw/osv-scanner.json |