Executive summary
TheAngryByrd/IcedTasks meets our standard for a preview release. It scores 71 out of 100 and is rated Strong, and 16 of its 20 critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 59, is the weakest lens and counts most in the score. The best first step is updating the outdated dependencies, worth about 5 points. Adding a release approval would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 62 would lift the score to about 73.
Fourteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One known security hole in a package the code depends on can be used by attackers, and one secret can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting the secret to its own step would close these risks. The three sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 7,823 lines, about €22,000 to rebuild.
If Production Readiness rose from 59 to 62, the lowest score rated Strong, the score would rise from 71 to about 73.
New since the last survey: 2 findings
- Code Coverage · No test project references benchmarks benchmarks/FSharpBenchmarks/benchmarks.fsproj
- Code Coverage · No test project references CSharpTaskBenchmarks benchmarks/CSharpTaskBenchmarks/CSharpTaskBenchmarks.csproj
Rebuild cost: about €22,000 · Estimate
| Cost to rebuild | €7,300 to €36,000, for 121 to 383 hours of work, about 0.2 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 | ×1.0 at a score of 71. 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: 7,823 lines of product code |
| Comment lines | The estimate prices 7,821 lines. Comment lines count towards the size of 7,823 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Build | 2 Build.FSharpAnalyzers | 3 Build.dotnet | 4 Changelog | 5 Fake.DotNet.Fsdocs | 6 IcedTasks.AsyncEx | 7 IcedTasks.AsyncEx.AsyncExExtensionsHighPriority | 8 IcedTasks.AsyncEx.AsyncExtensions | 9 IcedTasks.AutoOpens | 10 IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.AsyncExtensions | 11 IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskModule | 12 IcedTasks.CancellableTaskBase.CancellableTaskBase | 13 IcedTasks.ColdTasks.ColdTasks | 14 IcedTasks.ParallelAsync | 15 IcedTasks.TaskBase.TaskBase | 16 Build.DocsTool | 17 IcedTasks.AsyncEx.AsyncExExtensionsLowPriority | 18 IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks | 19 IcedTasks.CancellableTaskBase.CancellableTaskBase.HighPriority | 20 IcedTasks.CancellableTaskBase.CancellableTaskBase.LowPriority | 21 IcedTasks.CancellableTasks.CancellableTasks | 22 IcedTasks.CancellableValueTasks.CancellableValueTasks | 23 IcedTasks.ColdTasks.ColdTasks.ColdTaskBuilderModule | 24 IcedTasks.ColdTasks.ColdTasks.LowPriority | 25 IcedTasks.ParallelAsync.ParallelAsyncs | 26 IcedTasks.Polyfill.Async.PolyfillBuilders | 27 IcedTasks.Polyfill.Task.Tasks | 28 IcedTasks.PoolingValueTasks.PoolingValueTasks | 29 IcedTasks.TaskBase.TaskBase.LowPriority | 30 IcedTasks.TasksUnit.TasksUnit | 31 IcedTasks.ValueTasks.ValueTasks | 32 IcedTasks.ValueTasksUnit.ValueTasksUnit | 33 IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskBuilder | 34 IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilderModule | 35 IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilderModule | 36 IcedTasks.Polyfill.Task.Tasks.TaskBuilderModule | 37 IcedTasks.PoolingValueTasks.PoolingValueTasks.ValueTaskBuilder | 38 IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilderModule | 39 IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilderModule | 40 IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskBuilder |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Build | ||||||||||||||||||||||||||||||||||||||||
| 2 Build.FSharpAnalyzers | ||||||||||||||||||||||||||||||||||||||||
| 3 Build.dotnet | ||||||||||||||||||||||||||||||||||||||||
| 4 Changelog | ||||||||||||||||||||||||||||||||||||||||
| 5 Fake.DotNet.Fsdocs | ||||||||||||||||||||||||||||||||||||||||
| 6 IcedTasks.AsyncEx | ||||||||||||||||||||||||||||||||||||||||
| 7 IcedTasks.AsyncEx.AsyncExExtensionsHighPriority | ||||||||||||||||||||||||||||||||||||||||
| 8 IcedTasks.AsyncEx.AsyncExtensions | ||||||||||||||||||||||||||||||||||||||||
| 9 IcedTasks.AutoOpens | ||||||||||||||||||||||||||||||||||||||||
| 10 IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.AsyncExtensions | ||||||||||||||||||||||||||||||||||||||||
| 11 IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskModule | ||||||||||||||||||||||||||||||||||||||||
| 12 IcedTasks.CancellableTaskBase.CancellableTaskBase | ||||||||||||||||||||||||||||||||||||||||
| 13 IcedTasks.ColdTasks.ColdTasks | ||||||||||||||||||||||||||||||||||||||||
| 14 IcedTasks.ParallelAsync | ||||||||||||||||||||||||||||||||||||||||
| 15 IcedTasks.TaskBase.TaskBase | ||||||||||||||||||||||||||||||||||||||||
| 16 Build.DocsTool | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 IcedTasks.AsyncEx.AsyncExExtensionsLowPriority | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 IcedTasks.CancellableTaskBase.CancellableTaskBase.HighPriority | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 IcedTasks.CancellableTaskBase.CancellableTaskBase.LowPriority | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 IcedTasks.CancellableTasks.CancellableTasks | 4 | |||||||||||||||||||||||||||||||||||||||
| 22 IcedTasks.CancellableValueTasks.CancellableValueTasks | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 IcedTasks.ColdTasks.ColdTasks.ColdTaskBuilderModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 IcedTasks.ColdTasks.ColdTasks.LowPriority | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 IcedTasks.ParallelAsync.ParallelAsyncs | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 IcedTasks.Polyfill.Async.PolyfillBuilders | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 IcedTasks.Polyfill.Task.Tasks | 4 | |||||||||||||||||||||||||||||||||||||||
| 28 IcedTasks.PoolingValueTasks.PoolingValueTasks | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 IcedTasks.TaskBase.TaskBase.LowPriority | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 IcedTasks.TasksUnit.TasksUnit | 4 | |||||||||||||||||||||||||||||||||||||||
| 31 IcedTasks.ValueTasks.ValueTasks | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 IcedTasks.ValueTasksUnit.ValueTasksUnit | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskBuilder | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilderModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilderModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 IcedTasks.Polyfill.Task.Tasks.TaskBuilderModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 IcedTasks.PoolingValueTasks.PoolingValueTasks.ValueTaskBuilder | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilderModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 39 IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilderModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskBuilder | 1 |
16→5 Build.DocsTool uses Fake.DotNet.Fsdocs✕
- Connections
- 1 pair of types, where a type in Build.DocsTool uses a type in Fake.DotNet.Fsdocs.
- The types involved
Build.DocsTool.DocsTool→Fake.DotNet.Fsdocs.BuildCommandParams
- Direction
- Build.DocsTool uses Fake.DotNet.Fsdocs, so a change to Fake.DotNet.Fsdocs can break Build.DocsTool, while a change to Build.DocsTool can't break Fake.DotNet.Fsdocs.
- Position
- Below the diagonal: Build.DocsTool uses a module listed above it, which is the healthy direction.
17→6 IcedTasks.AsyncEx.AsyncExExtensionsLowPriority uses IcedTasks.AsyncEx✕
- Connections
- 1 pair of types, where a type in IcedTasks.AsyncEx.AsyncExExtensionsLowPriority uses a type in IcedTasks.AsyncEx.
- The types involved
IcedTasks.AsyncEx.AsyncExExtensionsLowPriority.AsyncExExtensionsLowPriority→IcedTasks.AsyncEx.AsyncExBuilder
- Direction
- IcedTasks.AsyncEx.AsyncExExtensionsLowPriority uses IcedTasks.AsyncEx, so a change to IcedTasks.AsyncEx can break IcedTasks.AsyncEx.AsyncExExtensionsLowPriority, while a change to IcedTasks.AsyncEx.AsyncExExtensionsLowPriority can't break IcedTasks.AsyncEx.
- Position
- Below the diagonal: IcedTasks.AsyncEx.AsyncExExtensionsLowPriority uses a module listed above it, which is the healthy direction.
18→12 IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks uses IcedTasks.CancellableTaskBase.CancellableTaskBase✕
- Connections
- 2 pairs of types, where a type in IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks uses a type in IcedTasks.CancellableTaskBase.CancellableTaskBase.
- The types involved
IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellablePoolingValueTaskBuilder→IcedTasks.CancellableTaskBase.CancellableTaskBase.CancellableTaskBaseStateMachineData`2IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellablePoolingValueTaskBuilder→IcedTasks.CancellableTaskBase.CancellableTaskBase.CancellableTaskBuilderBase
- Direction
- IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks uses IcedTasks.CancellableTaskBase.CancellableTaskBase, so a change to IcedTasks.CancellableTaskBase.CancellableTaskBase can break IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks, while a change to IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks can't break IcedTasks.CancellableTaskBase.CancellableTaskBase.
- Position
- Below the diagonal: IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks uses a module listed above it, which is the healthy direction.
19→12 IcedTasks.CancellableTaskBase.CancellableTaskBase.HighPriority uses IcedTasks.CancellableTaskBase.CancellableTaskBase✕
- Connections
- 1 pair of types, where a type in IcedTasks.CancellableTaskBase.CancellableTaskBase.HighPriority uses a type in IcedTasks.CancellableTaskBase.CancellableTaskBase.
- The types involved
IcedTasks.CancellableTaskBase.CancellableTaskBase.HighPriority.HighPriority→IcedTasks.CancellableTaskBase.CancellableTaskBase.CancellableTaskBaseStateMachineData`2
- Direction
- IcedTasks.CancellableTaskBase.CancellableTaskBase.HighPriority uses IcedTasks.CancellableTaskBase.CancellableTaskBase, so a change to IcedTasks.CancellableTaskBase.CancellableTaskBase can break IcedTasks.CancellableTaskBase.CancellableTaskBase.HighPriority, while a change to IcedTasks.CancellableTaskBase.CancellableTaskBase.HighPriority can't break IcedTasks.CancellableTaskBase.CancellableTaskBase.
- Position
- Below the diagonal: IcedTasks.CancellableTaskBase.CancellableTaskBase.HighPriority uses a module listed above it, which is the healthy direction.
20→12 IcedTasks.CancellableTaskBase.CancellableTaskBase.LowPriority uses IcedTasks.CancellableTaskBase.CancellableTaskBase✕
- Connections
- 1 pair of types, where a type in IcedTasks.CancellableTaskBase.CancellableTaskBase.LowPriority uses a type in IcedTasks.CancellableTaskBase.CancellableTaskBase.
- The types involved
IcedTasks.CancellableTaskBase.CancellableTaskBase.LowPriority.LowPriority→IcedTasks.CancellableTaskBase.CancellableTaskBase.CancellableTaskBaseStateMachineData`2
- Direction
- IcedTasks.CancellableTaskBase.CancellableTaskBase.LowPriority uses IcedTasks.CancellableTaskBase.CancellableTaskBase, so a change to IcedTasks.CancellableTaskBase.CancellableTaskBase can break IcedTasks.CancellableTaskBase.CancellableTaskBase.LowPriority, while a change to IcedTasks.CancellableTaskBase.CancellableTaskBase.LowPriority can't break IcedTasks.CancellableTaskBase.CancellableTaskBase.
- Position
- Below the diagonal: IcedTasks.CancellableTaskBase.CancellableTaskBase.LowPriority uses a module listed above it, which is the healthy direction.
21→12 IcedTasks.CancellableTasks.CancellableTasks uses IcedTasks.CancellableTaskBase.CancellableTaskBase✕
- Connections
- 4 pairs of types, where a type in IcedTasks.CancellableTasks.CancellableTasks uses a type in IcedTasks.CancellableTaskBase.CancellableTaskBase.
- The types involved
IcedTasks.CancellableTasks.CancellableTasks.BackgroundCancellableTaskBuilder→IcedTasks.CancellableTaskBase.CancellableTaskBase.CancellableTaskBaseStateMachineData`2IcedTasks.CancellableTasks.CancellableTasks.BackgroundCancellableTaskBuilder→IcedTasks.CancellableTaskBase.CancellableTaskBase.CancellableTaskBuilderBaseIcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilder→IcedTasks.CancellableTaskBase.CancellableTaskBase.CancellableTaskBaseStateMachineData`2IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilder→IcedTasks.CancellableTaskBase.CancellableTaskBase.CancellableTaskBuilderBase
- Direction
- IcedTasks.CancellableTasks.CancellableTasks uses IcedTasks.CancellableTaskBase.CancellableTaskBase, so a change to IcedTasks.CancellableTaskBase.CancellableTaskBase can break IcedTasks.CancellableTasks.CancellableTasks, while a change to IcedTasks.CancellableTasks.CancellableTasks can't break IcedTasks.CancellableTaskBase.CancellableTaskBase.
- Position
- Below the diagonal: IcedTasks.CancellableTasks.CancellableTasks uses a module listed above it, which is the healthy direction.
22→12 IcedTasks.CancellableValueTasks.CancellableValueTasks uses IcedTasks.CancellableTaskBase.CancellableTaskBase✕
- Connections
- 2 pairs of types, where a type in IcedTasks.CancellableValueTasks.CancellableValueTasks uses a type in IcedTasks.CancellableTaskBase.CancellableTaskBase.
- The types involved
IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilder→IcedTasks.CancellableTaskBase.CancellableTaskBase.CancellableTaskBaseStateMachineData`2IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilder→IcedTasks.CancellableTaskBase.CancellableTaskBase.CancellableTaskBuilderBase
- Direction
- IcedTasks.CancellableValueTasks.CancellableValueTasks uses IcedTasks.CancellableTaskBase.CancellableTaskBase, so a change to IcedTasks.CancellableTaskBase.CancellableTaskBase can break IcedTasks.CancellableValueTasks.CancellableValueTasks, while a change to IcedTasks.CancellableValueTasks.CancellableValueTasks can't break IcedTasks.CancellableTaskBase.CancellableTaskBase.
- Position
- Below the diagonal: IcedTasks.CancellableValueTasks.CancellableValueTasks uses a module listed above it, which is the healthy direction.
23→13 IcedTasks.ColdTasks.ColdTasks.ColdTaskBuilderModule uses IcedTasks.ColdTasks.ColdTasks✕
- Connections
- 2 pairs of types, where a type in IcedTasks.ColdTasks.ColdTasks.ColdTaskBuilderModule uses a type in IcedTasks.ColdTasks.ColdTasks.
- The types involved
IcedTasks.ColdTasks.ColdTasks.ColdTaskBuilderModule.ColdTaskBuilderModule→IcedTasks.ColdTasks.ColdTasks.BackgroundColdTaskBuilderIcedTasks.ColdTasks.ColdTasks.ColdTaskBuilderModule.ColdTaskBuilderModule→IcedTasks.ColdTasks.ColdTasks.ColdTaskBuilder
- Direction
- IcedTasks.ColdTasks.ColdTasks.ColdTaskBuilderModule uses IcedTasks.ColdTasks.ColdTasks, so a change to IcedTasks.ColdTasks.ColdTasks can break IcedTasks.ColdTasks.ColdTasks.ColdTaskBuilderModule, while a change to IcedTasks.ColdTasks.ColdTasks.ColdTaskBuilderModule can't break IcedTasks.ColdTasks.ColdTasks.
- Position
- Below the diagonal: IcedTasks.ColdTasks.ColdTasks.ColdTaskBuilderModule uses a module listed above it, which is the healthy direction.
24→13 IcedTasks.ColdTasks.ColdTasks.LowPriority uses IcedTasks.ColdTasks.ColdTasks✕
- Connections
- 1 pair of types, where a type in IcedTasks.ColdTasks.ColdTasks.LowPriority uses a type in IcedTasks.ColdTasks.ColdTasks.
- The types involved
IcedTasks.ColdTasks.ColdTasks.LowPriority.LowPriority→IcedTasks.ColdTasks.ColdTasks.ColdTaskStateMachineData`1
- Direction
- IcedTasks.ColdTasks.ColdTasks.LowPriority uses IcedTasks.ColdTasks.ColdTasks, so a change to IcedTasks.ColdTasks.ColdTasks can break IcedTasks.ColdTasks.ColdTasks.LowPriority, while a change to IcedTasks.ColdTasks.ColdTasks.LowPriority can't break IcedTasks.ColdTasks.ColdTasks.
- Position
- Below the diagonal: IcedTasks.ColdTasks.ColdTasks.LowPriority uses a module listed above it, which is the healthy direction.
25→14 IcedTasks.ParallelAsync.ParallelAsyncs uses IcedTasks.ParallelAsync✕
- Connections
- 2 pairs of types, where a type in IcedTasks.ParallelAsync.ParallelAsyncs uses a type in IcedTasks.ParallelAsync.
- The types involved
IcedTasks.ParallelAsync.ParallelAsyncs.ParallelAsyncs→IcedTasks.ParallelAsync.ParallelAsyncBuilderUsingStartChildIcedTasks.ParallelAsync.ParallelAsyncs.ParallelAsyncs→IcedTasks.ParallelAsync.ParallelAsyncBuilderUsingStartImmediateAsTask
- Direction
- IcedTasks.ParallelAsync.ParallelAsyncs uses IcedTasks.ParallelAsync, so a change to IcedTasks.ParallelAsync can break IcedTasks.ParallelAsync.ParallelAsyncs, while a change to IcedTasks.ParallelAsync.ParallelAsyncs can't break IcedTasks.ParallelAsync.
- Position
- Below the diagonal: IcedTasks.ParallelAsync.ParallelAsyncs uses a module listed above it, which is the healthy direction.
26→6 IcedTasks.Polyfill.Async.PolyfillBuilders uses IcedTasks.AsyncEx✕
- Connections
- 1 pair of types, where a type in IcedTasks.Polyfill.Async.PolyfillBuilders uses a type in IcedTasks.AsyncEx.
- The types involved
IcedTasks.Polyfill.Async.PolyfillBuilders.PolyfillBuilders→IcedTasks.AsyncEx.AsyncExBuilder
- Direction
- IcedTasks.Polyfill.Async.PolyfillBuilders uses IcedTasks.AsyncEx, so a change to IcedTasks.AsyncEx can break IcedTasks.Polyfill.Async.PolyfillBuilders, while a change to IcedTasks.Polyfill.Async.PolyfillBuilders can't break IcedTasks.AsyncEx.
- Position
- Below the diagonal: IcedTasks.Polyfill.Async.PolyfillBuilders uses a module listed above it, which is the healthy direction.
27→15 IcedTasks.Polyfill.Task.Tasks uses IcedTasks.TaskBase.TaskBase✕
- Connections
- 4 pairs of types, where a type in IcedTasks.Polyfill.Task.Tasks uses a type in IcedTasks.TaskBase.TaskBase.
- The types involved
IcedTasks.Polyfill.Task.Tasks.BackgroundTaskBuilder→IcedTasks.TaskBase.TaskBase.TaskBaseStateMachineData`2IcedTasks.Polyfill.Task.Tasks.BackgroundTaskBuilder→IcedTasks.TaskBase.TaskBase.TaskBuilderBaseIcedTasks.Polyfill.Task.Tasks.TaskBuilder→IcedTasks.TaskBase.TaskBase.TaskBaseStateMachineData`2IcedTasks.Polyfill.Task.Tasks.TaskBuilder→IcedTasks.TaskBase.TaskBase.TaskBuilderBase
- Direction
- IcedTasks.Polyfill.Task.Tasks uses IcedTasks.TaskBase.TaskBase, so a change to IcedTasks.TaskBase.TaskBase can break IcedTasks.Polyfill.Task.Tasks, while a change to IcedTasks.Polyfill.Task.Tasks can't break IcedTasks.TaskBase.TaskBase.
- Position
- Below the diagonal: IcedTasks.Polyfill.Task.Tasks uses a module listed above it, which is the healthy direction.
28→15 IcedTasks.PoolingValueTasks.PoolingValueTasks uses IcedTasks.TaskBase.TaskBase✕
- Connections
- 2 pairs of types, where a type in IcedTasks.PoolingValueTasks.PoolingValueTasks uses a type in IcedTasks.TaskBase.TaskBase.
- The types involved
IcedTasks.PoolingValueTasks.PoolingValueTasks.PoolingValueTaskBuilder→IcedTasks.TaskBase.TaskBase.TaskBaseStateMachineData`2IcedTasks.PoolingValueTasks.PoolingValueTasks.PoolingValueTaskBuilder→IcedTasks.TaskBase.TaskBase.TaskBuilderBase
- Direction
- IcedTasks.PoolingValueTasks.PoolingValueTasks uses IcedTasks.TaskBase.TaskBase, so a change to IcedTasks.TaskBase.TaskBase can break IcedTasks.PoolingValueTasks.PoolingValueTasks, while a change to IcedTasks.PoolingValueTasks.PoolingValueTasks can't break IcedTasks.TaskBase.TaskBase.
- Position
- Below the diagonal: IcedTasks.PoolingValueTasks.PoolingValueTasks uses a module listed above it, which is the healthy direction.
29→15 IcedTasks.TaskBase.TaskBase.LowPriority uses IcedTasks.TaskBase.TaskBase✕
- Connections
- 1 pair of types, where a type in IcedTasks.TaskBase.TaskBase.LowPriority uses a type in IcedTasks.TaskBase.TaskBase.
- The types involved
IcedTasks.TaskBase.TaskBase.LowPriority.LowPriority→IcedTasks.TaskBase.TaskBase.TaskBaseStateMachineData`2
- Direction
- IcedTasks.TaskBase.TaskBase.LowPriority uses IcedTasks.TaskBase.TaskBase, so a change to IcedTasks.TaskBase.TaskBase can break IcedTasks.TaskBase.TaskBase.LowPriority, while a change to IcedTasks.TaskBase.TaskBase.LowPriority can't break IcedTasks.TaskBase.TaskBase.
- Position
- Below the diagonal: IcedTasks.TaskBase.TaskBase.LowPriority uses a module listed above it, which is the healthy direction.
30→15 IcedTasks.TasksUnit.TasksUnit uses IcedTasks.TaskBase.TaskBase✕
- Connections
- 4 pairs of types, where a type in IcedTasks.TasksUnit.TasksUnit uses a type in IcedTasks.TaskBase.TaskBase.
- The types involved
IcedTasks.TasksUnit.TasksUnit.BackgroundTaskUnitBuilder→IcedTasks.TaskBase.TaskBase.TaskBaseStateMachineData`2IcedTasks.TasksUnit.TasksUnit.BackgroundTaskUnitBuilder→IcedTasks.TaskBase.TaskBase.TaskBuilderBaseIcedTasks.TasksUnit.TasksUnit.TaskUnitBuilder→IcedTasks.TaskBase.TaskBase.TaskBaseStateMachineData`2IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilder→IcedTasks.TaskBase.TaskBase.TaskBuilderBase
- Direction
- IcedTasks.TasksUnit.TasksUnit uses IcedTasks.TaskBase.TaskBase, so a change to IcedTasks.TaskBase.TaskBase can break IcedTasks.TasksUnit.TasksUnit, while a change to IcedTasks.TasksUnit.TasksUnit can't break IcedTasks.TaskBase.TaskBase.
- Position
- Below the diagonal: IcedTasks.TasksUnit.TasksUnit uses a module listed above it, which is the healthy direction.
31→15 IcedTasks.ValueTasks.ValueTasks uses IcedTasks.TaskBase.TaskBase✕
- Connections
- 2 pairs of types, where a type in IcedTasks.ValueTasks.ValueTasks uses a type in IcedTasks.TaskBase.TaskBase.
- The types involved
IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilder→IcedTasks.TaskBase.TaskBase.TaskBaseStateMachineData`2IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilder→IcedTasks.TaskBase.TaskBase.TaskBuilderBase
- Direction
- IcedTasks.ValueTasks.ValueTasks uses IcedTasks.TaskBase.TaskBase, so a change to IcedTasks.TaskBase.TaskBase can break IcedTasks.ValueTasks.ValueTasks, while a change to IcedTasks.ValueTasks.ValueTasks can't break IcedTasks.TaskBase.TaskBase.
- Position
- Below the diagonal: IcedTasks.ValueTasks.ValueTasks uses a module listed above it, which is the healthy direction.
32→15 IcedTasks.ValueTasksUnit.ValueTasksUnit uses IcedTasks.TaskBase.TaskBase✕
- Connections
- 2 pairs of types, where a type in IcedTasks.ValueTasksUnit.ValueTasksUnit uses a type in IcedTasks.TaskBase.TaskBase.
- The types involved
IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskUnitBuilder→IcedTasks.TaskBase.TaskBase.TaskBaseStateMachineData`2IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskUnitBuilder→IcedTasks.TaskBase.TaskBase.TaskBuilderBase
- Direction
- IcedTasks.ValueTasksUnit.ValueTasksUnit uses IcedTasks.TaskBase.TaskBase, so a change to IcedTasks.TaskBase.TaskBase can break IcedTasks.ValueTasksUnit.ValueTasksUnit, while a change to IcedTasks.ValueTasksUnit.ValueTasksUnit can't break IcedTasks.TaskBase.TaskBase.
- Position
- Below the diagonal: IcedTasks.ValueTasksUnit.ValueTasksUnit uses a module listed above it, which is the healthy direction.
33→18 IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskBuilder uses IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks✕
- Connections
- 1 pair of types, where a type in IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskBuilder uses a type in IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.
- The types involved
IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskBuilder.CancellableValueTaskBuilder→IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellablePoolingValueTaskBuilder
- Direction
- IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskBuilder uses IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks, so a change to IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks can break IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskBuilder, while a change to IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskBuilder can't break IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.
- Position
- Below the diagonal: IcedTasks.CancellablePoolingValueTasks.CancellablePoolingValueTasks.CancellableValueTaskBuilder uses a module listed above it, which is the healthy direction.
34→21 IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilderModule uses IcedTasks.CancellableTasks.CancellableTasks✕
- Connections
- 2 pairs of types, where a type in IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilderModule uses a type in IcedTasks.CancellableTasks.CancellableTasks.
- The types involved
IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilderModule.CancellableTaskBuilderModule→IcedTasks.CancellableTasks.CancellableTasks.BackgroundCancellableTaskBuilderIcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilderModule.CancellableTaskBuilderModule→IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilder
- Direction
- IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilderModule uses IcedTasks.CancellableTasks.CancellableTasks, so a change to IcedTasks.CancellableTasks.CancellableTasks can break IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilderModule, while a change to IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilderModule can't break IcedTasks.CancellableTasks.CancellableTasks.
- Position
- Below the diagonal: IcedTasks.CancellableTasks.CancellableTasks.CancellableTaskBuilderModule uses a module listed above it, which is the healthy direction.
35→22 IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilderModule uses IcedTasks.CancellableValueTasks.CancellableValueTasks✕
- Connections
- 1 pair of types, where a type in IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilderModule uses a type in IcedTasks.CancellableValueTasks.CancellableValueTasks.
- The types involved
IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilderModule.CancellableValueTaskBuilderModule→IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilder
- Direction
- IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilderModule uses IcedTasks.CancellableValueTasks.CancellableValueTasks, so a change to IcedTasks.CancellableValueTasks.CancellableValueTasks can break IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilderModule, while a change to IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilderModule can't break IcedTasks.CancellableValueTasks.CancellableValueTasks.
- Position
- Below the diagonal: IcedTasks.CancellableValueTasks.CancellableValueTasks.CancellableValueTaskBuilderModule uses a module listed above it, which is the healthy direction.
36→27 IcedTasks.Polyfill.Task.Tasks.TaskBuilderModule uses IcedTasks.Polyfill.Task.Tasks✕
- Connections
- 2 pairs of types, where a type in IcedTasks.Polyfill.Task.Tasks.TaskBuilderModule uses a type in IcedTasks.Polyfill.Task.Tasks.
- The types involved
IcedTasks.Polyfill.Task.Tasks.TaskBuilderModule.TaskBuilderModule→IcedTasks.Polyfill.Task.Tasks.BackgroundTaskBuilderIcedTasks.Polyfill.Task.Tasks.TaskBuilderModule.TaskBuilderModule→IcedTasks.Polyfill.Task.Tasks.TaskBuilder
- Direction
- IcedTasks.Polyfill.Task.Tasks.TaskBuilderModule uses IcedTasks.Polyfill.Task.Tasks, so a change to IcedTasks.Polyfill.Task.Tasks can break IcedTasks.Polyfill.Task.Tasks.TaskBuilderModule, while a change to IcedTasks.Polyfill.Task.Tasks.TaskBuilderModule can't break IcedTasks.Polyfill.Task.Tasks.
- Position
- Below the diagonal: IcedTasks.Polyfill.Task.Tasks.TaskBuilderModule uses a module listed above it, which is the healthy direction.
37→28 IcedTasks.PoolingValueTasks.PoolingValueTasks.ValueTaskBuilder uses IcedTasks.PoolingValueTasks.PoolingValueTasks✕
- Connections
- 1 pair of types, where a type in IcedTasks.PoolingValueTasks.PoolingValueTasks.ValueTaskBuilder uses a type in IcedTasks.PoolingValueTasks.PoolingValueTasks.
- The types involved
IcedTasks.PoolingValueTasks.PoolingValueTasks.ValueTaskBuilder.ValueTaskBuilder→IcedTasks.PoolingValueTasks.PoolingValueTasks.PoolingValueTaskBuilder
- Direction
- IcedTasks.PoolingValueTasks.PoolingValueTasks.ValueTaskBuilder uses IcedTasks.PoolingValueTasks.PoolingValueTasks, so a change to IcedTasks.PoolingValueTasks.PoolingValueTasks can break IcedTasks.PoolingValueTasks.PoolingValueTasks.ValueTaskBuilder, while a change to IcedTasks.PoolingValueTasks.PoolingValueTasks.ValueTaskBuilder can't break IcedTasks.PoolingValueTasks.PoolingValueTasks.
- Position
- Below the diagonal: IcedTasks.PoolingValueTasks.PoolingValueTasks.ValueTaskBuilder uses a module listed above it, which is the healthy direction.
38→30 IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilderModule uses IcedTasks.TasksUnit.TasksUnit✕
- Connections
- 2 pairs of types, where a type in IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilderModule uses a type in IcedTasks.TasksUnit.TasksUnit.
- The types involved
IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilderModule.TaskUnitBuilderModule→IcedTasks.TasksUnit.TasksUnit.BackgroundTaskUnitBuilderIcedTasks.TasksUnit.TasksUnit.TaskUnitBuilderModule.TaskUnitBuilderModule→IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilder
- Direction
- IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilderModule uses IcedTasks.TasksUnit.TasksUnit, so a change to IcedTasks.TasksUnit.TasksUnit can break IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilderModule, while a change to IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilderModule can't break IcedTasks.TasksUnit.TasksUnit.
- Position
- Below the diagonal: IcedTasks.TasksUnit.TasksUnit.TaskUnitBuilderModule uses a module listed above it, which is the healthy direction.
39→31 IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilderModule uses IcedTasks.ValueTasks.ValueTasks✕
- Connections
- 1 pair of types, where a type in IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilderModule uses a type in IcedTasks.ValueTasks.ValueTasks.
- The types involved
IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilderModule.ValueTaskBuilderModule→IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilder
- Direction
- IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilderModule uses IcedTasks.ValueTasks.ValueTasks, so a change to IcedTasks.ValueTasks.ValueTasks can break IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilderModule, while a change to IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilderModule can't break IcedTasks.ValueTasks.ValueTasks.
- Position
- Below the diagonal: IcedTasks.ValueTasks.ValueTasks.ValueTaskBuilderModule uses a module listed above it, which is the healthy direction.
40→32 IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskBuilder uses IcedTasks.ValueTasksUnit.ValueTasksUnit✕
- Connections
- 1 pair of types, where a type in IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskBuilder uses a type in IcedTasks.ValueTasksUnit.ValueTasksUnit.
- The types involved
IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskBuilder.ValueTaskBuilder→IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskUnitBuilder
- Direction
- IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskBuilder uses IcedTasks.ValueTasksUnit.ValueTasksUnit, so a change to IcedTasks.ValueTasksUnit.ValueTasksUnit can break IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskBuilder, while a change to IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskBuilder can't break IcedTasks.ValueTasksUnit.ValueTasksUnit.
- Position
- Below the diagonal: IcedTasks.ValueTasksUnit.ValueTasksUnit.ValueTaskBuilder uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 19 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2); Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it; Resolve the 1 No test project references CSharpTaskBenchmarks finding(s) in Code Coverage — start with CSharpTaskBenchmarks.csproj.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2). | +5.1 pts | Low | Dependency Hygiene |
| Resolve the 1 No test project references CSharpTaskBenchmarks finding(s) in Code Coverage — start with CSharpTaskBenchmarks.csproj. | +4.2 pts | Low | Code Coverage |
| Resolve the 1 No test project references benchmarks finding(s) in Code Coverage — start with benchmarks.fsproj. | +4.2 pts | Low | Code Coverage |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +4.4 pts | Medium | Deployment & Rollback |
| Resolve the 1 FileScopedPragmaDisable finding(s) in Explicit Debt — start with Class1.cs. | +1.8 pts | Low | Explicit Debt |
| Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (3). | +1.8 pts | Low | Explicit Debt |
| Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose. | +1.6 pts | Medium | Cryptographic Hygiene |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| benchmarks/CSharpTaskBenchmarks/Class1.cs | 6.1 | Mixed | Explicit Debt: FileScopedPragmaDisable |
| Directory.Build.props | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/IcedTasks/CancellableTask.fs | 7.0 | Near-clean | Cognitive Complexity: BackgroundCancellableTaskBuilder.Run (cognitive 20) |
| src/IcedTasks/CancellableTaskBuilderBase.fs | 7.1 | Near-clean | Code Duplication: Duplicated block (36 lines × 2) |
| src/IcedTasks/TaskUnit.fs | 7.1 | Near-clean | Code Duplication: Duplicated block (23–24 lines × 2) |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| src/IcedTasks/Task.fs | 7.4 | Near-clean | Code Duplication: Duplicated block (15 lines × 4) |
| tests/Directory.Build.props | 7.6 | Near-clean | Explicit Debt: NoWarnInCsproj |
| src/IcedTasks/ColdTask.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (23 lines × 2) |
| benchmarks/FSharpBenchmarks/FileWritingBenchmarks.fs | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: FileWriteBenchmarks (LCOM4 11) |
| benchmarks/FSharpBenchmarks/benchmarks.fsproj | 8.5 | Near-clean | Code Coverage: No test project references benchmarks |
| benchmarks/CSharpTaskBenchmarks/CSharpTaskBenchmarks.csproj | 8.5 | Near-clean | Code Coverage: No test project references CSharpTaskBenchmarks |
| Directory.Packages.props | 9.3 | Near-clean | Dependency Hygiene: Outdated: Microsoft.Bcl.AsyncInterfaces |
| REDACTED | 9.3 | Near-clean | IaC & Container Security: Low IaC: REDACTED |
| adr/0012-namespace-per-builder-file.md | 9.5 | Near-clean | ADR Quality: ADR has no Context and Decision section |
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 43 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 — 43 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, 69 of 94 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 290 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 3 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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/IcedTasks/IcedTasks.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 4 deducted marker(s) and the 1.7/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (7,643 lines, 98% 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. 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.
- D26 Project Cohesion — 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. `CSharpTaskBenchmarks(net8.0)` (173 LoC, 201 public types across 92 namespaces) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X27 Collection changed while being enumerated — 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was TaskPerfCSharp.perf2_AsyncEnumerable at 21.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with TaskPerfCSharp.perf2_AsyncEnumerable (cognitive 21), BackgroundCancellableTaskBuilder.Run (cognitive 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
29 duplicated block group(s) detected. 11.7 % of the production lines (916 of 7,816) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with CancellableTask.fs (2), TaskUnit.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Members sharing a duplicated core (7 members, 50+ identical tokens) finding(s) in Code Duplication — start with CancellableTask.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with CancellableTask.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 3 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with FileWritingBenchmarks.fs. — One of this dimension's main actionable groups (1 warning-level).
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.
D8 · Code Coverage
Line coverage 30.0%, branch coverage 13.1%.
What to do
- Resolve the 1 No test project references benchmarks finding(s) in Code Coverage — start with benchmarks.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references CSharpTaskBenchmarks finding(s) in Code Coverage — start with CSharpTaskBenchmarks.csproj. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
22 outdated, 0 vulnerable, 0 deprecated packages.
What to do
- Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2). — One of this dimension's main actionable groups (2 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 106 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 21 direct `PackageReference`(s), and 100 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
4 deducted debt markers + unmeasured dead symbols across 173 LoC in the .NET projects (1.7/KLoC) → score 6.5. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (98% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 FileScopedPragmaDisable finding(s) in Explicit Debt — start with Class1.cs. — One of this dimension's main actionable groups (1 issue-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 2 unit(s).
D20 · ADR Quality
1 of 12 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D27 · Navigability
85 % of calls cross a namespace and 0 % go through an interface, but 83 % 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)
19 finding(s): 0 critical, 15 high, 2 medium, 2 low. 14 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `REDACTED` (line 79, line 147) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 14 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 (14 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 0 medium, 1 low.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 19 of the 23 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-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 9 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
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
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 3 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:8
- `Directory.Packages.props` 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`. — Directory.Packages.props:15
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
S1 · Cryptographic Hygiene
- `https://code.iconify.design/iconify-icon/1.0.7/iconify-icon.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — REDACTED:32
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81% | Strong | Solid. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 89% | Exemplary | Solid. |
| Readiness | 59% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 77% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
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 — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- 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
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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 — ~11111 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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 — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (7,816 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 — None of 12 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D26 Project Cohesion — D26 could not read how the parts of this repository's one project reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This 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 14 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — X1 reached only 2% of this repository's production lines — fsharp (7,643 lines), javascript (7 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 2% of this repository's production lines — fsharp (7,643 lines), javascript (7 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X16 reached only 2% of this repository's production lines — fsharp (7,643 lines), javascript (7 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X2 reached only 2% of this repository's production lines — fsharp (7,643 lines), javascript (7 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — 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 — X27 reached only 2% of this repository's production lines — fsharp (7,643 lines), javascript (7 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — 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
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 20 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj Directory.Build.props:17
- NoWarnInCsproj Directory.Build.props:18
- NoWarnInCsproj tests/Directory.Build.props:10
- FileScopedPragmaDisable benchmarks/CSharpTaskBenchmarks/Class1.cs:7
- REDACTED
- REDACTED
Serious — 42 finding(s)
- Duplicated block (13 lines × 2) src/IcedTasks/CancellableTask.fs:55
- Duplicated block (13 lines × 2) src/IcedTasks/CancellableTask.fs:151
- Duplicated block (13 lines × 2) src/IcedTasks/TaskUnit.fs:220
- TaskPerfCSharp.perf2_AsyncEnumerable (cognitive 21) benchmarks/CSharpTaskBenchmarks/Class1.cs:173
- BackgroundCancellableTaskBuilder.Run (cognitive 20) src/IcedTasks/CancellableTask.fs:252
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (7 members, 50+ identical tokens) src/IcedTasks/CancellableTask.fs:12
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/IcedTasks/CancellableTask.fs:12
- Duplicated block (36 lines × 2) src/IcedTasks/CancellableTaskBuilderBase.fs:553
- Duplicated block (29–30 lines × 2) src/IcedTasks/CancellableTaskBuilderBase.fs:273
- Duplicated block (23–24 lines × 2) src/IcedTasks/TaskUnit.fs:57
- Duplicated block (23 lines × 2) src/IcedTasks/ColdTask.fs:342
- Duplicated block (20–22 lines × 4) src/IcedTasks/CancellableTaskBuilderBase.fs:267
- Duplicated block (20–22 lines × 2) src/IcedTasks/CancellableTaskBuilderBase.fs:818
- Duplicated block (19–20 lines × 6) src/IcedTasks/CancellableTask.fs:72
- Duplicated block (20 lines × 3) src/IcedTasks/TaskUnit.fs:99
- Duplicated block (19 lines × 5) src/IcedTasks/CancellableTask.fs:108
- Duplicated block (19 lines × 4) src/IcedTasks/CancellableTaskBuilderBase.fs:225
- Duplicated block (19 lines × 2) src/IcedTasks/CancellableTask.fs:186
- Duplicated block (18 lines × 2) src/IcedTasks/CancellableTask.fs:166
- Duplicated block (16–17 lines × 7) src/IcedTasks/CancellableTask.fs:69
- Duplicated block (16 lines × 2) src/IcedTasks/CancellableTask.fs:207
- Duplicated block (15 lines × 4) src/IcedTasks/Task.fs:52
- Duplicated block (13–14 lines × 2) src/IcedTasks/Task.fs:127
- Duplicated block (12 lines × 8) src/IcedTasks/CancellableTask.fs:118
- Duplicated block (11–12 lines × 4) src/IcedTasks/Task.fs:98
- Duplicated block (9–11 lines × 2) src/IcedTasks/CancellableTask.fs:130
- Duplicated block (11 lines × 2) src/IcedTasks/TaskUnit.fs:127
- Duplicated block (8–9 lines × 6) src/IcedTasks/CancellableTask.fs:60
- Duplicated block (9 lines × 2) src/IcedTasks/CancellableTask.fs:21
- Duplicated block (8 lines × 4) src/IcedTasks/CancellableTask.fs:21
- Duplicated block (8 lines × 3) src/IcedTasks/TaskUnit.fs:132
- Duplicated block (8 lines × 2) src/IcedTasks/CancellableTaskBuilderBase.fs:256
- Duplicated block (5 lines × 2) src/IcedTasks/CancellableTask.fs:106
- Low cohesion: FileWriteBenchmarks (LCOM4 11) benchmarks/FSharpBenchmarks/FileWritingBenchmarks.fs:25
- No test project references benchmarks benchmarks/FSharpBenchmarks/benchmarks.fsproj
- No test project references CSharpTaskBenchmarks benchmarks/CSharpTaskBenchmarks/CSharpTaskBenchmarks.csproj
- Third-party script without Subresource Integrity REDACTED:32
Minor — 12 finding(s)
- Outdated: Microsoft.Bcl.AsyncInterfaces Directory.Packages.props:16
- Outdated: Microsoft.Bcl.TimeProvider Directory.Packages.props:25
- REDACTED
- REDACTED
- ADR has no Context and Decision section adr/0012-namespace-per-builder-file.md:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No SAST REDACTED:8
- No dependency-update automation Directory.Packages.props:15
Minor — 20 finding(s)
- Outdated: FSharp.Analyzers.Build
- Outdated: FSharp.Core
- Outdated: G-Research.FSharp.Analyzers
- Outdated: Ionide.Analyzers
- Outdated: Expecto
- Outdated: Expecto.FsCheck
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: YoloDev.Expecto.TestSdk
- Outdated: Fake.Api.GitHub
- Outdated: Fake.BuildServer.GitHubActions
- Outdated: Fake.Core.Environment
- Outdated: Fake.Core.Process
- Outdated: Fake.Core.ReleaseNotes
- Outdated: Fake.Core.Target
- Outdated: Fake.DotNet.AssemblyInfoFile
- Outdated: Fake.DotNet.Cli
- Outdated: Fake.IO.FileSystem
- Outdated: Fake.Tools.Git
- Outdated: MSBuild.StructuredLogger
- Outdated: BenchmarkDotNet
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-3f1c08ec9bfc460783b7c5cc54ce4dfa/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-3f1c08ec9bfc460783b7c5cc54ce4dfa/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 . | 19 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list IcedTasks.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-479409f8cda041fab4eb6b4a91719523 | 0 | artifacts/raw/osv-scanner.json |