Executive summary
QuipNetwork/quip-validator is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because it has packages under a licence on your banned list. It scores 58 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 43, is the weakest lens and counts most in the score. The best first step is replacing the eight packages under a banned licence, worth about 13 points. Documenting the recovery plan comes next, worth about 7 points. Raising Production Readiness to 62 would lift the score to about 66.
Ten known security holes in the packages the code depends on can be used by attackers. Eight packages carry licence risk, and three passwords or keys are open to anyone who can read the repository. Updating the vulnerable packages, replacing or clearing the banned-licence packages and replacing each exposed password or key would close these risks. The two unsafe settings in infrastructure or container files need changing to safe values.
The product code is 26,974 lines, about €30,000 to rebuild.
If Production Readiness rose from 43 to 62, the lowest score rated Strong, the score would rise from 58 to about 66.
New since the last survey: 38 findings
- Cognitive Complexity · Pallet::do_submit_solution (cognitive 19) pallets/quantum-compute-mempool/src/lib.rs
- God Classes · MethodTooLong: Pallet.do_submit_solution pallets/quantum-compute-mempool/src/lib.rs
- God Classes · FileTooLong: src/benchmarking.rs pallets/quantum-compute-mempool/src/benchmarking.rs
- Code Duplication · Duplicated block (22 lines × 2) pallets/quantum-compute-mempool/src/benchmarking.rs
- Code Duplication · Duplicated block (10 lines × 2) pallets/quantum-compute-mempool/src/benchmarking.rs
- Code Duplication · Duplicated block (9 lines × 2) pallets/quantum-compute-mempool/src/benchmarking.rs
- Secrets (history) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 5 findings
- God Classes · MethodTooLong: Pallet.submit_solution pallets/quantum-compute-mempool/src/lib.rs
- Code Duplication · Duplicated block (7 lines × 2) pallets/quantum-compute-mempool/src/benchmarking.rs
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Rebuild cost: about €30,000 · Estimate
| Cost to rebuild | €10,000 to €50,000, for 167 to 530 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.8 at a score of 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 26,974 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 js.quip-signer.src | 2 pallet_emission_controller | 3 pallet_emission_controller.weights | 4 pallet_faucet_ops | 5 pallet_miner_registry | 6 pallet_quantum_compute_mempool.types | 7 pallet_validator_admission | 8 quantum_validation.errors | 9 quantum_validation.puzzle_spec | 10 quantum_validation.validation | 11 js.quip-signer | 12 pallet_emission_controller.pallet | 13 pallet_faucet_ops.weights | 14 pallet_miner_registry.weights | 15 pallet_quantum_compute_mempool.benchmark_weights | 16 pallet_quantum_compute_mempool.benchmarking | 17 pallet_quantum_compute_mempool.delivery | 18 pallet_quantum_compute_mempool.lifecycle | 19 pallet_quantum_compute_mempool.rewards | 20 pallet_quantum_compute_mempool.weights | 21 pallet_quantum_pow.benchmark_weights | 22 pallet_quantum_pow.topology | 23 pallet_quantum_pow.types | 24 pallet_quantum_pow.weights | 25 pallet_template.weights | 26 pallet_validator_admission.weights | 27 pallet_xqvm.weights | 28 quantum_validation.energy | 29 quantum_validation.ising | 30 pallet_evm_chain_id.pallet | 31 pallet_faucet_ops.pallet | 32 pallet_miner_registry.pallet | 33 pallet_quantum_compute_mempool.pallet | 34 pallet_quantum_pow.benchmarking | 35 pallet_quantum_pow.difficulty | 36 pallet_quantum_pow.migration.v5 | 37 pallet_template.pallet | 38 pallet_validator_admission.pallet | 39 pallet_xqvm.pallet | 40 pallet_quantum_pow.pallet |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 js.quip-signer.src | ||||||||||||||||||||||||||||||||||||||||
| 2 pallet_emission_controller | ||||||||||||||||||||||||||||||||||||||||
| 3 pallet_emission_controller.weights | ||||||||||||||||||||||||||||||||||||||||
| 4 pallet_faucet_ops | ||||||||||||||||||||||||||||||||||||||||
| 5 pallet_miner_registry | ||||||||||||||||||||||||||||||||||||||||
| 6 pallet_quantum_compute_mempool.types | ||||||||||||||||||||||||||||||||||||||||
| 7 pallet_validator_admission | ||||||||||||||||||||||||||||||||||||||||
| 8 quantum_validation.errors | ||||||||||||||||||||||||||||||||||||||||
| 9 quantum_validation.puzzle_spec | ||||||||||||||||||||||||||||||||||||||||
| 10 quantum_validation.validation | ||||||||||||||||||||||||||||||||||||||||
| 11 js.quip-signer | 4 | |||||||||||||||||||||||||||||||||||||||
| 12 pallet_emission_controller.pallet | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 pallet_faucet_ops.weights | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 pallet_miner_registry.weights | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 pallet_quantum_compute_mempool.benchmark_weights | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 pallet_quantum_compute_mempool.benchmarking | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 pallet_quantum_compute_mempool.delivery | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 pallet_quantum_compute_mempool.lifecycle | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 pallet_quantum_compute_mempool.rewards | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 pallet_quantum_compute_mempool.weights | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 pallet_quantum_pow.benchmark_weights | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 pallet_quantum_pow.topology | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 pallet_quantum_pow.types | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 pallet_quantum_pow.weights | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 pallet_template.weights | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 pallet_validator_admission.weights | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 pallet_xqvm.weights | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 quantum_validation.energy | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 quantum_validation.ising | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 pallet_evm_chain_id.pallet | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 pallet_faucet_ops.pallet | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 pallet_miner_registry.pallet | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 pallet_quantum_compute_mempool.pallet | 6 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 pallet_quantum_pow.benchmarking | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 pallet_quantum_pow.difficulty | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 pallet_quantum_pow.migration.v5 | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 pallet_template.pallet | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 pallet_validator_admission.pallet | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 pallet_xqvm.pallet | 2 | |||||||||||||||||||||||||||||||||||||||
| 40 pallet_quantum_pow.pallet | 1 | 1 | 1 | 1 | 2 |
11→1 js.quip-signer uses js.quip-signer.src✕
- Connections
- 4 pairs of types, where a type in js.quip-signer uses a type in js.quip-signer.src.
- The types involved
js.quip-signer.index→js.quip-signer.src.QuipInjectedExtensionjs.quip-signer.index→js.quip-signer.src.QuipInjectedProviderjs.quip-signer.index→js.quip-signer.src.QuipInjectionOptionsjs.quip-signer.index→js.quip-signer.src.QuipWasmCrypto
- Direction
- js.quip-signer uses js.quip-signer.src, so a change to js.quip-signer.src can break js.quip-signer, while a change to js.quip-signer can't break js.quip-signer.src.
- Position
- Below the diagonal: js.quip-signer uses a module listed above it, which is the healthy direction.
12→2 pallet_emission_controller.pallet uses pallet_emission_controller✕
- Connections
- 1 pair of types, where a type in pallet_emission_controller.pallet uses a type in pallet_emission_controller.
- The types involved
pallet_emission_controller.pallet.Pallet→pallet_emission_controller.FaucetMint
- Direction
- pallet_emission_controller.pallet uses pallet_emission_controller, so a change to pallet_emission_controller can break pallet_emission_controller.pallet, while a change to pallet_emission_controller.pallet can't break pallet_emission_controller.
- Position
- Below the diagonal: pallet_emission_controller.pallet uses a module listed above it, which is the healthy direction.
13→3 pallet_faucet_ops.weights uses pallet_emission_controller.weights✕
- Connections
- 1 pair of types, where a type in pallet_faucet_ops.weights uses a type in pallet_emission_controller.weights.
- The types involved
pallet_faucet_ops.weights.SubstrateWeight→pallet_emission_controller.weights.WeightInfo
- Direction
- pallet_faucet_ops.weights uses pallet_emission_controller.weights, so a change to pallet_emission_controller.weights can break pallet_faucet_ops.weights, while a change to pallet_faucet_ops.weights can't break pallet_emission_controller.weights.
- Position
- Below the diagonal: pallet_faucet_ops.weights uses a module listed above it, which is the healthy direction.
14→3 pallet_miner_registry.weights uses pallet_emission_controller.weights✕
- Connections
- 1 pair of types, where a type in pallet_miner_registry.weights uses a type in pallet_emission_controller.weights.
- The types involved
pallet_miner_registry.weights.SubstrateWeight→pallet_emission_controller.weights.WeightInfo
- Direction
- pallet_miner_registry.weights uses pallet_emission_controller.weights, so a change to pallet_emission_controller.weights can break pallet_miner_registry.weights, while a change to pallet_miner_registry.weights can't break pallet_emission_controller.weights.
- Position
- Below the diagonal: pallet_miner_registry.weights uses a module listed above it, which is the healthy direction.
15→3 pallet_quantum_compute_mempool.benchmark_weights uses pallet_emission_controller.weights✕
- Connections
- 1 pair of types, where a type in pallet_quantum_compute_mempool.benchmark_weights uses a type in pallet_emission_controller.weights.
- The types involved
pallet_quantum_compute_mempool.benchmark_weights.SubstrateWeight→pallet_emission_controller.weights.WeightInfo
- Direction
- pallet_quantum_compute_mempool.benchmark_weights uses pallet_emission_controller.weights, so a change to pallet_emission_controller.weights can break pallet_quantum_compute_mempool.benchmark_weights, while a change to pallet_quantum_compute_mempool.benchmark_weights can't break pallet_emission_controller.weights.
- Position
- Below the diagonal: pallet_quantum_compute_mempool.benchmark_weights uses a module listed above it, which is the healthy direction.
16→6 pallet_quantum_compute_mempool.benchmarking uses pallet_quantum_compute_mempool.types✕
- Connections
- 3 pairs of types, where a type in pallet_quantum_compute_mempool.benchmarking uses a type in pallet_quantum_compute_mempool.types.
- The types involved
pallet_quantum_compute_mempool.benchmarking.benchmarking$module→pallet_quantum_compute_mempool.types.Formulationpallet_quantum_compute_mempool.benchmarking.benchmarking$module→pallet_quantum_compute_mempool.types.ResultDeliverypallet_quantum_compute_mempool.benchmarking.benchmarking$module→pallet_quantum_compute_mempool.types.RewardResolution
- Direction
- pallet_quantum_compute_mempool.benchmarking uses pallet_quantum_compute_mempool.types, so a change to pallet_quantum_compute_mempool.types can break pallet_quantum_compute_mempool.benchmarking, while a change to pallet_quantum_compute_mempool.benchmarking can't break pallet_quantum_compute_mempool.types.
- Position
- Below the diagonal: pallet_quantum_compute_mempool.benchmarking uses a module listed above it, which is the healthy direction.
17→6 pallet_quantum_compute_mempool.delivery uses pallet_quantum_compute_mempool.types✕
- Connections
- 2 pairs of types, where a type in pallet_quantum_compute_mempool.delivery uses a type in pallet_quantum_compute_mempool.types.
- The types involved
pallet_quantum_compute_mempool.delivery.delivery$module→pallet_quantum_compute_mempool.types.JobModepallet_quantum_compute_mempool.delivery.delivery$module→pallet_quantum_compute_mempool.types.ResultDelivery
- Direction
- pallet_quantum_compute_mempool.delivery uses pallet_quantum_compute_mempool.types, so a change to pallet_quantum_compute_mempool.types can break pallet_quantum_compute_mempool.delivery, while a change to pallet_quantum_compute_mempool.delivery can't break pallet_quantum_compute_mempool.types.
- Position
- Below the diagonal: pallet_quantum_compute_mempool.delivery uses a module listed above it, which is the healthy direction.
18→6 pallet_quantum_compute_mempool.lifecycle uses pallet_quantum_compute_mempool.types✕
- Connections
- 1 pair of types, where a type in pallet_quantum_compute_mempool.lifecycle uses a type in pallet_quantum_compute_mempool.types.
- The types involved
pallet_quantum_compute_mempool.lifecycle.lifecycle$module→pallet_quantum_compute_mempool.types.OrderTiming
- Direction
- pallet_quantum_compute_mempool.lifecycle uses pallet_quantum_compute_mempool.types, so a change to pallet_quantum_compute_mempool.types can break pallet_quantum_compute_mempool.lifecycle, while a change to pallet_quantum_compute_mempool.lifecycle can't break pallet_quantum_compute_mempool.types.
- Position
- Below the diagonal: pallet_quantum_compute_mempool.lifecycle uses a module listed above it, which is the healthy direction.
19→6 pallet_quantum_compute_mempool.rewards uses pallet_quantum_compute_mempool.types✕
- Connections
- 2 pairs of types, where a type in pallet_quantum_compute_mempool.rewards uses a type in pallet_quantum_compute_mempool.types.
- The types involved
pallet_quantum_compute_mempool.rewards.rewards$module→pallet_quantum_compute_mempool.types.FrontRunnerpallet_quantum_compute_mempool.rewards.rewards$module→pallet_quantum_compute_mempool.types.RankedSolver
- Direction
- pallet_quantum_compute_mempool.rewards uses pallet_quantum_compute_mempool.types, so a change to pallet_quantum_compute_mempool.types can break pallet_quantum_compute_mempool.rewards, while a change to pallet_quantum_compute_mempool.rewards can't break pallet_quantum_compute_mempool.types.
- Position
- Below the diagonal: pallet_quantum_compute_mempool.rewards uses a module listed above it, which is the healthy direction.
20→3 pallet_quantum_compute_mempool.weights uses pallet_emission_controller.weights✕
- Connections
- 1 pair of types, where a type in pallet_quantum_compute_mempool.weights uses a type in pallet_emission_controller.weights.
- The types involved
pallet_quantum_compute_mempool.weights.SubstrateWeight→pallet_emission_controller.weights.WeightInfo
- Direction
- pallet_quantum_compute_mempool.weights uses pallet_emission_controller.weights, so a change to pallet_emission_controller.weights can break pallet_quantum_compute_mempool.weights, while a change to pallet_quantum_compute_mempool.weights can't break pallet_emission_controller.weights.
- Position
- Below the diagonal: pallet_quantum_compute_mempool.weights uses a module listed above it, which is the healthy direction.
21→3 pallet_quantum_pow.benchmark_weights uses pallet_emission_controller.weights✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.benchmark_weights uses a type in pallet_emission_controller.weights.
- The types involved
pallet_quantum_pow.benchmark_weights.SubstrateWeight→pallet_emission_controller.weights.WeightInfo
- Direction
- pallet_quantum_pow.benchmark_weights uses pallet_emission_controller.weights, so a change to pallet_emission_controller.weights can break pallet_quantum_pow.benchmark_weights, while a change to pallet_quantum_pow.benchmark_weights can't break pallet_emission_controller.weights.
- Position
- Below the diagonal: pallet_quantum_pow.benchmark_weights uses a module listed above it, which is the healthy direction.
22→9 pallet_quantum_pow.topology uses quantum_validation.puzzle_spec✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.topology uses a type in quantum_validation.puzzle_spec.
- The types involved
pallet_quantum_pow.topology.topology$module→quantum_validation.puzzle_spec.AllowedValueSpec
- Direction
- pallet_quantum_pow.topology uses quantum_validation.puzzle_spec, so a change to quantum_validation.puzzle_spec can break pallet_quantum_pow.topology, while a change to pallet_quantum_pow.topology can't break quantum_validation.puzzle_spec.
- Position
- Below the diagonal: pallet_quantum_pow.topology uses a module listed above it, which is the healthy direction.
23→9 pallet_quantum_pow.types uses quantum_validation.puzzle_spec✕
- Connections
- 2 pairs of types, where a type in pallet_quantum_pow.types uses a type in quantum_validation.puzzle_spec.
- The types involved
pallet_quantum_pow.types.MiningSnapshot→quantum_validation.puzzle_spec.AllowedValueSpecpallet_quantum_pow.types.TopologyMeta→quantum_validation.puzzle_spec.AllowedValueSpec
- Direction
- pallet_quantum_pow.types uses quantum_validation.puzzle_spec, so a change to quantum_validation.puzzle_spec can break pallet_quantum_pow.types, while a change to pallet_quantum_pow.types can't break quantum_validation.puzzle_spec.
- Position
- Below the diagonal: pallet_quantum_pow.types uses a module listed above it, which is the healthy direction.
24→3 pallet_quantum_pow.weights uses pallet_emission_controller.weights✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.weights uses a type in pallet_emission_controller.weights.
- The types involved
pallet_quantum_pow.weights.SubstrateWeight→pallet_emission_controller.weights.WeightInfo
- Direction
- pallet_quantum_pow.weights uses pallet_emission_controller.weights, so a change to pallet_emission_controller.weights can break pallet_quantum_pow.weights, while a change to pallet_quantum_pow.weights can't break pallet_emission_controller.weights.
- Position
- Below the diagonal: pallet_quantum_pow.weights uses a module listed above it, which is the healthy direction.
25→3 pallet_template.weights uses pallet_emission_controller.weights✕
- Connections
- 1 pair of types, where a type in pallet_template.weights uses a type in pallet_emission_controller.weights.
- The types involved
pallet_template.weights.SubstrateWeight→pallet_emission_controller.weights.WeightInfo
- Direction
- pallet_template.weights uses pallet_emission_controller.weights, so a change to pallet_emission_controller.weights can break pallet_template.weights, while a change to pallet_template.weights can't break pallet_emission_controller.weights.
- Position
- Below the diagonal: pallet_template.weights uses a module listed above it, which is the healthy direction.
26→3 pallet_validator_admission.weights uses pallet_emission_controller.weights✕
- Connections
- 1 pair of types, where a type in pallet_validator_admission.weights uses a type in pallet_emission_controller.weights.
- The types involved
pallet_validator_admission.weights.SubstrateWeight→pallet_emission_controller.weights.WeightInfo
- Direction
- pallet_validator_admission.weights uses pallet_emission_controller.weights, so a change to pallet_emission_controller.weights can break pallet_validator_admission.weights, while a change to pallet_validator_admission.weights can't break pallet_emission_controller.weights.
- Position
- Below the diagonal: pallet_validator_admission.weights uses a module listed above it, which is the healthy direction.
27→3 pallet_xqvm.weights uses pallet_emission_controller.weights✕
- Connections
- 1 pair of types, where a type in pallet_xqvm.weights uses a type in pallet_emission_controller.weights.
- The types involved
pallet_xqvm.weights.SubstrateWeight→pallet_emission_controller.weights.WeightInfo
- Direction
- pallet_xqvm.weights uses pallet_emission_controller.weights, so a change to pallet_emission_controller.weights can break pallet_xqvm.weights, while a change to pallet_xqvm.weights can't break pallet_emission_controller.weights.
- Position
- Below the diagonal: pallet_xqvm.weights uses a module listed above it, which is the healthy direction.
28→9 quantum_validation.energy uses quantum_validation.puzzle_spec✕
- Connections
- 1 pair of types, where a type in quantum_validation.energy uses a type in quantum_validation.puzzle_spec.
- The types involved
quantum_validation.energy.energy$module→quantum_validation.puzzle_spec.AllowedValueSpec
- Direction
- quantum_validation.energy uses quantum_validation.puzzle_spec, so a change to quantum_validation.puzzle_spec can break quantum_validation.energy, while a change to quantum_validation.energy can't break quantum_validation.puzzle_spec.
- Position
- Below the diagonal: quantum_validation.energy uses a module listed above it, which is the healthy direction.
28→10 quantum_validation.energy uses quantum_validation.validation✕
- Connections
- 1 pair of types, where a type in quantum_validation.energy uses a type in quantum_validation.validation.
- The types involved
quantum_validation.energy.energy$module→quantum_validation.validation.TopologyIndex
- Direction
- quantum_validation.energy uses quantum_validation.validation, so a change to quantum_validation.validation can break quantum_validation.energy, while a change to quantum_validation.energy can't break quantum_validation.validation.
- Position
- Below the diagonal: quantum_validation.energy uses a module listed above it, which is the healthy direction.
29→9 quantum_validation.ising uses quantum_validation.puzzle_spec✕
- Connections
- 1 pair of types, where a type in quantum_validation.ising uses a type in quantum_validation.puzzle_spec.
- The types involved
quantum_validation.ising.ising$module→quantum_validation.puzzle_spec.AllowedValueSpec
- Direction
- quantum_validation.ising uses quantum_validation.puzzle_spec, so a change to quantum_validation.puzzle_spec can break quantum_validation.ising, while a change to quantum_validation.ising can't break quantum_validation.puzzle_spec.
- Position
- Below the diagonal: quantum_validation.ising uses a module listed above it, which is the healthy direction.
29→10 quantum_validation.ising uses quantum_validation.validation✕
- Connections
- 1 pair of types, where a type in quantum_validation.ising uses a type in quantum_validation.validation.
- The types involved
quantum_validation.ising.ising$module→quantum_validation.validation.TopologyIndex
- Direction
- quantum_validation.ising uses quantum_validation.validation, so a change to quantum_validation.validation can break quantum_validation.ising, while a change to quantum_validation.ising can't break quantum_validation.validation.
- Position
- Below the diagonal: quantum_validation.ising uses a module listed above it, which is the healthy direction.
30→12 pallet_evm_chain_id.pallet uses pallet_emission_controller.pallet✕
- Connections
- 1 pair of types, where a type in pallet_evm_chain_id.pallet uses a type in pallet_emission_controller.pallet.
- The types involved
pallet_evm_chain_id.pallet.Config→pallet_emission_controller.pallet.Config
- Direction
- pallet_evm_chain_id.pallet uses pallet_emission_controller.pallet, so a change to pallet_emission_controller.pallet can break pallet_evm_chain_id.pallet, while a change to pallet_evm_chain_id.pallet can't break pallet_emission_controller.pallet.
- Position
- Below the diagonal: pallet_evm_chain_id.pallet uses a module listed above it, which is the healthy direction.
31→4 pallet_faucet_ops.pallet uses pallet_faucet_ops✕
- Connections
- 1 pair of types, where a type in pallet_faucet_ops.pallet uses a type in pallet_faucet_ops.
- The types involved
pallet_faucet_ops.pallet.GenesisConfig→pallet_faucet_ops.FaucetState
- Direction
- pallet_faucet_ops.pallet uses pallet_faucet_ops, so a change to pallet_faucet_ops can break pallet_faucet_ops.pallet, while a change to pallet_faucet_ops.pallet can't break pallet_faucet_ops.
- Position
- Below the diagonal: pallet_faucet_ops.pallet uses a module listed above it, which is the healthy direction.
31→12 pallet_faucet_ops.pallet uses pallet_emission_controller.pallet✕
- Connections
- 1 pair of types, where a type in pallet_faucet_ops.pallet uses a type in pallet_emission_controller.pallet.
- The types involved
pallet_faucet_ops.pallet.Config→pallet_emission_controller.pallet.Config
- Direction
- pallet_faucet_ops.pallet uses pallet_emission_controller.pallet, so a change to pallet_emission_controller.pallet can break pallet_faucet_ops.pallet, while a change to pallet_faucet_ops.pallet can't break pallet_emission_controller.pallet.
- Position
- Below the diagonal: pallet_faucet_ops.pallet uses a module listed above it, which is the healthy direction.
32→5 pallet_miner_registry.pallet uses pallet_miner_registry✕
- Connections
- 1 pair of types, where a type in pallet_miner_registry.pallet uses a type in pallet_miner_registry.
- The types involved
pallet_miner_registry.pallet.Pallet→pallet_miner_registry.MinerKind
- Direction
- pallet_miner_registry.pallet uses pallet_miner_registry, so a change to pallet_miner_registry can break pallet_miner_registry.pallet, while a change to pallet_miner_registry.pallet can't break pallet_miner_registry.
- Position
- Below the diagonal: pallet_miner_registry.pallet uses a module listed above it, which is the healthy direction.
32→12 pallet_miner_registry.pallet uses pallet_emission_controller.pallet✕
- Connections
- 1 pair of types, where a type in pallet_miner_registry.pallet uses a type in pallet_emission_controller.pallet.
- The types involved
pallet_miner_registry.pallet.Config→pallet_emission_controller.pallet.Config
- Direction
- pallet_miner_registry.pallet uses pallet_emission_controller.pallet, so a change to pallet_emission_controller.pallet can break pallet_miner_registry.pallet, while a change to pallet_miner_registry.pallet can't break pallet_emission_controller.pallet.
- Position
- Below the diagonal: pallet_miner_registry.pallet uses a module listed above it, which is the healthy direction.
33→6 pallet_quantum_compute_mempool.pallet uses pallet_quantum_compute_mempool.types✕
- Connections
- 6 pairs of types, where a type in pallet_quantum_compute_mempool.pallet uses a type in pallet_quantum_compute_mempool.types.
- The types involved
pallet_quantum_compute_mempool.pallet.Pallet→pallet_quantum_compute_mempool.types.Formulationpallet_quantum_compute_mempool.pallet.Pallet→pallet_quantum_compute_mempool.types.MinerTypepallet_quantum_compute_mempool.pallet.Pallet→pallet_quantum_compute_mempool.types.RankedSolverpallet_quantum_compute_mempool.pallet.Pallet→pallet_quantum_compute_mempool.types.ResultDeliverypallet_quantum_compute_mempool.pallet.Pallet→pallet_quantum_compute_mempool.types.RewardResolutionpallet_quantum_compute_mempool.pallet.Pallet→pallet_quantum_compute_mempool.types.WinnerPayee
- Direction
- pallet_quantum_compute_mempool.pallet uses pallet_quantum_compute_mempool.types, so a change to pallet_quantum_compute_mempool.types can break pallet_quantum_compute_mempool.pallet, while a change to pallet_quantum_compute_mempool.pallet can't break pallet_quantum_compute_mempool.types.
- Position
- Below the diagonal: pallet_quantum_compute_mempool.pallet uses a module listed above it, which is the healthy direction.
33→8 pallet_quantum_compute_mempool.pallet uses quantum_validation.errors✕
- Connections
- 1 pair of types, where a type in pallet_quantum_compute_mempool.pallet uses a type in quantum_validation.errors.
- The types involved
pallet_quantum_compute_mempool.pallet.Pallet→quantum_validation.errors.ValidationError
- Direction
- pallet_quantum_compute_mempool.pallet uses quantum_validation.errors, so a change to quantum_validation.errors can break pallet_quantum_compute_mempool.pallet, while a change to pallet_quantum_compute_mempool.pallet can't break quantum_validation.errors.
- Position
- Below the diagonal: pallet_quantum_compute_mempool.pallet uses a module listed above it, which is the healthy direction.
33→12 pallet_quantum_compute_mempool.pallet uses pallet_emission_controller.pallet✕
- Connections
- 2 pairs of types, where a type in pallet_quantum_compute_mempool.pallet uses a type in pallet_emission_controller.pallet.
- The types involved
pallet_quantum_compute_mempool.pallet.Config→pallet_emission_controller.pallet.Configpallet_quantum_compute_mempool.pallet.Pallet→pallet_emission_controller.pallet.Error
- Direction
- pallet_quantum_compute_mempool.pallet uses pallet_emission_controller.pallet, so a change to pallet_emission_controller.pallet can break pallet_quantum_compute_mempool.pallet, while a change to pallet_quantum_compute_mempool.pallet can't break pallet_emission_controller.pallet.
- Position
- Below the diagonal: pallet_quantum_compute_mempool.pallet uses a module listed above it, which is the healthy direction.
34→9 pallet_quantum_pow.benchmarking uses quantum_validation.puzzle_spec✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.benchmarking uses a type in quantum_validation.puzzle_spec.
- The types involved
pallet_quantum_pow.benchmarking.benchmarking$module→quantum_validation.puzzle_spec.AllowedValueSpec
- Direction
- pallet_quantum_pow.benchmarking uses quantum_validation.puzzle_spec, so a change to quantum_validation.puzzle_spec can break pallet_quantum_pow.benchmarking, while a change to pallet_quantum_pow.benchmarking can't break quantum_validation.puzzle_spec.
- Position
- Below the diagonal: pallet_quantum_pow.benchmarking uses a module listed above it, which is the healthy direction.
34→23 pallet_quantum_pow.benchmarking uses pallet_quantum_pow.types✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.benchmarking uses a type in pallet_quantum_pow.types.
- The types involved
pallet_quantum_pow.benchmarking.benchmarking$module→pallet_quantum_pow.types.DifficultyConfig
- Direction
- pallet_quantum_pow.benchmarking uses pallet_quantum_pow.types, so a change to pallet_quantum_pow.types can break pallet_quantum_pow.benchmarking, while a change to pallet_quantum_pow.benchmarking can't break pallet_quantum_pow.types.
- Position
- Below the diagonal: pallet_quantum_pow.benchmarking uses a module listed above it, which is the healthy direction.
35→9 pallet_quantum_pow.difficulty uses quantum_validation.puzzle_spec✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.difficulty uses a type in quantum_validation.puzzle_spec.
- The types involved
pallet_quantum_pow.difficulty.EnergyCurve→quantum_validation.puzzle_spec.AllowedValueSpec
- Direction
- pallet_quantum_pow.difficulty uses quantum_validation.puzzle_spec, so a change to quantum_validation.puzzle_spec can break pallet_quantum_pow.difficulty, while a change to pallet_quantum_pow.difficulty can't break quantum_validation.puzzle_spec.
- Position
- Below the diagonal: pallet_quantum_pow.difficulty uses a module listed above it, which is the healthy direction.
35→23 pallet_quantum_pow.difficulty uses pallet_quantum_pow.types✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.difficulty uses a type in pallet_quantum_pow.types.
- The types involved
pallet_quantum_pow.difficulty.difficulty$module→pallet_quantum_pow.types.DifficultyConfig
- Direction
- pallet_quantum_pow.difficulty uses pallet_quantum_pow.types, so a change to pallet_quantum_pow.types can break pallet_quantum_pow.difficulty, while a change to pallet_quantum_pow.difficulty can't break pallet_quantum_pow.types.
- Position
- Below the diagonal: pallet_quantum_pow.difficulty uses a module listed above it, which is the healthy direction.
36→23 pallet_quantum_pow.migration.v5 uses pallet_quantum_pow.types✕
- Connections
- 2 pairs of types, where a type in pallet_quantum_pow.migration.v5 uses a type in pallet_quantum_pow.types.
- The types involved
pallet_quantum_pow.migration.v5.PreTopologyQBlock→pallet_quantum_pow.types.DifficultyConfigpallet_quantum_pow.migration.v5.V4QBlock→pallet_quantum_pow.types.DifficultyConfig
- Direction
- pallet_quantum_pow.migration.v5 uses pallet_quantum_pow.types, so a change to pallet_quantum_pow.types can break pallet_quantum_pow.migration.v5, while a change to pallet_quantum_pow.migration.v5 can't break pallet_quantum_pow.types.
- Position
- Below the diagonal: pallet_quantum_pow.migration.v5 uses a module listed above it, which is the healthy direction.
37→12 pallet_template.pallet uses pallet_emission_controller.pallet✕
- Connections
- 1 pair of types, where a type in pallet_template.pallet uses a type in pallet_emission_controller.pallet.
- The types involved
pallet_template.pallet.Config→pallet_emission_controller.pallet.Config
- Direction
- pallet_template.pallet uses pallet_emission_controller.pallet, so a change to pallet_emission_controller.pallet can break pallet_template.pallet, while a change to pallet_template.pallet can't break pallet_emission_controller.pallet.
- Position
- Below the diagonal: pallet_template.pallet uses a module listed above it, which is the healthy direction.
38→7 pallet_validator_admission.pallet uses pallet_validator_admission✕
- Connections
- 2 pairs of types, where a type in pallet_validator_admission.pallet uses a type in pallet_validator_admission.
- The types involved
pallet_validator_admission.pallet.GenesisConfig→pallet_validator_admission.AdmissionModepallet_validator_admission.pallet.Pallet→pallet_validator_admission.AdmissionMode
- Direction
- pallet_validator_admission.pallet uses pallet_validator_admission, so a change to pallet_validator_admission can break pallet_validator_admission.pallet, while a change to pallet_validator_admission.pallet can't break pallet_validator_admission.
- Position
- Below the diagonal: pallet_validator_admission.pallet uses a module listed above it, which is the healthy direction.
38→12 pallet_validator_admission.pallet uses pallet_emission_controller.pallet✕
- Connections
- 1 pair of types, where a type in pallet_validator_admission.pallet uses a type in pallet_emission_controller.pallet.
- The types involved
pallet_validator_admission.pallet.Config→pallet_emission_controller.pallet.Config
- Direction
- pallet_validator_admission.pallet uses pallet_emission_controller.pallet, so a change to pallet_emission_controller.pallet can break pallet_validator_admission.pallet, while a change to pallet_validator_admission.pallet can't break pallet_emission_controller.pallet.
- Position
- Below the diagonal: pallet_validator_admission.pallet uses a module listed above it, which is the healthy direction.
39→12 pallet_xqvm.pallet uses pallet_emission_controller.pallet✕
- Connections
- 2 pairs of types, where a type in pallet_xqvm.pallet uses a type in pallet_emission_controller.pallet.
- The types involved
pallet_xqvm.pallet.Config→pallet_emission_controller.pallet.Configpallet_xqvm.pallet.pallet$module→pallet_emission_controller.pallet.Error
- Direction
- pallet_xqvm.pallet uses pallet_emission_controller.pallet, so a change to pallet_emission_controller.pallet can break pallet_xqvm.pallet, while a change to pallet_xqvm.pallet can't break pallet_emission_controller.pallet.
- Position
- Below the diagonal: pallet_xqvm.pallet uses a module listed above it, which is the healthy direction.
40→9 pallet_quantum_pow.pallet uses quantum_validation.puzzle_spec✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.pallet uses a type in quantum_validation.puzzle_spec.
- The types involved
pallet_quantum_pow.pallet.Pallet→quantum_validation.puzzle_spec.AllowedValueSpec
- Direction
- pallet_quantum_pow.pallet uses quantum_validation.puzzle_spec, so a change to quantum_validation.puzzle_spec can break pallet_quantum_pow.pallet, while a change to pallet_quantum_pow.pallet can't break quantum_validation.puzzle_spec.
- Position
- Below the diagonal: pallet_quantum_pow.pallet uses a module listed above it, which is the healthy direction.
40→10 pallet_quantum_pow.pallet uses quantum_validation.validation✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.pallet uses a type in quantum_validation.validation.
- The types involved
pallet_quantum_pow.pallet.Pallet→quantum_validation.validation.TopologyIndex
- Direction
- pallet_quantum_pow.pallet uses quantum_validation.validation, so a change to quantum_validation.validation can break pallet_quantum_pow.pallet, while a change to pallet_quantum_pow.pallet can't break quantum_validation.validation.
- Position
- Below the diagonal: pallet_quantum_pow.pallet uses a module listed above it, which is the healthy direction.
40→12 pallet_quantum_pow.pallet uses pallet_emission_controller.pallet✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.pallet uses a type in pallet_emission_controller.pallet.
- The types involved
pallet_quantum_pow.pallet.Config→pallet_emission_controller.pallet.Config
- Direction
- pallet_quantum_pow.pallet uses pallet_emission_controller.pallet, so a change to pallet_emission_controller.pallet can break pallet_quantum_pow.pallet, while a change to pallet_quantum_pow.pallet can't break pallet_emission_controller.pallet.
- Position
- Below the diagonal: pallet_quantum_pow.pallet uses a module listed above it, which is the healthy direction.
40→23 pallet_quantum_pow.pallet uses pallet_quantum_pow.types✕
- Connections
- 1 pair of types, where a type in pallet_quantum_pow.pallet uses a type in pallet_quantum_pow.types.
- The types involved
pallet_quantum_pow.pallet.Pallet→pallet_quantum_pow.types.DifficultyConfig
- Direction
- pallet_quantum_pow.pallet uses pallet_quantum_pow.types, so a change to pallet_quantum_pow.types can break pallet_quantum_pow.pallet, while a change to pallet_quantum_pow.pallet can't break pallet_quantum_pow.types.
- Position
- Below the diagonal: pallet_quantum_pow.pallet uses a module listed above it, which is the healthy direction.
40→35 pallet_quantum_pow.pallet uses pallet_quantum_pow.difficulty✕
- Connections
- 2 pairs of types, where a type in pallet_quantum_pow.pallet uses a type in pallet_quantum_pow.difficulty.
- The types involved
pallet_quantum_pow.pallet.Pallet→pallet_quantum_pow.difficulty.CurveCpallet_quantum_pow.pallet.Pallet→pallet_quantum_pow.difficulty.EnergyCurve
- Direction
- pallet_quantum_pow.pallet uses pallet_quantum_pow.difficulty, so a change to pallet_quantum_pow.difficulty can break pallet_quantum_pow.pallet, while a change to pallet_quantum_pow.pallet can't break pallet_quantum_pow.difficulty.
- Position
- Below the diagonal: pallet_quantum_pow.pallet uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 75 | High / Critical |
| A02:2025 — Security Misconfiguration | 13 | High / Critical |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
First, resolve the eight banned license findings to ensure full compliance. Next, codify backups and geo-recovery in infrastructure as code while documenting recovery procedures, and enable automated dependency scanning to strengthen security. Finally, organize architecture decision records under a standard directory structure and maintain a changelog to track release details.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Banned license finding(s) in License Compliance. | +12.8 pts | Low | License Compliance |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +6.8 pts | Medium | DR & Backup |
| Enable Dependabot/Renovate or a dependency-review gate. | +2.1 pts | Medium | Security & performance tooling |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 3 Off-boarding risk finding(s) in Bus Factor. | +0.9 pts | Low | Bus Factor |
| Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. | +0.8 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 4.1 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| pallets/quantum-compute-mempool/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| pallets/miner-registry/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| node/src/service.rs | 6.7 | Mixed | Explicit Debt: FixmeComment |
| runtime/src/genesis_config_presets.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| pallets/quantum-compute-mempool/src/benchmarking.rs | 7.1 | Near-clean | God Classes: FileTooLong: src/benchmarking.rs |
| REDACTED | 7.2 | Near-clean | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High vulnerability: REDACTED |
| pallets/quantum-pow/src/lib.rs | 7.8 | Near-clean | God Classes: FileTooLong: src/lib.rs |
| node/src/command.rs | 7.8 | Near-clean | God Classes: FunctionTooLong: quip_network_node::command::run |
| pallets/xqvm/src/benchmarking.rs | 7.8 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| pallets/quantum-compute-mempool/src/xqvm.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| crates/quantum-validation/src/validation.rs | 8.5 | Near-clean | Cognitive Complexity: quantum_validation::validation::validate_topology_consistency (cognitive 30) |
| crates/quantum-validation/src/diversity.rs | 8.5 | Near-clean | Cognitive Complexity: quantum_validation::diversity::select_diverse (cognitive 25) |
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
Watchdog 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. 75 of 75 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 75 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, 123 of 158 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog 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 (.rs, .ts, .mjs) 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 (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) 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 (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) 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 — Watchdog 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 source is present (.rs, .ts, .mjs) and this repository declares a Cargo test suite (repository root, 33 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog 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 — Watchdog 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.
- D44 Platform End-of-Life — not measured this run — Watchdog 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — node2 Error Get "https://registry-1.docker.io/v2/": Forbidden node3 Error Get "https://registry-1.docker.io/v2/": Forbidden failed to solve: rust:1.95.0-bookworm: failed to resolve source metadata for docker.io/library/rust:1.95.0-bookworm: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/1.95.0-bookworm": Forbidden; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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). 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.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being pallet_xqvm::pallet::map_vm_error at 22 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: pallets/xqvm/src/lib.rs (pallet_xqvm::pallet::map_vm_error at 22), node/src/command.rs (quip_network_node::command::run at 21). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was quantum_validation::validation::validate_topology_consistency at 30.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with quantum_validation::validation::validate_topology_consistency (cognitive 30), quantum_validation::diversity::select_diverse (cognitive 25), Pallet::do_submit_solution (cognitive 19). — 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 3 together lifts Cognitive Complexity from 9.0 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
8 god class(es) detected.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with lib.rs (3), benchmarking.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with service.rs, command.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with lib.rs. — 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
12 duplicated block group(s) detected. 1 of the 12 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with command.rs, lib.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with benchmarking.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with benchmarking.rs (2). — One of this dimension's main actionable groups (2 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.
D5 · Coupling
18 production modules (Cargo+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 16 of the 18 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 32 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D9 · Test Distribution
475 test methods: 451 unit, 24 integration, 0 BDD, 0 e2e. The Rust suite contributes 465 `#[test]` function(s) across 33 file(s) declaring at least one; its unit/integration split is Cargo's own — 6 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Python suite contributes 10 test function(s) across 2 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D12 · Dependency Hygiene
10 outdated, 0 yanked direct Cargo dependencies. 21 of 23 direct crates were graded against crates.io (0 not published there, 2 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
8 of 1127 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 173 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT-0, which is its own choice and is not judged here.
What to do
- Resolve the 8 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (8 issue-level).
- Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
Top hotspots: pallets/xqvm/src/lib.rs (12×22=264) Repeated repair below the complexity floor: pallets/xqvm/src/benchmarking.rs (7 of 9 changes were fixes)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with benchmarking.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
14 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is pallets/quantum-pow/src/tests.rs. Counted over 55 of the 76 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 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
D17 · Explicit Debt
7 deducted task-comment markers across 26974 LoC (0.0/KLoC) → score 10.0. 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 6 TodoComment finding(s) in Explicit Debt — start with lib.rs (4), genesis_config_presets.rs, xqvm.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with service.rs. — 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 32 document(s) read across 1 unit(s).
D20 · ADR Quality
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question). How well each record argues its case is not measured.
D26 · Project Cohesion
0 of 18 build units (Cargo, npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 3 file(s) — `scripts/check-weights-staleness.sh` (line 37), `scripts/push-weights.sh` (line 34), `scripts/python-dists.sh` (line 191) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D30 · Dependency Vulnerabilities
71 finding(s): 1 critical, 9 high, 60 medium, 1 low.
What to do
- Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
13 finding(s): 0 critical, 2 high, 9 medium, 2 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 9 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 55 of the 76 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/3 supply-chain integrity signals present (provenance, signing, SBOM).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
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
AX9 · CQS / query purity
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Add a README to the 15 of 18 project(s) that lack one — worth up to 1.7 pts.
M2 · Architecture documentation
- 1 ADR-shaped document(s) detected by content — `docs/miner-registry-system-info-v2-spec.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
- Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) — even for a small library, every public type is a stability contract.
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `node`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
- `readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — js/quip-signer/test/revive-fund-account.mjs:517
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
- 2 typed · 5 plain JS — the untyped files are js/quip-signer/test/local-node.mjs, js/quip-signer/test/revive-fund-account.mjs, js/quip-signer/test/revive-fund-account.test.mjs, js/quip-signer/test/validator-rotation.mjs, js/quip-signer/test/xqvm-onchain-smoke.mjs.
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- js/quip-signer/src/index.ts:262 · js/quip-signer/src/index.ts:277 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — js/quip-signer/src/index.ts:262
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- js/quip-signer/test/index.test.ts:242 imports '../../../quip-transaction-crypto-wasm/quip_transaction_crypto_wasm.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — js/quip-signer/test/index.test.ts:242
R5 · Dependency Freshness
R6 · Tooling
- This repository declares test tooling, and the ✓ above records that declaration — but js/quip-signer/test/index.test.ts cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — js/quip-signer/test/index.test.ts:242
What to do
- Add eslint as package.json scripts and run them in CI.
R7 · Dead Code
- 8 file(s) (~2194 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: js/quip-signer/test/local-node.mjs imports '../../quip-transaction-crypto-wasm/quip_transaction_crypto_wasm.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — js/quip-signer
R8 · Dependency Hygiene
R9 · Circular Imports
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
X19 · Unrestored process-global state
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
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 79% | Adequate — gated by R1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 75% | Strong | Solid. |
| Readiness | 43% | Adequate — gated by D14, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Adequate — gated by D30, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 85% | Exemplary | Solid. |
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's Python 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; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript 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 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. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — node2 Error Get "https://registry-1.docker.io/v2/": Forbidden node3 Error Get "https://registry-1.docker.io/v2/": Forbidden failed to solve: rust:1.95.0-bookworm: failed to resolve source metadata for docker.io/library/rust:1.95.0-bookworm: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/1.95.0-bookworm": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2114 lines of test source are present (.rs, .ts, .mjs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Python, Rust, TypeScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust, TypeScript surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .py, .rs, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), 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.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 26 value object(s); 8 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, Rust 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 (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) 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 `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — No web surface: 63 Rust 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 crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) 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 — 23 finding(s)
- Banned license: xqvm
- Banned license: pqhybridsign
- Banned license: array-bytes
- Banned license: array-bytes
- Banned license: smoldot-light
- Banned license: rug
- Banned license: smoldot
- Banned license: gmp-mpfr-sys
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 111 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment runtime/src/genesis_config_presets.rs:412
- TodoComment pallets/quantum-compute-mempool/src/lib.rs:341
- TodoComment pallets/quantum-compute-mempool/src/lib.rs:593
- TodoComment pallets/quantum-compute-mempool/src/lib.rs:715
- TodoComment pallets/quantum-compute-mempool/src/xqvm.rs:7
- TodoComment pallets/miner-registry/src/lib.rs:868
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: src/lib.rs pallets/quantum-compute-mempool/src/lib.rs
- FileTooLong: src/lib.rs pallets/quantum-pow/src/lib.rs
- FileTooLong: src/lib.rs pallets/miner-registry/src/lib.rs
- FileTooLong: src/benchmarking.rs pallets/quantum-compute-mempool/src/benchmarking.rs
- Off the main sequence: quantum-validation
- Off the main sequence: quip-transaction-crypto-core
- Off the main sequence: pallet-evm-chain-id
- Off the main sequence: pallet-miner-registry
- quantum_validation::validation::validate_topology_consistency (cognitive 30) crates/quantum-validation/src/validation.rs:104
- quantum_validation::diversity::select_diverse (cognitive 25) crates/quantum-validation/src/diversity.rs:96
- FunctionTooLong: quip_network_node::service::new_full node/src/service.rs:160
- FunctionTooLong: quip_network_node::command::run node/src/command.rs:58
- Duplicated block (11 lines × 2) node/src/command.rs:70
- Duplicated block (11 lines × 2) pallets/miner-registry/src/lib.rs:767
- Duplicated block (9 lines × 2) pallets/quantum-compute-mempool/src/benchmarking.rs:410
- Duplicated block (9 lines × 2) pallets/quantum-compute-mempool/src/benchmarking.rs:370
- Duplicated block (5 lines × 2) pallets/quantum-compute-mempool/src/benchmarking.rs:160
- Duplicated block (5 lines × 2) pallets/xqvm/src/benchmarking.rs:300
- Hotspot: pallets/xqvm/src/lib.rs pallets/xqvm/src/lib.rs:369
- Repeated repair: pallets/xqvm/src/benchmarking.rs pallets/xqvm/src/benchmarking.rs:80
- FixmeComment node/src/service.rs:342
- Pallet::do_submit_solution (cognitive 19) pallets/quantum-compute-mempool/src/lib.rs:1178
- MethodTooLong: Pallet.do_submit_solution pallets/quantum-compute-mempool/src/lib.rs:1178
- TooManyMethods: Pallet pallets/quantum-compute-mempool/src/lib.rs:186
- Duplicated block (22–27 lines × 2) runtime/src/genesis_config_presets.rs:296
- Duplicated block (22 lines × 2) pallets/quantum-compute-mempool/src/benchmarking.rs:444
- Duplicated block (10 lines × 2) pallets/quantum-compute-mempool/src/benchmarking.rs:546
- Duplicated block (7 lines × 2) pallets/xqvm/src/benchmarking.rs:358
- Duplicated block (6 lines × 2) pallets/quantum-pow/src/lib.rs:1420
- Duplicated block (8 lines × 3) scripts/generate_quantum_validation_fixtures.py:115
- No DR/backup evidence
- Sync-over-async blocking js/quip-signer/test/revive-fund-account.mjs:517
- Type Safety
- Duplicated block (10 lines × 2 locations) js/quip-signer/src/index.ts:262
- This test file cannot be loaded js/quip-signer/test/index.test.ts:242
- The declared test suite includes a file that cannot be loaded js/quip-signer/test/index.test.ts:242
Minor — 14 finding(s)
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- ADRs not easily discoverable
- Logging is not universal
- No changelog
Minor — 10 finding(s)
- Outdated: blake3
- Outdated: clap
- Outdated: futures
- Outdated: log
- Outdated: pqhybridsign
- Outdated: serde
- Outdated: serde_json
- Outdated: thiserror
- Outdated: wasm-bindgen
- Outdated: zeroize
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d182591f45994011a1c021bb06b64af5/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d182591f45994011a1c021bb06b64af5/tree.json --exit-code 0 --source . | 2 | 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/watchdog-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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 71 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 13 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |