Executive summary
SpinalHDL/NaxRiscv falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 49 out of 100 and is rated Weak, and all six of its critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first steps are adding a diagnostic log and adding automated security scanning, each worth about 9 points. Raising Production Readiness to 70 would lift the score to about 61.
Five 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. Pinning each tool to an exact version and updating the vulnerable packages would close both risks.
The product code is 23,589 lines, about €24,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 49 to about 61.
Rebuild cost: about €24,000 · Estimate
| Cost to rebuild | €8,100 to €41,000, for 135 to 427 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 49. 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 | Medium: 23,589 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 naxriscv.compatibility | 3 naxriscv.execute.ExecutionUnitElementSimple.Logic | 4 naxriscv.lsu2 | 5 naxriscv.platform | 6 naxriscv.utilities.AdderAggregator | 7 naxriscv.utilities.MulSpliter | 8 naxriscv.utilities.Reservation | 9 naxriscv.interfaces | 10 naxriscv.lsu2.Lsu2Plugin | 11 naxriscv.platform.PeripheralEmulator | 12 naxriscv.platform.tilelinkdemo.SocSim | 13 naxriscv.execute.ExecutionUnitBase | 14 naxriscv.execute.ExecutionUnitElementSimple | 15 naxriscv.execute.IntFormatPlugin | 16 naxriscv.fetch.PcPlugin | 17 naxriscv.frontend.RfDependencyPlugin | 18 naxriscv.interfaces.AddressTranslationPortUsage | 19 naxriscv.misc.RegFilePlugin | 20 naxriscv.misc.RobPlugin | 21 naxriscv.platform.tilelinkdemo | 22 naxriscv.riscv | 23 naxriscv.utilities | 24 naxriscv | 25 naxriscv.debug | 26 naxriscv.execute | 27 naxriscv.execute.BranchPlugin | 28 naxriscv.execute.CsrAccessPlugin | 29 naxriscv.execute.fpu | 30 naxriscv.fetch | 31 naxriscv.frontend | 32 naxriscv.lsu | 33 naxriscv.misc | 34 naxriscv.platform.litex | 35 naxriscv.lsu.DataCachePlugin | 36 naxriscv.lsu.LsuPlugin | 37 naxriscv.misc.MmuPlugin | 38 naxriscv.misc.StaticAddressTranslationPlugin | 39 naxriscv.prediction | 40 naxriscv.prediction.HistoryPlugin |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 naxriscv.compatibility | ||||||||||||||||||||||||||||||||||||||||
| 3 naxriscv.execute.ExecutionUnitElementSimple.Logic | ||||||||||||||||||||||||||||||||||||||||
| 4 naxriscv.lsu2 | ||||||||||||||||||||||||||||||||||||||||
| 5 naxriscv.platform | ||||||||||||||||||||||||||||||||||||||||
| 6 naxriscv.utilities.AdderAggregator | ||||||||||||||||||||||||||||||||||||||||
| 7 naxriscv.utilities.MulSpliter | ||||||||||||||||||||||||||||||||||||||||
| 8 naxriscv.utilities.Reservation | ||||||||||||||||||||||||||||||||||||||||
| 9 naxriscv.interfaces | 17 | |||||||||||||||||||||||||||||||||||||||
| 10 naxriscv.lsu2.Lsu2Plugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 naxriscv.platform.PeripheralEmulator | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 naxriscv.platform.tilelinkdemo.SocSim | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 naxriscv.execute.ExecutionUnitBase | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 naxriscv.execute.ExecutionUnitElementSimple | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 naxriscv.execute.IntFormatPlugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 naxriscv.fetch.PcPlugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 naxriscv.frontend.RfDependencyPlugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 naxriscv.interfaces.AddressTranslationPortUsage | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 naxriscv.misc.RegFilePlugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 naxriscv.misc.RobPlugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 naxriscv.platform.tilelinkdemo | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 naxriscv.riscv | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 naxriscv.utilities | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 naxriscv | 3 | |||||||||||||||||||||||||||||||||||||||
| 25 naxriscv.debug | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 naxriscv.execute | 15 | 1 | 7 | |||||||||||||||||||||||||||||||||||||
| 27 naxriscv.execute.BranchPlugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 naxriscv.execute.CsrAccessPlugin | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 naxriscv.execute.fpu | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 naxriscv.fetch | 3 | 4 | ||||||||||||||||||||||||||||||||||||||
| 31 naxriscv.frontend | 8 | 5 | ||||||||||||||||||||||||||||||||||||||
| 32 naxriscv.lsu | 6 | 6 | ||||||||||||||||||||||||||||||||||||||
| 33 naxriscv.misc | 19 | 10 | ||||||||||||||||||||||||||||||||||||||
| 34 naxriscv.platform.litex | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 naxriscv.lsu.DataCachePlugin | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 naxriscv.lsu.LsuPlugin | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 naxriscv.misc.MmuPlugin | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 naxriscv.misc.StaticAddressTranslationPlugin | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 naxriscv.prediction | 1 | 9 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 naxriscv.prediction.HistoryPlugin | 2 |
9→23 naxriscv.interfaces uses naxriscv.utilities part of a loop✕
- Connections
- 17 pairs of types, where a type in naxriscv.interfaces uses a type in naxriscv.utilities.
- The types involved
naxriscv.interfaces.AddressTranslationService→naxriscv.utilities.Servicenaxriscv.interfaces.CommitService→naxriscv.utilities.Servicenaxriscv.interfaces.CsrService→naxriscv.utilities.Servicenaxriscv.interfaces.DecoderService→naxriscv.utilities.Servicenaxriscv.interfaces.ExecuteUnitService→naxriscv.utilities.Servicenaxriscv.interfaces.FetchInjector→naxriscv.utilities.Servicenaxriscv.interfaces.InitCycles→naxriscv.utilities.Servicenaxriscv.interfaces.IssueService→naxriscv.utilities.Servicenaxriscv.interfaces.PostCommitBusy→naxriscv.utilities.Servicenaxriscv.interfaces.PrivilegedService→naxriscv.utilities.Servicenaxriscv.interfaces.RegfileService→naxriscv.utilities.Servicenaxriscv.interfaces.RfAllocationService→naxriscv.utilities.AllocatorMultiPortPopnaxriscv.interfaces.RfAllocationService→naxriscv.utilities.Servicenaxriscv.interfaces.RobService→naxriscv.utilities.Servicenaxriscv.interfaces.WakeRegFileService→naxriscv.utilities.Servicenaxriscv.interfaces.WakeRobService→naxriscv.utilities.Servicenaxriscv.interfaces.WakeWithBypassService→naxriscv.utilities.Service
- Direction
- naxriscv.interfaces uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv.interfaces, while a change to naxriscv.interfaces can't break naxriscv.utilities.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→4 naxriscv.lsu2.Lsu2Plugin uses naxriscv.lsu2✕
- Connections
- 1 pair of types, where a type in naxriscv.lsu2.Lsu2Plugin uses a type in naxriscv.lsu2.
- The types involved
naxriscv.lsu2.Lsu2Plugin.AguPortSpec→naxriscv.lsu2.AguPort
- Direction
- naxriscv.lsu2.Lsu2Plugin uses naxriscv.lsu2, so a change to naxriscv.lsu2 can break naxriscv.lsu2.Lsu2Plugin, while a change to naxriscv.lsu2.Lsu2Plugin can't break naxriscv.lsu2.
- Position
- Below the diagonal: naxriscv.lsu2.Lsu2Plugin uses a module listed above it, which is the healthy direction.
11→5 naxriscv.platform.PeripheralEmulator uses naxriscv.platform✕
- Connections
- 3 pairs of types, where a type in naxriscv.platform.PeripheralEmulator uses a type in naxriscv.platform.
- The types involved
naxriscv.platform.PeripheralEmulator.DoGetc→naxriscv.platform.TestSchedulenaxriscv.platform.PeripheralEmulator.DoSuccess→naxriscv.platform.TestSchedulenaxriscv.platform.PeripheralEmulator.WaitPutc→naxriscv.platform.TestSchedule
- Direction
- naxriscv.platform.PeripheralEmulator uses naxriscv.platform, so a change to naxriscv.platform can break naxriscv.platform.PeripheralEmulator, while a change to naxriscv.platform.PeripheralEmulator can't break naxriscv.platform.
- Position
- Below the diagonal: naxriscv.platform.PeripheralEmulator uses a module listed above it, which is the healthy direction.
12→21 naxriscv.platform.tilelinkdemo.SocSim uses naxriscv.platform.tilelinkdemo part of a loop✕
- Connections
- 1 pair of types, where a type in naxriscv.platform.tilelinkdemo.SocSim uses a type in naxriscv.platform.tilelinkdemo.
- The types involved
naxriscv.platform.tilelinkdemo.SocSim.SocDemoSim→naxriscv.platform.tilelinkdemo.SocDemo
- Direction
- naxriscv.platform.tilelinkdemo.SocSim uses naxriscv.platform.tilelinkdemo, so a change to naxriscv.platform.tilelinkdemo can break naxriscv.platform.tilelinkdemo.SocSim, while a change to naxriscv.platform.tilelinkdemo.SocSim can't break naxriscv.platform.tilelinkdemo.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→9 naxriscv.execute.ExecutionUnitBase uses naxriscv.interfaces✕
- Connections
- 2 pairs of types, where a type in naxriscv.execute.ExecutionUnitBase uses a type in naxriscv.interfaces.
- The types involved
naxriscv.execute.ExecutionUnitBase.WriteBackKey→naxriscv.interfaces.RegfileSpecnaxriscv.execute.ExecutionUnitBase.WriteBackKey→naxriscv.interfaces.RfAccess
- Direction
- naxriscv.execute.ExecutionUnitBase uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.execute.ExecutionUnitBase, while a change to naxriscv.execute.ExecutionUnitBase can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.execute.ExecutionUnitBase uses a module listed above it, which is the healthy direction.
14→9 naxriscv.execute.ExecutionUnitElementSimple uses naxriscv.interfaces✕
- Connections
- 1 pair of types, where a type in naxriscv.execute.ExecutionUnitElementSimple uses a type in naxriscv.interfaces.
- The types involved
naxriscv.execute.ExecutionUnitElementSimple.Setup→naxriscv.interfaces.MicroOp
- Direction
- naxriscv.execute.ExecutionUnitElementSimple uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.execute.ExecutionUnitElementSimple, while a change to naxriscv.execute.ExecutionUnitElementSimple can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.execute.ExecutionUnitElementSimple uses a module listed above it, which is the healthy direction.
14→26 naxriscv.execute.ExecutionUnitElementSimple uses naxriscv.execute part of a loop✕
- Connections
- 1 pair of types, where a type in naxriscv.execute.ExecutionUnitElementSimple uses a type in naxriscv.execute.
- The types involved
naxriscv.execute.ExecutionUnitElementSimple.Setup→naxriscv.execute.SrcKeys
- Direction
- naxriscv.execute.ExecutionUnitElementSimple uses naxriscv.execute, so a change to naxriscv.execute can break naxriscv.execute.ExecutionUnitElementSimple, while a change to naxriscv.execute.ExecutionUnitElementSimple can't break naxriscv.execute.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→9 naxriscv.execute.IntFormatPlugin uses naxriscv.interfaces✕
- Connections
- 1 pair of types, where a type in naxriscv.execute.IntFormatPlugin uses a type in naxriscv.interfaces.
- The types involved
naxriscv.execute.IntFormatPlugin.SignExtend→naxriscv.interfaces.MicroOp
- Direction
- naxriscv.execute.IntFormatPlugin uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.execute.IntFormatPlugin, while a change to naxriscv.execute.IntFormatPlugin can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.execute.IntFormatPlugin uses a module listed above it, which is the healthy direction.
16→9 naxriscv.fetch.PcPlugin uses naxriscv.interfaces✕
- Connections
- 1 pair of types, where a type in naxriscv.fetch.PcPlugin uses a type in naxriscv.interfaces.
- The types involved
naxriscv.fetch.PcPlugin.JumpSpec→naxriscv.interfaces.JumpCmd
- Direction
- naxriscv.fetch.PcPlugin uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.fetch.PcPlugin, while a change to naxriscv.fetch.PcPlugin can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.fetch.PcPlugin uses a module listed above it, which is the healthy direction.
17→9 naxriscv.frontend.RfDependencyPlugin uses naxriscv.interfaces✕
- Connections
- 1 pair of types, where a type in naxriscv.frontend.RfDependencyPlugin uses a type in naxriscv.interfaces.
- The types involved
naxriscv.frontend.RfDependencyPlugin.IssueSkipSpec→naxriscv.interfaces.MicroOp
- Direction
- naxriscv.frontend.RfDependencyPlugin uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.frontend.RfDependencyPlugin, while a change to naxriscv.frontend.RfDependencyPlugin can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.frontend.RfDependencyPlugin uses a module listed above it, which is the healthy direction.
18→9 naxriscv.interfaces.AddressTranslationPortUsage uses naxriscv.interfaces✕
- Connections
- 2 pairs of types, where a type in naxriscv.interfaces.AddressTranslationPortUsage uses a type in naxriscv.interfaces.
- The types involved
naxriscv.interfaces.AddressTranslationPortUsage.FETCH→naxriscv.interfaces.AddressTranslationPortUsagenaxriscv.interfaces.AddressTranslationPortUsage.LOAD_STORE→naxriscv.interfaces.AddressTranslationPortUsage
- Direction
- naxriscv.interfaces.AddressTranslationPortUsage uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.interfaces.AddressTranslationPortUsage, while a change to naxriscv.interfaces.AddressTranslationPortUsage can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.interfaces.AddressTranslationPortUsage uses a module listed above it, which is the healthy direction.
19→9 naxriscv.misc.RegFilePlugin uses naxriscv.interfaces✕
- Connections
- 1 pair of types, where a type in naxriscv.misc.RegFilePlugin uses a type in naxriscv.interfaces.
- The types involved
naxriscv.misc.RegFilePlugin.WriteSpec→naxriscv.interfaces.RegFileWrite
- Direction
- naxriscv.misc.RegFilePlugin uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.misc.RegFilePlugin, while a change to naxriscv.misc.RegFilePlugin can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.misc.RegFilePlugin uses a module listed above it, which is the healthy direction.
20→9 naxriscv.misc.RobPlugin uses naxriscv.interfaces✕
- Connections
- 1 pair of types, where a type in naxriscv.misc.RobPlugin uses a type in naxriscv.interfaces.
- The types involved
naxriscv.misc.RobPlugin.Completion→naxriscv.interfaces.RobCompletion
- Direction
- naxriscv.misc.RobPlugin uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.misc.RobPlugin, while a change to naxriscv.misc.RobPlugin can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.misc.RobPlugin uses a module listed above it, which is the healthy direction.
21→12 naxriscv.platform.tilelinkdemo uses naxriscv.platform.tilelinkdemo.SocSim✕
- Connections
- 1 pair of types, where a type in naxriscv.platform.tilelinkdemo uses a type in naxriscv.platform.tilelinkdemo.SocSim.
- The types involved
naxriscv.platform.tilelinkdemo.SocSim→naxriscv.platform.tilelinkdemo.SocSim.SocDemoSim
- Direction
- naxriscv.platform.tilelinkdemo uses naxriscv.platform.tilelinkdemo.SocSim, so a change to naxriscv.platform.tilelinkdemo.SocSim can break naxriscv.platform.tilelinkdemo, while a change to naxriscv.platform.tilelinkdemo can't break naxriscv.platform.tilelinkdemo.SocSim.
- Position
- Below the diagonal: naxriscv.platform.tilelinkdemo uses a module listed above it, which is the healthy direction.
22→9 naxriscv.riscv uses naxriscv.interfaces✕
- Connections
- 2 pairs of types, where a type in naxriscv.riscv uses a type in naxriscv.interfaces.
- The types involved
naxriscv.riscv.FloatRegFile→naxriscv.interfaces.RegfileSpecnaxriscv.riscv.IntRegFile→naxriscv.interfaces.RegfileSpec
- Direction
- naxriscv.riscv uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.riscv, while a change to naxriscv.riscv can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.riscv uses a module listed above it, which is the healthy direction.
23→6 naxriscv.utilities uses naxriscv.utilities.AdderAggregator✕
- Connections
- 2 pairs of types, where a type in naxriscv.utilities uses a type in naxriscv.utilities.AdderAggregator.
- The types involved
naxriscv.utilities.AdderAggregator→naxriscv.utilities.AdderAggregator.Addernaxriscv.utilities.AdderAggregator→naxriscv.utilities.AdderAggregator.Source
- Direction
- naxriscv.utilities uses naxriscv.utilities.AdderAggregator, so a change to naxriscv.utilities.AdderAggregator can break naxriscv.utilities, while a change to naxriscv.utilities can't break naxriscv.utilities.AdderAggregator.
- Position
- Below the diagonal: naxriscv.utilities uses a module listed above it, which is the healthy direction.
23→7 naxriscv.utilities uses naxriscv.utilities.MulSpliter✕
- Connections
- 1 pair of types, where a type in naxriscv.utilities uses a type in naxriscv.utilities.MulSpliter.
- The types involved
naxriscv.utilities.AdderAggregator→naxriscv.utilities.MulSpliter.Splits
- Direction
- naxriscv.utilities uses naxriscv.utilities.MulSpliter, so a change to naxriscv.utilities.MulSpliter can break naxriscv.utilities, while a change to naxriscv.utilities can't break naxriscv.utilities.MulSpliter.
- Position
- Below the diagonal: naxriscv.utilities uses a module listed above it, which is the healthy direction.
23→8 naxriscv.utilities uses naxriscv.utilities.Reservation✕
- Connections
- 1 pair of types, where a type in naxriscv.utilities uses a type in naxriscv.utilities.Reservation.
- The types involved
naxriscv.utilities.Reservation→naxriscv.utilities.Reservation.Entry
- Direction
- naxriscv.utilities uses naxriscv.utilities.Reservation, so a change to naxriscv.utilities.Reservation can break naxriscv.utilities, while a change to naxriscv.utilities can't break naxriscv.utilities.Reservation.
- Position
- Below the diagonal: naxriscv.utilities uses a module listed above it, which is the healthy direction.
23→9 naxriscv.utilities uses naxriscv.interfaces✕
- Connections
- 1 pair of types, where a type in naxriscv.utilities uses a type in naxriscv.interfaces.
- The types involved
naxriscv.utilities.WithRfWriteSharedSpec→naxriscv.interfaces.RegfileSpec
- Direction
- naxriscv.utilities uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.utilities, while a change to naxriscv.utilities can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.utilities uses a module listed above it, which is the healthy direction.
24→23 naxriscv uses naxriscv.utilities✕
- Connections
- 3 pairs of types, where a type in naxriscv uses a type in naxriscv.utilities.
- The types involved
naxriscv.Config→naxriscv.utilities.Pluginnaxriscv.NaxRiscv→naxriscv.utilities.Pluginnaxriscv.Tweek→naxriscv.utilities.Plugin
- Direction
- naxriscv uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv, while a change to naxriscv can't break naxriscv.utilities.
- Position
- Below the diagonal: naxriscv uses a module listed above it, which is the healthy direction.
25→23 naxriscv.debug uses naxriscv.utilities✕
- Connections
- 1 pair of types, where a type in naxriscv.debug uses a type in naxriscv.utilities.
- The types involved
naxriscv.debug.EmbeddedJtagPlugin→naxriscv.utilities.Plugin
- Direction
- naxriscv.debug uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv.debug, while a change to naxriscv.debug can't break naxriscv.utilities.
- Position
- Below the diagonal: naxriscv.debug uses a module listed above it, which is the healthy direction.
26→9 naxriscv.execute uses naxriscv.interfaces✕
- Connections
- 15 pairs of types, where a type in naxriscv.execute uses a type in naxriscv.interfaces.
- The types involved
naxriscv.execute.ExecuteUnitDemo→naxriscv.interfaces.ExecuteUnitServicenaxriscv.execute.ExecuteUnitDemo→naxriscv.interfaces.LockedImplnaxriscv.execute.ExecuteUnitDemo→naxriscv.interfaces.MicroOpnaxriscv.execute.ExecuteUnitDemo→naxriscv.interfaces.WakeRegFileServicenaxriscv.execute.ExecuteUnitDemo→naxriscv.interfaces.WakeRobServicenaxriscv.execute.ExecutionUnitBase→naxriscv.interfaces.ExecuteUnitServicenaxriscv.execute.ExecutionUnitBase→naxriscv.interfaces.LockedImplnaxriscv.execute.ExecutionUnitBase→naxriscv.interfaces.MicroOpnaxriscv.execute.ExecutionUnitBase→naxriscv.interfaces.RegfileSpecnaxriscv.execute.ExecutionUnitBase→naxriscv.interfaces.RfAccessnaxriscv.execute.ExecutionUnitBase→naxriscv.interfaces.RfResourcenaxriscv.execute.ExecutionUnitBase→naxriscv.interfaces.WakeRegFileServicenaxriscv.execute.ExecutionUnitBase→naxriscv.interfaces.WakeRobServicenaxriscv.execute.IntFormatPlugin→naxriscv.interfaces.MicroOpnaxriscv.execute.SrcPlugin→naxriscv.interfaces.MicroOp
- Direction
- naxriscv.execute uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.execute, while a change to naxriscv.execute can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.execute uses a module listed above it, which is the healthy direction.
26→14 naxriscv.execute uses naxriscv.execute.ExecutionUnitElementSimple✕
- Connections
- 1 pair of types, where a type in naxriscv.execute uses a type in naxriscv.execute.ExecutionUnitElementSimple.
- The types involved
naxriscv.execute.ExecutionUnitElementSimple→naxriscv.execute.ExecutionUnitElementSimple.Setup
- Direction
- naxriscv.execute uses naxriscv.execute.ExecutionUnitElementSimple, so a change to naxriscv.execute.ExecutionUnitElementSimple can break naxriscv.execute, while a change to naxriscv.execute can't break naxriscv.execute.ExecutionUnitElementSimple.
- Position
- Below the diagonal: naxriscv.execute uses a module listed above it, which is the healthy direction.
26→23 naxriscv.execute uses naxriscv.utilities✕
- Connections
- 7 pairs of types, where a type in naxriscv.execute uses a type in naxriscv.utilities.
- The types involved
naxriscv.execute.CsrTracer→naxriscv.utilities.Pluginnaxriscv.execute.ExecuteUnitDemo→naxriscv.utilities.Pluginnaxriscv.execute.ExecutionUnitBase→naxriscv.utilities.Pluginnaxriscv.execute.ExecutionUnitBase→naxriscv.utilities.WithRfWriteSharedSpecnaxriscv.execute.ExecutionUnitElementSimple→naxriscv.utilities.Pluginnaxriscv.execute.IntFormatPlugin→naxriscv.utilities.Pluginnaxriscv.execute.SrcPlugin→naxriscv.utilities.Plugin
- Direction
- naxriscv.execute uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv.execute, while a change to naxriscv.execute can't break naxriscv.utilities.
- Position
- Below the diagonal: naxriscv.execute uses a module listed above it, which is the healthy direction.
27→14 naxriscv.execute.BranchPlugin uses naxriscv.execute.ExecutionUnitElementSimple✕
- Connections
- 1 pair of types, where a type in naxriscv.execute.BranchPlugin uses a type in naxriscv.execute.ExecutionUnitElementSimple.
- The types involved
naxriscv.execute.BranchPlugin.BranchSetup→naxriscv.execute.ExecutionUnitElementSimple.Setup
- Direction
- naxriscv.execute.BranchPlugin uses naxriscv.execute.ExecutionUnitElementSimple, so a change to naxriscv.execute.ExecutionUnitElementSimple can break naxriscv.execute.BranchPlugin, while a change to naxriscv.execute.BranchPlugin can't break naxriscv.execute.ExecutionUnitElementSimple.
- Position
- Below the diagonal: naxriscv.execute.BranchPlugin uses a module listed above it, which is the healthy direction.
28→14 naxriscv.execute.CsrAccessPlugin uses naxriscv.execute.ExecutionUnitElementSimple✕
- Connections
- 2 pairs of types, where a type in naxriscv.execute.CsrAccessPlugin uses a type in naxriscv.execute.ExecutionUnitElementSimple.
- The types involved
naxriscv.execute.CsrAccessPlugin.CsrLogic→naxriscv.execute.ExecutionUnitElementSimple.Logicnaxriscv.execute.CsrAccessPlugin.CsrSetup→naxriscv.execute.ExecutionUnitElementSimple.Setup
- Direction
- naxriscv.execute.CsrAccessPlugin uses naxriscv.execute.ExecutionUnitElementSimple, so a change to naxriscv.execute.ExecutionUnitElementSimple can break naxriscv.execute.CsrAccessPlugin, while a change to naxriscv.execute.CsrAccessPlugin can't break naxriscv.execute.ExecutionUnitElementSimple.
- Position
- Below the diagonal: naxriscv.execute.CsrAccessPlugin uses a module listed above it, which is the healthy direction.
29→23 naxriscv.execute.fpu uses naxriscv.utilities✕
- Connections
- 2 pairs of types, where a type in naxriscv.execute.fpu uses a type in naxriscv.utilities.
- The types involved
naxriscv.execute.fpu.FpuEmbedded→naxriscv.utilities.Pluginnaxriscv.execute.fpu.FpuSettingPlugin→naxriscv.utilities.Plugin
- Direction
- naxriscv.execute.fpu uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv.execute.fpu, while a change to naxriscv.execute.fpu can't break naxriscv.utilities.
- Position
- Below the diagonal: naxriscv.execute.fpu uses a module listed above it, which is the healthy direction.
30→9 naxriscv.fetch uses naxriscv.interfaces✕
- Connections
- 3 pairs of types, where a type in naxriscv.fetch uses a type in naxriscv.interfaces.
- The types involved
naxriscv.fetch.AlignerPlugin→naxriscv.interfaces.FetchInjectornaxriscv.fetch.PcPlugin→naxriscv.interfaces.JumpCmdnaxriscv.fetch.PcPlugin→naxriscv.interfaces.JumpService
- Direction
- naxriscv.fetch uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.fetch, while a change to naxriscv.fetch can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.fetch uses a module listed above it, which is the healthy direction.
30→23 naxriscv.fetch uses naxriscv.utilities✕
- Connections
- 4 pairs of types, where a type in naxriscv.fetch uses a type in naxriscv.utilities.
- The types involved
naxriscv.fetch.AlignerPlugin→naxriscv.utilities.Pluginnaxriscv.fetch.FetchAxi4→naxriscv.utilities.Pluginnaxriscv.fetch.FetchCachePlugin→naxriscv.utilities.Pluginnaxriscv.fetch.PcPlugin→naxriscv.utilities.Plugin
- Direction
- naxriscv.fetch uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv.fetch, while a change to naxriscv.fetch can't break naxriscv.utilities.
- Position
- Below the diagonal: naxriscv.fetch uses a module listed above it, which is the healthy direction.
31→9 naxriscv.frontend uses naxriscv.interfaces✕
- Connections
- 8 pairs of types, where a type in naxriscv.frontend uses a type in naxriscv.interfaces.
- The types involved
naxriscv.frontend.FrontendPlugin→naxriscv.interfaces.LockedImplnaxriscv.frontend.RfAllocationPlugin→naxriscv.interfaces.InitCyclesnaxriscv.frontend.RfAllocationPlugin→naxriscv.interfaces.RegfileSpecnaxriscv.frontend.RfAllocationPlugin→naxriscv.interfaces.RfAllocationServicenaxriscv.frontend.RfDependencyPlugin→naxriscv.interfaces.InitCyclesnaxriscv.frontend.RfDependencyPlugin→naxriscv.interfaces.MicroOpnaxriscv.frontend.RfTranslationPlugin→naxriscv.interfaces.InitCyclesnaxriscv.frontend.RfTranslationPlugin→naxriscv.interfaces.RegfileSpec
- Direction
- naxriscv.frontend uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.frontend, while a change to naxriscv.frontend can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.frontend uses a module listed above it, which is the healthy direction.
31→23 naxriscv.frontend uses naxriscv.utilities✕
- Connections
- 5 pairs of types, where a type in naxriscv.frontend uses a type in naxriscv.utilities.
- The types involved
naxriscv.frontend.DecompressorPlugin→naxriscv.utilities.Pluginnaxriscv.frontend.FrontendPlugin→naxriscv.utilities.Pluginnaxriscv.frontend.RfAllocationPlugin→naxriscv.utilities.Pluginnaxriscv.frontend.RfDependencyPlugin→naxriscv.utilities.Pluginnaxriscv.frontend.RfTranslationPlugin→naxriscv.utilities.Plugin
- Direction
- naxriscv.frontend uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv.frontend, while a change to naxriscv.frontend can't break naxriscv.utilities.
- Position
- Below the diagonal: naxriscv.frontend uses a module listed above it, which is the healthy direction.
32→9 naxriscv.lsu uses naxriscv.interfaces✕
- Connections
- 6 pairs of types, where a type in naxriscv.lsu uses a type in naxriscv.interfaces.
- The types involved
naxriscv.lsu.DataCachePlugin→naxriscv.interfaces.LockedImplnaxriscv.lsu.LsuPlugin→naxriscv.interfaces.LockedImplnaxriscv.lsu.LsuPlugin→naxriscv.interfaces.PostCommitBusynaxriscv.lsu.LsuPlugin→naxriscv.interfaces.RegfileSpecnaxriscv.lsu.LsuPlugin→naxriscv.interfaces.WakeRegFileServicenaxriscv.lsu.LsuPlugin→naxriscv.interfaces.WakeRobService
- Direction
- naxriscv.lsu uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.lsu, while a change to naxriscv.lsu can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.lsu uses a module listed above it, which is the healthy direction.
32→23 naxriscv.lsu uses naxriscv.utilities✕
- Connections
- 6 pairs of types, where a type in naxriscv.lsu uses a type in naxriscv.utilities.
- The types involved
naxriscv.lsu.DataCacheAxi4→naxriscv.utilities.Pluginnaxriscv.lsu.DataCachePlugin→naxriscv.utilities.Pluginnaxriscv.lsu.LsuFlusher→naxriscv.utilities.Servicenaxriscv.lsu.LsuPeripheralAxiLite4→naxriscv.utilities.Pluginnaxriscv.lsu.LsuPlugin→naxriscv.utilities.Pluginnaxriscv.lsu.LsuPlugin→naxriscv.utilities.WithRfWriteSharedSpec
- Direction
- naxriscv.lsu uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv.lsu, while a change to naxriscv.lsu can't break naxriscv.utilities.
- Position
- Below the diagonal: naxriscv.lsu uses a module listed above it, which is the healthy direction.
33→9 naxriscv.misc uses naxriscv.interfaces✕
- Connections
- 19 pairs of types, where a type in naxriscv.misc uses a type in naxriscv.interfaces.
- The types involved
naxriscv.misc.CommitPlugin→naxriscv.interfaces.CommitEventnaxriscv.misc.CommitPlugin→naxriscv.interfaces.CommitServicenaxriscv.misc.CsrRamPlugin→naxriscv.interfaces.CsrRamAllocationnaxriscv.misc.CsrRamPlugin→naxriscv.interfaces.CsrRamReadnaxriscv.misc.CsrRamPlugin→naxriscv.interfaces.CsrRamServicenaxriscv.misc.CsrRamPlugin→naxriscv.interfaces.CsrRamWritenaxriscv.misc.CsrRamPlugin→naxriscv.interfaces.InitCyclesnaxriscv.misc.MmuPlugin→naxriscv.interfaces.AddressTranslationPortUsagenaxriscv.misc.MmuPlugin→naxriscv.interfaces.AddressTranslationServicenaxriscv.misc.PerformanceCounterPlugin→naxriscv.interfaces.PerformanceCounterServicenaxriscv.misc.PrivilegedPlugin→naxriscv.interfaces.PrivilegedServicenaxriscv.misc.RegFilePlugin→naxriscv.interfaces.InitCyclesnaxriscv.misc.RegFilePlugin→naxriscv.interfaces.RegFileBypassnaxriscv.misc.RegFilePlugin→naxriscv.interfaces.RegfileServicenaxriscv.misc.RegFilePlugin→naxriscv.interfaces.RegfileSpecnaxriscv.misc.RobPlugin→naxriscv.interfaces.RobServicenaxriscv.misc.StaticAddressTranslationPlugin→naxriscv.interfaces.AddressTranslationPortUsagenaxriscv.misc.StaticAddressTranslationPlugin→naxriscv.interfaces.AddressTranslationRspnaxriscv.misc.StaticAddressTranslationPlugin→naxriscv.interfaces.AddressTranslationService
- Direction
- naxriscv.misc uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.misc, while a change to naxriscv.misc can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.misc uses a module listed above it, which is the healthy direction.
33→23 naxriscv.misc uses naxriscv.utilities✕
- Connections
- 10 pairs of types, where a type in naxriscv.misc uses a type in naxriscv.utilities.
- The types involved
naxriscv.misc.CommitDebugFilterPlugin→naxriscv.utilities.Pluginnaxriscv.misc.CommitPlugin→naxriscv.utilities.Pluginnaxriscv.misc.CsrRamPlugin→naxriscv.utilities.Pluginnaxriscv.misc.MmuPlugin→naxriscv.utilities.Pluginnaxriscv.misc.PerfCsrPlugin→naxriscv.utilities.Pluginnaxriscv.misc.PerformanceCounterPlugin→naxriscv.utilities.Pluginnaxriscv.misc.PrivilegedPlugin→naxriscv.utilities.Pluginnaxriscv.misc.RegFilePlugin→naxriscv.utilities.Pluginnaxriscv.misc.RobPlugin→naxriscv.utilities.Pluginnaxriscv.misc.StaticAddressTranslationPlugin→naxriscv.utilities.Plugin
- Direction
- naxriscv.misc uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv.misc, while a change to naxriscv.misc can't break naxriscv.utilities.
- Position
- Below the diagonal: naxriscv.misc uses a module listed above it, which is the healthy direction.
34→23 naxriscv.platform.litex uses naxriscv.utilities✕
- Connections
- 1 pair of types, where a type in naxriscv.platform.litex uses a type in naxriscv.utilities.
- The types involved
naxriscv.platform.litex.NaxSocConfig→naxriscv.utilities.Plugin
- Direction
- naxriscv.platform.litex uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv.platform.litex, while a change to naxriscv.platform.litex can't break naxriscv.utilities.
- Position
- Below the diagonal: naxriscv.platform.litex uses a module listed above it, which is the healthy direction.
35→32 naxriscv.lsu.DataCachePlugin uses naxriscv.lsu✕
- Connections
- 2 pairs of types, where a type in naxriscv.lsu.DataCachePlugin uses a type in naxriscv.lsu.
- The types involved
naxriscv.lsu.DataCachePlugin.LoadPortSpec→naxriscv.lsu.DataLoadPortnaxriscv.lsu.DataCachePlugin.StorePortSpec→naxriscv.lsu.DataStorePort
- Direction
- naxriscv.lsu.DataCachePlugin uses naxriscv.lsu, so a change to naxriscv.lsu can break naxriscv.lsu.DataCachePlugin, while a change to naxriscv.lsu.DataCachePlugin can't break naxriscv.lsu.
- Position
- Below the diagonal: naxriscv.lsu.DataCachePlugin uses a module listed above it, which is the healthy direction.
36→32 naxriscv.lsu.LsuPlugin uses naxriscv.lsu✕
- Connections
- 2 pairs of types, where a type in naxriscv.lsu.LsuPlugin uses a type in naxriscv.lsu.
- The types involved
naxriscv.lsu.LsuPlugin.LoadPortSpec→naxriscv.lsu.LsuLoadPortnaxriscv.lsu.LsuPlugin.StorePortSpec→naxriscv.lsu.LsuStorePort
- Direction
- naxriscv.lsu.LsuPlugin uses naxriscv.lsu, so a change to naxriscv.lsu can break naxriscv.lsu.LsuPlugin, while a change to naxriscv.lsu.LsuPlugin can't break naxriscv.lsu.
- Position
- Below the diagonal: naxriscv.lsu.LsuPlugin uses a module listed above it, which is the healthy direction.
37→9 naxriscv.misc.MmuPlugin uses naxriscv.interfaces✕
- Connections
- 2 pairs of types, where a type in naxriscv.misc.MmuPlugin uses a type in naxriscv.interfaces.
- The types involved
naxriscv.misc.MmuPlugin.PortSpec→naxriscv.interfaces.AddressTranslationPortUsagenaxriscv.misc.MmuPlugin.PortSpec→naxriscv.interfaces.AddressTranslationRsp
- Direction
- naxriscv.misc.MmuPlugin uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.misc.MmuPlugin, while a change to naxriscv.misc.MmuPlugin can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.misc.MmuPlugin uses a module listed above it, which is the healthy direction.
37→33 naxriscv.misc.MmuPlugin uses naxriscv.misc✕
- Connections
- 2 pairs of types, where a type in naxriscv.misc.MmuPlugin uses a type in naxriscv.misc.
- The types involved
naxriscv.misc.MmuPlugin.PortSpec→naxriscv.misc.MmuPortParameternaxriscv.misc.MmuPlugin.StorageSpec→naxriscv.misc.MmuStorageParameter
- Direction
- naxriscv.misc.MmuPlugin uses naxriscv.misc, so a change to naxriscv.misc can break naxriscv.misc.MmuPlugin, while a change to naxriscv.misc.MmuPlugin can't break naxriscv.misc.
- Position
- Below the diagonal: naxriscv.misc.MmuPlugin uses a module listed above it, which is the healthy direction.
38→9 naxriscv.misc.StaticAddressTranslationPlugin uses naxriscv.interfaces✕
- Connections
- 1 pair of types, where a type in naxriscv.misc.StaticAddressTranslationPlugin uses a type in naxriscv.interfaces.
- The types involved
naxriscv.misc.StaticAddressTranslationPlugin.Spec→naxriscv.interfaces.AddressTranslationRsp
- Direction
- naxriscv.misc.StaticAddressTranslationPlugin uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.misc.StaticAddressTranslationPlugin, while a change to naxriscv.misc.StaticAddressTranslationPlugin can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.misc.StaticAddressTranslationPlugin uses a module listed above it, which is the healthy direction.
38→33 naxriscv.misc.StaticAddressTranslationPlugin uses naxriscv.misc✕
- Connections
- 1 pair of types, where a type in naxriscv.misc.StaticAddressTranslationPlugin uses a type in naxriscv.misc.
- The types involved
naxriscv.misc.StaticAddressTranslationPlugin.Spec→naxriscv.misc.StaticAddressTranslationParameter
- Direction
- naxriscv.misc.StaticAddressTranslationPlugin uses naxriscv.misc, so a change to naxriscv.misc can break naxriscv.misc.StaticAddressTranslationPlugin, while a change to naxriscv.misc.StaticAddressTranslationPlugin can't break naxriscv.misc.
- Position
- Below the diagonal: naxriscv.misc.StaticAddressTranslationPlugin uses a module listed above it, which is the healthy direction.
39→9 naxriscv.prediction uses naxriscv.interfaces✕
- Connections
- 1 pair of types, where a type in naxriscv.prediction uses a type in naxriscv.interfaces.
- The types involved
naxriscv.prediction.BranchContextPlugin→naxriscv.interfaces.LockedImpl
- Direction
- naxriscv.prediction uses naxriscv.interfaces, so a change to naxriscv.interfaces can break naxriscv.prediction, while a change to naxriscv.prediction can't break naxriscv.interfaces.
- Position
- Below the diagonal: naxriscv.prediction uses a module listed above it, which is the healthy direction.
39→23 naxriscv.prediction uses naxriscv.utilities✕
- Connections
- 9 pairs of types, where a type in naxriscv.prediction uses a type in naxriscv.utilities.
- The types involved
naxriscv.prediction.BranchContextPlugin→naxriscv.utilities.Pluginnaxriscv.prediction.BtbPlugin→naxriscv.utilities.Pluginnaxriscv.prediction.DecoderPrediction→naxriscv.utilities.Servicenaxriscv.prediction.DecoderPredictionPlugin→naxriscv.utilities.Pluginnaxriscv.prediction.FetchConditionalPrediction→naxriscv.utilities.Servicenaxriscv.prediction.FetchWordPrediction→naxriscv.utilities.Servicenaxriscv.prediction.GSharePlugin→naxriscv.utilities.Pluginnaxriscv.prediction.HistoryPlugin→naxriscv.utilities.Pluginnaxriscv.prediction.HistoryUser→naxriscv.utilities.Service
- Direction
- naxriscv.prediction uses naxriscv.utilities, so a change to naxriscv.utilities can break naxriscv.prediction, while a change to naxriscv.prediction can't break naxriscv.utilities.
- Position
- Below the diagonal: naxriscv.prediction uses a module listed above it, which is the healthy direction.
39→31 naxriscv.prediction uses naxriscv.frontend✕
- Connections
- 1 pair of types, where a type in naxriscv.prediction uses a type in naxriscv.frontend.
- The types involved
naxriscv.prediction.DecoderPredictionPlugin→naxriscv.frontend.FrontendPlugin
- Direction
- naxriscv.prediction uses naxriscv.frontend, so a change to naxriscv.frontend can break naxriscv.prediction, while a change to naxriscv.prediction can't break naxriscv.frontend.
- Position
- Below the diagonal: naxriscv.prediction uses a module listed above it, which is the healthy direction.
40→39 naxriscv.prediction.HistoryPlugin uses naxriscv.prediction✕
- Connections
- 2 pairs of types, where a type in naxriscv.prediction.HistoryPlugin uses a type in naxriscv.prediction.
- The types involved
naxriscv.prediction.HistoryPlugin.HistoryJumpSpec→naxriscv.prediction.HistoryJumpnaxriscv.prediction.HistoryPlugin.HistoryPushSpec→naxriscv.prediction.HistoryPush
- Direction
- naxriscv.prediction.HistoryPlugin uses naxriscv.prediction, so a change to naxriscv.prediction can break naxriscv.prediction.HistoryPlugin, while a change to naxriscv.prediction.HistoryPlugin can't break naxriscv.prediction.
- Position
- Below the diagonal: naxriscv.prediction.HistoryPlugin 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 91 Orphaned file finding(s) in Knowledge Freshness — start with WaitTable.scala (5), SlotSelector.scala (5), FpuCore.scala.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +8.9 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +8.9 pts | Medium | Security & performance tooling |
| Resolve the 91 Orphaned file finding(s) in Knowledge Freshness — start with WaitTable.scala (5), SlotSelector.scala (5), FpuCore.scala. | +8.1 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.9 pts | Medium | Architecture documentation |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +4.4 pts | Medium | Release Hygiene |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +2.9 pts | Medium | Nullable reference types |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +1.0 pts | Low | Project Cohesion |
| 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. | +1.6 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | Static Analysis (SAST): High: REDACTED |
| src/main/scala/naxriscv/Gen.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/lsu/LsuPlugin.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/lsu2/Lsu2Plugin.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/lsu/DataCache.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/misc/PrivilegedPlugin.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/fetch/AlignerPlugin.scala | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/platform/asic/Sky130.scala | 6.7 | Mixed | Explicit Debt: FixmeComment |
| src/main/scala/naxriscv/prediction/BtbPlugin.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/frontend/RfDependencyPlugin.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/compatibility/MultiportRam.scala | 7.2 | Mixed | Cognitive Complexity: MultiPortWritesSymplifier.doBlackboxing (cognitive 17) |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/main/scala/naxriscv/platform/tilelinkdemo/SocSim.scala | 7.8 | Mixed | Cyclomatic Complexity: SocSim.testIt (cyclomatic 34) |
| src/main/scala/naxriscv/frontend/DecompressorPlugin.scala | 7.8 | Mixed | Cyclomatic Complexity: RvcDecompressor.apply (cyclomatic 20) |
| src/main/scala/naxriscv/platform/PeripheralEmulator.scala | 7.8 | Mixed | Cyclomatic Complexity: PeripheralEmulator.onA (cyclomatic 17) |
| src/main/scala/naxriscv/platform/NaxriscvProbe.scala | 7.8 | Mixed | Cognitive Complexity: NaxriscvProbe.checkCommits (cognitive 35) |
| src/main/scala/naxriscv/sandbox/cam2/Integration.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/sandbox/cam/Integration.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/prediction/GSharePlugin.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/naxriscv/platform/litex/NaxSoc.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
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 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 52 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, 235 of 242 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala, .py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`, or `coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`, or `coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the Python suite (repository root, 2 test files) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/net/fornwall/jelf/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- 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 (9 contributor(s) across 1129 commit(s) sampled, automation and bot accounts excluded). One of them holds 92% of the history; the other 8 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D20 ADR Quality — 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. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — 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. `src/main/scala/naxriscv/sandbox/Stats.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- 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
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Config.plugins at 39.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Config.plugins (cyclomatic 39), SocSim.testIt (cyclomatic 34), RvcDecompressor.apply (cyclomatic 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 4 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was SocSim.testIt at 72.
What to do
- Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with SocSim.testIt (cognitive 72), Config.plugins (cognitive 47), NaxriscvProbe.checkCommits (cognitive 35). — 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 10 together lifts Cognitive Complexity from 7.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
9 god class(es) detected.
What to do
- Resolve the 5 FileTooLong finding(s) in God Classes — start with LsuPlugin.scala, Lsu2Plugin.scala, DataCache.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with LsuPlugin.scala, DataCache.scala, PrivilegedPlugin.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with Gen.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
6 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with Litex.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Elf.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with MultiportRam.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 13 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ExecutionUnitBase.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
68 deducted task-comment markers across 23589 LoC (0.3/KLoC) → score 9.5. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 67 TodoComment finding(s) in Explicit Debt — start with Lsu2Plugin.scala (16), LsuPlugin.scala (11), PrivilegedPlugin.scala (9). — One of this dimension's main actionable groups (67 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with Sky130.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
1 of 1 build units (sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 5 high, 3 medium, 0 low. 5 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) — `src/main/scala/naxriscv/sandbox/Stats.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- No action in Static Analysis (SAST) — all 5 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 (5 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).
D34 · Knowledge Freshness
94 of 94 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/main/scala/naxriscv/lsu/LsuPlugin.scala. Counted over 94 of the 127 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 91 Orphaned file finding(s) in Knowledge Freshness — start with WaitTable.scala (5), SlotSelector.scala (5), FpuCore.scala. — One of this dimension's main actionable groups (91 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with LsuPlugin.scala, Lsu2Plugin.scala, DataCache.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 1 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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `DecoderService` declares 28 abstract members: `addEuOp`, `addResourceDecoding`, `covers`, `euGroups`, `addMicroOpDecoding`, `addMicroOpDecodingDefault`, `addDecodingToRob`, `READ_RS`, `ARCH_RS`, `PHYS_RS`, `READ_RS`, `ARCH_RS`, `PHYS_RS`, `WRITE_RD`, `PHYS_RD`, `PHYS_RD_FREE`, `ARCH_RD`, `REGFILE_RD`, `REGFILE_RS`, `REGFILE_RS`, `rsCount`, `rsCountMax`, `rsPhysicalDepthMax`, `getTrap`, `trapHalt`, `trapRaise`, `trapReady`, `debugEnter`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 28 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/scala/naxriscv/interfaces/Service.scala:63
- `CsrService` declares 16 abstract members: `onReadHalt`, `onWriteHalt`, `onWriteBits`, `onWriteAddress`, `onWriteFlushPipeline`, `onReadAddress`, `getCsrRam`, `onReadMovingOff`, `onWriteMovingOff`, `onDecodeTrap`, `onDecodeUntrap`, `onDecodeFlushPipeline`, `onDecodeRead`, `onDecodeWrite`, `onDecodeAddress`, `onReadToWriteBits`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/scala/naxriscv/interfaces/Service.scala:435
- `TraceBackend` declares 22 abstract members: `newCpuMemoryView`, `newCpu`, `loadElf`, `loadU32`, `loadBin`, `setPc`, `writeRf`, `readRf`, `commit`, `trap`, `ioAccess`, `setInterrupt`, `addRegion`, `loadExecute`, `loadCommit`, `loadFlush`, `storeCommit`, `storeBroadcast`, `storeConditional`, `time`, `flush`, `close`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/scala/naxriscv/platform/Tracer.scala:18
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
- `hasFixedLatency` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:18, src/main/scala/naxriscv/execute/ExecutionUnitBase.scala:30
- `getFixedLatencies` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:19, src/main/scala/naxriscv/execute/ExecutionUnitBase.scala:31
- `wakeRobs` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:24
- `wakeRegFile` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:25
- `getFreePort` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/main/scala/naxriscv/frontend/RfAllocationPlugin.scala:25
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `ExecuteUnitDemo` has 4 unfinished members out of 7 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented. — src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:15
- `hasFixedLatency` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:18, src/main/scala/naxriscv/execute/ExecutionUnitBase.scala:30
- `getFixedLatencies` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:19, src/main/scala/naxriscv/execute/ExecutionUnitBase.scala:31
- `wakeRobs` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:24
- `wakeRegFile` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:25
- `getFreePort` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — src/main/scala/naxriscv/frontend/RfAllocationPlugin.scala:25
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1888 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:7
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `scala.io.Source.fromFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.mkString` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(scala.io.Source.fromFile(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. (×2) — src/main/scala/naxriscv/platform/Litex.scala:178, src/main/scala/naxriscv/platform/litex/NaxGen.scala:122
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 125 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 66% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 85% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 49% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 95% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2715 lines of test source are present (.scala, .py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — No tests discovered
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 3 pinned sbt dependency coordinate(s) were read from its 1 sbt build file(s), but Maven Central could not be asked for the licence of 2 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/net/fornwall/jelf/0.7.0/jelf-0.7.0.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — Repository kind not determined
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, Python, Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D5 Coupling — Not applicable — this sbt build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.scala, .py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 201 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Java and Scala code has 27,992 production line(s), 3 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 126 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- 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 — 6 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 119 finding(s)
- TodoComment src/main/scala/naxriscv/Gen.scala:178
- TodoComment src/main/scala/naxriscv/Gen.scala:675
- TodoComment src/main/scala/naxriscv/Gen.scala:699
- TodoComment src/main/scala/naxriscv/sandbox/cam2/Integration.scala:30
- TodoComment src/main/scala/naxriscv/sandbox/cam/Integration.scala:30
- TodoComment src/main/scala/naxriscv/prediction/BtbPlugin.scala:48
- TodoComment src/main/scala/naxriscv/prediction/BtbPlugin.scala:51
- TodoComment src/main/scala/naxriscv/prediction/BtbPlugin.scala:61
- TodoComment src/main/scala/naxriscv/prediction/GSharePlugin.scala:70
- TodoComment src/main/scala/naxriscv/platform/litex/NaxSoc.scala:164
- TodoComment src/main/scala/naxriscv/misc/CommitPlugin.scala:161
- TodoComment src/main/scala/naxriscv/misc/PrivilegedPlugin.scala:235
- TodoComment src/main/scala/naxriscv/misc/PrivilegedPlugin.scala:241
- TodoComment src/main/scala/naxriscv/misc/PrivilegedPlugin.scala:267
- TodoComment src/main/scala/naxriscv/lsu2/Lsu2Plugin.scala:250
- TodoComment src/main/scala/naxriscv/lsu2/Lsu2Plugin.scala:425
- TodoComment src/main/scala/naxriscv/lsu2/Lsu2Plugin.scala:559
- TodoComment src/main/scala/naxriscv/lsu2/Lsu2Plugin.scala:1913
- TodoComment src/main/scala/naxriscv/lsu2/Lsu2Plugin.scala:1922
- TodoComment src/main/scala/naxriscv/lsu2/Lsu2Plugin.scala:1926
- TodoComment src/main/scala/naxriscv/lsu/DataCache.scala:1887
- TodoComment src/main/scala/naxriscv/lsu/LsuPlugin.scala:755
- TodoComment src/main/scala/naxriscv/lsu/LsuPlugin.scala:1370
- TodoComment src/main/scala/naxriscv/debug/EmbeddedJtagPlugin.scala:81
- TodoComment src/main/scala/naxriscv/misc/PrivilegedPlugin.scala:356
- Unfinished stub — body is `???` src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:18
- Unfinished stub — body is `???` src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:19
- Unfinished stub — body is `???` src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:24
- Unfinished stub — body is `???` src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:25
- Unfinished stub — body is `???` src/main/scala/naxriscv/execute/ExecutionUnitBase.scala:30
- Unfinished stub — body is `???` src/main/scala/naxriscv/execute/ExecutionUnitBase.scala:31
- Unfinished stub — body is `???` src/main/scala/naxriscv/frontend/RfAllocationPlugin.scala:25
- Unfinished stub — body is ??? / NotImplementedError src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:18
- Unfinished stub — body is ??? / NotImplementedError src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:19
- Unfinished stub — body is ??? / NotImplementedError src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:24
- Unfinished stub — body is ??? / NotImplementedError src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:25
- Unfinished stub — body is ??? / NotImplementedError src/main/scala/naxriscv/execute/ExecutionUnitBase.scala:30
- Unfinished stub — body is ??? / NotImplementedError src/main/scala/naxriscv/execute/ExecutionUnitBase.scala:31
- Unfinished stub — body is ??? / NotImplementedError src/main/scala/naxriscv/frontend/RfAllocationPlugin.scala:25
- FileTooLong: lsu/LsuPlugin.scala src/main/scala/naxriscv/lsu/LsuPlugin.scala
- FileTooLong: lsu2/Lsu2Plugin.scala src/main/scala/naxriscv/lsu2/Lsu2Plugin.scala
- FileTooLong: lsu/DataCache.scala src/main/scala/naxriscv/lsu/DataCache.scala
- FileTooLong: fpu/FpuCore.scala src/main/scala/naxriscv/execute/fpu/FpuCore.scala
- FileTooLong: misc/PrivilegedPlugin.scala src/main/scala/naxriscv/misc/PrivilegedPlugin.scala
- REDACTED
- REDACTED
- REDACTED
- ClassTooLong: LsuPlugin src/main/scala/naxriscv/lsu/LsuPlugin.scala:293
- ClassTooLong: DataCache src/main/scala/naxriscv/lsu/DataCache.scala:696
- ClassTooLong: PrivilegedPlugin src/main/scala/naxriscv/misc/PrivilegedPlugin.scala:58
- Disposable created and abandoned in the function that made it src/main/scala/naxriscv/platform/Litex.scala:178
- Disposable created and abandoned in the function that made it src/main/scala/naxriscv/platform/litex/NaxGen.scala:122
- Config.plugins (cyclomatic 39) src/main/scala/naxriscv/Gen.scala:44
- SocSim.testIt (cyclomatic 34) src/main/scala/naxriscv/platform/tilelinkdemo/SocSim.scala:223
- RvcDecompressor.apply (cyclomatic 20) src/main/scala/naxriscv/frontend/DecompressorPlugin.scala:71
- PeripheralEmulator.onA (cyclomatic 17) src/main/scala/naxriscv/platform/PeripheralEmulator.scala:94
- FixmeComment src/main/scala/naxriscv/platform/asic/Sky130.scala:177
- SocSim.testIt (cognitive 72) src/main/scala/naxriscv/platform/tilelinkdemo/SocSim.scala:223
- Config.plugins (cognitive 47) src/main/scala/naxriscv/Gen.scala:44
- NaxriscvProbe.checkCommits (cognitive 35) src/main/scala/naxriscv/platform/NaxriscvProbe.scala:241
- AdderAggregator.apply (cognitive 35) src/main/scala/naxriscv/utilities/Misc.scala:180
- NaxriscvProbe.checkRob (cognitive 29) src/main/scala/naxriscv/platform/NaxriscvProbe.scala:168
- PeripheralEmulator.onA (cognitive 27) src/main/scala/naxriscv/platform/PeripheralEmulator.scala:94
- OpenRamPhase.impl (cognitive 23) src/main/scala/naxriscv/platform/asic/Sky130.scala:40
- RvcDecompressor.apply (cognitive 19) src/main/scala/naxriscv/frontend/DecompressorPlugin.scala:71
- MultiPortWritesSymplifier.doBlackboxing (cognitive 17) src/main/scala/naxriscv/compatibility/MultiportRam.scala:193
- MemReadDuringWriteHazardPhase.doBlackboxing (cognitive 16) src/main/scala/naxriscv/compatibility/MultiportRam.scala:313
- MethodTooLong: Config.plugins src/main/scala/naxriscv/Gen.scala:44
- Duplicated block (14 lines × 2) src/main/scala/naxriscv/platform/Litex.scala:191
- Duplicated block (13 lines × 2) src/main/scala/spinal/lib/misc/Elf.scala:54
- Duplicated block (8 lines × 2) src/main/scala/naxriscv/compatibility/MultiportRam.scala:316
- Duplicated block (6–7 lines × 3) src/main/scala/naxriscv/compatibility/MultiportRam.scala:197
- Duplicated block (6 lines × 2) src/main/scala/naxriscv/platform/asic/NaxAsicGen.scala:72
- Duplicated block (5 lines × 2) src/main/scala/naxriscv/lsu/DataCache.scala:536
- Low cohesion: ExecutionUnitBase (LCOM4 5) src/main/scala/naxriscv/execute/ExecutionUnitBase.scala:21
- Skeleton type — most members are unfinished src/main/scala/naxriscv/execute/ExecuteUnitDemo.scala:15
- No structured logging
Minor — 117 finding(s)
- Orphaned file src/main/scala/naxriscv/execute/fpu/FpuCore.scala:1
- Orphaned file src/main/scala/naxriscv/misc/PrivilegedPlugin.scala:1
- Orphaned file src/main/scala/naxriscv/Gen.scala:1
- Orphaned file src/main/scala/naxriscv/platform/Litex.scala:1
- Orphaned file src/main/scala/naxriscv/platform/litex/NaxGen.scala:1
- Orphaned file src/main/scala/naxriscv/misc/MmuPlugin.scala:1
- Orphaned file src/main/scala/naxriscv/fetch/FetchCachePlugin.scala:1
- Orphaned file src/main/scala/naxriscv/interfaces/Service.scala:1
- Orphaned file src/main/scala/naxriscv/platform/tilelinkdemo/SocSim.scala:1
- Orphaned file src/main/scala/naxriscv/frontend/DecoderPlugin.scala:1
- Orphaned file src/main/scala/naxriscv/compatibility/MultiportRam.scala:1
- Orphaned file src/main/scala/naxriscv/frontend/DispatchPlugin.scala:1
- Orphaned file src/main/scala/naxriscv/execute/CsrAccessPlugin.scala:1
- Orphaned file src/main/scala/naxriscv/platform/NaxriscvProbe.scala:1
- Orphaned file src/main/scala/naxriscv/misc/RegFilePlugin.scala:1
- Orphaned file src/main/scala/naxriscv/execute/ExecutionUnitBase.scala:1
- Orphaned file src/main/scala/naxriscv/utilities/Misc.scala:1
- Orphaned file src/main/scala/naxriscv/fetch/AlignerPlugin.scala:1
- Orphaned file src/main/scala/naxriscv/prediction/DecoderPredictionPlugin.scala:1
- Orphaned file src/main/scala/naxriscv/misc/CommitPlugin.scala:1
- Orphaned file src/main/scala/naxriscv/platform/Tracer.scala:1
- Orphaned file src/main/scala/naxriscv/frontend/DecompressorPlugin.scala:1
- Orphaned file src/main/scala/naxriscv/misc/PerformanceCounterPlugin.scala:1
- Orphaned file src/main/scala/naxriscv/riscv/Rvi.scala:1
- Orphaned file src/main/scala/naxriscv/frontend/RfDependencyPlugin.scala:1
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:1739
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:1752
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:1240
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:1111
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:1851
- Duplicated predicate src/main/scala/naxriscv/execute/fpu/FpuFloatExecute.scala:129
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:1899
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:1931
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:1729
- Duplicated predicate src/main/scala/naxriscv/platform/Litex.scala:106
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:1019
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:986
- Duplicated predicate src/main/scala/naxriscv/lsu/LsuPlugin.scala:2096
- Fat interface: DecoderService (28 abstract members) src/main/scala/naxriscv/interfaces/Service.scala:63
- Fat interface: CsrService (16 abstract members) src/main/scala/naxriscv/interfaces/Service.scala:435
- Fat interface: TraceBackend (22 abstract members) src/main/scala/naxriscv/platform/Tracer.scala:18
- Most significant orphaned file src/main/scala/naxriscv/lsu/LsuPlugin.scala:1
- Most significant orphaned file src/main/scala/naxriscv/lsu2/Lsu2Plugin.scala:1
- Most significant orphaned file src/main/scala/naxriscv/lsu/DataCache.scala:1
- Projects may be oversized for their cohesion
- Dormant codebase
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:7
- No changelog
- Scala's null is not held to the type system everywhere
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-fdba308ba891430cbd201e834d8708e9/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-fdba308ba891430cbd201e834d8708e9/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 . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | 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-3ff5858959304823b5979d37d82bc78b | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/main/scala/naxriscv/sandbox/Stats.scala` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). | 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-3ff5858959304823b5979d37d82bc78b | 0 | artifacts/raw/osv-scanner.json |