Executive summary
mimblewimble/grin falls short of our standard for production, held back most by its Security and Compliance lens, the code's security and compliance. It scores 58 out of 100 and is rated Adequate, and all 35 of its critical findings are security problems.
Security and Compliance, at 49, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 5 points. Naming the access rules would lift Security and Compliance itself, worth about 7 points. Raising Security and Compliance to 70 would lift the score to about 64.
Twenty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven secrets can leak from the build pipeline, and two settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Updating the vulnerable packages would fix the package with a known security hole.
The product code is 48,885 lines, about €63,000 to rebuild.
If Security and Compliance rose from 49 to 70, the lowest score rated Strong, the score would rise from 58 to about 64.
New since the last survey: 8 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 4 findings
- Test Reliability · Flaky test: grin_chain::store_indices.test_store_indices
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €63,000 · Estimate
| Cost to rebuild | €21,000 to €100,000, for 348 to 1,104 hours of work, about 0.4 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: 48,885 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 grin_api.json_rpc | 2 grin_util | 3 grin_api.router | 4 grin_core.ser | 5 grin_core.core.hash | 6 grin_p2p.conn | 7 grin_core.core.pmmr.readonly_pmmr | 8 grin_core.pow.common | 9 grin_core.pow.types | 10 grin_core.core.pmmr.segment | 11 grin_chain.txhashset.bitmap_accumulator | 12 grin_chain.types | 13 grin_p2p.types | 14 grin_p2p.handshake | 15 grin_p2p.msg | 16 grin_keychain.types | 17 grin_p2p.codec | 18 grin_core.core.transaction | 19 grin_core.core.compact_block | 20 grin_pool.types | 21 grin_core.core.block | 22 grin_api.types | 23 grin_core.global | 24 grin_p2p.peer | 25 grin_pool.transaction_pool | 26 grin_store.pmmr | 27 grin_chain.store | 28 grin_p2p.peers | 29 grin_servers.common.stats | 30 grin_chain.txhashset.utxo_view | 31 grin_p2p.serv | 32 grin_servers.common.types | 33 grin_chain.txhashset.txhashset | 34 grin_config.types | 35 grin_chain.txhashset.desegmenter | 36 grin_chain.chain | 37 grin_api.handlers | 38 grin_servers.common.adapters | 39 grin_servers.grin.server | 40 grin_servers.mining.stratumserver |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 grin_api.json_rpc | ||||||||||||||||||||||||||||||||||||||||
| 2 grin_util | ||||||||||||||||||||||||||||||||||||||||
| 3 grin_api.router | 2 | |||||||||||||||||||||||||||||||||||||||
| 4 grin_core.ser | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 5 grin_core.core.hash | 6 | |||||||||||||||||||||||||||||||||||||||
| 6 grin_p2p.conn | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 7 grin_core.core.pmmr.readonly_pmmr | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 grin_core.pow.common | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 grin_core.pow.types | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 grin_core.core.pmmr.segment | 6 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 11 grin_chain.txhashset.bitmap_accumulator | 9 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 12 grin_chain.types | 1 | 4 | 4 | 1 | 2 | 6 | 2 | |||||||||||||||||||||||||||||||||
| 13 grin_p2p.types | 1 | 4 | 3 | 4 | 2 | 2 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||
| 14 grin_p2p.handshake | 1 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 15 grin_p2p.msg | 37 | 9 | 1 | 4 | 2 | 1 | 6 | 2 | ||||||||||||||||||||||||||||||||
| 16 grin_keychain.types | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 grin_p2p.codec | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 grin_core.core.transaction | 1 | 25 | 8 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 19 grin_core.core.compact_block | 5 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 20 grin_pool.types | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 21 grin_core.core.block | 1 | 11 | 6 | 5 | 2 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 22 grin_api.types | 2 | 1 | 4 | 5 | ||||||||||||||||||||||||||||||||||||
| 23 grin_core.global | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 grin_p2p.peer | 2 | 3 | 2 | 3 | 3 | 10 | 1 | 1 | 1 | 2 | 2 | 3 | ||||||||||||||||||||||||||||
| 25 grin_pool.transaction_pool | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 26 grin_store.pmmr | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 grin_chain.store | 3 | 3 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 28 grin_p2p.peers | 1 | 2 | 2 | 2 | 9 | 1 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||
| 29 grin_servers.common.stats | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 30 grin_chain.txhashset.utxo_view | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 31 grin_p2p.serv | 1 | 2 | 1 | 2 | 2 | 8 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||
| 32 grin_servers.common.types | 1 | 1 | 4 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 33 grin_chain.txhashset.txhashset | 2 | 1 | 2 | 2 | 1 | 2 | 3 | 2 | 6 | 6 | 1 | 7 | 1 | |||||||||||||||||||||||||||
| 34 grin_config.types | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 grin_chain.txhashset.desegmenter | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 36 grin_chain.chain | 2 | 3 | 2 | 4 | 3 | 3 | 4 | 1 | ||||||||||||||||||||||||||||||||
| 37 grin_api.handlers | 4 | 1 | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 38 grin_servers.common.adapters | 4 | 2 | 2 | 6 | 2 | 3 | 1 | 4 | 3 | 2 | 3 | 2 | 2 | |||||||||||||||||||||||||||
| 39 grin_servers.grin.server | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 40 grin_servers.mining.stratumserver | 1 | 2 | 1 | 1 | 1 | 3 | 2 | 2 |
3→1 grin_api.router uses grin_api.json_rpc✕
- Connections
- 2 pairs of types, where a type in grin_api.router uses a type in grin_api.json_rpc.
- The types involved
grin_api.router.Handler→grin_api.json_rpc.Requestgrin_api.router.Router→grin_api.json_rpc.Request
- Direction
- grin_api.router uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_api.router, while a change to grin_api.router can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_api.router uses a module listed above it, which is the healthy direction.
4→1 grin_core.ser uses grin_api.json_rpc✕
- Connections
- 2 pairs of types, where a type in grin_core.ser uses a type in grin_api.json_rpc.
- The types involved
grin_core.ser.Error→grin_api.json_rpc.Errorgrin_core.ser.ser$module→grin_api.json_rpc.Error
- Direction
- grin_core.ser uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_core.ser, while a change to grin_core.ser can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_core.ser uses a module listed above it, which is the healthy direction.
4→5 grin_core.ser uses grin_core.core.hash part of a loop✕
- Connections
- 2 pairs of types, where a type in grin_core.ser uses a type in grin_core.core.hash.
- The types involved
grin_core.ser.PMMRIndexHashable→grin_core.core.hash.Hashgrin_core.ser.PMMRable→grin_core.core.hash.DefaultHashable
- Direction
- grin_core.ser uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_core.ser, while a change to grin_core.ser can't break grin_core.core.hash.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→4 grin_core.core.hash uses grin_core.ser✕
- Connections
- 6 pairs of types, where a type in grin_core.core.hash uses a type in grin_core.ser.
- The types involved
grin_core.core.hash.DefaultHashable→grin_core.ser.Writeablegrin_core.core.hash.Hash→grin_core.ser.Readablegrin_core.core.hash.Hash→grin_core.ser.Writeablegrin_core.core.hash.HashWriter→grin_core.ser.ProtocolVersiongrin_core.core.hash.HashWriter→grin_core.ser.SerializationModegrin_core.core.hash.HashWriter→grin_core.ser.Writer
- Direction
- grin_core.core.hash uses grin_core.ser, so a change to grin_core.ser can break grin_core.core.hash, while a change to grin_core.core.hash can't break grin_core.ser.
- Position
- Below the diagonal: grin_core.core.hash uses a module listed above it, which is the healthy direction.
6→4 grin_p2p.conn uses grin_core.ser✕
- Connections
- 1 pair of types, where a type in grin_p2p.conn uses a type in grin_core.ser.
- The types involved
grin_p2p.conn.conn$module→grin_core.ser.ProtocolVersion
- Direction
- grin_p2p.conn uses grin_core.ser, so a change to grin_core.ser can break grin_p2p.conn, while a change to grin_p2p.conn can't break grin_core.ser.
- Position
- Below the diagonal: grin_p2p.conn uses a module listed above it, which is the healthy direction.
6→15 grin_p2p.conn uses grin_p2p.msg part of a loop✕
- Connections
- 2 pairs of types, where a type in grin_p2p.conn uses a type in grin_p2p.msg.
- The types involved
grin_p2p.conn.ConnHandle→grin_p2p.msg.Msggrin_p2p.conn.MessageHandler→grin_p2p.msg.Message
- Direction
- grin_p2p.conn uses grin_p2p.msg, so a change to grin_p2p.msg can break grin_p2p.conn, while a change to grin_p2p.conn can't break grin_p2p.msg.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→5 grin_core.core.pmmr.readonly_pmmr uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_core.core.pmmr.readonly_pmmr uses a type in grin_core.core.hash.
- The types involved
grin_core.core.pmmr.readonly_pmmr.ReadonlyPMMR→grin_core.core.hash.Hash
- Direction
- grin_core.core.pmmr.readonly_pmmr uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_core.core.pmmr.readonly_pmmr, while a change to grin_core.core.pmmr.readonly_pmmr can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_core.core.pmmr.readonly_pmmr uses a module listed above it, which is the healthy direction.
8→5 grin_core.pow.common uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_core.pow.common uses a type in grin_core.core.hash.
- The types involved
grin_core.pow.common.EdgeType→grin_core.core.hash.Hash
- Direction
- grin_core.pow.common uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_core.pow.common, while a change to grin_core.pow.common can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_core.pow.common uses a module listed above it, which is the healthy direction.
9→4 grin_core.pow.types uses grin_core.ser✕
- Connections
- 6 pairs of types, where a type in grin_core.pow.types uses a type in grin_core.ser.
- The types involved
grin_core.pow.types.Difficulty→grin_core.ser.Readablegrin_core.pow.types.Difficulty→grin_core.ser.Writeablegrin_core.pow.types.Proof→grin_core.ser.Readablegrin_core.pow.types.Proof→grin_core.ser.Writeablegrin_core.pow.types.ProofOfWork→grin_core.ser.Readablegrin_core.pow.types.ProofOfWork→grin_core.ser.Writeable
- Direction
- grin_core.pow.types uses grin_core.ser, so a change to grin_core.ser can break grin_core.pow.types, while a change to grin_core.pow.types can't break grin_core.ser.
- Position
- Below the diagonal: grin_core.pow.types uses a module listed above it, which is the healthy direction.
9→5 grin_core.pow.types uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_core.pow.types uses a type in grin_core.core.hash.
- The types involved
grin_core.pow.types.Proof→grin_core.core.hash.DefaultHashable
- Direction
- grin_core.pow.types uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_core.pow.types, while a change to grin_core.pow.types can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_core.pow.types uses a module listed above it, which is the healthy direction.
10→4 grin_core.core.pmmr.segment uses grin_core.ser✕
- Connections
- 6 pairs of types, where a type in grin_core.core.pmmr.segment uses a type in grin_core.ser.
- The types involved
grin_core.core.pmmr.segment.Segment→grin_core.ser.Readablegrin_core.core.pmmr.segment.Segment→grin_core.ser.Writeablegrin_core.core.pmmr.segment.SegmentIdentifier→grin_core.ser.Readablegrin_core.core.pmmr.segment.SegmentIdentifier→grin_core.ser.Writeablegrin_core.core.pmmr.segment.SegmentProof→grin_core.ser.Readablegrin_core.core.pmmr.segment.SegmentProof→grin_core.ser.Writeable
- Direction
- grin_core.core.pmmr.segment uses grin_core.ser, so a change to grin_core.ser can break grin_core.core.pmmr.segment, while a change to grin_core.core.pmmr.segment can't break grin_core.ser.
- Position
- Below the diagonal: grin_core.core.pmmr.segment uses a module listed above it, which is the healthy direction.
10→5 grin_core.core.pmmr.segment uses grin_core.core.hash✕
- Connections
- 2 pairs of types, where a type in grin_core.core.pmmr.segment uses a type in grin_core.core.hash.
- The types involved
grin_core.core.pmmr.segment.Segment→grin_core.core.hash.Hashgrin_core.core.pmmr.segment.SegmentProof→grin_core.core.hash.Hash
- Direction
- grin_core.core.pmmr.segment uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_core.core.pmmr.segment, while a change to grin_core.core.pmmr.segment can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_core.core.pmmr.segment uses a module listed above it, which is the healthy direction.
10→7 grin_core.core.pmmr.segment uses grin_core.core.pmmr.readonly_pmmr✕
- Connections
- 2 pairs of types, where a type in grin_core.core.pmmr.segment uses a type in grin_core.core.pmmr.readonly_pmmr.
- The types involved
grin_core.core.pmmr.segment.Segment→grin_core.core.pmmr.readonly_pmmr.ReadonlyPMMRgrin_core.core.pmmr.segment.SegmentProof→grin_core.core.pmmr.readonly_pmmr.ReadonlyPMMR
- Direction
- grin_core.core.pmmr.segment uses grin_core.core.pmmr.readonly_pmmr, so a change to grin_core.core.pmmr.readonly_pmmr can break grin_core.core.pmmr.segment, while a change to grin_core.core.pmmr.segment can't break grin_core.core.pmmr.readonly_pmmr.
- Position
- Below the diagonal: grin_core.core.pmmr.segment uses a module listed above it, which is the healthy direction.
10→11 grin_core.core.pmmr.segment uses grin_chain.txhashset.bitmap_accumulator part of a loop✕
- Connections
- 1 pair of types, where a type in grin_core.core.pmmr.segment uses a type in grin_chain.txhashset.bitmap_accumulator.
- The types involved
grin_core.core.pmmr.segment.Segment→grin_chain.txhashset.bitmap_accumulator.BitmapSegment
- Direction
- grin_core.core.pmmr.segment uses grin_chain.txhashset.bitmap_accumulator, so a change to grin_chain.txhashset.bitmap_accumulator can break grin_core.core.pmmr.segment, while a change to grin_core.core.pmmr.segment can't break grin_chain.txhashset.bitmap_accumulator.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→4 grin_chain.txhashset.bitmap_accumulator uses grin_core.ser✕
- Connections
- 9 pairs of types, where a type in grin_chain.txhashset.bitmap_accumulator uses a type in grin_core.ser.
- The types involved
grin_chain.txhashset.bitmap_accumulator.BitmapBlock→grin_core.ser.Readablegrin_chain.txhashset.bitmap_accumulator.BitmapBlock→grin_core.ser.Writeablegrin_chain.txhashset.bitmap_accumulator.BitmapBlockSerialization→grin_core.ser.Readablegrin_chain.txhashset.bitmap_accumulator.BitmapBlockSerialization→grin_core.ser.Writeablegrin_chain.txhashset.bitmap_accumulator.BitmapChunk→grin_core.ser.PMMRablegrin_chain.txhashset.bitmap_accumulator.BitmapChunk→grin_core.ser.Readablegrin_chain.txhashset.bitmap_accumulator.BitmapChunk→grin_core.ser.Writeablegrin_chain.txhashset.bitmap_accumulator.BitmapSegment→grin_core.ser.Readablegrin_chain.txhashset.bitmap_accumulator.BitmapSegment→grin_core.ser.Writeable
- Direction
- grin_chain.txhashset.bitmap_accumulator uses grin_core.ser, so a change to grin_core.ser can break grin_chain.txhashset.bitmap_accumulator, while a change to grin_chain.txhashset.bitmap_accumulator can't break grin_core.ser.
- Position
- Below the diagonal: grin_chain.txhashset.bitmap_accumulator uses a module listed above it, which is the healthy direction.
11→5 grin_chain.txhashset.bitmap_accumulator uses grin_core.core.hash✕
- Connections
- 2 pairs of types, where a type in grin_chain.txhashset.bitmap_accumulator uses a type in grin_core.core.hash.
- The types involved
grin_chain.txhashset.bitmap_accumulator.BitmapAccumulator→grin_core.core.hash.Hashgrin_chain.txhashset.bitmap_accumulator.BitmapChunk→grin_core.core.hash.DefaultHashable
- Direction
- grin_chain.txhashset.bitmap_accumulator uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_chain.txhashset.bitmap_accumulator, while a change to grin_chain.txhashset.bitmap_accumulator can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_chain.txhashset.bitmap_accumulator uses a module listed above it, which is the healthy direction.
11→7 grin_chain.txhashset.bitmap_accumulator uses grin_core.core.pmmr.readonly_pmmr✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.bitmap_accumulator uses a type in grin_core.core.pmmr.readonly_pmmr.
- The types involved
grin_chain.txhashset.bitmap_accumulator.BitmapAccumulator→grin_core.core.pmmr.readonly_pmmr.ReadonlyPMMR
- Direction
- grin_chain.txhashset.bitmap_accumulator uses grin_core.core.pmmr.readonly_pmmr, so a change to grin_core.core.pmmr.readonly_pmmr can break grin_chain.txhashset.bitmap_accumulator, while a change to grin_chain.txhashset.bitmap_accumulator can't break grin_core.core.pmmr.readonly_pmmr.
- Position
- Below the diagonal: grin_chain.txhashset.bitmap_accumulator uses a module listed above it, which is the healthy direction.
11→10 grin_chain.txhashset.bitmap_accumulator uses grin_core.core.pmmr.segment✕
- Connections
- 3 pairs of types, where a type in grin_chain.txhashset.bitmap_accumulator uses a type in grin_core.core.pmmr.segment.
- The types involved
grin_chain.txhashset.bitmap_accumulator.BitmapSegment→grin_core.core.pmmr.segment.Segmentgrin_chain.txhashset.bitmap_accumulator.BitmapSegment→grin_core.core.pmmr.segment.SegmentIdentifiergrin_chain.txhashset.bitmap_accumulator.BitmapSegment→grin_core.core.pmmr.segment.SegmentProof
- Direction
- grin_chain.txhashset.bitmap_accumulator uses grin_core.core.pmmr.segment, so a change to grin_core.core.pmmr.segment can break grin_chain.txhashset.bitmap_accumulator, while a change to grin_chain.txhashset.bitmap_accumulator can't break grin_core.core.pmmr.segment.
- Position
- Below the diagonal: grin_chain.txhashset.bitmap_accumulator uses a module listed above it, which is the healthy direction.
12→1 grin_chain.types uses grin_api.json_rpc✕
- Connections
- 1 pair of types, where a type in grin_chain.types uses a type in grin_api.json_rpc.
- The types involved
grin_chain.types.SyncState→grin_api.json_rpc.Error
- Direction
- grin_chain.types uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_chain.types, while a change to grin_chain.types can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_chain.types uses a module listed above it, which is the healthy direction.
12→4 grin_chain.types uses grin_core.ser✕
- Connections
- 4 pairs of types, where a type in grin_chain.types uses a type in grin_core.ser.
- The types involved
grin_chain.types.CommitPos→grin_core.ser.Readablegrin_chain.types.CommitPos→grin_core.ser.Writeablegrin_chain.types.Tip→grin_core.ser.Readablegrin_chain.types.Tip→grin_core.ser.Writeable
- Direction
- grin_chain.types uses grin_core.ser, so a change to grin_core.ser can break grin_chain.types, while a change to grin_chain.types can't break grin_core.ser.
- Position
- Below the diagonal: grin_chain.types uses a module listed above it, which is the healthy direction.
12→5 grin_chain.types uses grin_core.core.hash✕
- Connections
- 4 pairs of types, where a type in grin_chain.types uses a type in grin_core.core.hash.
- The types involved
grin_chain.types.OutputRoots→grin_core.core.hash.Hashgrin_chain.types.Tip→grin_core.core.hash.Hashgrin_chain.types.Tip→grin_core.core.hash.Hashedgrin_chain.types.TxHashSetRoots→grin_core.core.hash.Hash
- Direction
- grin_chain.types uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_chain.types, while a change to grin_chain.types can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_chain.types uses a module listed above it, which is the healthy direction.
12→9 grin_chain.types uses grin_core.pow.types✕
- Connections
- 1 pair of types, where a type in grin_chain.types uses a type in grin_core.pow.types.
- The types involved
grin_chain.types.Tip→grin_core.pow.types.Difficulty
- Direction
- grin_chain.types uses grin_core.pow.types, so a change to grin_core.pow.types can break grin_chain.types, while a change to grin_chain.types can't break grin_core.pow.types.
- Position
- Below the diagonal: grin_chain.types uses a module listed above it, which is the healthy direction.
12→10 grin_chain.types uses grin_core.core.pmmr.segment✕
- Connections
- 2 pairs of types, where a type in grin_chain.types uses a type in grin_core.core.pmmr.segment.
- The types involved
grin_chain.types.PIBDSegmentContainer→grin_core.core.pmmr.segment.SegmentTypeIdentifiergrin_chain.types.SyncState→grin_core.core.pmmr.segment.SegmentTypeIdentifier
- Direction
- grin_chain.types uses grin_core.core.pmmr.segment, so a change to grin_core.core.pmmr.segment can break grin_chain.types, while a change to grin_chain.types can't break grin_core.core.pmmr.segment.
- Position
- Below the diagonal: grin_chain.types uses a module listed above it, which is the healthy direction.
12→21 grin_chain.types uses grin_core.core.block part of a loop✕
- Connections
- 6 pairs of types, where a type in grin_chain.types uses a type in grin_core.core.block.
- The types involved
grin_chain.types.ChainAdapter→grin_core.core.block.Blockgrin_chain.types.NoopAdapter→grin_core.core.block.Blockgrin_chain.types.OutputRoots→grin_core.core.block.BlockHeadergrin_chain.types.SyncState→grin_core.core.block.BlockHeadergrin_chain.types.Tip→grin_core.core.block.BlockHeadergrin_chain.types.TxHashSetRoots→grin_core.core.block.BlockHeader
- Direction
- grin_chain.types uses grin_core.core.block, so a change to grin_core.core.block can break grin_chain.types, while a change to grin_chain.types can't break grin_core.core.block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→22 grin_chain.types uses grin_api.types part of a loop✕
- Connections
- 2 pairs of types, where a type in grin_chain.types uses a type in grin_api.types.
- The types involved
grin_chain.types.SyncState→grin_api.types.Tipgrin_chain.types.Tip→grin_api.types.Tip
- Direction
- grin_chain.types uses grin_api.types, so a change to grin_api.types can break grin_chain.types, while a change to grin_chain.types can't break grin_api.types.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 grin_p2p.types uses grin_api.json_rpc✕
- Connections
- 1 pair of types, where a type in grin_p2p.types uses a type in grin_api.json_rpc.
- The types involved
grin_p2p.types.Error→grin_api.json_rpc.Error
- Direction
- grin_p2p.types uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_p2p.types, while a change to grin_p2p.types can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_p2p.types uses a module listed above it, which is the healthy direction.
13→4 grin_p2p.types uses grin_core.ser✕
- Connections
- 4 pairs of types, where a type in grin_p2p.types uses a type in grin_core.ser.
- The types involved
grin_p2p.types.PeerAddr→grin_core.ser.Readablegrin_p2p.types.PeerAddr→grin_core.ser.Writeablegrin_p2p.types.PeerInfo→grin_core.ser.ProtocolVersiongrin_p2p.types.PeerInfoDisplay→grin_core.ser.ProtocolVersion
- Direction
- grin_p2p.types uses grin_core.ser, so a change to grin_core.ser can break grin_p2p.types, while a change to grin_p2p.types can't break grin_core.ser.
- Position
- Below the diagonal: grin_p2p.types uses a module listed above it, which is the healthy direction.
13→5 grin_p2p.types uses grin_core.core.hash✕
- Connections
- 3 pairs of types, where a type in grin_p2p.types uses a type in grin_core.core.hash.
- The types involved
grin_p2p.types.AttachmentMeta→grin_core.core.hash.Hashgrin_p2p.types.ChainAdapter→grin_core.core.hash.Hashgrin_p2p.types.PeerAddr→grin_core.core.hash.Hash
- Direction
- grin_p2p.types uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_p2p.types, while a change to grin_p2p.types can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_p2p.types uses a module listed above it, which is the healthy direction.
13→9 grin_p2p.types uses grin_core.pow.types✕
- Connections
- 4 pairs of types, where a type in grin_p2p.types uses a type in grin_core.pow.types.
- The types involved
grin_p2p.types.NetAdapter→grin_core.pow.types.Difficultygrin_p2p.types.PeerInfo→grin_core.pow.types.Difficultygrin_p2p.types.PeerInfoDisplay→grin_core.pow.types.Difficultygrin_p2p.types.PeerLiveInfo→grin_core.pow.types.Difficulty
- Direction
- grin_p2p.types uses grin_core.pow.types, so a change to grin_core.pow.types can break grin_p2p.types, while a change to grin_p2p.types can't break grin_core.pow.types.
- Position
- Below the diagonal: grin_p2p.types uses a module listed above it, which is the healthy direction.
13→10 grin_p2p.types uses grin_core.core.pmmr.segment✕
- Connections
- 2 pairs of types, where a type in grin_p2p.types uses a type in grin_core.core.pmmr.segment.
- The types involved
grin_p2p.types.ChainAdapter→grin_core.core.pmmr.segment.Segmentgrin_p2p.types.ChainAdapter→grin_core.core.pmmr.segment.SegmentIdentifier
- Direction
- grin_p2p.types uses grin_core.core.pmmr.segment, so a change to grin_core.core.pmmr.segment can break grin_p2p.types, while a change to grin_p2p.types can't break grin_core.core.pmmr.segment.
- Position
- Below the diagonal: grin_p2p.types uses a module listed above it, which is the healthy direction.
13→12 grin_p2p.types uses grin_chain.types✕
- Connections
- 2 pairs of types, where a type in grin_p2p.types uses a type in grin_chain.types.
- The types involved
grin_p2p.types.ChainAdapter→grin_chain.types.Optionsgrin_p2p.types.NetAdapter→grin_chain.types.ChainAdapter
- Direction
- grin_p2p.types uses grin_chain.types, so a change to grin_chain.types can break grin_p2p.types, while a change to grin_p2p.types can't break grin_chain.types.
- Position
- Below the diagonal: grin_p2p.types uses a module listed above it, which is the healthy direction.
13→15 grin_p2p.types uses grin_p2p.msg part of a loop✕
- Connections
- 1 pair of types, where a type in grin_p2p.types uses a type in grin_p2p.msg.
- The types involved
grin_p2p.types.P2PConfig→grin_p2p.msg.PeerAddrs
- Direction
- grin_p2p.types uses grin_p2p.msg, so a change to grin_p2p.msg can break grin_p2p.types, while a change to grin_p2p.types can't break grin_p2p.msg.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→18 grin_p2p.types uses grin_core.core.transaction part of a loop✕
- Connections
- 1 pair of types, where a type in grin_p2p.types uses a type in grin_core.core.transaction.
- The types involved
grin_p2p.types.ChainAdapter→grin_core.core.transaction.Transaction
- Direction
- grin_p2p.types uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_p2p.types, while a change to grin_p2p.types can't break grin_core.core.transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→19 grin_p2p.types uses grin_core.core.compact_block part of a loop✕
- Connections
- 1 pair of types, where a type in grin_p2p.types uses a type in grin_core.core.compact_block.
- The types involved
grin_p2p.types.ChainAdapter→grin_core.core.compact_block.CompactBlock
- Direction
- grin_p2p.types uses grin_core.core.compact_block, so a change to grin_core.core.compact_block can break grin_p2p.types, while a change to grin_p2p.types can't break grin_core.core.compact_block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→21 grin_p2p.types uses grin_core.core.block part of a loop✕
- Connections
- 2 pairs of types, where a type in grin_p2p.types uses a type in grin_core.core.block.
- The types involved
grin_p2p.types.ChainAdapter→grin_core.core.block.Blockgrin_p2p.types.ChainAdapter→grin_core.core.block.BlockHeader
- Direction
- grin_p2p.types uses grin_core.core.block, so a change to grin_core.core.block can break grin_p2p.types, while a change to grin_p2p.types can't break grin_core.core.block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→4 grin_p2p.handshake uses grin_core.ser✕
- Connections
- 1 pair of types, where a type in grin_p2p.handshake uses a type in grin_core.ser.
- The types involved
grin_p2p.handshake.Handshake→grin_core.ser.ProtocolVersion
- Direction
- grin_p2p.handshake uses grin_core.ser, so a change to grin_core.ser can break grin_p2p.handshake, while a change to grin_p2p.handshake can't break grin_core.ser.
- Position
- Below the diagonal: grin_p2p.handshake uses a module listed above it, which is the healthy direction.
14→5 grin_p2p.handshake uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_p2p.handshake uses a type in grin_core.core.hash.
- The types involved
grin_p2p.handshake.Handshake→grin_core.core.hash.Hash
- Direction
- grin_p2p.handshake uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_p2p.handshake, while a change to grin_p2p.handshake can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_p2p.handshake uses a module listed above it, which is the healthy direction.
14→6 grin_p2p.handshake uses grin_p2p.conn✕
- Connections
- 1 pair of types, where a type in grin_p2p.handshake uses a type in grin_p2p.conn.
- The types involved
grin_p2p.handshake.Handshake→grin_p2p.conn.Tracker
- Direction
- grin_p2p.handshake uses grin_p2p.conn, so a change to grin_p2p.conn can break grin_p2p.handshake, while a change to grin_p2p.handshake can't break grin_p2p.conn.
- Position
- Below the diagonal: grin_p2p.handshake uses a module listed above it, which is the healthy direction.
14→9 grin_p2p.handshake uses grin_core.pow.types✕
- Connections
- 1 pair of types, where a type in grin_p2p.handshake uses a type in grin_core.pow.types.
- The types involved
grin_p2p.handshake.Handshake→grin_core.pow.types.Difficulty
- Direction
- grin_p2p.handshake uses grin_core.pow.types, so a change to grin_core.pow.types can break grin_p2p.handshake, while a change to grin_p2p.handshake can't break grin_core.pow.types.
- Position
- Below the diagonal: grin_p2p.handshake uses a module listed above it, which is the healthy direction.
14→13 grin_p2p.handshake uses grin_p2p.types✕
- Connections
- 4 pairs of types, where a type in grin_p2p.handshake uses a type in grin_p2p.types.
- The types involved
grin_p2p.handshake.Handshake→grin_p2p.types.Capabilitiesgrin_p2p.handshake.Handshake→grin_p2p.types.P2PConfiggrin_p2p.handshake.Handshake→grin_p2p.types.PeerAddrgrin_p2p.handshake.handshake$module→grin_p2p.types.PeerAddr
- Direction
- grin_p2p.handshake uses grin_p2p.types, so a change to grin_p2p.types can break grin_p2p.handshake, while a change to grin_p2p.handshake can't break grin_p2p.types.
- Position
- Below the diagonal: grin_p2p.handshake uses a module listed above it, which is the healthy direction.
15→4 grin_p2p.msg uses grin_core.ser✕
- Connections
- 37 pairs of types, where a type in grin_p2p.msg uses a type in grin_core.ser. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
grin_p2p.msg.BanReason→grin_core.ser.Readablegrin_p2p.msg.BanReason→grin_core.ser.Writeablegrin_p2p.msg.GetPeerAddrs→grin_core.ser.Readablegrin_p2p.msg.GetPeerAddrs→grin_core.ser.Writeablegrin_p2p.msg.Hand→grin_core.ser.ProtocolVersiongrin_p2p.msg.Hand→grin_core.ser.Readablegrin_p2p.msg.Hand→grin_core.ser.Writeablegrin_p2p.msg.Headers→grin_core.ser.Writeablegrin_p2p.msg.Locator→grin_core.ser.Readablegrin_p2p.msg.Locator→grin_core.ser.Writeablegrin_p2p.msg.Msg→grin_core.ser.ProtocolVersiongrin_p2p.msg.MsgHeader→grin_core.ser.Writeablegrin_p2p.msg.MsgHeaderWrapper→grin_core.ser.Readablegrin_p2p.msg.OutputBitmapSegmentResponse→grin_core.ser.Readablegrin_p2p.msg.OutputBitmapSegmentResponse→grin_core.ser.Writeablegrin_p2p.msg.OutputSegmentResponse→grin_core.ser.Readablegrin_p2p.msg.OutputSegmentResponse→grin_core.ser.Writeablegrin_p2p.msg.PeerAddrs→grin_core.ser.Readablegrin_p2p.msg.PeerAddrs→grin_core.ser.Writeablegrin_p2p.msg.PeerError→grin_core.ser.Readablegrin_p2p.msg.PeerError→grin_core.ser.Writeablegrin_p2p.msg.Ping→grin_core.ser.Readablegrin_p2p.msg.Ping→grin_core.ser.Writeablegrin_p2p.msg.Pong→grin_core.ser.Readablegrin_p2p.msg.Pong→grin_core.ser.Writeable
- Direction
- grin_p2p.msg uses grin_core.ser, so a change to grin_core.ser can break grin_p2p.msg, while a change to grin_p2p.msg can't break grin_core.ser.
- Position
- Below the diagonal: grin_p2p.msg uses a module listed above it, which is the healthy direction.
15→5 grin_p2p.msg uses grin_core.core.hash✕
- Connections
- 9 pairs of types, where a type in grin_p2p.msg uses a type in grin_core.core.hash.
- The types involved
grin_p2p.msg.Hand→grin_core.core.hash.Hashgrin_p2p.msg.Locator→grin_core.core.hash.Hashgrin_p2p.msg.OutputBitmapSegmentResponse→grin_core.core.hash.Hashgrin_p2p.msg.OutputSegmentResponse→grin_core.core.hash.Hashgrin_p2p.msg.SegmentRequest→grin_core.core.hash.Hashgrin_p2p.msg.SegmentResponse→grin_core.core.hash.Hashgrin_p2p.msg.Shake→grin_core.core.hash.Hashgrin_p2p.msg.TxHashSetArchive→grin_core.core.hash.Hashgrin_p2p.msg.TxHashSetRequest→grin_core.core.hash.Hash
- Direction
- grin_p2p.msg uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_p2p.msg, while a change to grin_p2p.msg can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_p2p.msg uses a module listed above it, which is the healthy direction.
15→6 grin_p2p.msg uses grin_p2p.conn✕
- Connections
- 1 pair of types, where a type in grin_p2p.msg uses a type in grin_p2p.conn.
- The types involved
grin_p2p.msg.msg$module→grin_p2p.conn.Tracker
- Direction
- grin_p2p.msg uses grin_p2p.conn, so a change to grin_p2p.conn can break grin_p2p.msg, while a change to grin_p2p.msg can't break grin_p2p.conn.
- Position
- Below the diagonal: grin_p2p.msg uses a module listed above it, which is the healthy direction.
15→9 grin_p2p.msg uses grin_core.pow.types✕
- Connections
- 4 pairs of types, where a type in grin_p2p.msg uses a type in grin_core.pow.types.
- The types involved
grin_p2p.msg.Hand→grin_core.pow.types.Difficultygrin_p2p.msg.Ping→grin_core.pow.types.Difficultygrin_p2p.msg.Pong→grin_core.pow.types.Difficultygrin_p2p.msg.Shake→grin_core.pow.types.Difficulty
- Direction
- grin_p2p.msg uses grin_core.pow.types, so a change to grin_core.pow.types can break grin_p2p.msg, while a change to grin_p2p.msg can't break grin_core.pow.types.
- Position
- Below the diagonal: grin_p2p.msg uses a module listed above it, which is the healthy direction.
15→10 grin_p2p.msg uses grin_core.core.pmmr.segment✕
- Connections
- 2 pairs of types, where a type in grin_p2p.msg uses a type in grin_core.core.pmmr.segment.
- The types involved
grin_p2p.msg.SegmentRequest→grin_core.core.pmmr.segment.SegmentIdentifiergrin_p2p.msg.SegmentResponse→grin_core.core.pmmr.segment.Segment
- Direction
- grin_p2p.msg uses grin_core.core.pmmr.segment, so a change to grin_core.core.pmmr.segment can break grin_p2p.msg, while a change to grin_p2p.msg can't break grin_core.core.pmmr.segment.
- Position
- Below the diagonal: grin_p2p.msg uses a module listed above it, which is the healthy direction.
15→11 grin_p2p.msg uses grin_chain.txhashset.bitmap_accumulator✕
- Connections
- 1 pair of types, where a type in grin_p2p.msg uses a type in grin_chain.txhashset.bitmap_accumulator.
- The types involved
grin_p2p.msg.OutputBitmapSegmentResponse→grin_chain.txhashset.bitmap_accumulator.BitmapSegment
- Direction
- grin_p2p.msg uses grin_chain.txhashset.bitmap_accumulator, so a change to grin_chain.txhashset.bitmap_accumulator can break grin_p2p.msg, while a change to grin_p2p.msg can't break grin_chain.txhashset.bitmap_accumulator.
- Position
- Below the diagonal: grin_p2p.msg uses a module listed above it, which is the healthy direction.
15→13 grin_p2p.msg uses grin_p2p.types✕
- Connections
- 6 pairs of types, where a type in grin_p2p.msg uses a type in grin_p2p.types.
- The types involved
grin_p2p.msg.BanReason→grin_p2p.types.ReasonForBangrin_p2p.msg.GetPeerAddrs→grin_p2p.types.Capabilitiesgrin_p2p.msg.Hand→grin_p2p.types.Capabilitiesgrin_p2p.msg.Hand→grin_p2p.types.PeerAddrgrin_p2p.msg.PeerAddrs→grin_p2p.types.PeerAddrgrin_p2p.msg.Shake→grin_p2p.types.Capabilities
- Direction
- grin_p2p.msg uses grin_p2p.types, so a change to grin_p2p.types can break grin_p2p.msg, while a change to grin_p2p.msg can't break grin_p2p.types.
- Position
- Below the diagonal: grin_p2p.msg uses a module listed above it, which is the healthy direction.
15→21 grin_p2p.msg uses grin_core.core.block part of a loop✕
- Connections
- 2 pairs of types, where a type in grin_p2p.msg uses a type in grin_core.core.block.
- The types involved
grin_p2p.msg.Headers→grin_core.core.block.BlockHeadergrin_p2p.msg.HeadersData→grin_core.core.block.BlockHeader
- Direction
- grin_p2p.msg uses grin_core.core.block, so a change to grin_core.core.block can break grin_p2p.msg, while a change to grin_p2p.msg can't break grin_core.core.block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→1 grin_keychain.types uses grin_api.json_rpc✕
- Connections
- 1 pair of types, where a type in grin_keychain.types uses a type in grin_api.json_rpc.
- The types involved
grin_keychain.types.Error→grin_api.json_rpc.Error
- Direction
- grin_keychain.types uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_keychain.types, while a change to grin_keychain.types can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_keychain.types uses a module listed above it, which is the healthy direction.
16→4 grin_keychain.types uses grin_core.ser✕
- Connections
- 4 pairs of types, where a type in grin_keychain.types uses a type in grin_core.ser.
- The types involved
grin_keychain.types.BlindingFactor→grin_core.ser.Readablegrin_keychain.types.BlindingFactor→grin_core.ser.Writeablegrin_keychain.types.Identifier→grin_core.ser.Readablegrin_keychain.types.Identifier→grin_core.ser.Writeable
- Direction
- grin_keychain.types uses grin_core.ser, so a change to grin_core.ser can break grin_keychain.types, while a change to grin_keychain.types can't break grin_core.ser.
- Position
- Below the diagonal: grin_keychain.types uses a module listed above it, which is the healthy direction.
16→15 grin_keychain.types uses grin_p2p.msg✕
- Connections
- 1 pair of types, where a type in grin_keychain.types uses a type in grin_p2p.msg.
- The types involved
grin_keychain.types.Keychain→grin_p2p.msg.Message
- Direction
- grin_keychain.types uses grin_p2p.msg, so a change to grin_p2p.msg can break grin_keychain.types, while a change to grin_keychain.types can't break grin_p2p.msg.
- Position
- Below the diagonal: grin_keychain.types uses a module listed above it, which is the healthy direction.
17→4 grin_p2p.codec uses grin_core.ser✕
- Connections
- 2 pairs of types, where a type in grin_p2p.codec uses a type in grin_core.ser.
- The types involved
grin_p2p.codec.Codec→grin_core.ser.ProtocolVersiongrin_p2p.codec.codec$module→grin_core.ser.ProtocolVersion
- Direction
- grin_p2p.codec uses grin_core.ser, so a change to grin_core.ser can break grin_p2p.codec, while a change to grin_p2p.codec can't break grin_core.ser.
- Position
- Below the diagonal: grin_p2p.codec uses a module listed above it, which is the healthy direction.
17→13 grin_p2p.codec uses grin_p2p.types✕
- Connections
- 1 pair of types, where a type in grin_p2p.codec uses a type in grin_p2p.types.
- The types involved
grin_p2p.codec.Codec→grin_p2p.types.AttachmentMeta
- Direction
- grin_p2p.codec uses grin_p2p.types, so a change to grin_p2p.types can break grin_p2p.codec, while a change to grin_p2p.codec can't break grin_p2p.types.
- Position
- Below the diagonal: grin_p2p.codec uses a module listed above it, which is the healthy direction.
17→15 grin_p2p.codec uses grin_p2p.msg✕
- Connections
- 1 pair of types, where a type in grin_p2p.codec uses a type in grin_p2p.msg.
- The types involved
grin_p2p.codec.codec$module→grin_p2p.msg.MsgHeader
- Direction
- grin_p2p.codec uses grin_p2p.msg, so a change to grin_p2p.msg can break grin_p2p.codec, while a change to grin_p2p.codec can't break grin_p2p.msg.
- Position
- Below the diagonal: grin_p2p.codec uses a module listed above it, which is the healthy direction.
18→1 grin_core.core.transaction uses grin_api.json_rpc✕
- Connections
- 1 pair of types, where a type in grin_core.core.transaction uses a type in grin_api.json_rpc.
- The types involved
grin_core.core.transaction.Error→grin_api.json_rpc.Error
- Direction
- grin_core.core.transaction uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_core.core.transaction, while a change to grin_core.core.transaction can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_core.core.transaction uses a module listed above it, which is the healthy direction.
18→4 grin_core.core.transaction uses grin_core.ser✕
- Connections
- 25 pairs of types, where a type in grin_core.core.transaction uses a type in grin_core.ser.
- The types involved
grin_core.core.transaction.CommitWrapper→grin_core.ser.Readablegrin_core.core.transaction.CommitWrapper→grin_core.ser.Writeablegrin_core.core.transaction.FeeFields→grin_core.ser.Readablegrin_core.core.transaction.FeeFields→grin_core.ser.Writeablegrin_core.core.transaction.Input→grin_core.ser.Readablegrin_core.core.transaction.Input→grin_core.ser.Writeablegrin_core.core.transaction.Inputs→grin_core.ser.Writeablegrin_core.core.transaction.KernelFeatures→grin_core.ser.Readablegrin_core.core.transaction.KernelFeatures→grin_core.ser.Writeablegrin_core.core.transaction.NRDRelativeHeight→grin_core.ser.Readablegrin_core.core.transaction.NRDRelativeHeight→grin_core.ser.Writeablegrin_core.core.transaction.Output→grin_core.ser.Readablegrin_core.core.transaction.Output→grin_core.ser.Writeablegrin_core.core.transaction.OutputFeatures→grin_core.ser.Readablegrin_core.core.transaction.OutputFeatures→grin_core.ser.Writeablegrin_core.core.transaction.OutputIdentifier→grin_core.ser.PMMRablegrin_core.core.transaction.OutputIdentifier→grin_core.ser.Readablegrin_core.core.transaction.OutputIdentifier→grin_core.ser.Writeablegrin_core.core.transaction.Transaction→grin_core.ser.Readablegrin_core.core.transaction.Transaction→grin_core.ser.Writeablegrin_core.core.transaction.TransactionBody→grin_core.ser.Readablegrin_core.core.transaction.TransactionBody→grin_core.ser.Writeablegrin_core.core.transaction.TxKernel→grin_core.ser.PMMRablegrin_core.core.transaction.TxKernel→grin_core.ser.Readablegrin_core.core.transaction.TxKernel→grin_core.ser.Writeable
- Direction
- grin_core.core.transaction uses grin_core.ser, so a change to grin_core.ser can break grin_core.core.transaction, while a change to grin_core.core.transaction can't break grin_core.ser.
- Position
- Below the diagonal: grin_core.core.transaction uses a module listed above it, which is the healthy direction.
18→5 grin_core.core.transaction uses grin_core.core.hash✕
- Connections
- 8 pairs of types, where a type in grin_core.core.transaction uses a type in grin_core.core.hash.
- The types involved
grin_core.core.transaction.CommitWrapper→grin_core.core.hash.DefaultHashablegrin_core.core.transaction.FeeFields→grin_core.core.hash.DefaultHashablegrin_core.core.transaction.Input→grin_core.core.hash.DefaultHashablegrin_core.core.transaction.NRDRelativeHeight→grin_core.core.hash.DefaultHashablegrin_core.core.transaction.OutputIdentifier→grin_core.core.hash.DefaultHashablegrin_core.core.transaction.Transaction→grin_core.core.hash.DefaultHashablegrin_core.core.transaction.TxKernel→grin_core.core.hash.DefaultHashablegrin_core.core.transaction.TxKernel→grin_core.core.hash.Hash
- Direction
- grin_core.core.transaction uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_core.core.transaction, while a change to grin_core.core.transaction can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_core.core.transaction uses a module listed above it, which is the healthy direction.
18→16 grin_core.core.transaction uses grin_keychain.types✕
- Connections
- 1 pair of types, where a type in grin_core.core.transaction uses a type in grin_keychain.types.
- The types involved
grin_core.core.transaction.Transaction→grin_keychain.types.BlindingFactor
- Direction
- grin_core.core.transaction uses grin_keychain.types, so a change to grin_keychain.types can break grin_core.core.transaction, while a change to grin_core.core.transaction can't break grin_keychain.types.
- Position
- Below the diagonal: grin_core.core.transaction uses a module listed above it, which is the healthy direction.
18→22 grin_core.core.transaction uses grin_api.types part of a loop✕
- Connections
- 4 pairs of types, where a type in grin_core.core.transaction uses a type in grin_api.types.
- The types involved
grin_core.core.transaction.Output→grin_api.types.Outputgrin_core.core.transaction.OutputIdentifier→grin_api.types.Outputgrin_core.core.transaction.Transaction→grin_api.types.Outputgrin_core.core.transaction.TransactionBody→grin_api.types.Output
- Direction
- grin_core.core.transaction uses grin_api.types, so a change to grin_api.types can break grin_core.core.transaction, while a change to grin_core.core.transaction can't break grin_api.types.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→4 grin_core.core.compact_block uses grin_core.ser✕
- Connections
- 5 pairs of types, where a type in grin_core.core.compact_block uses a type in grin_core.ser.
- The types involved
grin_core.core.compact_block.CompactBlock→grin_core.ser.Readablegrin_core.core.compact_block.CompactBlock→grin_core.ser.Writeablegrin_core.core.compact_block.CompactBlockBody→grin_core.ser.Readablegrin_core.core.compact_block.CompactBlockBody→grin_core.ser.Writeablegrin_core.core.compact_block.UntrustedCompactBlock→grin_core.ser.Readable
- Direction
- grin_core.core.compact_block uses grin_core.ser, so a change to grin_core.ser can break grin_core.core.compact_block, while a change to grin_core.core.compact_block can't break grin_core.ser.
- Position
- Below the diagonal: grin_core.core.compact_block uses a module listed above it, which is the healthy direction.
19→5 grin_core.core.compact_block uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_core.core.compact_block uses a type in grin_core.core.hash.
- The types involved
grin_core.core.compact_block.CompactBlock→grin_core.core.hash.DefaultHashable
- Direction
- grin_core.core.compact_block uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_core.core.compact_block, while a change to grin_core.core.compact_block can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_core.core.compact_block uses a module listed above it, which is the healthy direction.
19→18 grin_core.core.compact_block uses grin_core.core.transaction✕
- Connections
- 1 pair of types, where a type in grin_core.core.compact_block uses a type in grin_core.core.transaction.
- The types involved
grin_core.core.compact_block.CompactBlockBody→grin_core.core.transaction.TxKernel
- Direction
- grin_core.core.compact_block uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_core.core.compact_block, while a change to grin_core.core.compact_block can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_core.core.compact_block uses a module listed above it, which is the healthy direction.
19→21 grin_core.core.compact_block uses grin_core.core.block part of a loop✕
- Connections
- 2 pairs of types, where a type in grin_core.core.compact_block uses a type in grin_core.core.block.
- The types involved
grin_core.core.compact_block.CompactBlock→grin_core.core.block.Blockgrin_core.core.compact_block.CompactBlock→grin_core.core.block.BlockHeader
- Direction
- grin_core.core.compact_block uses grin_core.core.block, so a change to grin_core.core.block can break grin_core.core.compact_block, while a change to grin_core.core.compact_block can't break grin_core.core.block.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→22 grin_core.core.compact_block uses grin_api.types part of a loop✕
- Connections
- 1 pair of types, where a type in grin_core.core.compact_block uses a type in grin_api.types.
- The types involved
grin_core.core.compact_block.CompactBlockBody→grin_api.types.Output
- Direction
- grin_core.core.compact_block uses grin_api.types, so a change to grin_api.types can break grin_core.core.compact_block, while a change to grin_core.core.compact_block can't break grin_api.types.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→1 grin_pool.types uses grin_api.json_rpc✕
- Connections
- 1 pair of types, where a type in grin_pool.types uses a type in grin_api.json_rpc.
- The types involved
grin_pool.types.PoolError→grin_api.json_rpc.Error
- Direction
- grin_pool.types uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_pool.types, while a change to grin_pool.types can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_pool.types uses a module listed above it, which is the healthy direction.
20→5 grin_pool.types uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_pool.types uses a type in grin_core.core.hash.
- The types involved
grin_pool.types.BlockChain→grin_core.core.hash.Hash
- Direction
- grin_pool.types uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_pool.types, while a change to grin_pool.types can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_pool.types uses a module listed above it, which is the healthy direction.
20→18 grin_pool.types uses grin_core.core.transaction✕
- Connections
- 3 pairs of types, where a type in grin_pool.types uses a type in grin_core.core.transaction.
- The types involved
grin_pool.types.BlockChain→grin_core.core.transaction.Inputsgrin_pool.types.BlockChain→grin_core.core.transaction.Transactiongrin_pool.types.PoolEntry→grin_core.core.transaction.Transaction
- Direction
- grin_pool.types uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_pool.types, while a change to grin_pool.types can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_pool.types uses a module listed above it, which is the healthy direction.
21→1 grin_core.core.block uses grin_api.json_rpc✕
- Connections
- 1 pair of types, where a type in grin_core.core.block uses a type in grin_api.json_rpc.
- The types involved
grin_core.core.block.Error→grin_api.json_rpc.Error
- Direction
- grin_core.core.block uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_core.core.block, while a change to grin_core.core.block can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_core.core.block uses a module listed above it, which is the healthy direction.
21→4 grin_core.core.block uses grin_core.ser✕
- Connections
- 11 pairs of types, where a type in grin_core.core.block uses a type in grin_core.ser.
- The types involved
grin_core.core.block.Block→grin_core.ser.Readablegrin_core.core.block.Block→grin_core.ser.Writeablegrin_core.core.block.BlockHeader→grin_core.ser.PMMRablegrin_core.core.block.BlockHeader→grin_core.ser.Readablegrin_core.core.block.BlockHeader→grin_core.ser.Writeablegrin_core.core.block.HeaderEntry→grin_core.ser.Readablegrin_core.core.block.HeaderEntry→grin_core.ser.Writeablegrin_core.core.block.HeaderVersion→grin_core.ser.Readablegrin_core.core.block.HeaderVersion→grin_core.ser.Writeablegrin_core.core.block.UntrustedBlock→grin_core.ser.Readablegrin_core.core.block.UntrustedBlockHeader→grin_core.ser.Readable
- Direction
- grin_core.core.block uses grin_core.ser, so a change to grin_core.ser can break grin_core.core.block, while a change to grin_core.core.block can't break grin_core.ser.
- Position
- Below the diagonal: grin_core.core.block uses a module listed above it, which is the healthy direction.
21→5 grin_core.core.block uses grin_core.core.hash✕
- Connections
- 6 pairs of types, where a type in grin_core.core.block uses a type in grin_core.core.hash.
- The types involved
grin_core.core.block.Block→grin_core.core.hash.Hashgrin_core.core.block.Block→grin_core.core.hash.Hashedgrin_core.core.block.BlockHeader→grin_core.core.hash.DefaultHashablegrin_core.core.block.BlockHeader→grin_core.core.hash.Hashgrin_core.core.block.HeaderEntry→grin_core.core.hash.Hashgrin_core.core.block.HeaderEntry→grin_core.core.hash.Hashed
- Direction
- grin_core.core.block uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_core.core.block, while a change to grin_core.core.block can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_core.core.block uses a module listed above it, which is the healthy direction.
21→9 grin_core.core.block uses grin_core.pow.types✕
- Connections
- 5 pairs of types, where a type in grin_core.core.block uses a type in grin_core.pow.types.
- The types involved
grin_core.core.block.Block→grin_core.pow.types.Difficultygrin_core.core.block.BlockHeader→grin_core.pow.types.Difficultygrin_core.core.block.BlockHeader→grin_core.pow.types.Proofgrin_core.core.block.BlockHeader→grin_core.pow.types.ProofOfWorkgrin_core.core.block.HeaderEntry→grin_core.pow.types.Difficulty
- Direction
- grin_core.core.block uses grin_core.pow.types, so a change to grin_core.pow.types can break grin_core.core.block, while a change to grin_core.core.block can't break grin_core.pow.types.
- Position
- Below the diagonal: grin_core.core.block uses a module listed above it, which is the healthy direction.
21→16 grin_core.core.block uses grin_keychain.types✕
- Connections
- 2 pairs of types, where a type in grin_core.core.block uses a type in grin_keychain.types.
- The types involved
grin_core.core.block.Block→grin_keychain.types.BlindingFactorgrin_core.core.block.BlockHeader→grin_keychain.types.BlindingFactor
- Direction
- grin_core.core.block uses grin_keychain.types, so a change to grin_keychain.types can break grin_core.core.block, while a change to grin_core.core.block can't break grin_keychain.types.
- Position
- Below the diagonal: grin_core.core.block uses a module listed above it, which is the healthy direction.
21→18 grin_core.core.block uses grin_core.core.transaction✕
- Connections
- 3 pairs of types, where a type in grin_core.core.block uses a type in grin_core.core.transaction.
- The types involved
grin_core.core.block.Block→grin_core.core.transaction.Inputsgrin_core.core.block.Block→grin_core.core.transaction.TransactionBodygrin_core.core.block.Block→grin_core.core.transaction.TxKernel
- Direction
- grin_core.core.block uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_core.core.block, while a change to grin_core.core.block can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_core.core.block uses a module listed above it, which is the healthy direction.
21→19 grin_core.core.block uses grin_core.core.compact_block✕
- Connections
- 1 pair of types, where a type in grin_core.core.block uses a type in grin_core.core.compact_block.
- The types involved
grin_core.core.block.Block→grin_core.core.compact_block.CompactBlock
- Direction
- grin_core.core.block uses grin_core.core.compact_block, so a change to grin_core.core.compact_block can break grin_core.core.block, while a change to grin_core.core.block can't break grin_core.core.compact_block.
- Position
- Below the diagonal: grin_core.core.block uses a module listed above it, which is the healthy direction.
21→22 grin_core.core.block uses grin_api.types part of a loop✕
- Connections
- 1 pair of types, where a type in grin_core.core.block uses a type in grin_api.types.
- The types involved
grin_core.core.block.Block→grin_api.types.Output
- Direction
- grin_core.core.block uses grin_api.types, so a change to grin_api.types can break grin_core.core.block, while a change to grin_core.core.block can't break grin_api.types.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→18 grin_api.types uses grin_core.core.transaction✕
- Connections
- 2 pairs of types, where a type in grin_api.types uses a type in grin_core.core.transaction.
- The types involved
grin_api.types.LocatedTxKernel→grin_core.core.transaction.TxKernelgrin_api.types.TxKernelPrintable→grin_core.core.transaction.TxKernel
- Direction
- grin_api.types uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_api.types, while a change to grin_api.types can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_api.types uses a module listed above it, which is the healthy direction.
22→19 grin_api.types uses grin_core.core.compact_block✕
- Connections
- 1 pair of types, where a type in grin_api.types uses a type in grin_core.core.compact_block.
- The types involved
grin_api.types.CompactBlockPrintable→grin_core.core.compact_block.CompactBlock
- Direction
- grin_api.types uses grin_core.core.compact_block, so a change to grin_core.core.compact_block can break grin_api.types, while a change to grin_api.types can't break grin_core.core.compact_block.
- Position
- Below the diagonal: grin_api.types uses a module listed above it, which is the healthy direction.
22→21 grin_api.types uses grin_core.core.block✕
- Connections
- 4 pairs of types, where a type in grin_api.types uses a type in grin_core.core.block.
- The types involved
grin_api.types.BlockHeaderDifficultyInfo→grin_core.core.block.BlockHeadergrin_api.types.BlockHeaderPrintable→grin_core.core.block.BlockHeadergrin_api.types.BlockPrintable→grin_core.core.block.Blockgrin_api.types.OutputPrintable→grin_core.core.block.BlockHeader
- Direction
- grin_api.types uses grin_core.core.block, so a change to grin_core.core.block can break grin_api.types, while a change to grin_api.types can't break grin_core.core.block.
- Position
- Below the diagonal: grin_api.types uses a module listed above it, which is the healthy direction.
22→36 grin_api.types uses grin_chain.chain part of a loop✕
- Connections
- 5 pairs of types, where a type in grin_api.types uses a type in grin_chain.chain.
- The types involved
grin_api.types.BlockPrintable→grin_chain.chain.Chaingrin_api.types.CompactBlockPrintable→grin_chain.chain.Chaingrin_api.types.OutputPrintable→grin_chain.chain.Chaingrin_api.types.TxHashSet→grin_chain.chain.Chaingrin_api.types.TxHashSetNode→grin_chain.chain.Chain
- Direction
- grin_api.types uses grin_chain.chain, so a change to grin_chain.chain can break grin_api.types, while a change to grin_api.types can't break grin_chain.chain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→21 grin_core.global uses grin_core.core.block✕
- Connections
- 1 pair of types, where a type in grin_core.global uses a type in grin_core.core.block.
- The types involved
grin_core.global.global$module→grin_core.core.block.Block
- Direction
- grin_core.global uses grin_core.core.block, so a change to grin_core.core.block can break grin_core.global, while a change to grin_core.global can't break grin_core.core.block.
- Position
- Below the diagonal: grin_core.global uses a module listed above it, which is the healthy direction.
24→5 grin_p2p.peer uses grin_core.core.hash✕
- Connections
- 2 pairs of types, where a type in grin_p2p.peer uses a type in grin_core.core.hash.
- The types involved
grin_p2p.peer.Peer→grin_core.core.hash.Hashgrin_p2p.peer.TrackingAdapter→grin_core.core.hash.Hash
- Direction
- grin_p2p.peer uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→6 grin_p2p.peer uses grin_p2p.conn✕
- Connections
- 3 pairs of types, where a type in grin_p2p.peer uses a type in grin_p2p.conn.
- The types involved
grin_p2p.peer.Peer→grin_p2p.conn.ConnHandlegrin_p2p.peer.Peer→grin_p2p.conn.StopHandlegrin_p2p.peer.Peer→grin_p2p.conn.Tracker
- Direction
- grin_p2p.peer uses grin_p2p.conn, so a change to grin_p2p.conn can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_p2p.conn.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→9 grin_p2p.peer uses grin_core.pow.types✕
- Connections
- 2 pairs of types, where a type in grin_p2p.peer uses a type in grin_core.pow.types.
- The types involved
grin_p2p.peer.Peer→grin_core.pow.types.Difficultygrin_p2p.peer.TrackingAdapter→grin_core.pow.types.Difficulty
- Direction
- grin_p2p.peer uses grin_core.pow.types, so a change to grin_core.pow.types can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_core.pow.types.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→10 grin_p2p.peer uses grin_core.core.pmmr.segment✕
- Connections
- 3 pairs of types, where a type in grin_p2p.peer uses a type in grin_core.core.pmmr.segment.
- The types involved
grin_p2p.peer.Peer→grin_core.core.pmmr.segment.SegmentIdentifiergrin_p2p.peer.TrackingAdapter→grin_core.core.pmmr.segment.Segmentgrin_p2p.peer.TrackingAdapter→grin_core.core.pmmr.segment.SegmentIdentifier
- Direction
- grin_p2p.peer uses grin_core.core.pmmr.segment, so a change to grin_core.core.pmmr.segment can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_core.core.pmmr.segment.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→12 grin_p2p.peer uses grin_chain.types✕
- Connections
- 3 pairs of types, where a type in grin_p2p.peer uses a type in grin_chain.types.
- The types involved
grin_p2p.peer.Peer→grin_chain.types.Optionsgrin_p2p.peer.TrackingAdapter→grin_chain.types.ChainAdaptergrin_p2p.peer.TrackingAdapter→grin_chain.types.Options
- Direction
- grin_p2p.peer uses grin_chain.types, so a change to grin_chain.types can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_chain.types.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→13 grin_p2p.peer uses grin_p2p.types✕
- Connections
- 10 pairs of types, where a type in grin_p2p.peer uses a type in grin_p2p.types.
- The types involved
grin_p2p.peer.Peer→grin_p2p.types.Capabilitiesgrin_p2p.peer.Peer→grin_p2p.types.P2PConfiggrin_p2p.peer.Peer→grin_p2p.types.PeerAddrgrin_p2p.peer.Peer→grin_p2p.types.PeerInfogrin_p2p.peer.Peer→grin_p2p.types.ReasonForBangrin_p2p.peer.TrackingAdapter→grin_p2p.types.Capabilitiesgrin_p2p.peer.TrackingAdapter→grin_p2p.types.NetAdaptergrin_p2p.peer.TrackingAdapter→grin_p2p.types.PeerAddrgrin_p2p.peer.TrackingAdapter→grin_p2p.types.PeerInfogrin_p2p.peer.TrackingAdapter→grin_p2p.types.TxHashSetRead
- Direction
- grin_p2p.peer uses grin_p2p.types, so a change to grin_p2p.types can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_p2p.types.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→14 grin_p2p.peer uses grin_p2p.handshake✕
- Connections
- 1 pair of types, where a type in grin_p2p.peer uses a type in grin_p2p.handshake.
- The types involved
grin_p2p.peer.Peer→grin_p2p.handshake.Handshake
- Direction
- grin_p2p.peer uses grin_p2p.handshake, so a change to grin_p2p.handshake can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_p2p.handshake.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→15 grin_p2p.peer uses grin_p2p.msg✕
- Connections
- 1 pair of types, where a type in grin_p2p.peer uses a type in grin_p2p.msg.
- The types involved
grin_p2p.peer.Peer→grin_p2p.msg.Type
- Direction
- grin_p2p.peer uses grin_p2p.msg, so a change to grin_p2p.msg can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_p2p.msg.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→17 grin_p2p.peer uses grin_p2p.codec✕
- Connections
- 1 pair of types, where a type in grin_p2p.peer uses a type in grin_p2p.codec.
- The types involved
grin_p2p.peer.Peer→grin_p2p.codec.State
- Direction
- grin_p2p.peer uses grin_p2p.codec, so a change to grin_p2p.codec can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_p2p.codec.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→18 grin_p2p.peer uses grin_core.core.transaction✕
- Connections
- 2 pairs of types, where a type in grin_p2p.peer uses a type in grin_core.core.transaction.
- The types involved
grin_p2p.peer.Peer→grin_core.core.transaction.Transactiongrin_p2p.peer.TrackingAdapter→grin_core.core.transaction.Transaction
- Direction
- grin_p2p.peer uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→19 grin_p2p.peer uses grin_core.core.compact_block✕
- Connections
- 2 pairs of types, where a type in grin_p2p.peer uses a type in grin_core.core.compact_block.
- The types involved
grin_p2p.peer.Peer→grin_core.core.compact_block.CompactBlockgrin_p2p.peer.TrackingAdapter→grin_core.core.compact_block.CompactBlock
- Direction
- grin_p2p.peer uses grin_core.core.compact_block, so a change to grin_core.core.compact_block can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_core.core.compact_block.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
24→21 grin_p2p.peer uses grin_core.core.block✕
- Connections
- 3 pairs of types, where a type in grin_p2p.peer uses a type in grin_core.core.block.
- The types involved
grin_p2p.peer.Peer→grin_core.core.block.BlockHeadergrin_p2p.peer.TrackingAdapter→grin_core.core.block.Blockgrin_p2p.peer.TrackingAdapter→grin_core.core.block.BlockHeader
- Direction
- grin_p2p.peer uses grin_core.core.block, so a change to grin_core.core.block can break grin_p2p.peer, while a change to grin_p2p.peer can't break grin_core.core.block.
- Position
- Below the diagonal: grin_p2p.peer uses a module listed above it, which is the healthy direction.
25→5 grin_pool.transaction_pool uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_pool.transaction_pool uses a type in grin_core.core.hash.
- The types involved
grin_pool.transaction_pool.TransactionPool→grin_core.core.hash.Hash
- Direction
- grin_pool.transaction_pool uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_pool.transaction_pool, while a change to grin_pool.transaction_pool can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_pool.transaction_pool uses a module listed above it, which is the healthy direction.
25→18 grin_pool.transaction_pool uses grin_core.core.transaction✕
- Connections
- 1 pair of types, where a type in grin_pool.transaction_pool uses a type in grin_core.core.transaction.
- The types involved
grin_pool.transaction_pool.TransactionPool→grin_core.core.transaction.Transaction
- Direction
- grin_pool.transaction_pool uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_pool.transaction_pool, while a change to grin_pool.transaction_pool can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_pool.transaction_pool uses a module listed above it, which is the healthy direction.
25→20 grin_pool.transaction_pool uses grin_pool.types✕
- Connections
- 3 pairs of types, where a type in grin_pool.transaction_pool uses a type in grin_pool.types.
- The types involved
grin_pool.transaction_pool.TransactionPool→grin_pool.types.PoolConfiggrin_pool.transaction_pool.TransactionPool→grin_pool.types.PoolEntrygrin_pool.transaction_pool.TransactionPool→grin_pool.types.TxSource
- Direction
- grin_pool.transaction_pool uses grin_pool.types, so a change to grin_pool.types can break grin_pool.transaction_pool, while a change to grin_pool.transaction_pool can't break grin_pool.types.
- Position
- Below the diagonal: grin_pool.transaction_pool uses a module listed above it, which is the healthy direction.
25→21 grin_pool.transaction_pool uses grin_core.core.block✕
- Connections
- 2 pairs of types, where a type in grin_pool.transaction_pool uses a type in grin_core.core.block.
- The types involved
grin_pool.transaction_pool.TransactionPool→grin_core.core.block.Blockgrin_pool.transaction_pool.TransactionPool→grin_core.core.block.BlockHeader
- Direction
- grin_pool.transaction_pool uses grin_core.core.block, so a change to grin_core.core.block can break grin_pool.transaction_pool, while a change to grin_pool.transaction_pool can't break grin_core.core.block.
- Position
- Below the diagonal: grin_pool.transaction_pool uses a module listed above it, which is the healthy direction.
26→4 grin_store.pmmr uses grin_core.ser✕
- Connections
- 1 pair of types, where a type in grin_store.pmmr uses a type in grin_core.ser.
- The types involved
grin_store.pmmr.PMMRBackend→grin_core.ser.ProtocolVersion
- Direction
- grin_store.pmmr uses grin_core.ser, so a change to grin_core.ser can break grin_store.pmmr, while a change to grin_store.pmmr can't break grin_core.ser.
- Position
- Below the diagonal: grin_store.pmmr uses a module listed above it, which is the healthy direction.
26→5 grin_store.pmmr uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_store.pmmr uses a type in grin_core.core.hash.
- The types involved
grin_store.pmmr.PMMRBackend→grin_core.core.hash.Hash
- Direction
- grin_store.pmmr uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_store.pmmr, while a change to grin_store.pmmr can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_store.pmmr uses a module listed above it, which is the healthy direction.
26→21 grin_store.pmmr uses grin_core.core.block✕
- Connections
- 1 pair of types, where a type in grin_store.pmmr uses a type in grin_core.core.block.
- The types involved
grin_store.pmmr.PMMRBackend→grin_core.core.block.BlockHeader
- Direction
- grin_store.pmmr uses grin_core.core.block, so a change to grin_core.core.block can break grin_store.pmmr, while a change to grin_store.pmmr can't break grin_core.core.block.
- Position
- Below the diagonal: grin_store.pmmr uses a module listed above it, which is the healthy direction.
27→4 grin_chain.store uses grin_core.ser✕
- Connections
- 3 pairs of types, where a type in grin_chain.store uses a type in grin_core.ser.
- The types involved
grin_chain.store.Batch→grin_core.ser.ProtocolVersiongrin_chain.store.BoolFlag→grin_core.ser.Readablegrin_chain.store.BoolFlag→grin_core.ser.Writeable
- Direction
- grin_chain.store uses grin_core.ser, so a change to grin_core.ser can break grin_chain.store, while a change to grin_chain.store can't break grin_core.ser.
- Position
- Below the diagonal: grin_chain.store uses a module listed above it, which is the healthy direction.
27→5 grin_chain.store uses grin_core.core.hash✕
- Connections
- 3 pairs of types, where a type in grin_chain.store uses a type in grin_core.core.hash.
- The types involved
grin_chain.store.Batch→grin_core.core.hash.Hashgrin_chain.store.ChainStore→grin_core.core.hash.Hashgrin_chain.store.DifficultyIter→grin_core.core.hash.Hash
- Direction
- grin_chain.store uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_chain.store, while a change to grin_chain.store can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_chain.store uses a module listed above it, which is the healthy direction.
27→12 grin_chain.store uses grin_chain.types✕
- Connections
- 1 pair of types, where a type in grin_chain.store uses a type in grin_chain.types.
- The types involved
grin_chain.store.Batch→grin_chain.types.CommitPos
- Direction
- grin_chain.store uses grin_chain.types, so a change to grin_chain.types can break grin_chain.store, while a change to grin_chain.store can't break grin_chain.types.
- Position
- Below the diagonal: grin_chain.store uses a module listed above it, which is the healthy direction.
27→21 grin_chain.store uses grin_core.core.block✕
- Connections
- 4 pairs of types, where a type in grin_chain.store uses a type in grin_core.core.block.
- The types involved
grin_chain.store.Batch→grin_core.core.block.Blockgrin_chain.store.Batch→grin_core.core.block.BlockHeadergrin_chain.store.ChainStore→grin_core.core.block.BlockHeadergrin_chain.store.DifficultyIter→grin_core.core.block.BlockHeader
- Direction
- grin_chain.store uses grin_core.core.block, so a change to grin_core.core.block can break grin_chain.store, while a change to grin_chain.store can't break grin_core.core.block.
- Position
- Below the diagonal: grin_chain.store uses a module listed above it, which is the healthy direction.
27→22 grin_chain.store uses grin_api.types✕
- Connections
- 1 pair of types, where a type in grin_chain.store uses a type in grin_api.types.
- The types involved
grin_chain.store.Batch→grin_api.types.Tip
- Direction
- grin_chain.store uses grin_api.types, so a change to grin_api.types can break grin_chain.store, while a change to grin_chain.store can't break grin_api.types.
- Position
- Below the diagonal: grin_chain.store uses a module listed above it, which is the healthy direction.
28→5 grin_p2p.peers uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_p2p.peers uses a type in grin_core.core.hash.
- The types involved
grin_p2p.peers.Peers→grin_core.core.hash.Hash
- Direction
- grin_p2p.peers uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_p2p.peers, while a change to grin_p2p.peers can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_p2p.peers uses a module listed above it, which is the healthy direction.
28→9 grin_p2p.peers uses grin_core.pow.types✕
- Connections
- 2 pairs of types, where a type in grin_p2p.peers uses a type in grin_core.pow.types.
- The types involved
grin_p2p.peers.Peers→grin_core.pow.types.Difficultygrin_p2p.peers.PeersIter→grin_core.pow.types.Difficulty
- Direction
- grin_p2p.peers uses grin_core.pow.types, so a change to grin_core.pow.types can break grin_p2p.peers, while a change to grin_p2p.peers can't break grin_core.pow.types.
- Position
- Below the diagonal: grin_p2p.peers uses a module listed above it, which is the healthy direction.
28→10 grin_p2p.peers uses grin_core.core.pmmr.segment✕
- Connections
- 2 pairs of types, where a type in grin_p2p.peers uses a type in grin_core.core.pmmr.segment.
- The types involved
grin_p2p.peers.Peers→grin_core.core.pmmr.segment.Segmentgrin_p2p.peers.Peers→grin_core.core.pmmr.segment.SegmentIdentifier
- Direction
- grin_p2p.peers uses grin_core.core.pmmr.segment, so a change to grin_core.core.pmmr.segment can break grin_p2p.peers, while a change to grin_p2p.peers can't break grin_core.core.pmmr.segment.
- Position
- Below the diagonal: grin_p2p.peers uses a module listed above it, which is the healthy direction.
28→12 grin_p2p.peers uses grin_chain.types✕
- Connections
- 2 pairs of types, where a type in grin_p2p.peers uses a type in grin_chain.types.
- The types involved
grin_p2p.peers.Peers→grin_chain.types.ChainAdaptergrin_p2p.peers.Peers→grin_chain.types.Options
- Direction
- grin_p2p.peers uses grin_chain.types, so a change to grin_chain.types can break grin_p2p.peers, while a change to grin_p2p.peers can't break grin_chain.types.
- Position
- Below the diagonal: grin_p2p.peers uses a module listed above it, which is the healthy direction.
28→13 grin_p2p.peers uses grin_p2p.types✕
- Connections
- 9 pairs of types, where a type in grin_p2p.peers uses a type in grin_p2p.types.
- The types involved
grin_p2p.peers.Peers→grin_p2p.types.Capabilitiesgrin_p2p.peers.Peers→grin_p2p.types.NetAdaptergrin_p2p.peers.Peers→grin_p2p.types.P2PConfiggrin_p2p.peers.Peers→grin_p2p.types.PeerAddrgrin_p2p.peers.Peers→grin_p2p.types.PeerInfogrin_p2p.peers.Peers→grin_p2p.types.ReasonForBangrin_p2p.peers.Peers→grin_p2p.types.TxHashSetReadgrin_p2p.peers.PeersIter→grin_p2p.types.Capabilitiesgrin_p2p.peers.PeersIter→grin_p2p.types.PeerAddr
- Direction
- grin_p2p.peers uses grin_p2p.types, so a change to grin_p2p.types can break grin_p2p.peers, while a change to grin_p2p.peers can't break grin_p2p.types.
- Position
- Below the diagonal: grin_p2p.peers uses a module listed above it, which is the healthy direction.
28→17 grin_p2p.peers uses grin_p2p.codec✕
- Connections
- 1 pair of types, where a type in grin_p2p.peers uses a type in grin_p2p.codec.
- The types involved
grin_p2p.peers.Peers→grin_p2p.codec.State
- Direction
- grin_p2p.peers uses grin_p2p.codec, so a change to grin_p2p.codec can break grin_p2p.peers, while a change to grin_p2p.peers can't break grin_p2p.codec.
- Position
- Below the diagonal: grin_p2p.peers uses a module listed above it, which is the healthy direction.
28→18 grin_p2p.peers uses grin_core.core.transaction✕
- Connections
- 1 pair of types, where a type in grin_p2p.peers uses a type in grin_core.core.transaction.
- The types involved
grin_p2p.peers.Peers→grin_core.core.transaction.Transaction
- Direction
- grin_p2p.peers uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_p2p.peers, while a change to grin_p2p.peers can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_p2p.peers uses a module listed above it, which is the healthy direction.
28→19 grin_p2p.peers uses grin_core.core.compact_block✕
- Connections
- 1 pair of types, where a type in grin_p2p.peers uses a type in grin_core.core.compact_block.
- The types involved
grin_p2p.peers.Peers→grin_core.core.compact_block.CompactBlock
- Direction
- grin_p2p.peers uses grin_core.core.compact_block, so a change to grin_core.core.compact_block can break grin_p2p.peers, while a change to grin_p2p.peers can't break grin_core.core.compact_block.
- Position
- Below the diagonal: grin_p2p.peers uses a module listed above it, which is the healthy direction.
28→21 grin_p2p.peers uses grin_core.core.block✕
- Connections
- 2 pairs of types, where a type in grin_p2p.peers uses a type in grin_core.core.block.
- The types involved
grin_p2p.peers.Peers→grin_core.core.block.Blockgrin_p2p.peers.Peers→grin_core.core.block.BlockHeader
- Direction
- grin_p2p.peers uses grin_core.core.block, so a change to grin_core.core.block can break grin_p2p.peers, while a change to grin_p2p.peers can't break grin_core.core.block.
- Position
- Below the diagonal: grin_p2p.peers uses a module listed above it, which is the healthy direction.
28→24 grin_p2p.peers uses grin_p2p.peer✕
- Connections
- 2 pairs of types, where a type in grin_p2p.peers uses a type in grin_p2p.peer.
- The types involved
grin_p2p.peers.Peers→grin_p2p.peer.Peergrin_p2p.peers.PeersIter→grin_p2p.peer.Peer
- Direction
- grin_p2p.peers uses grin_p2p.peer, so a change to grin_p2p.peer can break grin_p2p.peers, while a change to grin_p2p.peers can't break grin_p2p.peer.
- Position
- Below the diagonal: grin_p2p.peers uses a module listed above it, which is the healthy direction.
29→4 grin_servers.common.stats uses grin_core.ser✕
- Connections
- 1 pair of types, where a type in grin_servers.common.stats uses a type in grin_core.ser.
- The types involved
grin_servers.common.stats.PeerStats→grin_core.ser.ProtocolVersion
- Direction
- grin_servers.common.stats uses grin_core.ser, so a change to grin_core.ser can break grin_servers.common.stats, while a change to grin_servers.common.stats can't break grin_core.ser.
- Position
- Below the diagonal: grin_servers.common.stats uses a module listed above it, which is the healthy direction.
29→5 grin_servers.common.stats uses grin_core.core.hash✕
- Connections
- 2 pairs of types, where a type in grin_servers.common.stats uses a type in grin_core.core.hash.
- The types involved
grin_servers.common.stats.ChainStats→grin_core.core.hash.Hashgrin_servers.common.stats.DiffBlock→grin_core.core.hash.Hash
- Direction
- grin_servers.common.stats uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_servers.common.stats, while a change to grin_servers.common.stats can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_servers.common.stats uses a module listed above it, which is the healthy direction.
29→9 grin_servers.common.stats uses grin_core.pow.types✕
- Connections
- 1 pair of types, where a type in grin_servers.common.stats uses a type in grin_core.pow.types.
- The types involved
grin_servers.common.stats.ChainStats→grin_core.pow.types.Difficulty
- Direction
- grin_servers.common.stats uses grin_core.pow.types, so a change to grin_core.pow.types can break grin_servers.common.stats, while a change to grin_servers.common.stats can't break grin_core.pow.types.
- Position
- Below the diagonal: grin_servers.common.stats uses a module listed above it, which is the healthy direction.
29→12 grin_servers.common.stats uses grin_chain.types✕
- Connections
- 1 pair of types, where a type in grin_servers.common.stats uses a type in grin_chain.types.
- The types involved
grin_servers.common.stats.ServerStats→grin_chain.types.SyncStatus
- Direction
- grin_servers.common.stats uses grin_chain.types, so a change to grin_chain.types can break grin_servers.common.stats, while a change to grin_servers.common.stats can't break grin_chain.types.
- Position
- Below the diagonal: grin_servers.common.stats uses a module listed above it, which is the healthy direction.
29→13 grin_servers.common.stats uses grin_p2p.types✕
- Connections
- 1 pair of types, where a type in grin_servers.common.stats uses a type in grin_p2p.types.
- The types involved
grin_servers.common.stats.PeerStats→grin_p2p.types.Capabilities
- Direction
- grin_servers.common.stats uses grin_p2p.types, so a change to grin_p2p.types can break grin_servers.common.stats, while a change to grin_servers.common.stats can't break grin_p2p.types.
- Position
- Below the diagonal: grin_servers.common.stats uses a module listed above it, which is the healthy direction.
29→24 grin_servers.common.stats uses grin_p2p.peer✕
- Connections
- 1 pair of types, where a type in grin_servers.common.stats uses a type in grin_p2p.peer.
- The types involved
grin_servers.common.stats.PeerStats→grin_p2p.peer.Peer
- Direction
- grin_servers.common.stats uses grin_p2p.peer, so a change to grin_p2p.peer can break grin_servers.common.stats, while a change to grin_servers.common.stats can't break grin_p2p.peer.
- Position
- Below the diagonal: grin_servers.common.stats uses a module listed above it, which is the healthy direction.
30→5 grin_chain.txhashset.utxo_view uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.utxo_view uses a type in grin_core.core.hash.
- The types involved
grin_chain.txhashset.utxo_view.UTXOView→grin_core.core.hash.Hash
- Direction
- grin_chain.txhashset.utxo_view uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_chain.txhashset.utxo_view, while a change to grin_chain.txhashset.utxo_view can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_chain.txhashset.utxo_view uses a module listed above it, which is the healthy direction.
30→7 grin_chain.txhashset.utxo_view uses grin_core.core.pmmr.readonly_pmmr✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.utxo_view uses a type in grin_core.core.pmmr.readonly_pmmr.
- The types involved
grin_chain.txhashset.utxo_view.UTXOView→grin_core.core.pmmr.readonly_pmmr.ReadonlyPMMR
- Direction
- grin_chain.txhashset.utxo_view uses grin_core.core.pmmr.readonly_pmmr, so a change to grin_core.core.pmmr.readonly_pmmr can break grin_chain.txhashset.utxo_view, while a change to grin_chain.txhashset.utxo_view can't break grin_core.core.pmmr.readonly_pmmr.
- Position
- Below the diagonal: grin_chain.txhashset.utxo_view uses a module listed above it, which is the healthy direction.
30→18 grin_chain.txhashset.utxo_view uses grin_core.core.transaction✕
- Connections
- 2 pairs of types, where a type in grin_chain.txhashset.utxo_view uses a type in grin_core.core.transaction.
- The types involved
grin_chain.txhashset.utxo_view.UTXOView→grin_core.core.transaction.Inputsgrin_chain.txhashset.utxo_view.UTXOView→grin_core.core.transaction.Transaction
- Direction
- grin_chain.txhashset.utxo_view uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_chain.txhashset.utxo_view, while a change to grin_chain.txhashset.utxo_view can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_chain.txhashset.utxo_view uses a module listed above it, which is the healthy direction.
30→21 grin_chain.txhashset.utxo_view uses grin_core.core.block✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.utxo_view uses a type in grin_core.core.block.
- The types involved
grin_chain.txhashset.utxo_view.UTXOView→grin_core.core.block.Block
- Direction
- grin_chain.txhashset.utxo_view uses grin_core.core.block, so a change to grin_core.core.block can break grin_chain.txhashset.utxo_view, while a change to grin_chain.txhashset.utxo_view can't break grin_core.core.block.
- Position
- Below the diagonal: grin_chain.txhashset.utxo_view uses a module listed above it, which is the healthy direction.
30→22 grin_chain.txhashset.utxo_view uses grin_api.types✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.utxo_view uses a type in grin_api.types.
- The types involved
grin_chain.txhashset.utxo_view.UTXOView→grin_api.types.Output
- Direction
- grin_chain.txhashset.utxo_view uses grin_api.types, so a change to grin_api.types can break grin_chain.txhashset.utxo_view, while a change to grin_chain.txhashset.utxo_view can't break grin_api.types.
- Position
- Below the diagonal: grin_chain.txhashset.utxo_view uses a module listed above it, which is the healthy direction.
30→27 grin_chain.txhashset.utxo_view uses grin_chain.store✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.utxo_view uses a type in grin_chain.store.
- The types involved
grin_chain.txhashset.utxo_view.UTXOView→grin_chain.store.Batch
- Direction
- grin_chain.txhashset.utxo_view uses grin_chain.store, so a change to grin_chain.store can break grin_chain.txhashset.utxo_view, while a change to grin_chain.txhashset.utxo_view can't break grin_chain.store.
- Position
- Below the diagonal: grin_chain.txhashset.utxo_view uses a module listed above it, which is the healthy direction.
31→2 grin_p2p.serv uses grin_util✕
- Connections
- 1 pair of types, where a type in grin_p2p.serv uses a type in grin_util.
- The types involved
grin_p2p.serv.Server→grin_util.StopState
- Direction
- grin_p2p.serv uses grin_util, so a change to grin_util can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_util.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
31→5 grin_p2p.serv uses grin_core.core.hash✕
- Connections
- 2 pairs of types, where a type in grin_p2p.serv uses a type in grin_core.core.hash.
- The types involved
grin_p2p.serv.DummyAdapter→grin_core.core.hash.Hashgrin_p2p.serv.Server→grin_core.core.hash.Hash
- Direction
- grin_p2p.serv uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
31→9 grin_p2p.serv uses grin_core.pow.types✕
- Connections
- 1 pair of types, where a type in grin_p2p.serv uses a type in grin_core.pow.types.
- The types involved
grin_p2p.serv.DummyAdapter→grin_core.pow.types.Difficulty
- Direction
- grin_p2p.serv uses grin_core.pow.types, so a change to grin_core.pow.types can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_core.pow.types.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
31→10 grin_p2p.serv uses grin_core.core.pmmr.segment✕
- Connections
- 2 pairs of types, where a type in grin_p2p.serv uses a type in grin_core.core.pmmr.segment.
- The types involved
grin_p2p.serv.DummyAdapter→grin_core.core.pmmr.segment.Segmentgrin_p2p.serv.DummyAdapter→grin_core.core.pmmr.segment.SegmentIdentifier
- Direction
- grin_p2p.serv uses grin_core.core.pmmr.segment, so a change to grin_core.core.pmmr.segment can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_core.core.pmmr.segment.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
31→12 grin_p2p.serv uses grin_chain.types✕
- Connections
- 2 pairs of types, where a type in grin_p2p.serv uses a type in grin_chain.types.
- The types involved
grin_p2p.serv.DummyAdapter→grin_chain.types.ChainAdaptergrin_p2p.serv.DummyAdapter→grin_chain.types.Options
- Direction
- grin_p2p.serv uses grin_chain.types, so a change to grin_chain.types can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_chain.types.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
31→13 grin_p2p.serv uses grin_p2p.types✕
- Connections
- 8 pairs of types, where a type in grin_p2p.serv uses a type in grin_p2p.types.
- The types involved
grin_p2p.serv.DummyAdapter→grin_p2p.types.Capabilitiesgrin_p2p.serv.DummyAdapter→grin_p2p.types.NetAdaptergrin_p2p.serv.DummyAdapter→grin_p2p.types.PeerAddrgrin_p2p.serv.DummyAdapter→grin_p2p.types.PeerInfogrin_p2p.serv.DummyAdapter→grin_p2p.types.TxHashSetReadgrin_p2p.serv.Server→grin_p2p.types.Capabilitiesgrin_p2p.serv.Server→grin_p2p.types.P2PConfiggrin_p2p.serv.Server→grin_p2p.types.PeerAddr
- Direction
- grin_p2p.serv uses grin_p2p.types, so a change to grin_p2p.types can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_p2p.types.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
31→14 grin_p2p.serv uses grin_p2p.handshake✕
- Connections
- 1 pair of types, where a type in grin_p2p.serv uses a type in grin_p2p.handshake.
- The types involved
grin_p2p.serv.Server→grin_p2p.handshake.Handshake
- Direction
- grin_p2p.serv uses grin_p2p.handshake, so a change to grin_p2p.handshake can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_p2p.handshake.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
31→18 grin_p2p.serv uses grin_core.core.transaction✕
- Connections
- 1 pair of types, where a type in grin_p2p.serv uses a type in grin_core.core.transaction.
- The types involved
grin_p2p.serv.DummyAdapter→grin_core.core.transaction.Transaction
- Direction
- grin_p2p.serv uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
31→19 grin_p2p.serv uses grin_core.core.compact_block✕
- Connections
- 1 pair of types, where a type in grin_p2p.serv uses a type in grin_core.core.compact_block.
- The types involved
grin_p2p.serv.DummyAdapter→grin_core.core.compact_block.CompactBlock
- Direction
- grin_p2p.serv uses grin_core.core.compact_block, so a change to grin_core.core.compact_block can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_core.core.compact_block.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
31→21 grin_p2p.serv uses grin_core.core.block✕
- Connections
- 2 pairs of types, where a type in grin_p2p.serv uses a type in grin_core.core.block.
- The types involved
grin_p2p.serv.DummyAdapter→grin_core.core.block.Blockgrin_p2p.serv.DummyAdapter→grin_core.core.block.BlockHeader
- Direction
- grin_p2p.serv uses grin_core.core.block, so a change to grin_core.core.block can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_core.core.block.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
31→28 grin_p2p.serv uses grin_p2p.peers✕
- Connections
- 1 pair of types, where a type in grin_p2p.serv uses a type in grin_p2p.peers.
- The types involved
grin_p2p.serv.Server→grin_p2p.peers.Peers
- Direction
- grin_p2p.serv uses grin_p2p.peers, so a change to grin_p2p.peers can break grin_p2p.serv, while a change to grin_p2p.serv can't break grin_p2p.peers.
- Position
- Below the diagonal: grin_p2p.serv uses a module listed above it, which is the healthy direction.
32→1 grin_servers.common.types uses grin_api.json_rpc✕
- Connections
- 1 pair of types, where a type in grin_servers.common.types uses a type in grin_api.json_rpc.
- The types involved
grin_servers.common.types.Error→grin_api.json_rpc.Error
- Direction
- grin_servers.common.types uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_servers.common.types, while a change to grin_servers.common.types can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_servers.common.types uses a module listed above it, which is the healthy direction.
32→13 grin_servers.common.types uses grin_p2p.types✕
- Connections
- 1 pair of types, where a type in grin_servers.common.types uses a type in grin_p2p.types.
- The types involved
grin_servers.common.types.ServerConfig→grin_p2p.types.P2PConfig
- Direction
- grin_servers.common.types uses grin_p2p.types, so a change to grin_p2p.types can break grin_servers.common.types, while a change to grin_servers.common.types can't break grin_p2p.types.
- Position
- Below the diagonal: grin_servers.common.types uses a module listed above it, which is the healthy direction.
32→20 grin_servers.common.types uses grin_pool.types✕
- Connections
- 4 pairs of types, where a type in grin_servers.common.types uses a type in grin_pool.types.
- The types involved
grin_servers.common.types.DandelionEpoch→grin_pool.types.DandelionConfiggrin_servers.common.types.Error→grin_pool.types.PoolErrorgrin_servers.common.types.ServerConfig→grin_pool.types.DandelionConfiggrin_servers.common.types.ServerConfig→grin_pool.types.PoolConfig
- Direction
- grin_servers.common.types uses grin_pool.types, so a change to grin_pool.types can break grin_servers.common.types, while a change to grin_servers.common.types can't break grin_pool.types.
- Position
- Below the diagonal: grin_servers.common.types uses a module listed above it, which is the healthy direction.
32→23 grin_servers.common.types uses grin_core.global✕
- Connections
- 1 pair of types, where a type in grin_servers.common.types uses a type in grin_core.global.
- The types involved
grin_servers.common.types.ServerConfig→grin_core.global.ChainTypes
- Direction
- grin_servers.common.types uses grin_core.global, so a change to grin_core.global can break grin_servers.common.types, while a change to grin_servers.common.types can't break grin_core.global.
- Position
- Below the diagonal: grin_servers.common.types uses a module listed above it, which is the healthy direction.
32→24 grin_servers.common.types uses grin_p2p.peer✕
- Connections
- 1 pair of types, where a type in grin_servers.common.types uses a type in grin_p2p.peer.
- The types involved
grin_servers.common.types.DandelionEpoch→grin_p2p.peer.Peer
- Direction
- grin_servers.common.types uses grin_p2p.peer, so a change to grin_p2p.peer can break grin_servers.common.types, while a change to grin_servers.common.types can't break grin_p2p.peer.
- Position
- Below the diagonal: grin_servers.common.types uses a module listed above it, which is the healthy direction.
32→28 grin_servers.common.types uses grin_p2p.peers✕
- Connections
- 1 pair of types, where a type in grin_servers.common.types uses a type in grin_p2p.peers.
- The types involved
grin_servers.common.types.DandelionEpoch→grin_p2p.peers.Peers
- Direction
- grin_servers.common.types uses grin_p2p.peers, so a change to grin_p2p.peers can break grin_servers.common.types, while a change to grin_servers.common.types can't break grin_p2p.peers.
- Position
- Below the diagonal: grin_servers.common.types uses a module listed above it, which is the healthy direction.
33→2 grin_chain.txhashset.txhashset uses grin_util✕
- Connections
- 2 pairs of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_util.
- The types involved
grin_chain.txhashset.txhashset.Extension→grin_util.StopStategrin_chain.txhashset.txhashset.TxHashSet→grin_util.StopState
- Direction
- grin_chain.txhashset.txhashset uses grin_util, so a change to grin_util can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_util.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→4 grin_chain.txhashset.txhashset uses grin_core.ser✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_core.ser.
- The types involved
grin_chain.txhashset.txhashset.PMMRHandle→grin_core.ser.ProtocolVersion
- Direction
- grin_chain.txhashset.txhashset uses grin_core.ser, so a change to grin_core.ser can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_core.ser.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→5 grin_chain.txhashset.txhashset uses grin_core.core.hash✕
- Connections
- 2 pairs of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_core.core.hash.
- The types involved
grin_chain.txhashset.txhashset.HeaderExtension→grin_core.core.hash.Hashgrin_chain.txhashset.txhashset.TxHashSet→grin_core.core.hash.Hash
- Direction
- grin_chain.txhashset.txhashset uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→7 grin_chain.txhashset.txhashset uses grin_core.core.pmmr.readonly_pmmr✕
- Connections
- 2 pairs of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_core.core.pmmr.readonly_pmmr.
- The types involved
grin_chain.txhashset.txhashset.Extension→grin_core.core.pmmr.readonly_pmmr.ReadonlyPMMRgrin_chain.txhashset.txhashset.TxHashSet→grin_core.core.pmmr.readonly_pmmr.ReadonlyPMMR
- Direction
- grin_chain.txhashset.txhashset uses grin_core.core.pmmr.readonly_pmmr, so a change to grin_core.core.pmmr.readonly_pmmr can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_core.core.pmmr.readonly_pmmr.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→10 grin_chain.txhashset.txhashset uses grin_core.core.pmmr.segment✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_core.core.pmmr.segment.
- The types involved
grin_chain.txhashset.txhashset.Extension→grin_core.core.pmmr.segment.Segment
- Direction
- grin_chain.txhashset.txhashset uses grin_core.core.pmmr.segment, so a change to grin_core.core.pmmr.segment can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_core.core.pmmr.segment.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→11 grin_chain.txhashset.txhashset uses grin_chain.txhashset.bitmap_accumulator✕
- Connections
- 2 pairs of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_chain.txhashset.bitmap_accumulator.
- The types involved
grin_chain.txhashset.txhashset.Extension→grin_chain.txhashset.bitmap_accumulator.BitmapAccumulatorgrin_chain.txhashset.txhashset.TxHashSet→grin_chain.txhashset.bitmap_accumulator.BitmapAccumulator
- Direction
- grin_chain.txhashset.txhashset uses grin_chain.txhashset.bitmap_accumulator, so a change to grin_chain.txhashset.bitmap_accumulator can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_chain.txhashset.bitmap_accumulator.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→12 grin_chain.txhashset.txhashset uses grin_chain.types✕
- Connections
- 3 pairs of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_chain.types.
- The types involved
grin_chain.txhashset.txhashset.Extension→grin_chain.types.CommitPosgrin_chain.txhashset.txhashset.TxHashSet→grin_chain.types.SyncStategrin_chain.txhashset.txhashset.txhashset$module→grin_chain.types.CommitPos
- Direction
- grin_chain.txhashset.txhashset uses grin_chain.types, so a change to grin_chain.types can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_chain.types.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→18 grin_chain.txhashset.txhashset uses grin_core.core.transaction✕
- Connections
- 2 pairs of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_core.core.transaction.
- The types involved
grin_chain.txhashset.txhashset.Extension→grin_core.core.transaction.TxKernelgrin_chain.txhashset.txhashset.txhashset$module→grin_core.core.transaction.TxKernel
- Direction
- grin_chain.txhashset.txhashset uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→21 grin_chain.txhashset.txhashset uses grin_core.core.block✕
- Connections
- 6 pairs of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_core.core.block.
- The types involved
grin_chain.txhashset.txhashset.Extension→grin_core.core.block.Blockgrin_chain.txhashset.txhashset.Extension→grin_core.core.block.BlockHeadergrin_chain.txhashset.txhashset.HeaderExtension→grin_core.core.block.BlockHeadergrin_chain.txhashset.txhashset.PMMRHandle→grin_core.core.block.BlockHeadergrin_chain.txhashset.txhashset.TxHashSet→grin_core.core.block.BlockHeadergrin_chain.txhashset.txhashset.txhashset$module→grin_core.core.block.BlockHeader
- Direction
- grin_chain.txhashset.txhashset uses grin_core.core.block, so a change to grin_core.core.block can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_core.core.block.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→22 grin_chain.txhashset.txhashset uses grin_api.types✕
- Connections
- 6 pairs of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_api.types.
- The types involved
grin_chain.txhashset.txhashset.Extension→grin_api.types.Outputgrin_chain.txhashset.txhashset.Extension→grin_api.types.Tipgrin_chain.txhashset.txhashset.Extension→grin_api.types.TxHashSetgrin_chain.txhashset.txhashset.HeaderExtension→grin_api.types.Tipgrin_chain.txhashset.txhashset.PMMRHandle→grin_api.types.Tipgrin_chain.txhashset.txhashset.txhashset$module→grin_api.types.TxHashSet
- Direction
- grin_chain.txhashset.txhashset uses grin_api.types, so a change to grin_api.types can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_api.types.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→26 grin_chain.txhashset.txhashset uses grin_store.pmmr✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_store.pmmr.
- The types involved
grin_chain.txhashset.txhashset.PMMRHandle→grin_store.pmmr.PMMRBackend
- Direction
- grin_chain.txhashset.txhashset uses grin_store.pmmr, so a change to grin_store.pmmr can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_store.pmmr.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→27 grin_chain.txhashset.txhashset uses grin_chain.store✕
- Connections
- 7 pairs of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_chain.store.
- The types involved
grin_chain.txhashset.txhashset.Extension→grin_chain.store.Batchgrin_chain.txhashset.txhashset.HeaderExtension→grin_chain.store.Batchgrin_chain.txhashset.txhashset.PMMRHandle→grin_chain.store.ChainStoregrin_chain.txhashset.txhashset.TxHashSet→grin_chain.store.Batchgrin_chain.txhashset.txhashset.TxHashSet→grin_chain.store.ChainStoregrin_chain.txhashset.txhashset.txhashset$module→grin_chain.store.Batchgrin_chain.txhashset.txhashset.txhashset$module→grin_chain.store.ChainStore
- Direction
- grin_chain.txhashset.txhashset uses grin_chain.store, so a change to grin_chain.store can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_chain.store.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
33→30 grin_chain.txhashset.txhashset uses grin_chain.txhashset.utxo_view✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.txhashset uses a type in grin_chain.txhashset.utxo_view.
- The types involved
grin_chain.txhashset.txhashset.Extension→grin_chain.txhashset.utxo_view.UTXOView
- Direction
- grin_chain.txhashset.txhashset uses grin_chain.txhashset.utxo_view, so a change to grin_chain.txhashset.utxo_view can break grin_chain.txhashset.txhashset, while a change to grin_chain.txhashset.txhashset can't break grin_chain.txhashset.utxo_view.
- Position
- Below the diagonal: grin_chain.txhashset.txhashset uses a module listed above it, which is the healthy direction.
34→1 grin_config.types uses grin_api.json_rpc✕
- Connections
- 1 pair of types, where a type in grin_config.types uses a type in grin_api.json_rpc.
- The types involved
grin_config.types.ConfigError→grin_api.json_rpc.Error
- Direction
- grin_config.types uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_config.types, while a change to grin_config.types can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_config.types uses a module listed above it, which is the healthy direction.
34→23 grin_config.types uses grin_core.global✕
- Connections
- 1 pair of types, where a type in grin_config.types uses a type in grin_core.global.
- The types involved
grin_config.types.GlobalConfig→grin_core.global.ChainTypes
- Direction
- grin_config.types uses grin_core.global, so a change to grin_core.global can break grin_config.types, while a change to grin_config.types can't break grin_core.global.
- Position
- Below the diagonal: grin_config.types uses a module listed above it, which is the healthy direction.
34→32 grin_config.types uses grin_servers.common.types✕
- Connections
- 1 pair of types, where a type in grin_config.types uses a type in grin_servers.common.types.
- The types involved
grin_config.types.ConfigMembers→grin_servers.common.types.ServerConfig
- Direction
- grin_config.types uses grin_servers.common.types, so a change to grin_servers.common.types can break grin_config.types, while a change to grin_config.types can't break grin_servers.common.types.
- Position
- Below the diagonal: grin_config.types uses a module listed above it, which is the healthy direction.
35→2 grin_chain.txhashset.desegmenter uses grin_util✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.desegmenter uses a type in grin_util.
- The types involved
grin_chain.txhashset.desegmenter.Desegmenter→grin_util.StopState
- Direction
- grin_chain.txhashset.desegmenter uses grin_util, so a change to grin_util can break grin_chain.txhashset.desegmenter, while a change to grin_chain.txhashset.desegmenter can't break grin_util.
- Position
- Below the diagonal: grin_chain.txhashset.desegmenter uses a module listed above it, which is the healthy direction.
35→5 grin_chain.txhashset.desegmenter uses grin_core.core.hash✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.desegmenter uses a type in grin_core.core.hash.
- The types involved
grin_chain.txhashset.desegmenter.Desegmenter→grin_core.core.hash.Hash
- Direction
- grin_chain.txhashset.desegmenter uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_chain.txhashset.desegmenter, while a change to grin_chain.txhashset.desegmenter can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_chain.txhashset.desegmenter uses a module listed above it, which is the healthy direction.
35→10 grin_chain.txhashset.desegmenter uses grin_core.core.pmmr.segment✕
- Connections
- 3 pairs of types, where a type in grin_chain.txhashset.desegmenter uses a type in grin_core.core.pmmr.segment.
- The types involved
grin_chain.txhashset.desegmenter.Desegmenter→grin_core.core.pmmr.segment.Segmentgrin_chain.txhashset.desegmenter.Desegmenter→grin_core.core.pmmr.segment.SegmentIdentifiergrin_chain.txhashset.desegmenter.Desegmenter→grin_core.core.pmmr.segment.SegmentTypeIdentifier
- Direction
- grin_chain.txhashset.desegmenter uses grin_core.core.pmmr.segment, so a change to grin_core.core.pmmr.segment can break grin_chain.txhashset.desegmenter, while a change to grin_chain.txhashset.desegmenter can't break grin_core.core.pmmr.segment.
- Position
- Below the diagonal: grin_chain.txhashset.desegmenter uses a module listed above it, which is the healthy direction.
35→11 grin_chain.txhashset.desegmenter uses grin_chain.txhashset.bitmap_accumulator✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.desegmenter uses a type in grin_chain.txhashset.bitmap_accumulator.
- The types involved
grin_chain.txhashset.desegmenter.Desegmenter→grin_chain.txhashset.bitmap_accumulator.BitmapAccumulator
- Direction
- grin_chain.txhashset.desegmenter uses grin_chain.txhashset.bitmap_accumulator, so a change to grin_chain.txhashset.bitmap_accumulator can break grin_chain.txhashset.desegmenter, while a change to grin_chain.txhashset.desegmenter can't break grin_chain.txhashset.bitmap_accumulator.
- Position
- Below the diagonal: grin_chain.txhashset.desegmenter uses a module listed above it, which is the healthy direction.
35→12 grin_chain.txhashset.desegmenter uses grin_chain.types✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.desegmenter uses a type in grin_chain.types.
- The types involved
grin_chain.txhashset.desegmenter.Desegmenter→grin_chain.types.SyncState
- Direction
- grin_chain.txhashset.desegmenter uses grin_chain.types, so a change to grin_chain.types can break grin_chain.txhashset.desegmenter, while a change to grin_chain.txhashset.desegmenter can't break grin_chain.types.
- Position
- Below the diagonal: grin_chain.txhashset.desegmenter uses a module listed above it, which is the healthy direction.
35→21 grin_chain.txhashset.desegmenter uses grin_core.core.block✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.desegmenter uses a type in grin_core.core.block.
- The types involved
grin_chain.txhashset.desegmenter.Desegmenter→grin_core.core.block.BlockHeader
- Direction
- grin_chain.txhashset.desegmenter uses grin_core.core.block, so a change to grin_core.core.block can break grin_chain.txhashset.desegmenter, while a change to grin_chain.txhashset.desegmenter can't break grin_core.core.block.
- Position
- Below the diagonal: grin_chain.txhashset.desegmenter uses a module listed above it, which is the healthy direction.
35→22 grin_chain.txhashset.desegmenter uses grin_api.types✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.desegmenter uses a type in grin_api.types.
- The types involved
grin_chain.txhashset.desegmenter.Desegmenter→grin_api.types.TxHashSet
- Direction
- grin_chain.txhashset.desegmenter uses grin_api.types, so a change to grin_api.types can break grin_chain.txhashset.desegmenter, while a change to grin_chain.txhashset.desegmenter can't break grin_api.types.
- Position
- Below the diagonal: grin_chain.txhashset.desegmenter uses a module listed above it, which is the healthy direction.
35→27 grin_chain.txhashset.desegmenter uses grin_chain.store✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.desegmenter uses a type in grin_chain.store.
- The types involved
grin_chain.txhashset.desegmenter.Desegmenter→grin_chain.store.ChainStore
- Direction
- grin_chain.txhashset.desegmenter uses grin_chain.store, so a change to grin_chain.store can break grin_chain.txhashset.desegmenter, while a change to grin_chain.txhashset.desegmenter can't break grin_chain.store.
- Position
- Below the diagonal: grin_chain.txhashset.desegmenter uses a module listed above it, which is the healthy direction.
35→33 grin_chain.txhashset.desegmenter uses grin_chain.txhashset.txhashset✕
- Connections
- 1 pair of types, where a type in grin_chain.txhashset.desegmenter uses a type in grin_chain.txhashset.txhashset.
- The types involved
grin_chain.txhashset.desegmenter.Desegmenter→grin_chain.txhashset.txhashset.PMMRHandle
- Direction
- grin_chain.txhashset.desegmenter uses grin_chain.txhashset.txhashset, so a change to grin_chain.txhashset.txhashset can break grin_chain.txhashset.desegmenter, while a change to grin_chain.txhashset.desegmenter can't break grin_chain.txhashset.txhashset.
- Position
- Below the diagonal: grin_chain.txhashset.desegmenter uses a module listed above it, which is the healthy direction.
36→5 grin_chain.chain uses grin_core.core.hash✕
- Connections
- 2 pairs of types, where a type in grin_chain.chain uses a type in grin_core.core.hash.
- The types involved
grin_chain.chain.Chain→grin_core.core.hash.Hashgrin_chain.chain.OrphanBlockPool→grin_core.core.hash.Hash
- Direction
- grin_chain.chain uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_chain.chain, while a change to grin_chain.chain can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_chain.chain uses a module listed above it, which is the healthy direction.
36→12 grin_chain.chain uses grin_chain.types✕
- Connections
- 3 pairs of types, where a type in grin_chain.chain uses a type in grin_chain.types.
- The types involved
grin_chain.chain.Chain→grin_chain.types.BlockStatusgrin_chain.chain.Chain→grin_chain.types.Optionsgrin_chain.chain.Orphan→grin_chain.types.Options
- Direction
- grin_chain.chain uses grin_chain.types, so a change to grin_chain.types can break grin_chain.chain, while a change to grin_chain.chain can't break grin_chain.types.
- Position
- Below the diagonal: grin_chain.chain uses a module listed above it, which is the healthy direction.
36→18 grin_chain.chain uses grin_core.core.transaction✕
- Connections
- 2 pairs of types, where a type in grin_chain.chain uses a type in grin_core.core.transaction.
- The types involved
grin_chain.chain.Chain→grin_core.core.transaction.Inputsgrin_chain.chain.Chain→grin_core.core.transaction.Transaction
- Direction
- grin_chain.chain uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_chain.chain, while a change to grin_chain.chain can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_chain.chain uses a module listed above it, which is the healthy direction.
36→21 grin_chain.chain uses grin_core.core.block✕
- Connections
- 4 pairs of types, where a type in grin_chain.chain uses a type in grin_core.core.block.
- The types involved
grin_chain.chain.Chain→grin_core.core.block.Blockgrin_chain.chain.Chain→grin_core.core.block.BlockHeadergrin_chain.chain.Orphan→grin_core.core.block.Blockgrin_chain.chain.chain$module→grin_core.core.block.Block
- Direction
- grin_chain.chain uses grin_core.core.block, so a change to grin_core.core.block can break grin_chain.chain, while a change to grin_chain.chain can't break grin_core.core.block.
- Position
- Below the diagonal: grin_chain.chain uses a module listed above it, which is the healthy direction.
36→22 grin_chain.chain uses grin_api.types✕
- Connections
- 3 pairs of types, where a type in grin_chain.chain uses a type in grin_api.types.
- The types involved
grin_chain.chain.Chain→grin_api.types.Tipgrin_chain.chain.Chain→grin_api.types.TxHashSetgrin_chain.chain.chain$module→grin_api.types.TxHashSet
- Direction
- grin_chain.chain uses grin_api.types, so a change to grin_api.types can break grin_chain.chain, while a change to grin_chain.chain can't break grin_api.types.
- Position
- Below the diagonal: grin_chain.chain uses a module listed above it, which is the healthy direction.
36→27 grin_chain.chain uses grin_chain.store✕
- Connections
- 3 pairs of types, where a type in grin_chain.chain uses a type in grin_chain.store.
- The types involved
grin_chain.chain.Chain→grin_chain.store.Batchgrin_chain.chain.Chain→grin_chain.store.ChainStoregrin_chain.chain.chain$module→grin_chain.store.ChainStore
- Direction
- grin_chain.chain uses grin_chain.store, so a change to grin_chain.store can break grin_chain.chain, while a change to grin_chain.chain can't break grin_chain.store.
- Position
- Below the diagonal: grin_chain.chain uses a module listed above it, which is the healthy direction.
36→33 grin_chain.chain uses grin_chain.txhashset.txhashset✕
- Connections
- 4 pairs of types, where a type in grin_chain.chain uses a type in grin_chain.txhashset.txhashset.
- The types involved
grin_chain.chain.Chain→grin_chain.txhashset.txhashset.ExtensionPairgrin_chain.chain.Chain→grin_chain.txhashset.txhashset.HeaderExtensiongrin_chain.chain.Chain→grin_chain.txhashset.txhashset.PMMRHandlegrin_chain.chain.chain$module→grin_chain.txhashset.txhashset.PMMRHandle
- Direction
- grin_chain.chain uses grin_chain.txhashset.txhashset, so a change to grin_chain.txhashset.txhashset can break grin_chain.chain, while a change to grin_chain.chain can't break grin_chain.txhashset.txhashset.
- Position
- Below the diagonal: grin_chain.chain uses a module listed above it, which is the healthy direction.
36→35 grin_chain.chain uses grin_chain.txhashset.desegmenter✕
- Connections
- 1 pair of types, where a type in grin_chain.chain uses a type in grin_chain.txhashset.desegmenter.
- The types involved
grin_chain.chain.Chain→grin_chain.txhashset.desegmenter.Desegmenter
- Direction
- grin_chain.chain uses grin_chain.txhashset.desegmenter, so a change to grin_chain.txhashset.desegmenter can break grin_chain.chain, while a change to grin_chain.chain can't break grin_chain.txhashset.desegmenter.
- Position
- Below the diagonal: grin_chain.chain uses a module listed above it, which is the healthy direction.
37→1 grin_api.handlers uses grin_api.json_rpc✕
- Connections
- 4 pairs of types, where a type in grin_api.handlers uses a type in grin_api.json_rpc.
- The types involved
grin_api.handlers.ForeignAPIHandlerV2→grin_api.json_rpc.Requestgrin_api.handlers.OwnerAPIHandlerV2→grin_api.json_rpc.Requestgrin_api.handlers.handlers$module→grin_api.json_rpc.Errorgrin_api.handlers.handlers$module→grin_api.json_rpc.Response
- Direction
- grin_api.handlers uses grin_api.json_rpc, so a change to grin_api.json_rpc can break grin_api.handlers, while a change to grin_api.handlers can't break grin_api.json_rpc.
- Position
- Below the diagonal: grin_api.handlers uses a module listed above it, which is the healthy direction.
37→2 grin_api.handlers uses grin_util✕
- Connections
- 1 pair of types, where a type in grin_api.handlers uses a type in grin_util.
- The types involved
grin_api.handlers.handlers$module→grin_util.StopState
- Direction
- grin_api.handlers uses grin_util, so a change to grin_util can break grin_api.handlers, while a change to grin_api.handlers can't break grin_util.
- Position
- Below the diagonal: grin_api.handlers uses a module listed above it, which is the healthy direction.
37→3 grin_api.handlers uses grin_api.router✕
- Connections
- 2 pairs of types, where a type in grin_api.handlers uses a type in grin_api.router.
- The types involved
grin_api.handlers.ForeignAPIHandlerV2→grin_api.router.Handlergrin_api.handlers.OwnerAPIHandlerV2→grin_api.router.Handler
- Direction
- grin_api.handlers uses grin_api.router, so a change to grin_api.router can break grin_api.handlers, while a change to grin_api.handlers can't break grin_api.router.
- Position
- Below the diagonal: grin_api.handlers uses a module listed above it, which is the healthy direction.
37→12 grin_api.handlers uses grin_chain.types✕
- Connections
- 1 pair of types, where a type in grin_api.handlers uses a type in grin_chain.types.
- The types involved
grin_api.handlers.handlers$module→grin_chain.types.SyncState
- Direction
- grin_api.handlers uses grin_chain.types, so a change to grin_chain.types can break grin_api.handlers, while a change to grin_api.handlers can't break grin_chain.types.
- Position
- Below the diagonal: grin_api.handlers uses a module listed above it, which is the healthy direction.
37→25 grin_api.handlers uses grin_pool.transaction_pool✕
- Connections
- 1 pair of types, where a type in grin_api.handlers uses a type in grin_pool.transaction_pool.
- The types involved
grin_api.handlers.handlers$module→grin_pool.transaction_pool.TransactionPool
- Direction
- grin_api.handlers uses grin_pool.transaction_pool, so a change to grin_pool.transaction_pool can break grin_api.handlers, while a change to grin_api.handlers can't break grin_pool.transaction_pool.
- Position
- Below the diagonal: grin_api.handlers uses a module listed above it, which is the healthy direction.
37→28 grin_api.handlers uses grin_p2p.peers✕
- Connections
- 1 pair of types, where a type in grin_api.handlers uses a type in grin_p2p.peers.
- The types involved
grin_api.handlers.handlers$module→grin_p2p.peers.Peers
- Direction
- grin_api.handlers uses grin_p2p.peers, so a change to grin_p2p.peers can break grin_api.handlers, while a change to grin_api.handlers can't break grin_p2p.peers.
- Position
- Below the diagonal: grin_api.handlers uses a module listed above it, which is the healthy direction.
37→36 grin_api.handlers uses grin_chain.chain✕
- Connections
- 1 pair of types, where a type in grin_api.handlers uses a type in grin_chain.chain.
- The types involved
grin_api.handlers.handlers$module→grin_chain.chain.Chain
- Direction
- grin_api.handlers uses grin_chain.chain, so a change to grin_chain.chain can break grin_api.handlers, while a change to grin_api.handlers can't break grin_chain.chain.
- Position
- Below the diagonal: grin_api.handlers uses a module listed above it, which is the healthy direction.
38→2 grin_servers.common.adapters uses grin_util✕
- Connections
- 4 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_util.
- The types involved
grin_servers.common.adapters.ChainToPoolAndNetAdapter→grin_util.OneTimegrin_servers.common.adapters.NetToChainAdapter→grin_util.OneTimegrin_servers.common.adapters.PoolToChainAdapter→grin_util.OneTimegrin_servers.common.adapters.PoolToNetAdapter→grin_util.OneTime
- Direction
- grin_servers.common.adapters uses grin_util, so a change to grin_util can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_util.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→5 grin_servers.common.adapters uses grin_core.core.hash✕
- Connections
- 2 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_core.core.hash.
- The types involved
grin_servers.common.adapters.NetToChainAdapter→grin_core.core.hash.Hashgrin_servers.common.adapters.PoolToChainAdapter→grin_core.core.hash.Hash
- Direction
- grin_servers.common.adapters uses grin_core.core.hash, so a change to grin_core.core.hash can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_core.core.hash.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→10 grin_servers.common.adapters uses grin_core.core.pmmr.segment✕
- Connections
- 2 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_core.core.pmmr.segment.
- The types involved
grin_servers.common.adapters.NetToChainAdapter→grin_core.core.pmmr.segment.Segmentgrin_servers.common.adapters.NetToChainAdapter→grin_core.core.pmmr.segment.SegmentIdentifier
- Direction
- grin_servers.common.adapters uses grin_core.core.pmmr.segment, so a change to grin_core.core.pmmr.segment can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_core.core.pmmr.segment.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→12 grin_servers.common.adapters uses grin_chain.types✕
- Connections
- 6 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_chain.types.
- The types involved
grin_servers.common.adapters.ChainToPoolAndNetAdapter→grin_chain.types.BlockStatusgrin_servers.common.adapters.ChainToPoolAndNetAdapter→grin_chain.types.ChainAdaptergrin_servers.common.adapters.ChainToPoolAndNetAdapter→grin_chain.types.Optionsgrin_servers.common.adapters.NetToChainAdapter→grin_chain.types.ChainAdaptergrin_servers.common.adapters.NetToChainAdapter→grin_chain.types.Optionsgrin_servers.common.adapters.NetToChainAdapter→grin_chain.types.SyncState
- Direction
- grin_servers.common.adapters uses grin_chain.types, so a change to grin_chain.types can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_chain.types.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→13 grin_servers.common.adapters uses grin_p2p.types✕
- Connections
- 2 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_p2p.types.
- The types involved
grin_servers.common.adapters.NetToChainAdapter→grin_p2p.types.PeerInfogrin_servers.common.adapters.NetToChainAdapter→grin_p2p.types.TxHashSetRead
- Direction
- grin_servers.common.adapters uses grin_p2p.types, so a change to grin_p2p.types can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_p2p.types.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→18 grin_servers.common.adapters uses grin_core.core.transaction✕
- Connections
- 3 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_core.core.transaction.
- The types involved
grin_servers.common.adapters.NetToChainAdapter→grin_core.core.transaction.Transactiongrin_servers.common.adapters.PoolToChainAdapter→grin_core.core.transaction.Inputsgrin_servers.common.adapters.PoolToChainAdapter→grin_core.core.transaction.Transaction
- Direction
- grin_servers.common.adapters uses grin_core.core.transaction, so a change to grin_core.core.transaction can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_core.core.transaction.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→19 grin_servers.common.adapters uses grin_core.core.compact_block✕
- Connections
- 1 pair of types, where a type in grin_servers.common.adapters uses a type in grin_core.core.compact_block.
- The types involved
grin_servers.common.adapters.NetToChainAdapter→grin_core.core.compact_block.CompactBlock
- Direction
- grin_servers.common.adapters uses grin_core.core.compact_block, so a change to grin_core.core.compact_block can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_core.core.compact_block.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→20 grin_servers.common.adapters uses grin_pool.types✕
- Connections
- 4 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_pool.types.
- The types involved
grin_servers.common.adapters.PoolToChainAdapter→grin_pool.types.BlockChaingrin_servers.common.adapters.PoolToNetAdapter→grin_pool.types.DandelionConfiggrin_servers.common.adapters.PoolToNetAdapter→grin_pool.types.PoolAdaptergrin_servers.common.adapters.PoolToNetAdapter→grin_pool.types.PoolEntry
- Direction
- grin_servers.common.adapters uses grin_pool.types, so a change to grin_pool.types can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_pool.types.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→21 grin_servers.common.adapters uses grin_core.core.block✕
- Connections
- 3 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_core.core.block.
- The types involved
grin_servers.common.adapters.ChainToPoolAndNetAdapter→grin_core.core.block.Blockgrin_servers.common.adapters.NetToChainAdapter→grin_core.core.block.Blockgrin_servers.common.adapters.NetToChainAdapter→grin_core.core.block.BlockHeader
- Direction
- grin_servers.common.adapters uses grin_core.core.block, so a change to grin_core.core.block can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_core.core.block.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→25 grin_servers.common.adapters uses grin_pool.transaction_pool✕
- Connections
- 2 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_pool.transaction_pool.
- The types involved
grin_servers.common.adapters.ChainToPoolAndNetAdapter→grin_pool.transaction_pool.TransactionPoolgrin_servers.common.adapters.NetToChainAdapter→grin_pool.transaction_pool.TransactionPool
- Direction
- grin_servers.common.adapters uses grin_pool.transaction_pool, so a change to grin_pool.transaction_pool can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_pool.transaction_pool.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→28 grin_servers.common.adapters uses grin_p2p.peers✕
- Connections
- 3 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_p2p.peers.
- The types involved
grin_servers.common.adapters.ChainToPoolAndNetAdapter→grin_p2p.peers.Peersgrin_servers.common.adapters.NetToChainAdapter→grin_p2p.peers.Peersgrin_servers.common.adapters.PoolToNetAdapter→grin_p2p.peers.Peers
- Direction
- grin_servers.common.adapters uses grin_p2p.peers, so a change to grin_p2p.peers can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_p2p.peers.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→32 grin_servers.common.adapters uses grin_servers.common.types✕
- Connections
- 2 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_servers.common.types.
- The types involved
grin_servers.common.adapters.NetToChainAdapter→grin_servers.common.types.ServerConfiggrin_servers.common.adapters.PoolToNetAdapter→grin_servers.common.types.DandelionEpoch
- Direction
- grin_servers.common.adapters uses grin_servers.common.types, so a change to grin_servers.common.types can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_servers.common.types.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
38→36 grin_servers.common.adapters uses grin_chain.chain✕
- Connections
- 2 pairs of types, where a type in grin_servers.common.adapters uses a type in grin_chain.chain.
- The types involved
grin_servers.common.adapters.NetToChainAdapter→grin_chain.chain.Chaingrin_servers.common.adapters.PoolToChainAdapter→grin_chain.chain.Chain
- Direction
- grin_servers.common.adapters uses grin_chain.chain, so a change to grin_chain.chain can break grin_servers.common.adapters, while a change to grin_servers.common.adapters can't break grin_chain.chain.
- Position
- Below the diagonal: grin_servers.common.adapters uses a module listed above it, which is the healthy direction.
39→2 grin_servers.grin.server uses grin_util✕
- Connections
- 1 pair of types, where a type in grin_servers.grin.server uses a type in grin_util.
- The types involved
grin_servers.grin.server.Server→grin_util.StopState
- Direction
- grin_servers.grin.server uses grin_util, so a change to grin_util can break grin_servers.grin.server, while a change to grin_servers.grin.server can't break grin_util.
- Position
- Below the diagonal: grin_servers.grin.server uses a module listed above it, which is the healthy direction.
39→4 grin_servers.grin.server uses grin_core.ser✕
- Connections
- 1 pair of types, where a type in grin_servers.grin.server uses a type in grin_core.ser.
- The types involved
grin_servers.grin.server.Server→grin_core.ser.ProtocolVersion
- Direction
- grin_servers.grin.server uses grin_core.ser, so a change to grin_core.ser can break grin_servers.grin.server, while a change to grin_servers.grin.server can't break grin_core.ser.
- Position
- Below the diagonal: grin_servers.grin.server uses a module listed above it, which is the healthy direction.
39→12 grin_servers.grin.server uses grin_chain.types✕
- Connections
- 1 pair of types, where a type in grin_servers.grin.server uses a type in grin_chain.types.
- The types involved
grin_servers.grin.server.Server→grin_chain.types.SyncState
- Direction
- grin_servers.grin.server uses grin_chain.types, so a change to grin_chain.types can break grin_servers.grin.server, while a change to grin_servers.grin.server can't break grin_chain.types.
- Position
- Below the diagonal: grin_servers.grin.server uses a module listed above it, which is the healthy direction.
39→13 grin_servers.grin.server uses grin_p2p.types✕
- Connections
- 1 pair of types, where a type in grin_servers.grin.server uses a type in grin_p2p.types.
- The types involved
grin_servers.grin.server.Server→grin_p2p.types.PeerAddr
- Direction
- grin_servers.grin.server uses grin_p2p.types, so a change to grin_p2p.types can break grin_servers.grin.server, while a change to grin_servers.grin.server can't break grin_p2p.types.
- Position
- Below the diagonal: grin_servers.grin.server uses a module listed above it, which is the healthy direction.
39→29 grin_servers.grin.server uses grin_servers.common.stats✕
- Connections
- 1 pair of types, where a type in grin_servers.grin.server uses a type in grin_servers.common.stats.
- The types involved
grin_servers.grin.server.Server→grin_servers.common.stats.ServerStateInfo
- Direction
- grin_servers.grin.server uses grin_servers.common.stats, so a change to grin_servers.common.stats can break grin_servers.grin.server, while a change to grin_servers.grin.server can't break grin_servers.common.stats.
- Position
- Below the diagonal: grin_servers.grin.server uses a module listed above it, which is the healthy direction.
39→31 grin_servers.grin.server uses grin_p2p.serv✕
- Connections
- 1 pair of types, where a type in grin_servers.grin.server uses a type in grin_p2p.serv.
- The types involved
grin_servers.grin.server.Server→grin_p2p.serv.Server
- Direction
- grin_servers.grin.server uses grin_p2p.serv, so a change to grin_p2p.serv can break grin_servers.grin.server, while a change to grin_servers.grin.server can't break grin_p2p.serv.
- Position
- Below the diagonal: grin_servers.grin.server uses a module listed above it, which is the healthy direction.
39→32 grin_servers.grin.server uses grin_servers.common.types✕
- Connections
- 2 pairs of types, where a type in grin_servers.grin.server uses a type in grin_servers.common.types.
- The types involved
grin_servers.grin.server.Server→grin_servers.common.types.ServerConfiggrin_servers.grin.server.Server→grin_servers.common.types.StratumServerConfig
- Direction
- grin_servers.grin.server uses grin_servers.common.types, so a change to grin_servers.common.types can break grin_servers.grin.server, while a change to grin_servers.grin.server can't break grin_servers.common.types.
- Position
- Below the diagonal: grin_servers.grin.server uses a module listed above it, which is the healthy direction.
39→36 grin_servers.grin.server uses grin_chain.chain✕
- Connections
- 1 pair of types, where a type in grin_servers.grin.server uses a type in grin_chain.chain.
- The types involved
grin_servers.grin.server.Server→grin_chain.chain.Chain
- Direction
- grin_servers.grin.server uses grin_chain.chain, so a change to grin_chain.chain can break grin_servers.grin.server, while a change to grin_servers.grin.server can't break grin_chain.chain.
- Position
- Below the diagonal: grin_servers.grin.server uses a module listed above it, which is the healthy direction.
40→3 grin_servers.mining.stratumserver uses grin_api.router✕
- Connections
- 1 pair of types, where a type in grin_servers.mining.stratumserver uses a type in grin_api.router.
- The types involved
grin_servers.mining.stratumserver.stratumserver$module→grin_api.router.Handler
- Direction
- grin_servers.mining.stratumserver uses grin_api.router, so a change to grin_api.router can break grin_servers.mining.stratumserver, while a change to grin_servers.mining.stratumserver can't break grin_api.router.
- Position
- Below the diagonal: grin_servers.mining.stratumserver uses a module listed above it, which is the healthy direction.
40→12 grin_servers.mining.stratumserver uses grin_chain.types✕
- Connections
- 2 pairs of types, where a type in grin_servers.mining.stratumserver uses a type in grin_chain.types.
- The types involved
grin_servers.mining.stratumserver.Handler→grin_chain.types.SyncStategrin_servers.mining.stratumserver.StratumServer→grin_chain.types.SyncState
- Direction
- grin_servers.mining.stratumserver uses grin_chain.types, so a change to grin_chain.types can break grin_servers.mining.stratumserver, while a change to grin_servers.mining.stratumserver can't break grin_chain.types.
- Position
- Below the diagonal: grin_servers.mining.stratumserver uses a module listed above it, which is the healthy direction.
40→16 grin_servers.mining.stratumserver uses grin_keychain.types✕
- Connections
- 1 pair of types, where a type in grin_servers.mining.stratumserver uses a type in grin_keychain.types.
- The types involved
grin_servers.mining.stratumserver.State→grin_keychain.types.Identifier
- Direction
- grin_servers.mining.stratumserver uses grin_keychain.types, so a change to grin_keychain.types can break grin_servers.mining.stratumserver, while a change to grin_servers.mining.stratumserver can't break grin_keychain.types.
- Position
- Below the diagonal: grin_servers.mining.stratumserver uses a module listed above it, which is the healthy direction.
40→17 grin_servers.mining.stratumserver uses grin_p2p.codec✕
- Connections
- 1 pair of types, where a type in grin_servers.mining.stratumserver uses a type in grin_p2p.codec.
- The types involved
grin_servers.mining.stratumserver.Handler→grin_p2p.codec.State
- Direction
- grin_servers.mining.stratumserver uses grin_p2p.codec, so a change to grin_p2p.codec can break grin_servers.mining.stratumserver, while a change to grin_servers.mining.stratumserver can't break grin_p2p.codec.
- Position
- Below the diagonal: grin_servers.mining.stratumserver uses a module listed above it, which is the healthy direction.
40→21 grin_servers.mining.stratumserver uses grin_core.core.block✕
- Connections
- 1 pair of types, where a type in grin_servers.mining.stratumserver uses a type in grin_core.core.block.
- The types involved
grin_servers.mining.stratumserver.State→grin_core.core.block.Block
- Direction
- grin_servers.mining.stratumserver uses grin_core.core.block, so a change to grin_core.core.block can break grin_servers.mining.stratumserver, while a change to grin_servers.mining.stratumserver can't break grin_core.core.block.
- Position
- Below the diagonal: grin_servers.mining.stratumserver uses a module listed above it, which is the healthy direction.
40→29 grin_servers.mining.stratumserver uses grin_servers.common.stats✕
- Connections
- 3 pairs of types, where a type in grin_servers.mining.stratumserver uses a type in grin_servers.common.stats.
- The types involved
grin_servers.mining.stratumserver.Handler→grin_servers.common.stats.StratumStatsgrin_servers.mining.stratumserver.StratumServer→grin_servers.common.stats.StratumStatsgrin_servers.mining.stratumserver.WorkersList→grin_servers.common.stats.StratumStats
- Direction
- grin_servers.mining.stratumserver uses grin_servers.common.stats, so a change to grin_servers.common.stats can break grin_servers.mining.stratumserver, while a change to grin_servers.mining.stratumserver can't break grin_servers.common.stats.
- Position
- Below the diagonal: grin_servers.mining.stratumserver uses a module listed above it, which is the healthy direction.
40→32 grin_servers.mining.stratumserver uses grin_servers.common.types✕
- Connections
- 2 pairs of types, where a type in grin_servers.mining.stratumserver uses a type in grin_servers.common.types.
- The types involved
grin_servers.mining.stratumserver.Handler→grin_servers.common.types.StratumServerConfiggrin_servers.mining.stratumserver.StratumServer→grin_servers.common.types.StratumServerConfig
- Direction
- grin_servers.mining.stratumserver uses grin_servers.common.types, so a change to grin_servers.common.types can break grin_servers.mining.stratumserver, while a change to grin_servers.mining.stratumserver can't break grin_servers.common.types.
- Position
- Below the diagonal: grin_servers.mining.stratumserver uses a module listed above it, which is the healthy direction.
40→36 grin_servers.mining.stratumserver uses grin_chain.chain✕
- Connections
- 2 pairs of types, where a type in grin_servers.mining.stratumserver uses a type in grin_chain.chain.
- The types involved
grin_servers.mining.stratumserver.Handler→grin_chain.chain.Chaingrin_servers.mining.stratumserver.StratumServer→grin_chain.chain.Chain
- Direction
- grin_servers.mining.stratumserver uses grin_chain.chain, so a change to grin_chain.chain can break grin_servers.mining.stratumserver, while a change to grin_servers.mining.stratumserver can't break grin_chain.chain.
- Position
- Below the diagonal: grin_servers.mining.stratumserver uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 33 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 30 | High / Critical |
| A02:2025 — Security Misconfiguration | 10 | High / Critical |
Roadmap
First, centralize access controls by defining roles and permissions in a single, reviewable location to ensure rules are testable and consistent. Second, address the lack of architectural documentation by resolving the missing Architecture Decision Records and cleaning up orphaned files, starting with types.rs and pmmr.rs. Finally, integrate static analysis and security scanning into the CI pipeline to automatically block regressions and dependency vulnerabilities before they reach production.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.6 pts | Low | ADR Quality |
| Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own. | +6.9 pts | Medium | Access Controls |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). | +2.4 pts | Low | Static Analysis (SAST) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +1.8 pts | Low | Static Analysis (SAST) |
| Resolve the 73 Orphaned file finding(s) in Knowledge Freshness — start with types.rs (6), pmmr.rs (2), transaction_pool.rs (2). | +3.3 pts | Medium | Knowledge Freshness |
| Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +3.1 pts | Medium | Security & performance tooling |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.1 pts | Medium | Architecture documentation |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.3 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| keychain/src/extkey_bip32.rs | 5.9 | Mixed | Code Duplication: Duplicated block (13 lines × 2) |
| chain/src/txhashset/desegmenter.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| servers/src/grin/sync/state_sync.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/pow/cuckatoo.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| p2p/src/codec.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| servers/src/grin/server.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/core/pmmr/segment.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| servers/src/common/adapters.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| chain/src/txhashset/txhashset.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| chain/src/chain.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| servers/src/mining/stratumserver.rs | 6.0 | Mixed | Explicit Debt: XxxComment |
| api/src/handlers/chain_api.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/libtx/proof.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| keychain/src/types.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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. 51 of 51 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 — 51 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, 353 of 393 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) 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`) 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`) 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.
- 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.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — 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.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — 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 REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:2 -------------------- 1 | # Builder 2 | >>> FROM rust:slim-trixie AS builder 3 | 4 | WORKDIR /usr/src/grin -------------------- ERROR: failed to solve: rust:slim-trixie: failed to resolve source metadata for docker.io/library/rust:slim-trixie: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/slim-trixie": Forbidden; runtime evidence skipped.
- C1 Data Protection — 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. 'heed' is imported (store/src/lmdb.rs:17), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — 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. 'heed' is imported (store/src/lmdb.rs:17), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'heed' is imported (store/src/lmdb.rs:17), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'heed' is imported (store/src/lmdb.rs:17), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- 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 no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust 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 no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — 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, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — 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, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — 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, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — 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, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — 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, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — 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, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust 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.
- X23 Unguarded diagnostic materialisation — 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, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — 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, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — 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, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — 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, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — 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 and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust 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.
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.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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".
- 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
17 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was grin_core::ser::deserialize_error_kind at 91. A further 4 function(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 grin_p2p::msg::max_msg_size at 29 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: p2p/src/msg.rs (grin_p2p::msg::max_msg_size at 29). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with grin_core::ser::deserialize_error_kind (cyclomatic 91). — Refactoring it lifts Cyclomatic Complexity from 6.8 to about 7.2/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
43 function(s) exceeded the cognitive complexity threshold of 15; the worst was StateSync::check_run at 74.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with StateSync::check_run (cognitive 74). — Refactoring it lifts Cognitive Complexity from 6.3 to about 6.5/10.
- 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
32 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 11 FileTooLong finding(s) in God Classes — start with txhashset.rs, transaction.rs, chain.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 8 MethodTooLong finding(s) in God Classes — start with state_sync.rs (2), protocol.rs, server.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 5 ClassTooLong finding(s) in God Classes — start with chain.rs, desegmenter.rs, adapters.rs. — One of this dimension's main actionable groups (5 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
51 duplicated block group(s) detected. A further 6 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 6 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with pmmr.rs (2), cuckaroo.rs (2), linked_list.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with chain_api.rs, desegmenter.rs, extkey_bip32.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with segmenter.rs (2), cuckaroo.rs, extkey_bip32.rs. — One of this dimension's main actionable groups (5 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
11 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 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)
4 of 154 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with types.rs (2), foreign.rs, extkey_bip32.rs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
280 test methods: 81 unit, 199 integration, 0 BDD, 0 e2e. The Rust suite contributes 280 `#[test]` function(s) across 81 file(s) declaring at least one; its unit/integration split is Cargo's own — 49 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.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 81 test files): measured (0 flaky).
D12 · Dependency Hygiene
20 outdated, 0 yanked direct Cargo dependencies. 62 of 64 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 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 356 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. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: servers/src/grin/server.rs (2×17=34)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with server.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
16 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is core/src/ser.rs. Counted over 97 of the 154 production source files in this repository: 46 are under the ~2,400-byte size floor this dimension measures over, and the remaining 11 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
53 deducted task-comment markers across 48885 LoC (0.1/KLoC) → score 9.8. 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 52 TodoComment finding(s) in Explicit Debt — start with state_sync.rs (4), bitmap_accumulator.rs (4), pmmr.rs (3). — One of this dimension's main actionable groups (52 warning-level).
- Resolve the 1 XxxComment finding(s) in Explicit Debt — start with stratumserver.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. 74 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 11 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
33 finding(s): 0 critical, 32 high, 1 medium, 0 low. 25 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 25 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (25 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
20 finding(s): 0 critical, 1 high, 19 medium, 0 low.
What to do
- Resolve the 11 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D31 · IaC & Container Security
10 finding(s): 0 critical, 2 high, 3 medium, 5 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 5 Low IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
76 of 108 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/src/core/transaction.rs. Counted over 108 of the 154 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 73 Orphaned file finding(s) in Knowledge Freshness — start with types.rs (6), pmmr.rs (2), transaction_pool.rs (2). — One of this dimension's main actionable groups (73 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with transaction.rs, txhashset.rs, chain.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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
AX9 · CQS / query purity
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
- Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
What to do
- Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
- Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 11 of 13 project(s) that lack one — worth up to 1.7 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 288/359 types (80%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
- Only 10/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `core/fuzz`.
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
- No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 17563 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection(` (api/src/rest.rs:248).
What to do
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
- `path_len` is read from the bytes being parsed at line 52 (`read_u64`), then used to size a `Vec::with_capacity` at line 53 — and nowhere in its scope is `path_len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `path_len` against the bytes actually remaining and a maximum the format allows before allocating. — core/src/core/merkle_proof.rs:53
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 89% | Strong | Solid. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 61% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 49% | Weak — gated by D29, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'heed' (store/src/lmdb.rs:17) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'heed' (store/src/lmdb.rs:17) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'heed' (store/src/lmdb.rs:17) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: 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.
- AX2 Stateful singletons — Not applicable: 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:2 -------------------- 1 | # Builder 2 | >>> FROM rust:slim-trixie AS builder 3 | 4 | WORKDIR /usr/src/grin -------------------- ERROR: failed to solve: rust:slim-trixie: failed to resolve source metadata for docker.io/library/rust:slim-trixie: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/slim-trixie": 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 — Not assessed: this repository stores data through 'heed' (store/src/lmdb.rs:17) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- D10 Test Quality — ~11262 lines of test source are present (.rs) 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.
- 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; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust 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 .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.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.
- 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
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (14 value object(s))
- 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 — Not assessed, and this one is on us: 17 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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 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.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X16 Unfloored truncation loop — 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — 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
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — 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.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — 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
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — 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 — 35 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
Serious — 238 finding(s)
- TodoComment store/tests/pmmr.rs:456
- TodoComment servers/src/grin/server.rs:450
- TodoComment servers/src/grin/server.rs:597
- TodoComment servers/src/grin/sync/header_sync.rs:66
- TodoComment servers/src/grin/sync/state_sync.rs:255
- TodoComment servers/src/grin/sync/state_sync.rs:300
- TodoComment chain/tests/test_pibd_copy.rs:185
- TodoComment servers/src/grin/sync/state_sync.rs:314
- TodoComment servers/src/grin/sync/state_sync.rs:347
- TodoComment servers/src/common/adapters.rs:565
- TodoComment pool/src/pool.rs:444
- TodoComment p2p/src/codec.rs:243
- TodoComment p2p/src/msg.rs:350
- TodoComment p2p/src/serv.rs:52
- TodoComment keychain/src/types.rs:28
- TodoComment keychain/src/types.rs:132
- TodoComment core/src/libtx/aggsig.rs:262
- TodoComment core/src/libtx/build.rs:73
- TodoComment core/src/libtx/build.rs:121
- TodoComment core/src/libtx/proof.rs:41
- TodoComment core/src/libtx/reward.rs:40
- TodoComment chain/tests/mine_simple_chain.rs:837
- TodoComment keychain/src/view_key.rs:175
- TodoComment core/tests/pmmr.rs:558
- TodoComment core/tests/pmmr.rs:567
- FileTooLong: txhashset/txhashset.rs chain/src/txhashset/txhashset.rs
- FileTooLong: core/transaction.rs core/src/core/transaction.rs
- FileTooLong: src/chain.rs chain/src/chain.rs
- FileTooLong: src/ser.rs core/src/ser.rs
- FileTooLong: txhashset/desegmenter.rs chain/src/txhashset/desegmenter.rs
- FileTooLong: common/adapters.rs servers/src/common/adapters.rs
- FileTooLong: src/lmdb.rs store/src/lmdb.rs
- FileTooLong: src/msg.rs p2p/src/msg.rs
- FileTooLong: mining/stratumserver.rs servers/src/mining/stratumserver.rs
- FileTooLong: src/peers.rs p2p/src/peers.rs
- FileTooLong: pmmr/segment.rs core/src/core/pmmr/segment.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: Protocol.consume p2p/src/protocol.rs:51
- MethodTooLong: StateSync.continue_pibd servers/src/grin/sync/state_sync.rs:249
- MethodTooLong: Server.new servers/src/grin/server.rs:145
- MethodTooLong: StateSync.check_run servers/src/grin/sync/state_sync.rs:77
- MethodTooLong: TUIStatusView.update_sync_status src/bin/tui/status.rs:36
- MethodTooLong: Handler.handle_submit servers/src/mining/stratumserver.rs:359
- MethodTooLong: TUIMiningView.create src/bin/tui/mining.rs:163
- MethodTooLong: Store.new store/src/lmdb.rs:165
- Duplicated block (12 lines × 2) chain/src/linked_list.rs:410
- Duplicated block (12 lines × 2) core/src/core/pmmr/pmmr.rs:361
- Duplicated block (12 lines × 2) core/src/pow/cuckaroo.rs:88
- Duplicated block (12 lines × 2) core/src/pow/cuckaroo.rs:98
- Duplicated block (12 lines × 2) core/src/core/pmmr/pmmr.rs:439
- Duplicated block (12 lines × 2) servers/src/common/hooks.rs:136
- ClassTooLong: Chain chain/src/chain.rs:148
- ClassTooLong: Desegmenter chain/src/txhashset/desegmenter.rs:41
- ClassTooLong: NetToChainAdapter servers/src/common/adapters.rs:58
- ClassTooLong: Extension chain/src/txhashset/txhashset.rs:1134
- ClassTooLong: Peers p2p/src/peers.rs:44
- Duplicated block (13 lines × 2) api/src/handlers/chain_api.rs:198
- Duplicated block (13 lines × 2) chain/src/txhashset/desegmenter.rs:816
- Duplicated block (13 lines × 2) keychain/src/extkey_bip32.rs:490
- Duplicated block (13 lines × 2) keychain/src/keychain.rs:135
- Duplicated block (13 lines × 2) p2p/src/peer.rs:114
- Duplicated block (9 lines × 2) chain/src/txhashset/segmenter.rs:63
- Duplicated block (9 lines × 2) chain/src/txhashset/segmenter.rs:100
- Duplicated block (9 lines × 2) core/src/pow/cuckaroo.rs:71
- Duplicated block (9 lines × 2) keychain/src/extkey_bip32.rs:568
- Duplicated block (9 lines × 2) core/src/core/pmmr/pmmr.rs:375
- Duplicated block (7 lines × 2) api/src/auth.rs:59
- Duplicated block (7 lines × 2) chain/src/linked_list.rs:341
- Duplicated block (7 lines × 2) chain/src/txhashset/txhashset.rs:753
- Duplicated block (7 lines × 2) core/src/libtx/secp_ser.rs:80
- Duplicated block (7 lines × 2) chain/src/store.rs:468
- Extension::verify_rangeproofs (cognitive 27) chain/src/txhashset/txhashset.rs:1955
- Extension::apply_output_segment (cognitive 20) chain/src/txhashset/txhashset.rs:1411
- Extension::apply_rangeproof_segment (cognitive 20) chain/src/txhashset/txhashset.rs:1458
- Extension::rewind_single_block (cognitive 20) chain/src/txhashset/txhashset.rs:1631
- TooManyMethods: Chain chain/src/chain.rs:148
- TooManyMethods: Extension chain/src/txhashset/txhashset.rs:1134
- TooManyMethods: Batch chain/src/store.rs:205
- TooManyMethods: Desegmenter chain/src/txhashset/desegmenter.rs:41
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (6 lines × 2) api/src/handlers/chain_api.rs:413
- Duplicated block (6 lines × 2) core/src/core/transaction.rs:1026
- Duplicated block (6 lines × 2) core/src/pow/cuckarood.rs:59
- Duplicated block (6 lines × 2) servers/src/common/adapters.rs:628
- Duplicated block (5 lines × 2) api/src/foreign_rpc.rs:1001
- Duplicated block (5 lines × 2) chain/src/linked_list.rs:359
- Duplicated block (5 lines × 2) chain/src/linked_list.rs:370
- Duplicated block (5 lines × 2) keychain/src/extkey_bip32.rs:553
- Low cohesion: P2PConfig (LCOM4 5) p2p/src/types.rs:262
- Low cohesion: Foreign (LCOM4 4) api/src/foreign.rs:39
- Low cohesion: BIP32GrinHasher (LCOM4 4) keychain/src/extkey_bip32.rs:91
- Low cohesion: Identifier (LCOM4 4) keychain/src/types.rs:80
- FunctionTooLong: grin_config::comments::comments config/src/comments.rs:19
- FunctionTooLong: grin_core::ser::deserialize_error_kind core/src/ser.rs:1136
- FunctionTooLong: grin_p2p::conn::poll p2p/src/conn.rs:211
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- StateSync::check_run (cyclomatic 31) servers/src/grin/sync/state_sync.rs:77
- StateSync::continue_pibd (cyclomatic 25) servers/src/grin/sync/state_sync.rs:249
- StateSync::check_run (cognitive 74) servers/src/grin/sync/state_sync.rs:77
- StateSync::continue_pibd (cognitive 55) servers/src/grin/sync/state_sync.rs:249
- Desegmenter::next_desired_segments (cognitive 59) chain/src/txhashset/desegmenter.rs:478
- Desegmenter::apply_next_segments (cognitive 28) chain/src/txhashset/desegmenter.rs:379
- grin_servers::grin::seed::monitor_peers (cognitive 34) servers/src/grin/seed.rs:131
- grin_servers::grin::seed::listen_for_addrs (cognitive 18) servers/src/grin/seed.rs:345
- Store::new (cognitive 34) store/src/lmdb.rs:165
- Store::migrate_to_default_env (cognitive 18) store/src/lmdb.rs:318
- Segment::root (cognitive 33) core/src/core/pmmr/segment.rs:413
- Segment::from_pmmr (cognitive 20) core/src/core/pmmr/segment.rs:343
- TxHashSet::verify_kernel_pos_index (cognitive 30) chain/src/txhashset/txhashset.rs:551
- TxHashSet::init_output_pos_index (cognitive 27) chain/src/txhashset/txhashset.rs:635
- Server::listen (cognitive 29) p2p/src/serv.rs:74
- Server::new (cognitive 23) servers/src/grin/server.rs:145
- grin_chain::chain::setup_head (cognitive 25) chain/src/chain.rs:1690
- grin_chain::pipe::validate_header (cognitive 16) chain/src/pipe.rs:366
- Members sharing a duplicated core (5 members, 50+ identical tokens) chain/src/chain.rs:1115
- Members sharing a duplicated core (5 members, 50+ identical tokens) core/src/pow/cuckaroo.rs:64
- Members sharing a duplicated core (4 members, 50+ identical tokens) chain/src/txhashset/segmenter.rs:56
- Members sharing a duplicated core (4 members, 50+ identical tokens) servers/src/common/adapters.rs:497
- Duplicated block (22 lines × 2) core/src/genesis.rs:70
- Duplicated block (22 lines × 2) core/src/ser.rs:1197
- Duplicated block (16 lines × 2) api/src/handlers.rs:171
- Duplicated block (16 lines × 2) chain/src/chain.rs:1210
- Duplicated block (15 lines × 2) core/src/pow/cuckaroo.rs:115
- Duplicated block (15 lines × 2) store/src/prune_list.rs:208
- Duplicated block (8 lines × 3) chain/src/txhashset/txhashset.rs:67
- Duplicated block (8 lines × 3) core/src/pow/cuckaroo.rs:76
- Duplicated block (8 lines × 2) chain/src/chain.rs:1168
- Duplicated block (8 lines × 2) core/src/genesis.rs:46
- grin_core::ser::deserialize_error_kind (cyclomatic 91) core/src/ser.rs:1136
- Protocol::consume (cyclomatic 41) p2p/src/protocol.rs:51
- Desegmenter::next_desired_segments (cyclomatic 31) chain/src/txhashset/desegmenter.rs:478
- TUIStatusView::update_sync_status (cyclomatic 23) src/bin/tui/status.rs:36
- grin_p2p::conn::poll (cyclomatic 21) p2p/src/conn.rs:211
- grin_servers::grin::seed::monitor_peers (cyclomatic 21) servers/src/grin/seed.rs:131
- grin::bin::grin::real_main (cyclomatic 21) src/bin/grin.rs:84
- CuckatooContext::verify_impl (cyclomatic 19) core/src/pow/cuckatoo.rs:257
- CuckarooContext::verify (cyclomatic 18) core/src/pow/cuckaroo.rs:64
- CuckaroozContext::verify (cyclomatic 17) core/src/pow/cuckarooz.rs:58
- Codec::read_inner (cyclomatic 17) p2p/src/codec.rs:126
- Server::new (cyclomatic 17) servers/src/grin/server.rs:145
- SyncRunner::sync_loop (cyclomatic 17) servers/src/grin/sync/syncer.rs:112
- Segment::root (cyclomatic 16) core/src/core/pmmr/segment.rs:413
- CuckaroodContext::verify (cyclomatic 16) core/src/pow/cuckarood.rs:58
- Hotspot: servers/src/grin/server.rs servers/src/grin/server.rs:145
- XxxComment servers/src/mining/stratumserver.rs:744
- Codec::read_inner (cognitive 37) p2p/src/codec.rs:126
- Pool::bucket_transactions (cognitive 37) pool/src/pool.rs:351
- SyncRunner::sync_loop (cognitive 37) servers/src/grin/sync/syncer.rs:112
- Protocol::consume (cognitive 35) p2p/src/protocol.rs:51
- HeaderSync::header_sync_due (cognitive 35) servers/src/grin/sync/header_sync.rs:96
- grin_p2p::conn::poll (cognitive 34) p2p/src/conn.rs:211
- CuckatooContext::verify_impl (cognitive 33) core/src/pow/cuckatoo.rs:257
- NetToChainAdapter::compact_block_received (cognitive 33) servers/src/common/adapters.rs:154
- CuckarooContext::verify (cognitive 32) core/src/pow/cuckaroo.rs:64
- grin_api::rest::start_server (cognitive 31) api/src/rest.rs:200
- CuckaroozContext::verify (cognitive 30) core/src/pow/cuckarooz.rs:58
- grin::bin::grin::real_main (cognitive 29) src/bin/grin.rs:84
- CuckaroodContext::verify (cognitive 27) core/src/pow/cuckarood.rs:58
- TUIStatusView::update_sync_status (cognitive 25) src/bin/tui/status.rs:36
- grin_core::ser::deserialize_error_kind (cognitive 24) core/src/ser.rs:1136
- CuckaroomContext::verify (cognitive 23) core/src/pow/cuckaroom.rs:57
- PMMR::validate (cognitive 21) core/src/core/pmmr/pmmr.rs:331
- Controller::run (cognitive 20) src/bin/tui/ui.rs:260
- BlockHandler::get_blocks (cognitive 19) api/src/handlers/blocks_api.rs:123
- Peers::clean_peers (cognitive 18) p2p/src/peers.rs:344
- DatabaseIterator::next (cognitive 17) store/src/lmdb.rs:879
- TransactionPool::add_to_pool (cognitive 16) pool/src/transaction_pool.rs:142
- BodySync::body_sync (cognitive 16) servers/src/grin/sync/body_sync.rs:82
- REDACTED
- TooManyFunctions: grin_core::global core/src/global.rs:181
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (48 shared lines) core/src/genesis.rs:45
- Near-duplicate member pair (17 shared lines) chain/src/linked_list.rs:339
- Duplicated block (29 lines × 2) core/src/pow/cuckaroo.rs:118
- Duplicated block (15–20 lines × 2) api/src/handlers/chain_api.rs:258
- Duplicated block (14 lines × 3) core/src/pow/cuckaroo.rs:139
- Duplicated block (14 lines × 2) core/src/libtx/proof.rs:209
- Duplicated block (12–13 lines × 2) core/src/core/transaction.rs:420
- Duplicated block (9–10 lines × 4) chain/src/txhashset/desegmenter.rs:649
- Duplicated block (7 lines × 4) chain/src/txhashset/segmenter.rs:63
- Duplicated block (6 lines × 5) core/src/pow/cuckaroo.rs:80
- Duplicated block (6 lines × 4) servers/src/common/adapters.rs:499
- Duplicated block (5 lines × 3) servers/src/common/adapters.rs:598
- Duplicated block (11 lines × 2) core/src/core/pmmr/pmmr.rs:427
- Duplicated block (18 lines × 2) core/src/genesis.rs:94
- Off the main sequence: grin_util
- Length read from the parsed input is spent without ever being bounded core/src/core/merkle_proof.rs:53
Minor — 100 finding(s)
- Orphaned file api/src/foreign_rpc.rs:1
- Orphaned file servers/src/mining/stratumserver.rs:1
- Orphaned file p2p/src/msg.rs:1
- Orphaned file keychain/src/extkey_bip32.rs:1
- Orphaned file core/src/core/block.rs:1
- Orphaned file chain/src/pipe.rs:1
- Orphaned file api/src/types.rs:1
- Orphaned file core/src/core/pmmr/pmmr.rs:1
- Orphaned file chain/src/store.rs:1
- Orphaned file p2p/src/peer.rs:1
- Orphaned file store/src/types.rs:1
- Orphaned file core/src/libtx/proof.rs:1
- Orphaned file store/src/pmmr.rs:1
- Orphaned file core/src/consensus.rs:1
- Orphaned file chain/src/linked_list.rs:1
- Orphaned file keychain/src/types.rs:1
- Orphaned file keychain/src/mnemonic.rs:1
- Orphaned file pool/src/pool.rs:1
- Orphaned file core/src/pow/types.rs:1
- Orphaned file core/src/libtx/aggsig.rs:1
- Orphaned file core/src/pow/cuckatoo.rs:1
- Orphaned file core/src/genesis.rs:1
- Orphaned file store/src/prune_list.rs:1
- Orphaned file p2p/src/serv.rs:1
- Orphaned file core/src/libtx/secp_ser.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Most significant orphaned file core/src/core/transaction.rs:1
- Most significant orphaned file chain/src/txhashset/txhashset.rs:1
- Most significant orphaned file chain/src/chain.rs:1
- No named authorization policies
- Thin authorization enforcement
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- No ADRs
- Large public API surface
- Logging is not universal
- No SAST
- No release approval gate
- No security response headers detected
- Duplicated predicate chain/src/pipe.rs:65
- Silent fallback default on Err src/bin/tui/peers.rs:67
Minor — 20 finding(s)
- Outdated: anyhow
- Outdated: backtrace
- Outdated: bytes
- Outdated: futures
- Outdated: http-body-util
- Outdated: hyper
- Outdated: hyper-rustls
- Outdated: hyper-util
- Outdated: lazy_static
- Outdated: libc
- Outdated: log
- Outdated: regex
- Outdated: rustls
- Outdated: serde
- Outdated: serde_derive
- Outdated: serde_json
- Outdated: tokio
- Outdated: tokio-rustls
- Outdated: tokio-util
- 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-3ac605d91290427586bd7cafc1bd1dc0/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3ac605d91290427586bd7cafc1bd1dc0/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/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 . | 33 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 20 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 10 | 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 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |