Executive summary
cberner/redb meets our standard for production, though the project keeps no record of its design decisions. It scores 71 out of 100 and is rated Strong, and all ten of its critical findings are security problems.
Maturity, at 66, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5 points. Adding build and run instructions to the README is another step, worth about 2 points. Raising Maturity to 70 would lift the score to about 73.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three settings leave the servers or containers unsafe, and one weakness in the code could be used by an attacker. Pinning each tool to an exact version, correcting the unsafe settings and fixing the weaknesses the scanner points to would close these risks.
The product code is 44,887 lines, about €88,000 to rebuild.
If Maturity rose from 66 to 70, the lowest score rated Strong, the score would rise from 71 to about 73.
New since the last survey: 90 findings
- Cyclomatic Complexity · TransactionalMemory::lock_whole_storage (cyclomatic 18) src/tree_store/page_store/page_manager.rs
- Cognitive Complexity · MultimapTable::insert_inner (cognitive 32) src/multimap_table.rs
- Cognitive Complexity · MultimapTable::remove_inner (cognitive 32) src/multimap_table.rs
- God Classes · MethodTooLong: MultimapTable.insert_inner src/multimap_table.rs
- God Classes · MethodTooLong: MultimapTable.remove_inner src/multimap_table.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/table.rs
- Code Duplication · Edited copy of a member (23 corresponding lines) src/tree_store/page_store/xxh3.rs
- Code Duplication · Edited copy of a member (23 corresponding lines) src/tree_store/btree.rs
- Code Duplication · Edited copy of a member (32 corresponding lines) src/tree_store/table_tree.rs
- Code Duplication · Edited copy of a member (28 corresponding lines) src/error.rs
- Code Duplication · Edited copy of a member (20 corresponding lines) src/tree_store/page_store/xxh3.rs
- Code Duplication · Edited copy of a member (23 corresponding lines) src/tree_store/table_tree.rs
- Code Duplication · Edited copy of a member (26 corresponding lines) src/tree_store/btree_base.rs
- Code Duplication · Edited copy of a member (22 corresponding lines) src/tree_store/page_store/xxh3.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) src/tree_store/page_store/xxh3.rs
- Code Duplication · Edited copy of a member (31 corresponding lines) src/tree_store/page_store/file_backend/optimized.rs
- Code Duplication · Edited copy of a member (22 corresponding lines) src/tree_store/btree_cursor.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/multimap_table.rs
- Code Duplication · Edited copy of a member (24 corresponding lines) src/tree_store/extract_if.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/table.rs
- Code Duplication · Edited copy of a member (25 corresponding lines) src/tree_store/page_store/xxh3.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/table.rs
- Code Duplication · Edited copy of a member (22 corresponding lines) src/multimap_table.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) src/multimap_table.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) src/transactions.rs
- Code Duplication · Edited copy of a member (24 corresponding lines) src/tree_store/btree_base.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) src/tree_store/btree_base.rs
- Code Duplication · Edited copy of a member (24 corresponding lines) src/transactions.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) src/tree_store/btree.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) src/tree_store/table_tree.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/transactions.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/tree_store/btree_base.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/tree_store/btree.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/tree_store/btree_base.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) src/tree_store/btree_cursor.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) src/tree_store/page_store/file_backend/optimized.rs
- Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) src/multimap_table.rs
- Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) src/tree_store/btree_base.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/tree_store/btree_cursor.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/tree_store/page_store/file_backend/fallback.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/db.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/table.rs
- Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) src/table.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) crates/redb-python/src/table.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/tree_store/btree_cursor.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/tree_store/page_store/page_manager.rs
- Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) fuzz/fuzz_targets/fuzz_corruption.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/tree_store/btree_base.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) src/db.rs
- Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) src/multimap_table.rs
- Code Duplication · Edited copies of one member (6 members, 6+ corresponding lines) src/table.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/tree_store/page_store/page_manager.rs
- Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) src/transactions.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/tree_store/btree_cursor.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) src/transactions.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/tree_store/btree.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/tree_store/page_store/page_manager.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/multimap_table.rs
- Code Duplication · Edited copy of a member (6 corresponding lines) src/tree_store/btree_cursor.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) src/table.rs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/multimap_table.rs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/multimap_table.rs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/multimap_table.rs
- Code Duplication · Edited copy of a member (5 corresponding lines) src/table.rs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/tree_store/btree.rs
- Code Duplication · Duplicated block (26–28 lines × 3) src/tree_store/btree_mutator.rs
- Code Duplication · Duplicated block (21 lines × 2) src/tree_store/btree.rs
- Code Duplication · Duplicated block (19–20 lines × 2) src/tree_store/btree_mutator.rs
- Code Duplication · Duplicated block (16 lines × 2) src/table.rs
- Code Duplication · Duplicated block (14 lines × 2) src/tree_store/btree_mutator.rs
- Code Duplication · Duplicated block (11 lines × 2) src/table.rs
- Code Duplication · Duplicated block (10 lines × 4) src/table.rs
- Code Duplication · Duplicated block (9 lines × 2) src/tree_store/btree_mutator.rs
- Code Duplication · Duplicated block (8 lines × 2) src/multimap_table.rs
- Code Duplication · Duplicated block (8 lines × 2) src/table.rs
- Code Duplication · Duplicated block (8 lines × 2) src/table.rs
- Code Duplication · Duplicated block (8 lines × 2) src/transactions.rs
- Code Duplication · Duplicated block (6 lines × 2) crates/redb-bench/src/lib.rs
- Code Duplication · Duplicated block (9 lines × 2) src/tree_store/page_store/xxh3.rs
- Code Duplication · Duplicated block (7 lines × 2) src/multimap_table.rs
- Code Duplication · Duplicated block (10 lines × 2) src/transactions.rs
- Code Duplication · Duplicated block (5 lines × 2) src/tree_store/page_store/xxh3.rs
- Code Duplication · Edited copy of a member (20 corresponding lines) fuzz/fuzz_targets/fuzz_redb.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) fuzz/fuzz_targets/fuzz_corruption.rs
- Code Duplication · Duplicated block (12–14 lines × 2) fuzz/fuzz_targets/fuzz_corruption.rs
- Code Duplication · Duplicated block (12 lines × 2) fuzz/fuzz_targets/fuzz_corruption.rs
- Code Duplication · Duplicated block (10 lines × 2) fuzz/fuzz_targets/fuzz_corruption.rs
- Code Duplication · Duplicated block (10 lines × 2) fuzz/fuzz_targets/fuzz_redb.rs
- Code Duplication · Duplicated block (6 lines × 2) fuzz/fuzz_targets/fuzz_redb.rs
- Static Analysis (SAST) · REDACTED
Fixed since the last survey: 21 findings
- Cognitive Complexity · MultimapTable::insert (cognitive 32) src/multimap_table.rs
- Cognitive Complexity · MultimapTable::remove (cognitive 32) src/multimap_table.rs
- God Classes · MethodTooLong: MultimapTable.insert src/multimap_table.rs
- God Classes · MethodTooLong: MultimapTable.remove src/multimap_table.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/table.rs
- Code Duplication · Duplicated block (26–28 lines × 3) src/tree_store/btree_mutator.rs
- Code Duplication · Duplicated block (21 lines × 2) src/tree_store/btree.rs
- Code Duplication · Duplicated block (10–12 lines × 2) src/transactions.rs
- Code Duplication · Duplicated block (10 lines × 4) src/table.rs
- Code Duplication · Duplicated block (8 lines × 2) src/table.rs
- Code Duplication · Duplicated block (7 lines × 2) src/table.rs
- Code Duplication · Duplicated block (6 lines × 2) src/tree_store/page_store/xxh3.rs
- Code Duplication · Duplicated block (7 lines × 2) src/multimap_table.rs
- Code Duplication · Duplicated block (11 lines × 2) src/transactions.rs
- Code Duplication · Duplicated block (5 lines × 2) src/tree_store/page_store/xxh3.rs
- Code Duplication · Duplicated block (10 lines × 2) fuzz/fuzz_targets/fuzz_redb.rs
- Code Duplication · Duplicated block (6 lines × 2) fuzz/fuzz_targets/fuzz_redb.rs
- Churn × Complexity Hotspots · Hotspot: src/error.rs src/error.rs
- Churn × Complexity Hotspots · Hotspot: fuzz/fuzz_targets/fuzz_redb.rs fuzz/fuzz_targets/fuzz_redb.rs
- Static Analysis (SAST) · High: watchdog-unpinned-package-install-in-run REDACTED
- Static Analysis (SAST) · High: watchdog-unpinned-package-install-in-run REDACTED
Rebuild cost: about €88,000 · Estimate
| Cost to rebuild | €29,000 to €150,000, for 487 to 1,545 hours of work, about 0.6 person-years for 1 to 2 engineers |
|---|---|
| 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 | ×1.0 at a score of 71. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 44,887 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 redb.sealed | 2 redb.tree_store.page_store.bitmap | 3 redb.types | 4 redb_python.fork | 5 redb.error | 6 redb.key_range | 7 redb.legacy_types | 8 redb.tree_store.page_store.buddy_allocator | 9 redb.tree_store.page_store.cached_file | 10 redb.tree_store.page_store.layout | 11 redb.tree_store.page_store.savepoint | 12 redb_python.types | 13 redb.tree_store.page_store.base | 14 redb.tree_store.page_store.file_backend.range_lock | 15 redb.tree_store.page_store.region | 16 redb.tree_store.btree_iters | 17 redb.tree_store.btree_mutator | 18 redb.tree_store.table_tree_base | 19 redb.tree_store.btree_cursor | 20 redb.tree_store.btree_cursor_range | 21 redb.tree_store.btree | 22 redb.tree_store.extract_if | 23 redb.tree_store.table_tree | 24 redb.transactions | 25 redb.table | 26 redb.tree_store.btree_base | 27 redb.tree_store.page_store.active_transactions | 28 redb.tree_store.page_store.header | 29 redb_python.table | 30 redb.tree_store.page_store.page_manager | 31 redb.transaction_tracker | 32 redb.tree_store.multimap_btree | 33 redb.db | 34 redb.multimap_table | 35 redb.tree_store.page_store.backends | 36 redb.tree_store.page_store.file_backend.fallback | 37 redb.tree_store.page_store.file_backend.optimized | 38 redb_bench | 39 redb_python.database | 40 redb_python.transaction |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 redb.sealed | ||||||||||||||||||||||||||||||||||||||||
| 2 redb.tree_store.page_store.bitmap | ||||||||||||||||||||||||||||||||||||||||
| 3 redb.types | ||||||||||||||||||||||||||||||||||||||||
| 4 redb_python.fork | ||||||||||||||||||||||||||||||||||||||||
| 5 redb.error | 4 | |||||||||||||||||||||||||||||||||||||||
| 6 redb.key_range | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 redb.legacy_types | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 redb.tree_store.page_store.buddy_allocator | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 redb.tree_store.page_store.cached_file | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 redb.tree_store.page_store.layout | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 redb.tree_store.page_store.savepoint | 2 | 2 | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||
| 12 redb_python.types | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 redb.tree_store.page_store.base | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 redb.tree_store.page_store.file_backend.range_lock | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 redb.tree_store.page_store.region | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 redb.tree_store.btree_iters | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 redb.tree_store.btree_mutator | 6 | 1 | 7 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 redb.tree_store.table_tree_base | 2 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 19 redb.tree_store.btree_cursor | 19 | 1 | 1 | 4 | 9 | 6 | ||||||||||||||||||||||||||||||||||
| 20 redb.tree_store.btree_cursor_range | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 redb.tree_store.btree | 12 | 1 | 2 | 1 | 5 | 6 | 2 | |||||||||||||||||||||||||||||||||
| 22 redb.tree_store.extract_if | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 redb.tree_store.table_tree | 4 | 3 | 1 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 24 redb.transactions | 1 | 9 | 1 | 1 | 5 | 1 | 4 | 4 | 5 | 10 | 5 | 12 | ||||||||||||||||||||||||||||
| 25 redb.table | 4 | 1 | 1 | 4 | 2 | 1 | 5 | 1 | 4 | 4 | 3 | 9 | ||||||||||||||||||||||||||||
| 26 redb.tree_store.btree_base | 13 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 27 redb.tree_store.page_store.active_transactions | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 redb.tree_store.page_store.header | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 redb_python.table | 1 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 redb.tree_store.page_store.page_manager | 1 | 4 | 1 | 10 | 2 | 1 | 3 | 2 | 3 | |||||||||||||||||||||||||||||||
| 31 redb.transaction_tracker | 3 | 4 | ||||||||||||||||||||||||||||||||||||||
| 32 redb.tree_store.multimap_btree | 2 | 3 | 1 | 4 | 3 | |||||||||||||||||||||||||||||||||||
| 33 redb.db | 9 | 1 | 2 | 1 | 12 | 6 | ||||||||||||||||||||||||||||||||||
| 34 redb.multimap_table | 3 | 6 | 2 | 3 | 1 | 5 | 5 | 6 | 9 | |||||||||||||||||||||||||||||||
| 35 redb.tree_store.page_store.backends | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 36 redb.tree_store.page_store.file_backend.fallback | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 redb.tree_store.page_store.file_backend.optimized | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 redb_bench | 2 | 4 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 39 redb_python.database | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 redb_python.transaction | 2 | 4 | 2 | 1 |
5→3 redb.error uses redb.types✕
- Connections
- 4 pairs of types, where a type in redb.error uses a type in redb.types.
- The types involved
redb.error.TableError→redb.types.TypeNameredb.error.TableTypeMismatch→redb.types.TypeNameredb.error.TypeDefinitionInfo→redb.types.TypeNameredb.error.error$module→redb.types.TypeName
- Direction
- redb.error uses redb.types, so a change to redb.types can break redb.error, while a change to redb.error can't break redb.types.
- Position
- Below the diagonal: redb.error uses a module listed above it, which is the healthy direction.
6→1 redb.key_range uses redb.sealed✕
- Connections
- 1 pair of types, where a type in redb.key_range uses a type in redb.sealed.
- The types involved
redb.key_range.KeyRange→redb.sealed.Sealed
- Direction
- redb.key_range uses redb.sealed, so a change to redb.sealed can break redb.key_range, while a change to redb.key_range can't break redb.sealed.
- Position
- Below the diagonal: redb.key_range uses a module listed above it, which is the healthy direction.
7→3 redb.legacy_types uses redb.types✕
- Connections
- 3 pairs of types, where a type in redb.legacy_types uses a type in redb.types.
- The types involved
redb.legacy_types.Legacy→redb.types.Keyredb.legacy_types.Legacy→redb.types.TypeNameredb.legacy_types.Legacy→redb.types.Value
- Direction
- redb.legacy_types uses redb.types, so a change to redb.types can break redb.legacy_types, while a change to redb.legacy_types can't break redb.types.
- Position
- Below the diagonal: redb.legacy_types uses a module listed above it, which is the healthy direction.
8→2 redb.tree_store.page_store.buddy_allocator uses redb.tree_store.page_store.bitmap✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.buddy_allocator uses a type in redb.tree_store.page_store.bitmap.
- The types involved
redb.tree_store.page_store.buddy_allocator.BuddyAllocator→redb.tree_store.page_store.bitmap.BtreeBitmap
- Direction
- redb.tree_store.page_store.buddy_allocator uses redb.tree_store.page_store.bitmap, so a change to redb.tree_store.page_store.bitmap can break redb.tree_store.page_store.buddy_allocator, while a change to redb.tree_store.page_store.buddy_allocator can't break redb.tree_store.page_store.bitmap.
- Position
- Below the diagonal: redb.tree_store.page_store.buddy_allocator uses a module listed above it, which is the healthy direction.
9→13 redb.tree_store.page_store.cached_file uses redb.tree_store.page_store.base part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.cached_file uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.page_store.cached_file.PagedCachedFile→redb.tree_store.page_store.base.PageHint
- Direction
- redb.tree_store.page_store.cached_file uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.page_store.cached_file, while a change to redb.tree_store.page_store.cached_file can't break redb.tree_store.page_store.base.
- 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.
9→31 redb.tree_store.page_store.cached_file uses redb.transaction_tracker part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.cached_file uses a type in redb.transaction_tracker.
- The types involved
redb.tree_store.page_store.cached_file.PagedCachedFile→redb.transaction_tracker.TransactionId
- Direction
- redb.tree_store.page_store.cached_file uses redb.transaction_tracker, so a change to redb.transaction_tracker can break redb.tree_store.page_store.cached_file, while a change to redb.tree_store.page_store.cached_file can't break redb.transaction_tracker.
- 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.
9→33 redb.tree_store.page_store.cached_file uses redb.db part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.cached_file uses a type in redb.db.
- The types involved
redb.tree_store.page_store.cached_file.PagedCachedFile→redb.db.CacheStats
- Direction
- redb.tree_store.page_store.cached_file uses redb.db, so a change to redb.db can break redb.tree_store.page_store.cached_file, while a change to redb.tree_store.page_store.cached_file can't break redb.db.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→25 redb.tree_store.page_store.layout uses redb.table part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.layout uses a type in redb.table.
- The types involved
redb.tree_store.page_store.layout.RegionLayout→redb.table.Range
- Direction
- redb.tree_store.page_store.layout uses redb.table, so a change to redb.table can break redb.tree_store.page_store.layout, while a change to redb.tree_store.page_store.layout can't break redb.table.
- 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→3 redb.tree_store.page_store.savepoint uses redb.types✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.page_store.savepoint uses a type in redb.types.
- The types involved
redb.tree_store.page_store.savepoint.SerializedSavepoint→redb.types.TypeNameredb.tree_store.page_store.savepoint.SerializedSavepoint→redb.types.Value
- Direction
- redb.tree_store.page_store.savepoint uses redb.types, so a change to redb.types can break redb.tree_store.page_store.savepoint, while a change to redb.tree_store.page_store.savepoint can't break redb.types.
- Position
- Below the diagonal: redb.tree_store.page_store.savepoint uses a module listed above it, which is the healthy direction.
11→26 redb.tree_store.page_store.savepoint uses redb.tree_store.btree_base part of a loop✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.page_store.savepoint uses a type in redb.tree_store.btree_base.
- The types involved
redb.tree_store.page_store.savepoint.PersistentSavepoint→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.page_store.savepoint.Savepoint→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.tree_store.page_store.savepoint uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.tree_store.page_store.savepoint, while a change to redb.tree_store.page_store.savepoint can't break redb.tree_store.btree_base.
- 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→30 redb.tree_store.page_store.savepoint uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.savepoint uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.page_store.savepoint.Savepoint→redb.tree_store.page_store.page_manager.TransactionalMemory
- Direction
- redb.tree_store.page_store.savepoint uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.page_store.savepoint, while a change to redb.tree_store.page_store.savepoint can't break redb.tree_store.page_store.page_manager.
- 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→31 redb.tree_store.page_store.savepoint uses redb.transaction_tracker part of a loop✕
- Connections
- 6 pairs of types, where a type in redb.tree_store.page_store.savepoint uses a type in redb.transaction_tracker.
- The types involved
redb.tree_store.page_store.savepoint.PersistentSavepoint→redb.transaction_tracker.SavepointIdredb.tree_store.page_store.savepoint.PersistentSavepoint→redb.transaction_tracker.TransactionIdredb.tree_store.page_store.savepoint.Savepoint→redb.transaction_tracker.LocalSavepointIdredb.tree_store.page_store.savepoint.Savepoint→redb.transaction_tracker.SavepointIdredb.tree_store.page_store.savepoint.Savepoint→redb.transaction_tracker.TransactionIdredb.tree_store.page_store.savepoint.SerializedSavepoint→redb.transaction_tracker.TransactionTracker
- Direction
- redb.tree_store.page_store.savepoint uses redb.transaction_tracker, so a change to redb.transaction_tracker can break redb.tree_store.page_store.savepoint, while a change to redb.tree_store.page_store.savepoint can't break redb.transaction_tracker.
- 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→33 redb.tree_store.page_store.savepoint uses redb.db part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.savepoint uses a type in redb.db.
- The types involved
redb.tree_store.page_store.savepoint.Savepoint→redb.db.TransactionGuard
- Direction
- redb.tree_store.page_store.savepoint uses redb.db, so a change to redb.db can break redb.tree_store.page_store.savepoint, while a change to redb.tree_store.page_store.savepoint can't break redb.db.
- 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→3 redb_python.types uses redb.types✕
- Connections
- 1 pair of types, where a type in redb_python.types uses a type in redb.types.
- The types involved
redb_python.types.PyValue→redb.types.Value
- Direction
- redb_python.types uses redb.types, so a change to redb.types can break redb_python.types, while a change to redb_python.types can't break redb.types.
- Position
- Below the diagonal: redb_python.types uses a module listed above it, which is the healthy direction.
13→9 redb.tree_store.page_store.base uses redb.tree_store.page_store.cached_file✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.base uses a type in redb.tree_store.page_store.cached_file.
- The types involved
redb.tree_store.page_store.base.PageMut→redb.tree_store.page_store.cached_file.WritablePage
- Direction
- redb.tree_store.page_store.base uses redb.tree_store.page_store.cached_file, so a change to redb.tree_store.page_store.cached_file can break redb.tree_store.page_store.base, while a change to redb.tree_store.page_store.base can't break redb.tree_store.page_store.cached_file.
- Position
- Below the diagonal: redb.tree_store.page_store.base uses a module listed above it, which is the healthy direction.
13→25 redb.tree_store.page_store.base uses redb.table part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.base uses a type in redb.table.
- The types involved
redb.tree_store.page_store.base.PageNumber→redb.table.Range
- Direction
- redb.tree_store.page_store.base uses redb.table, so a change to redb.table can break redb.tree_store.page_store.base, while a change to redb.tree_store.page_store.base can't break redb.table.
- 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→5 redb.tree_store.page_store.file_backend.range_lock uses redb.error✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.file_backend.range_lock uses a type in redb.error.
- The types involved
redb.tree_store.page_store.file_backend.range_lock.range_lock$module→redb.error.Error
- Direction
- redb.tree_store.page_store.file_backend.range_lock uses redb.error, so a change to redb.error can break redb.tree_store.page_store.file_backend.range_lock, while a change to redb.tree_store.page_store.file_backend.range_lock can't break redb.error.
- Position
- Below the diagonal: redb.tree_store.page_store.file_backend.range_lock uses a module listed above it, which is the healthy direction.
15→2 redb.tree_store.page_store.region uses redb.tree_store.page_store.bitmap✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.region uses a type in redb.tree_store.page_store.bitmap.
- The types involved
redb.tree_store.page_store.region.RegionTracker→redb.tree_store.page_store.bitmap.BtreeBitmap
- Direction
- redb.tree_store.page_store.region uses redb.tree_store.page_store.bitmap, so a change to redb.tree_store.page_store.bitmap can break redb.tree_store.page_store.region, while a change to redb.tree_store.page_store.region can't break redb.tree_store.page_store.bitmap.
- Position
- Below the diagonal: redb.tree_store.page_store.region uses a module listed above it, which is the healthy direction.
15→8 redb.tree_store.page_store.region uses redb.tree_store.page_store.buddy_allocator✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.region uses a type in redb.tree_store.page_store.buddy_allocator.
- The types involved
redb.tree_store.page_store.region.Allocators→redb.tree_store.page_store.buddy_allocator.BuddyAllocator
- Direction
- redb.tree_store.page_store.region uses redb.tree_store.page_store.buddy_allocator, so a change to redb.tree_store.page_store.buddy_allocator can break redb.tree_store.page_store.region, while a change to redb.tree_store.page_store.region can't break redb.tree_store.page_store.buddy_allocator.
- Position
- Below the diagonal: redb.tree_store.page_store.region uses a module listed above it, which is the healthy direction.
15→10 redb.tree_store.page_store.region uses redb.tree_store.page_store.layout✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.region uses a type in redb.tree_store.page_store.layout.
- The types involved
redb.tree_store.page_store.region.Allocators→redb.tree_store.page_store.layout.DatabaseLayout
- Direction
- redb.tree_store.page_store.region uses redb.tree_store.page_store.layout, so a change to redb.tree_store.page_store.layout can break redb.tree_store.page_store.region, while a change to redb.tree_store.page_store.region can't break redb.tree_store.page_store.layout.
- Position
- Below the diagonal: redb.tree_store.page_store.region uses a module listed above it, which is the healthy direction.
16→13 redb.tree_store.btree_iters uses redb.tree_store.page_store.base✕
- Connections
- 3 pairs of types, where a type in redb.tree_store.btree_iters uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.btree_iters.AllPageNumbersBtreeIter→redb.tree_store.page_store.base.PageHintredb.tree_store.btree_iters.AllPageNumbersBtreeIter→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_iters.EntryGuard→redb.tree_store.page_store.base.PageImpl
- Direction
- redb.tree_store.btree_iters uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.btree_iters, while a change to redb.tree_store.btree_iters can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.btree_iters uses a module listed above it, which is the healthy direction.
16→25 redb.tree_store.btree_iters uses redb.table part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree_iters uses a type in redb.table.
- The types involved
redb.tree_store.btree_iters.EntryGuard→redb.table.Range
- Direction
- redb.tree_store.btree_iters uses redb.table, so a change to redb.table can break redb.tree_store.btree_iters, while a change to redb.tree_store.btree_iters can't break redb.table.
- 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→30 redb.tree_store.btree_iters uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree_iters uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.btree_iters.AllPageNumbersBtreeIter→redb.tree_store.page_store.page_manager.PageResolver
- Direction
- redb.tree_store.btree_iters uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.btree_iters, while a change to redb.tree_store.btree_iters can't break redb.tree_store.page_store.page_manager.
- 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.
17→13 redb.tree_store.btree_mutator uses redb.tree_store.page_store.base✕
- Connections
- 6 pairs of types, where a type in redb.tree_store.btree_mutator uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.btree_mutator.InsertionResult→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_mutator.MutateHelper→redb.tree_store.page_store.base.PageImplredb.tree_store.btree_mutator.MutateHelper→redb.tree_store.page_store.base.PageMutredb.tree_store.btree_mutator.MutateHelper→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_mutator.MutateHelper→redb.tree_store.page_store.base.PageTrackerredb.tree_store.btree_mutator.MutateHelper→redb.tree_store.page_store.base.ScopedBorrow
- Direction
- redb.tree_store.btree_mutator uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.btree_mutator, while a change to redb.tree_store.btree_mutator can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.btree_mutator uses a module listed above it, which is the healthy direction.
17→25 redb.tree_store.btree_mutator uses redb.table part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree_mutator uses a type in redb.table.
- The types involved
redb.tree_store.btree_mutator.MutateHelper→redb.table.Range
- Direction
- redb.tree_store.btree_mutator uses redb.table, so a change to redb.table can break redb.tree_store.btree_mutator, while a change to redb.tree_store.btree_mutator can't break redb.table.
- 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.
17→26 redb.tree_store.btree_mutator uses redb.tree_store.btree_base part of a loop✕
- Connections
- 7 pairs of types, where a type in redb.tree_store.btree_mutator uses a type in redb.tree_store.btree_base.
- The types involved
redb.tree_store.btree_mutator.InsertionResult→redb.tree_store.btree_base.AccessGuardredb.tree_store.btree_mutator.InsertionResult→redb.tree_store.btree_base.AccessGuardMutInPlaceredb.tree_store.btree_mutator.MutateHelper→redb.tree_store.btree_base.BranchBuilderredb.tree_store.btree_mutator.MutateHelper→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.btree_mutator.MutateHelper→redb.tree_store.btree_base.LeafAccessorredb.tree_store.btree_mutator.MutateHelper→redb.tree_store.btree_base.LeafBuilderredb.tree_store.btree_mutator.MutateHelper→redb.tree_store.btree_base.OwnedEntryBuffer
- Direction
- redb.tree_store.btree_mutator uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.tree_store.btree_mutator, while a change to redb.tree_store.btree_mutator can't break redb.tree_store.btree_base.
- 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.
17→30 redb.tree_store.btree_mutator uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree_mutator uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.btree_mutator.MutateHelper→redb.tree_store.page_store.page_manager.PageAllocator
- Direction
- redb.tree_store.btree_mutator uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.btree_mutator, while a change to redb.tree_store.btree_mutator can't break redb.tree_store.page_store.page_manager.
- 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.
18→3 redb.tree_store.table_tree_base uses redb.types✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.table_tree_base uses a type in redb.types.
- The types involved
redb.tree_store.table_tree_base.InternalTableDefinition→redb.types.TypeNameredb.tree_store.table_tree_base.InternalTableDefinition→redb.types.Value
- Direction
- redb.tree_store.table_tree_base uses redb.types, so a change to redb.types can break redb.tree_store.table_tree_base, while a change to redb.tree_store.table_tree_base can't break redb.types.
- Position
- Below the diagonal: redb.tree_store.table_tree_base uses a module listed above it, which is the healthy direction.
18→13 redb.tree_store.table_tree_base uses redb.tree_store.page_store.base✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.table_tree_base uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.table_tree_base.InternalTableDefinition→redb.tree_store.page_store.base.PageHintredb.tree_store.table_tree_base.InternalTableDefinition→redb.tree_store.page_store.base.PageNumber
- Direction
- redb.tree_store.table_tree_base uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.table_tree_base, while a change to redb.tree_store.table_tree_base can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.table_tree_base uses a module listed above it, which is the healthy direction.
18→26 redb.tree_store.table_tree_base uses redb.tree_store.btree_base part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.table_tree_base uses a type in redb.tree_store.btree_base.
- The types involved
redb.tree_store.table_tree_base.InternalTableDefinition→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.tree_store.table_tree_base uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.tree_store.table_tree_base, while a change to redb.tree_store.table_tree_base can't break redb.tree_store.btree_base.
- 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.
18→30 redb.tree_store.table_tree_base uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.table_tree_base uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.table_tree_base.InternalTableDefinition→redb.tree_store.page_store.page_manager.PageAllocatorredb.tree_store.table_tree_base.InternalTableDefinition→redb.tree_store.page_store.page_manager.PageResolver
- Direction
- redb.tree_store.table_tree_base uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.table_tree_base, while a change to redb.tree_store.table_tree_base can't break redb.tree_store.page_store.page_manager.
- 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→13 redb.tree_store.btree_cursor uses redb.tree_store.page_store.base✕
- Connections
- 19 pairs of types, where a type in redb.tree_store.btree_cursor uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.btree_cursor.Branch→redb.tree_store.page_store.base.PageImplredb.tree_store.btree_cursor.BtreeCursor→redb.tree_store.page_store.base.PageHintredb.tree_store.btree_cursor.BtreeCursorMut→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_cursor.BtreeCursorMut→redb.tree_store.page_store.base.PageTrackerredb.tree_store.btree_cursor.Cursor→redb.tree_store.page_store.base.PageHintredb.tree_store.btree_cursor.Cursor→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_cursor.CursorMut→redb.tree_store.page_store.base.PageImplredb.tree_store.btree_cursor.CursorMut→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_cursor.CursorMut→redb.tree_store.page_store.base.PageTrackerredb.tree_store.btree_cursor.CursorMut→redb.tree_store.page_store.base.ScopedBorrowredb.tree_store.btree_cursor.CursorTree→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_cursor.CursorTree→redb.tree_store.page_store.base.PageTrackerredb.tree_store.btree_cursor.EntryRef→redb.tree_store.page_store.base.PageImplredb.tree_store.btree_cursor.Leaf→redb.tree_store.page_store.base.PageImplredb.tree_store.btree_cursor.LeafRunRewrite→redb.tree_store.page_store.base.PageImplredb.tree_store.btree_cursor.LeafRunRewrite→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_cursor.RangeMut→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_cursor.RangeMut→redb.tree_store.page_store.base.PageTrackerredb.tree_store.btree_cursor.btree_cursor$module→redb.tree_store.page_store.base.PageImpl
- Direction
- redb.tree_store.btree_cursor uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.btree_cursor, while a change to redb.tree_store.btree_cursor can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.btree_cursor uses a module listed above it, which is the healthy direction.
19→16 redb.tree_store.btree_cursor uses redb.tree_store.btree_iters✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree_cursor uses a type in redb.tree_store.btree_iters.
- The types involved
redb.tree_store.btree_cursor.btree_cursor$module→redb.tree_store.btree_iters.EntryGuard
- Direction
- redb.tree_store.btree_cursor uses redb.tree_store.btree_iters, so a change to redb.tree_store.btree_iters can break redb.tree_store.btree_cursor, while a change to redb.tree_store.btree_cursor can't break redb.tree_store.btree_iters.
- Position
- Below the diagonal: redb.tree_store.btree_cursor uses a module listed above it, which is the healthy direction.
19→17 redb.tree_store.btree_cursor uses redb.tree_store.btree_mutator✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree_cursor uses a type in redb.tree_store.btree_mutator.
- The types involved
redb.tree_store.btree_cursor.CursorMut→redb.tree_store.btree_mutator.MutateHelper
- Direction
- redb.tree_store.btree_cursor uses redb.tree_store.btree_mutator, so a change to redb.tree_store.btree_mutator can break redb.tree_store.btree_cursor, while a change to redb.tree_store.btree_cursor can't break redb.tree_store.btree_mutator.
- Position
- Below the diagonal: redb.tree_store.btree_cursor uses a module listed above it, which is the healthy direction.
19→25 redb.tree_store.btree_cursor uses redb.table part of a loop✕
- Connections
- 4 pairs of types, where a type in redb.tree_store.btree_cursor uses a type in redb.table.
- The types involved
redb.tree_store.btree_cursor.BtreeCursor→redb.table.Cursorredb.tree_store.btree_cursor.CursorTree→redb.table.CursorMutredb.tree_store.btree_cursor.EntryRef→redb.table.Rangeredb.tree_store.btree_cursor.LeafRunRewrite→redb.table.Range
- Direction
- redb.tree_store.btree_cursor uses redb.table, so a change to redb.table can break redb.tree_store.btree_cursor, while a change to redb.tree_store.btree_cursor can't break redb.table.
- 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→26 redb.tree_store.btree_cursor uses redb.tree_store.btree_base part of a loop✕
- Connections
- 9 pairs of types, where a type in redb.tree_store.btree_cursor uses a type in redb.tree_store.btree_base.
- The types involved
redb.tree_store.btree_cursor.BtreeCursor→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.btree_cursor.BtreeCursorMut→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.btree_cursor.CursorMut→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.btree_cursor.CursorTree→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.btree_cursor.InsertRun→redb.tree_store.btree_base.OwnedEntryBufferredb.tree_store.btree_cursor.LeafRunRewrite→redb.tree_store.btree_base.OwnedEntryBufferredb.tree_store.btree_cursor.RangeMut→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.btree_cursor.btree_cursor$module→redb.tree_store.btree_base.BranchAccessorredb.tree_store.btree_cursor.btree_cursor$module→redb.tree_store.btree_base.LeafAccessor
- Direction
- redb.tree_store.btree_cursor uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.tree_store.btree_cursor, while a change to redb.tree_store.btree_cursor can't break redb.tree_store.btree_base.
- 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→30 redb.tree_store.btree_cursor uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 6 pairs of types, where a type in redb.tree_store.btree_cursor uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.btree_cursor.BtreeCursor→redb.tree_store.page_store.page_manager.PageResolverredb.tree_store.btree_cursor.BtreeCursorMut→redb.tree_store.page_store.page_manager.PageAllocatorredb.tree_store.btree_cursor.Cursor→redb.tree_store.page_store.page_manager.PageResolverredb.tree_store.btree_cursor.CursorMut→redb.tree_store.page_store.page_manager.PageAllocatorredb.tree_store.btree_cursor.CursorTree→redb.tree_store.page_store.page_manager.PageAllocatorredb.tree_store.btree_cursor.RangeMut→redb.tree_store.page_store.page_manager.PageAllocator
- Direction
- redb.tree_store.btree_cursor uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.btree_cursor, while a change to redb.tree_store.btree_cursor can't break redb.tree_store.page_store.page_manager.
- 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→13 redb.tree_store.btree_cursor_range uses redb.tree_store.page_store.base✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.btree_cursor_range uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.btree_cursor_range.BtreeCursorRange→redb.tree_store.page_store.base.PageHintredb.tree_store.btree_cursor_range.BtreeCursorRange→redb.tree_store.page_store.base.PageNumber
- Direction
- redb.tree_store.btree_cursor_range uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.btree_cursor_range, while a change to redb.tree_store.btree_cursor_range can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.btree_cursor_range uses a module listed above it, which is the healthy direction.
20→16 redb.tree_store.btree_cursor_range uses redb.tree_store.btree_iters✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree_cursor_range uses a type in redb.tree_store.btree_iters.
- The types involved
redb.tree_store.btree_cursor_range.BtreeCursorRange→redb.tree_store.btree_iters.EntryGuard
- Direction
- redb.tree_store.btree_cursor_range uses redb.tree_store.btree_iters, so a change to redb.tree_store.btree_iters can break redb.tree_store.btree_cursor_range, while a change to redb.tree_store.btree_cursor_range can't break redb.tree_store.btree_iters.
- Position
- Below the diagonal: redb.tree_store.btree_cursor_range uses a module listed above it, which is the healthy direction.
20→25 redb.tree_store.btree_cursor_range uses redb.table part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree_cursor_range uses a type in redb.table.
- The types involved
redb.tree_store.btree_cursor_range.BtreeCursorRange→redb.table.Cursor
- Direction
- redb.tree_store.btree_cursor_range uses redb.table, so a change to redb.table can break redb.tree_store.btree_cursor_range, while a change to redb.tree_store.btree_cursor_range can't break redb.table.
- 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→30 redb.tree_store.btree_cursor_range uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree_cursor_range uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.btree_cursor_range.BtreeCursorRange→redb.tree_store.page_store.page_manager.PageResolver
- Direction
- redb.tree_store.btree_cursor_range uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.btree_cursor_range, while a change to redb.tree_store.btree_cursor_range can't break redb.tree_store.page_store.page_manager.
- 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.
21→13 redb.tree_store.btree uses redb.tree_store.page_store.base✕
- Connections
- 12 pairs of types, where a type in redb.tree_store.btree uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.btree.Btree→redb.tree_store.page_store.base.PageHintredb.tree_store.btree.Btree→redb.tree_store.page_store.base.PageImplredb.tree_store.btree.BtreeMut→redb.tree_store.page_store.base.PageMutredb.tree_store.btree.BtreeMut→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree.BtreeMut→redb.tree_store.page_store.base.PageTrackerredb.tree_store.btree.PagePath→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree.RawBtree→redb.tree_store.page_store.base.PageHintredb.tree_store.btree.RawBtree→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree.UntypedBtree→redb.tree_store.page_store.base.PageHintredb.tree_store.btree.UntypedBtreeMut→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree.btree$module→redb.tree_store.page_store.base.PageHintredb.tree_store.btree.btree$module→redb.tree_store.page_store.base.PageNumber
- Direction
- redb.tree_store.btree uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.btree, while a change to redb.tree_store.btree can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.btree uses a module listed above it, which is the healthy direction.
21→16 redb.tree_store.btree uses redb.tree_store.btree_iters✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree uses a type in redb.tree_store.btree_iters.
- The types involved
redb.tree_store.btree.BtreeMut→redb.tree_store.btree_iters.AllPageNumbersBtreeIter
- Direction
- redb.tree_store.btree uses redb.tree_store.btree_iters, so a change to redb.tree_store.btree_iters can break redb.tree_store.btree, while a change to redb.tree_store.btree can't break redb.tree_store.btree_iters.
- Position
- Below the diagonal: redb.tree_store.btree uses a module listed above it, which is the healthy direction.
21→19 redb.tree_store.btree uses redb.tree_store.btree_cursor✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.btree uses a type in redb.tree_store.btree_cursor.
- The types involved
redb.tree_store.btree.Btree→redb.tree_store.btree_cursor.BtreeCursorredb.tree_store.btree.BtreeMut→redb.tree_store.btree_cursor.BtreeCursorMut
- Direction
- redb.tree_store.btree uses redb.tree_store.btree_cursor, so a change to redb.tree_store.btree_cursor can break redb.tree_store.btree, while a change to redb.tree_store.btree can't break redb.tree_store.btree_cursor.
- Position
- Below the diagonal: redb.tree_store.btree uses a module listed above it, which is the healthy direction.
21→25 redb.tree_store.btree uses redb.table part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.btree uses a type in redb.table.
- The types involved
redb.tree_store.btree.BtreeMut→redb.table.CursorMut
- Direction
- redb.tree_store.btree uses redb.table, so a change to redb.table can break redb.tree_store.btree, while a change to redb.tree_store.btree can't break redb.table.
- 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.
21→26 redb.tree_store.btree uses redb.tree_store.btree_base part of a loop✕
- Connections
- 5 pairs of types, where a type in redb.tree_store.btree uses a type in redb.tree_store.btree_base.
- The types involved
redb.tree_store.btree.Btree→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.btree.BtreeMut→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.btree.RawBtree→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.btree.UntypedBtree→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.btree.UntypedBtreeMut→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.tree_store.btree uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.tree_store.btree, while a change to redb.tree_store.btree can't break redb.tree_store.btree_base.
- 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.
21→30 redb.tree_store.btree uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 6 pairs of types, where a type in redb.tree_store.btree uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.btree.Btree→redb.tree_store.page_store.page_manager.PageResolverredb.tree_store.btree.BtreeMut→redb.tree_store.page_store.page_manager.PageAllocatorredb.tree_store.btree.RawBtree→redb.tree_store.page_store.page_manager.PageResolverredb.tree_store.btree.UntypedBtree→redb.tree_store.page_store.page_manager.PageResolverredb.tree_store.btree.UntypedBtreeMut→redb.tree_store.page_store.page_manager.PageAllocatorredb.tree_store.btree.btree$module→redb.tree_store.page_store.page_manager.PageResolver
- Direction
- redb.tree_store.btree uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.btree, while a change to redb.tree_store.btree can't break redb.tree_store.page_store.page_manager.
- 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.
21→33 redb.tree_store.btree uses redb.db part of a loop✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.btree uses a type in redb.db.
- The types involved
redb.tree_store.btree.Btree→redb.db.TransactionGuardredb.tree_store.btree.BtreeMut→redb.db.TransactionGuard
- Direction
- redb.tree_store.btree uses redb.db, so a change to redb.db can break redb.tree_store.btree, while a change to redb.tree_store.btree can't break redb.db.
- 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→13 redb.tree_store.extract_if uses redb.tree_store.page_store.base✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.extract_if uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.extract_if.BtreeExtractIf→redb.tree_store.page_store.base.PageNumberredb.tree_store.extract_if.BtreeExtractIf→redb.tree_store.page_store.base.PageTracker
- Direction
- redb.tree_store.extract_if uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.extract_if, while a change to redb.tree_store.extract_if can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.extract_if uses a module listed above it, which is the healthy direction.
22→19 redb.tree_store.extract_if uses redb.tree_store.btree_cursor✕
- Connections
- 1 pair of types, where a type in redb.tree_store.extract_if uses a type in redb.tree_store.btree_cursor.
- The types involved
redb.tree_store.extract_if.BtreeExtractIf→redb.tree_store.btree_cursor.RangeMut
- Direction
- redb.tree_store.extract_if uses redb.tree_store.btree_cursor, so a change to redb.tree_store.btree_cursor can break redb.tree_store.extract_if, while a change to redb.tree_store.extract_if can't break redb.tree_store.btree_cursor.
- Position
- Below the diagonal: redb.tree_store.extract_if uses a module listed above it, which is the healthy direction.
22→26 redb.tree_store.extract_if uses redb.tree_store.btree_base part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.extract_if uses a type in redb.tree_store.btree_base.
- The types involved
redb.tree_store.extract_if.BtreeExtractIf→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.tree_store.extract_if uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.tree_store.extract_if, while a change to redb.tree_store.extract_if can't break redb.tree_store.btree_base.
- 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→30 redb.tree_store.extract_if uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 1 pair of types, where a type in redb.tree_store.extract_if uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.extract_if.BtreeExtractIf→redb.tree_store.page_store.page_manager.PageAllocator
- Direction
- redb.tree_store.extract_if uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.extract_if, while a change to redb.tree_store.extract_if can't break redb.tree_store.page_store.page_manager.
- 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→13 redb.tree_store.table_tree uses redb.tree_store.page_store.base✕
- Connections
- 4 pairs of types, where a type in redb.tree_store.table_tree uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.table_tree.PageListMut→redb.tree_store.page_store.base.PageNumberredb.tree_store.table_tree.TableTree→redb.tree_store.page_store.base.PageHintredb.tree_store.table_tree.TableTreeMut→redb.tree_store.page_store.base.PageNumberredb.tree_store.table_tree.TableTreeMut→redb.tree_store.page_store.base.PageTracker
- Direction
- redb.tree_store.table_tree uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.table_tree, while a change to redb.tree_store.table_tree can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.table_tree uses a module listed above it, which is the healthy direction.
23→18 redb.tree_store.table_tree uses redb.tree_store.table_tree_base✕
- Connections
- 3 pairs of types, where a type in redb.tree_store.table_tree uses a type in redb.tree_store.table_tree_base.
- The types involved
redb.tree_store.table_tree.TableNameIter→redb.tree_store.table_tree_base.TableTyperedb.tree_store.table_tree.TableTree→redb.tree_store.table_tree_base.TableTyperedb.tree_store.table_tree.TableTreeMut→redb.tree_store.table_tree_base.TableType
- Direction
- redb.tree_store.table_tree uses redb.tree_store.table_tree_base, so a change to redb.tree_store.table_tree_base can break redb.tree_store.table_tree, while a change to redb.tree_store.table_tree can't break redb.tree_store.table_tree_base.
- Position
- Below the diagonal: redb.tree_store.table_tree uses a module listed above it, which is the healthy direction.
23→20 redb.tree_store.table_tree uses redb.tree_store.btree_cursor_range✕
- Connections
- 1 pair of types, where a type in redb.tree_store.table_tree uses a type in redb.tree_store.btree_cursor_range.
- The types involved
redb.tree_store.table_tree.TableNameIter→redb.tree_store.btree_cursor_range.BtreeCursorRange
- Direction
- redb.tree_store.table_tree uses redb.tree_store.btree_cursor_range, so a change to redb.tree_store.btree_cursor_range can break redb.tree_store.table_tree, while a change to redb.tree_store.table_tree can't break redb.tree_store.btree_cursor_range.
- Position
- Below the diagonal: redb.tree_store.table_tree uses a module listed above it, which is the healthy direction.
23→21 redb.tree_store.table_tree uses redb.tree_store.btree✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.table_tree uses a type in redb.tree_store.btree.
- The types involved
redb.tree_store.table_tree.TableTree→redb.tree_store.btree.Btreeredb.tree_store.table_tree.TableTreeMut→redb.tree_store.btree.BtreeMut
- Direction
- redb.tree_store.table_tree uses redb.tree_store.btree, so a change to redb.tree_store.btree can break redb.tree_store.table_tree, while a change to redb.tree_store.table_tree can't break redb.tree_store.btree.
- Position
- Below the diagonal: redb.tree_store.table_tree uses a module listed above it, which is the healthy direction.
23→26 redb.tree_store.table_tree uses redb.tree_store.btree_base part of a loop✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.table_tree uses a type in redb.tree_store.btree_base.
- The types involved
redb.tree_store.table_tree.TableTree→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.table_tree.TableTreeMut→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.tree_store.table_tree uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.tree_store.table_tree, while a change to redb.tree_store.table_tree can't break redb.tree_store.btree_base.
- 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→30 redb.tree_store.table_tree uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.table_tree uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.table_tree.TableTree→redb.tree_store.page_store.page_manager.PageResolverredb.tree_store.table_tree.TableTreeMut→redb.tree_store.page_store.page_manager.PageAllocator
- Direction
- redb.tree_store.table_tree uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.table_tree, while a change to redb.tree_store.table_tree can't break redb.tree_store.page_store.page_manager.
- 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→33 redb.tree_store.table_tree uses redb.db part of a loop✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.table_tree uses a type in redb.db.
- The types involved
redb.tree_store.table_tree.TableTree→redb.db.TransactionGuardredb.tree_store.table_tree.TableTreeMut→redb.db.TransactionGuard
- Direction
- redb.tree_store.table_tree uses redb.db, so a change to redb.db can break redb.tree_store.table_tree, while a change to redb.tree_store.table_tree can't break redb.db.
- 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.
24→1 redb.transactions uses redb.sealed✕
- Connections
- 1 pair of types, where a type in redb.transactions uses a type in redb.sealed.
- The types involved
redb.transactions.SystemTableDefinition→redb.sealed.Sealed
- Direction
- redb.transactions uses redb.sealed, so a change to redb.sealed can break redb.transactions, while a change to redb.transactions can't break redb.sealed.
- Position
- Below the diagonal: redb.transactions uses a module listed above it, which is the healthy direction.
24→3 redb.transactions uses redb.types✕
- Connections
- 9 pairs of types, where a type in redb.transactions uses a type in redb.types.
- The types involved
redb.transactions.AllocatorStateKey→redb.types.Keyredb.transactions.AllocatorStateKey→redb.types.TypeNameredb.transactions.AllocatorStateKey→redb.types.Valueredb.transactions.PageList→redb.types.MutInPlaceValueredb.transactions.PageList→redb.types.TypeNameredb.transactions.PageList→redb.types.Valueredb.transactions.TransactionIdWithPagination→redb.types.Keyredb.transactions.TransactionIdWithPagination→redb.types.TypeNameredb.transactions.TransactionIdWithPagination→redb.types.Value
- Direction
- redb.transactions uses redb.types, so a change to redb.types can break redb.transactions, while a change to redb.transactions can't break redb.types.
- Position
- Below the diagonal: redb.transactions uses a module listed above it, which is the healthy direction.
24→10 redb.transactions uses redb.tree_store.page_store.layout✕
- Connections
- 1 pair of types, where a type in redb.transactions uses a type in redb.tree_store.page_store.layout.
- The types involved
redb.transactions.WriteTransaction→redb.tree_store.page_store.layout.DatabaseLayout
- Direction
- redb.transactions uses redb.tree_store.page_store.layout, so a change to redb.tree_store.page_store.layout can break redb.transactions, while a change to redb.transactions can't break redb.tree_store.page_store.layout.
- Position
- Below the diagonal: redb.transactions uses a module listed above it, which is the healthy direction.
24→11 redb.transactions uses redb.tree_store.page_store.savepoint✕
- Connections
- 1 pair of types, where a type in redb.transactions uses a type in redb.tree_store.page_store.savepoint.
- The types involved
redb.transactions.WriteTransaction→redb.tree_store.page_store.savepoint.Savepoint
- Direction
- redb.transactions uses redb.tree_store.page_store.savepoint, so a change to redb.tree_store.page_store.savepoint can break redb.transactions, while a change to redb.transactions can't break redb.tree_store.page_store.savepoint.
- Position
- Below the diagonal: redb.transactions uses a module listed above it, which is the healthy direction.
24→13 redb.transactions uses redb.tree_store.page_store.base✕
- Connections
- 5 pairs of types, where a type in redb.transactions uses a type in redb.tree_store.page_store.base.
- The types involved
redb.transactions.SystemNamespace→redb.tree_store.page_store.base.PageNumberredb.transactions.SystemTable→redb.tree_store.page_store.base.PageNumberredb.transactions.TableNamespace→redb.tree_store.page_store.base.PageNumberredb.transactions.TableNamespace→redb.tree_store.page_store.base.PageTrackerredb.transactions.WriteTransaction→redb.tree_store.page_store.base.PageNumber
- Direction
- redb.transactions uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.transactions, while a change to redb.transactions can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.transactions uses a module listed above it, which is the healthy direction.
24→18 redb.transactions uses redb.tree_store.table_tree_base✕
- Connections
- 1 pair of types, where a type in redb.transactions uses a type in redb.tree_store.table_tree_base.
- The types involved
redb.transactions.TableNamespace→redb.tree_store.table_tree_base.TableType
- Direction
- redb.transactions uses redb.tree_store.table_tree_base, so a change to redb.tree_store.table_tree_base can break redb.transactions, while a change to redb.transactions can't break redb.tree_store.table_tree_base.
- Position
- Below the diagonal: redb.transactions uses a module listed above it, which is the healthy direction.
24→21 redb.transactions uses redb.tree_store.btree✕
- Connections
- 4 pairs of types, where a type in redb.transactions uses a type in redb.tree_store.btree.
- The types involved
redb.transactions.SystemNamespace→redb.tree_store.btree.BtreeMutredb.transactions.SystemTable→redb.tree_store.btree.BtreeMutredb.transactions.TableNamespace→redb.tree_store.btree.BtreeMutredb.transactions.WriteTransaction→redb.tree_store.btree.BtreeMut
- Direction
- redb.transactions uses redb.tree_store.btree, so a change to redb.tree_store.btree can break redb.transactions, while a change to redb.transactions can't break redb.tree_store.btree.
- Position
- Below the diagonal: redb.transactions uses a module listed above it, which is the healthy direction.
24→23 redb.transactions uses redb.tree_store.table_tree✕
- Connections
- 4 pairs of types, where a type in redb.transactions uses a type in redb.tree_store.table_tree.
- The types involved
redb.transactions.ReadTransaction→redb.tree_store.table_tree.TableTreeredb.transactions.SystemNamespace→redb.tree_store.table_tree.TableTreeMutredb.transactions.TableNamespace→redb.tree_store.table_tree.TableTreeMutredb.transactions.WriteTransaction→redb.tree_store.table_tree.TableTreeMut
- Direction
- redb.transactions uses redb.tree_store.table_tree, so a change to redb.tree_store.table_tree can break redb.transactions, while a change to redb.transactions can't break redb.tree_store.table_tree.
- Position
- Below the diagonal: redb.transactions uses a module listed above it, which is the healthy direction.
24→26 redb.transactions uses redb.tree_store.btree_base part of a loop✕
- Connections
- 5 pairs of types, where a type in redb.transactions uses a type in redb.tree_store.btree_base.
- The types involved
redb.transactions.ReadTransaction→redb.tree_store.btree_base.BtreeHeaderredb.transactions.SystemNamespace→redb.tree_store.btree_base.BtreeHeaderredb.transactions.SystemTable→redb.tree_store.btree_base.BtreeHeaderredb.transactions.TableNamespace→redb.tree_store.btree_base.BtreeHeaderredb.transactions.WriteTransaction→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.transactions uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.transactions, while a change to redb.transactions can't break redb.tree_store.btree_base.
- 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.
24→30 redb.transactions uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 10 pairs of types, where a type in redb.transactions uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.transactions.AllocatorStateLatch→redb.tree_store.page_store.page_manager.TransactionalMemoryredb.transactions.ReadTransaction→redb.tree_store.page_store.page_manager.TransactionalMemoryredb.transactions.SystemNamespace→redb.tree_store.page_store.page_manager.PageAllocatorredb.transactions.SystemTable→redb.tree_store.page_store.page_manager.PageAllocatorredb.transactions.TableNamespace→redb.tree_store.page_store.page_manager.PageAllocatorredb.transactions.WriteTransaction→redb.tree_store.page_store.page_manager.AllocationPolicyredb.transactions.WriteTransaction→redb.tree_store.page_store.page_manager.HeaderGuardredb.transactions.WriteTransaction→redb.tree_store.page_store.page_manager.PageAllocatorredb.transactions.WriteTransaction→redb.tree_store.page_store.page_manager.ShrinkPolicyredb.transactions.WriteTransaction→redb.tree_store.page_store.page_manager.TransactionalMemory
- Direction
- redb.transactions uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.transactions, while a change to redb.transactions can't break redb.tree_store.page_store.page_manager.
- 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.
24→31 redb.transactions uses redb.transaction_tracker part of a loop✕
- Connections
- 5 pairs of types, where a type in redb.transactions uses a type in redb.transaction_tracker.
- The types involved
redb.transactions.SavepointTransactionState→redb.transaction_tracker.SavepointIdredb.transactions.SavepointTransactionState→redb.transaction_tracker.TransactionIdredb.transactions.SavepointTransactionState→redb.transaction_tracker.TransactionTrackerredb.transactions.WriteTransaction→redb.transaction_tracker.TransactionIdredb.transactions.WriteTransaction→redb.transaction_tracker.TransactionTracker
- Direction
- redb.transactions uses redb.transaction_tracker, so a change to redb.transaction_tracker can break redb.transactions, while a change to redb.transactions can't break redb.transaction_tracker.
- 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.
24→33 redb.transactions uses redb.db part of a loop✕
- Connections
- 12 pairs of types, where a type in redb.transactions uses a type in redb.db.
- The types involved
redb.transactions.ReadTransaction→redb.db.MultimapTableDefinitionredb.transactions.ReadTransaction→redb.db.TableDefinitionredb.transactions.ReadTransaction→redb.db.TransactionGuardredb.transactions.SystemNamespace→redb.db.TransactionGuardredb.transactions.SystemTable→redb.db.TransactionGuardredb.transactions.SystemTableDefinition→redb.db.TableHandleredb.transactions.TableNamespace→redb.db.MultimapTableDefinitionredb.transactions.TableNamespace→redb.db.TableDefinitionredb.transactions.TableNamespace→redb.db.TransactionGuardredb.transactions.WriteTransaction→redb.db.MultimapTableDefinitionredb.transactions.WriteTransaction→redb.db.TableDefinitionredb.transactions.WriteTransaction→redb.db.TransactionGuard
- Direction
- redb.transactions uses redb.db, so a change to redb.db can break redb.transactions, while a change to redb.transactions can't break redb.db.
- 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.
25→1 redb.table uses redb.sealed✕
- Connections
- 4 pairs of types, where a type in redb.table uses a type in redb.sealed.
- The types involved
redb.table.Range→redb.sealed.Sealedredb.table.ReadOnlyTable→redb.sealed.Sealedredb.table.ReadOnlyUntypedTable→redb.sealed.Sealedredb.table.Table→redb.sealed.Sealed
- Direction
- redb.table uses redb.sealed, so a change to redb.sealed can break redb.table, while a change to redb.table can't break redb.sealed.
- Position
- Below the diagonal: redb.table uses a module listed above it, which is the healthy direction.
25→5 redb.table uses redb.error✕
- Connections
- 1 pair of types, where a type in redb.table uses a type in redb.error.
- The types involved
redb.table.CursorMut→redb.error.StorageError
- Direction
- redb.table uses redb.error, so a change to redb.error can break redb.table, while a change to redb.table can't break redb.error.
- Position
- Below the diagonal: redb.table uses a module listed above it, which is the healthy direction.
25→6 redb.table uses redb.key_range✕
- Connections
- 1 pair of types, where a type in redb.table uses a type in redb.key_range.
- The types involved
redb.table.Range→redb.key_range.KeyRange
- Direction
- redb.table uses redb.key_range, so a change to redb.key_range can break redb.table, while a change to redb.table can't break redb.key_range.
- Position
- Below the diagonal: redb.table uses a module listed above it, which is the healthy direction.
25→13 redb.table uses redb.tree_store.page_store.base✕
- Connections
- 4 pairs of types, where a type in redb.table uses a type in redb.tree_store.page_store.base.
- The types involved
redb.table.Cursor→redb.tree_store.page_store.base.ScopedBorrowredb.table.ReadOnlyTable→redb.tree_store.page_store.base.PageHintredb.table.Table→redb.tree_store.page_store.base.PageNumberredb.table.Table→redb.tree_store.page_store.base.PageTracker
- Direction
- redb.table uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.table, while a change to redb.table can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.table uses a module listed above it, which is the healthy direction.
25→19 redb.table uses redb.tree_store.btree_cursor✕
- Connections
- 2 pairs of types, where a type in redb.table uses a type in redb.tree_store.btree_cursor.
- The types involved
redb.table.Cursor→redb.tree_store.btree_cursor.BtreeCursorredb.table.CursorMut→redb.tree_store.btree_cursor.BtreeCursorMut
- Direction
- redb.table uses redb.tree_store.btree_cursor, so a change to redb.tree_store.btree_cursor can break redb.table, while a change to redb.table can't break redb.tree_store.btree_cursor.
- Position
- Below the diagonal: redb.table uses a module listed above it, which is the healthy direction.
25→20 redb.table uses redb.tree_store.btree_cursor_range✕
- Connections
- 1 pair of types, where a type in redb.table uses a type in redb.tree_store.btree_cursor_range.
- The types involved
redb.table.Range→redb.tree_store.btree_cursor_range.BtreeCursorRange
- Direction
- redb.table uses redb.tree_store.btree_cursor_range, so a change to redb.tree_store.btree_cursor_range can break redb.table, while a change to redb.table can't break redb.tree_store.btree_cursor_range.
- Position
- Below the diagonal: redb.table uses a module listed above it, which is the healthy direction.
25→21 redb.table uses redb.tree_store.btree✕
- Connections
- 5 pairs of types, where a type in redb.table uses a type in redb.tree_store.btree.
- The types involved
redb.table.OccupiedEntry→redb.tree_store.btree.BtreeMutredb.table.ReadOnlyTable→redb.tree_store.btree.Btreeredb.table.ReadOnlyUntypedTable→redb.tree_store.btree.RawBtreeredb.table.Table→redb.tree_store.btree.BtreeMutredb.table.VacantEntry→redb.tree_store.btree.BtreeMut
- Direction
- redb.table uses redb.tree_store.btree, so a change to redb.tree_store.btree can break redb.table, while a change to redb.table can't break redb.tree_store.btree.
- Position
- Below the diagonal: redb.table uses a module listed above it, which is the healthy direction.
25→22 redb.table uses redb.tree_store.extract_if✕
- Connections
- 1 pair of types, where a type in redb.table uses a type in redb.tree_store.extract_if.
- The types involved
redb.table.ExtractIf→redb.tree_store.extract_if.BtreeExtractIf
- Direction
- redb.table uses redb.tree_store.extract_if, so a change to redb.tree_store.extract_if can break redb.table, while a change to redb.table can't break redb.tree_store.extract_if.
- Position
- Below the diagonal: redb.table uses a module listed above it, which is the healthy direction.
25→24 redb.table uses redb.transactions✕
- Connections
- 4 pairs of types, where a type in redb.table uses a type in redb.transactions.
- The types involved
redb.table.CursorMut→redb.transactions.WriteTransactionredb.table.ExtractIf→redb.transactions.WriteTransactionredb.table.PanicGuard→redb.transactions.WriteTransactionredb.table.Table→redb.transactions.WriteTransaction
- Direction
- redb.table uses redb.transactions, so a change to redb.transactions can break redb.table, while a change to redb.table can't break redb.transactions.
- Position
- Below the diagonal: redb.table uses a module listed above it, which is the healthy direction.
25→26 redb.table uses redb.tree_store.btree_base part of a loop✕
- Connections
- 4 pairs of types, where a type in redb.table uses a type in redb.tree_store.btree_base.
- The types involved
redb.table.OwnedAccessGuard→redb.tree_store.btree_base.AccessGuardredb.table.ReadOnlyTable→redb.tree_store.btree_base.BtreeHeaderredb.table.ReadOnlyUntypedTable→redb.tree_store.btree_base.BtreeHeaderredb.table.Table→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.table uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.table, while a change to redb.table can't break redb.tree_store.btree_base.
- 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.
25→30 redb.table uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 3 pairs of types, where a type in redb.table uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.table.ReadOnlyTable→redb.tree_store.page_store.page_manager.PageResolverredb.table.ReadOnlyUntypedTable→redb.tree_store.page_store.page_manager.PageResolverredb.table.Table→redb.tree_store.page_store.page_manager.PageAllocator
- Direction
- redb.table uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.table, while a change to redb.table can't break redb.tree_store.page_store.page_manager.
- 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.
25→33 redb.table uses redb.db part of a loop✕
- Connections
- 9 pairs of types, where a type in redb.table uses a type in redb.db.
- The types involved
redb.table.Cursor→redb.db.TransactionGuardredb.table.OwnedAccessGuard→redb.db.TransactionGuardredb.table.OwnedRange→redb.db.TransactionGuardredb.table.Range→redb.db.TransactionGuardredb.table.ReadOnlyTable→redb.db.TableHandleredb.table.ReadOnlyTable→redb.db.TransactionGuardredb.table.ReadOnlyUntypedTable→redb.db.TableHandleredb.table.ReadOnlyUntypedTable→redb.db.TransactionGuardredb.table.Table→redb.db.TableHandle
- Direction
- redb.table uses redb.db, so a change to redb.db can break redb.table, while a change to redb.table can't break redb.db.
- 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.
26→13 redb.tree_store.btree_base uses redb.tree_store.page_store.base✕
- Connections
- 13 pairs of types, where a type in redb.tree_store.btree_base uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.btree_base.AccessGuard→redb.tree_store.page_store.base.PageImplredb.tree_store.btree_base.AccessGuard→redb.tree_store.page_store.base.PageMutredb.tree_store.btree_base.AccessGuardMut→redb.tree_store.page_store.base.PageMutredb.tree_store.btree_base.AccessGuardMut→redb.tree_store.page_store.base.PageTrackerredb.tree_store.btree_base.AccessGuardMutInPlace→redb.tree_store.page_store.base.PageMutredb.tree_store.btree_base.BranchAccessor→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_base.BranchBuilder→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_base.BranchBuilder→redb.tree_store.page_store.base.PageTrackerredb.tree_store.btree_base.BranchMutator→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_base.BtreeHeader→redb.tree_store.page_store.base.PageNumberredb.tree_store.btree_base.LeafBuilder→redb.tree_store.page_store.base.PageTrackerredb.tree_store.btree_base.LeafPageMut→redb.tree_store.page_store.base.PageMutredb.tree_store.btree_base.RawBranchBuilder→redb.tree_store.page_store.base.PageNumber
- Direction
- redb.tree_store.btree_base uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.btree_base, while a change to redb.tree_store.btree_base can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.btree_base uses a module listed above it, which is the healthy direction.
26→25 redb.tree_store.btree_base uses redb.table✕
- Connections
- 3 pairs of types, where a type in redb.tree_store.btree_base uses a type in redb.table.
- The types involved
redb.tree_store.btree_base.AccessGuard→redb.table.Rangeredb.tree_store.btree_base.LeafMutator→redb.table.Rangeredb.tree_store.btree_base.OwnedEntryBuffer→redb.table.Range
- Direction
- redb.tree_store.btree_base uses redb.table, so a change to redb.table can break redb.tree_store.btree_base, while a change to redb.tree_store.btree_base can't break redb.table.
- Position
- Below the diagonal: redb.tree_store.btree_base uses a module listed above it, which is the healthy direction.
26→30 redb.tree_store.btree_base uses redb.tree_store.page_store.page_manager part of a loop✕
- Connections
- 3 pairs of types, where a type in redb.tree_store.btree_base uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.btree_base.AccessGuardMut→redb.tree_store.page_store.page_manager.PageAllocatorredb.tree_store.btree_base.BranchBuilder→redb.tree_store.page_store.page_manager.PageAllocatorredb.tree_store.btree_base.LeafBuilder→redb.tree_store.page_store.page_manager.PageAllocator
- Direction
- redb.tree_store.btree_base uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.btree_base, while a change to redb.tree_store.btree_base can't break redb.tree_store.page_store.page_manager.
- 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.
27→25 redb.tree_store.page_store.active_transactions uses redb.table✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.active_transactions uses a type in redb.table.
- The types involved
redb.tree_store.page_store.active_transactions.active_transactions$module→redb.table.Range
- Direction
- redb.tree_store.page_store.active_transactions uses redb.table, so a change to redb.table can break redb.tree_store.page_store.active_transactions, while a change to redb.tree_store.page_store.active_transactions can't break redb.table.
- Position
- Below the diagonal: redb.tree_store.page_store.active_transactions uses a module listed above it, which is the healthy direction.
28→10 redb.tree_store.page_store.header uses redb.tree_store.page_store.layout✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.header uses a type in redb.tree_store.page_store.layout.
- The types involved
redb.tree_store.page_store.header.DatabaseHeader→redb.tree_store.page_store.layout.DatabaseLayout
- Direction
- redb.tree_store.page_store.header uses redb.tree_store.page_store.layout, so a change to redb.tree_store.page_store.layout can break redb.tree_store.page_store.header, while a change to redb.tree_store.page_store.header can't break redb.tree_store.page_store.layout.
- Position
- Below the diagonal: redb.tree_store.page_store.header uses a module listed above it, which is the healthy direction.
28→26 redb.tree_store.page_store.header uses redb.tree_store.btree_base✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.page_store.header uses a type in redb.tree_store.btree_base.
- The types involved
redb.tree_store.page_store.header.DatabaseHeader→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.page_store.header.TransactionHeader→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.tree_store.page_store.header uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.tree_store.page_store.header, while a change to redb.tree_store.page_store.header can't break redb.tree_store.btree_base.
- Position
- Below the diagonal: redb.tree_store.page_store.header uses a module listed above it, which is the healthy direction.
28→31 redb.tree_store.page_store.header uses redb.transaction_tracker part of a loop✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.page_store.header uses a type in redb.transaction_tracker.
- The types involved
redb.tree_store.page_store.header.DatabaseHeader→redb.transaction_tracker.TransactionIdredb.tree_store.page_store.header.TransactionHeader→redb.transaction_tracker.TransactionId
- Direction
- redb.tree_store.page_store.header uses redb.transaction_tracker, so a change to redb.transaction_tracker can break redb.tree_store.page_store.header, while a change to redb.tree_store.page_store.header can't break redb.transaction_tracker.
- 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.
29→4 redb_python.table uses redb_python.fork✕
- Connections
- 1 pair of types, where a type in redb_python.table uses a type in redb_python.fork.
- The types involved
redb_python.table.PyReadOnlyTable→redb_python.fork.ProcessLocal
- Direction
- redb_python.table uses redb_python.fork, so a change to redb_python.fork can break redb_python.table, while a change to redb_python.table can't break redb_python.fork.
- Position
- Below the diagonal: redb_python.table uses a module listed above it, which is the healthy direction.
29→12 redb_python.table uses redb_python.types✕
- Connections
- 3 pairs of types, where a type in redb_python.table uses a type in redb_python.types.
- The types involved
redb_python.table.PyReadOnlyTable→redb_python.types.Typeredb_python.table.PyTable→redb_python.types.Typeredb_python.table.PyTableDefinition→redb_python.types.Type
- Direction
- redb_python.table uses redb_python.types, so a change to redb_python.types can break redb_python.table, while a change to redb_python.table can't break redb_python.types.
- Position
- Below the diagonal: redb_python.table uses a module listed above it, which is the healthy direction.
29→24 redb_python.table uses redb.transactions✕
- Connections
- 2 pairs of types, where a type in redb_python.table uses a type in redb.transactions.
- The types involved
redb_python.table.PyReadOnlyTable→redb.transactions.ReadTransactionredb_python.table.table$module→redb.transactions.WriteTransaction
- Direction
- redb_python.table uses redb.transactions, so a change to redb.transactions can break redb_python.table, while a change to redb_python.table can't break redb.transactions.
- Position
- Below the diagonal: redb_python.table uses a module listed above it, which is the healthy direction.
29→26 redb_python.table uses redb.tree_store.btree_base✕
- Connections
- 1 pair of types, where a type in redb_python.table uses a type in redb.tree_store.btree_base.
- The types involved
redb_python.table.table$module→redb.tree_store.btree_base.AccessGuard
- Direction
- redb_python.table uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb_python.table, while a change to redb_python.table can't break redb.tree_store.btree_base.
- Position
- Below the diagonal: redb_python.table uses a module listed above it, which is the healthy direction.
30→8 redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.buddy_allocator✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.page_manager uses a type in redb.tree_store.page_store.buddy_allocator.
- The types involved
redb.tree_store.page_store.page_manager.InMemoryState→redb.tree_store.page_store.buddy_allocator.BuddyAllocator
- Direction
- redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.buddy_allocator, so a change to redb.tree_store.page_store.buddy_allocator can break redb.tree_store.page_store.page_manager, while a change to redb.tree_store.page_store.page_manager can't break redb.tree_store.page_store.buddy_allocator.
- Position
- Below the diagonal: redb.tree_store.page_store.page_manager uses a module listed above it, which is the healthy direction.
30→9 redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.cached_file✕
- Connections
- 4 pairs of types, where a type in redb.tree_store.page_store.page_manager uses a type in redb.tree_store.page_store.cached_file.
- The types involved
redb.tree_store.page_store.page_manager.HeaderGuard→redb.tree_store.page_store.cached_file.PagedCachedFileredb.tree_store.page_store.page_manager.TransactionalMemory→redb.tree_store.page_store.cached_file.PagedCachedFileredb.tree_store.page_store.page_manager.WriterLock→redb.tree_store.page_store.cached_file.PagedCachedFileredb.tree_store.page_store.page_manager.page_manager$module→redb.tree_store.page_store.cached_file.PagedCachedFile
- Direction
- redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.cached_file, so a change to redb.tree_store.page_store.cached_file can break redb.tree_store.page_store.page_manager, while a change to redb.tree_store.page_store.page_manager can't break redb.tree_store.page_store.cached_file.
- Position
- Below the diagonal: redb.tree_store.page_store.page_manager uses a module listed above it, which is the healthy direction.
30→10 redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.layout✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.page_manager uses a type in redb.tree_store.page_store.layout.
- The types involved
redb.tree_store.page_store.page_manager.TransactionalMemory→redb.tree_store.page_store.layout.DatabaseLayout
- Direction
- redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.layout, so a change to redb.tree_store.page_store.layout can break redb.tree_store.page_store.page_manager, while a change to redb.tree_store.page_store.page_manager can't break redb.tree_store.page_store.layout.
- Position
- Below the diagonal: redb.tree_store.page_store.page_manager uses a module listed above it, which is the healthy direction.
30→13 redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.base✕
- Connections
- 10 pairs of types, where a type in redb.tree_store.page_store.page_manager uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.page_store.page_manager.PageAllocator→redb.tree_store.page_store.base.PageHintredb.tree_store.page_store.page_manager.PageAllocator→redb.tree_store.page_store.base.PageNumberredb.tree_store.page_store.page_manager.PageAllocator→redb.tree_store.page_store.base.PageTrackerredb.tree_store.page_store.page_manager.PageResolver→redb.tree_store.page_store.base.PageHintredb.tree_store.page_store.page_manager.PageResolver→redb.tree_store.page_store.base.PageNumberredb.tree_store.page_store.page_manager.TransactionalMemory→redb.tree_store.page_store.base.PageHintredb.tree_store.page_store.page_manager.TransactionalMemory→redb.tree_store.page_store.base.PageNumberredb.tree_store.page_store.page_manager.TransactionalMemory→redb.tree_store.page_store.base.PageTrackerredb.tree_store.page_store.page_manager.UncommittedPages→redb.tree_store.page_store.base.PageNumberredb.tree_store.page_store.page_manager.UnpersistedState→redb.tree_store.page_store.base.PageNumber
- Direction
- redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.page_store.page_manager, while a change to redb.tree_store.page_store.page_manager can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.page_store.page_manager uses a module listed above it, which is the healthy direction.
30→15 redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.region✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.page_store.page_manager uses a type in redb.tree_store.page_store.region.
- The types involved
redb.tree_store.page_store.page_manager.InMemoryState→redb.tree_store.page_store.region.Allocatorsredb.tree_store.page_store.page_manager.InMemoryState→redb.tree_store.page_store.region.RegionTracker
- Direction
- redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.region, so a change to redb.tree_store.page_store.region can break redb.tree_store.page_store.page_manager, while a change to redb.tree_store.page_store.page_manager can't break redb.tree_store.page_store.region.
- Position
- Below the diagonal: redb.tree_store.page_store.page_manager uses a module listed above it, which is the healthy direction.
30→26 redb.tree_store.page_store.page_manager uses redb.tree_store.btree_base✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.page_manager uses a type in redb.tree_store.btree_base.
- The types involved
redb.tree_store.page_store.page_manager.TransactionalMemory→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.tree_store.page_store.page_manager uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.tree_store.page_store.page_manager, while a change to redb.tree_store.page_store.page_manager can't break redb.tree_store.btree_base.
- Position
- Below the diagonal: redb.tree_store.page_store.page_manager uses a module listed above it, which is the healthy direction.
30→28 redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.header✕
- Connections
- 3 pairs of types, where a type in redb.tree_store.page_store.page_manager uses a type in redb.tree_store.page_store.header.
- The types involved
redb.tree_store.page_store.page_manager.InMemoryState→redb.tree_store.page_store.header.DatabaseHeaderredb.tree_store.page_store.page_manager.InMemoryState→redb.tree_store.page_store.header.TransactionHeaderredb.tree_store.page_store.page_manager.TransactionalMemory→redb.tree_store.page_store.header.DatabaseHeader
- Direction
- redb.tree_store.page_store.page_manager uses redb.tree_store.page_store.header, so a change to redb.tree_store.page_store.header can break redb.tree_store.page_store.page_manager, while a change to redb.tree_store.page_store.page_manager can't break redb.tree_store.page_store.header.
- Position
- Below the diagonal: redb.tree_store.page_store.page_manager uses a module listed above it, which is the healthy direction.
30→31 redb.tree_store.page_store.page_manager uses redb.transaction_tracker part of a loop✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.page_store.page_manager uses a type in redb.transaction_tracker.
- The types involved
redb.tree_store.page_store.page_manager.TransactionalMemory→redb.transaction_tracker.TransactionIdredb.tree_store.page_store.page_manager.UnpersistedState→redb.transaction_tracker.TransactionId
- Direction
- redb.tree_store.page_store.page_manager uses redb.transaction_tracker, so a change to redb.transaction_tracker can break redb.tree_store.page_store.page_manager, while a change to redb.tree_store.page_store.page_manager can't break redb.transaction_tracker.
- 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.
30→33 redb.tree_store.page_store.page_manager uses redb.db part of a loop✕
- Connections
- 3 pairs of types, where a type in redb.tree_store.page_store.page_manager uses a type in redb.db.
- The types involved
redb.tree_store.page_store.page_manager.TransactionalMemory→redb.db.CacheStatsredb.tree_store.page_store.page_manager.TransactionalMemory→redb.db.ConcurrencyModeredb.tree_store.page_store.page_manager.page_manager$module→redb.db.ConcurrencyMode
- Direction
- redb.tree_store.page_store.page_manager uses redb.db, so a change to redb.db can break redb.tree_store.page_store.page_manager, while a change to redb.tree_store.page_store.page_manager can't break redb.db.
- 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.
31→3 redb.transaction_tracker uses redb.types✕
- Connections
- 3 pairs of types, where a type in redb.transaction_tracker uses a type in redb.types.
- The types involved
redb.transaction_tracker.SavepointId→redb.types.Keyredb.transaction_tracker.SavepointId→redb.types.TypeNameredb.transaction_tracker.SavepointId→redb.types.Value
- Direction
- redb.transaction_tracker uses redb.types, so a change to redb.types can break redb.transaction_tracker, while a change to redb.transaction_tracker can't break redb.types.
- Position
- Below the diagonal: redb.transaction_tracker uses a module listed above it, which is the healthy direction.
31→30 redb.transaction_tracker uses redb.tree_store.page_store.page_manager✕
- Connections
- 4 pairs of types, where a type in redb.transaction_tracker uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.transaction_tracker.State→redb.tree_store.page_store.page_manager.HeaderGuardredb.transaction_tracker.State→redb.tree_store.page_store.page_manager.TransactionalMemoryredb.transaction_tracker.TransactionTracker→redb.tree_store.page_store.page_manager.TransactionalMemoryredb.transaction_tracker.TransactionTracker→redb.tree_store.page_store.page_manager.WriterLock
- Direction
- redb.transaction_tracker uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.transaction_tracker, while a change to redb.transaction_tracker can't break redb.tree_store.page_store.page_manager.
- Position
- Below the diagonal: redb.transaction_tracker uses a module listed above it, which is the healthy direction.
32→3 redb.tree_store.multimap_btree uses redb.types✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.multimap_btree uses a type in redb.types.
- The types involved
redb.tree_store.multimap_btree.DynamicCollection→redb.types.TypeNameredb.tree_store.multimap_btree.DynamicCollection→redb.types.Value
- Direction
- redb.tree_store.multimap_btree uses redb.types, so a change to redb.types can break redb.tree_store.multimap_btree, while a change to redb.tree_store.multimap_btree can't break redb.types.
- Position
- Below the diagonal: redb.tree_store.multimap_btree uses a module listed above it, which is the healthy direction.
32→13 redb.tree_store.multimap_btree uses redb.tree_store.page_store.base✕
- Connections
- 3 pairs of types, where a type in redb.tree_store.multimap_btree uses a type in redb.tree_store.page_store.base.
- The types involved
redb.tree_store.multimap_btree.UntypedMultiBtree→redb.tree_store.page_store.base.PageHintredb.tree_store.multimap_btree.multimap_btree$module→redb.tree_store.page_store.base.PageHintredb.tree_store.multimap_btree.multimap_btree$module→redb.tree_store.page_store.base.PageNumber
- Direction
- redb.tree_store.multimap_btree uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.tree_store.multimap_btree, while a change to redb.tree_store.multimap_btree can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.tree_store.multimap_btree uses a module listed above it, which is the healthy direction.
32→25 redb.tree_store.multimap_btree uses redb.table✕
- Connections
- 1 pair of types, where a type in redb.tree_store.multimap_btree uses a type in redb.table.
- The types involved
redb.tree_store.multimap_btree.DynamicCollection→redb.table.Range
- Direction
- redb.tree_store.multimap_btree uses redb.table, so a change to redb.table can break redb.tree_store.multimap_btree, while a change to redb.tree_store.multimap_btree can't break redb.table.
- Position
- Below the diagonal: redb.tree_store.multimap_btree uses a module listed above it, which is the healthy direction.
32→26 redb.tree_store.multimap_btree uses redb.tree_store.btree_base✕
- Connections
- 4 pairs of types, where a type in redb.tree_store.multimap_btree uses a type in redb.tree_store.btree_base.
- The types involved
redb.tree_store.multimap_btree.DynamicCollection→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.multimap_btree.UntypedDynamicCollection→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.multimap_btree.UntypedMultiBtree→redb.tree_store.btree_base.BtreeHeaderredb.tree_store.multimap_btree.multimap_btree$module→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.tree_store.multimap_btree uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.tree_store.multimap_btree, while a change to redb.tree_store.multimap_btree can't break redb.tree_store.btree_base.
- Position
- Below the diagonal: redb.tree_store.multimap_btree uses a module listed above it, which is the healthy direction.
32→30 redb.tree_store.multimap_btree uses redb.tree_store.page_store.page_manager✕
- Connections
- 3 pairs of types, where a type in redb.tree_store.multimap_btree uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.tree_store.multimap_btree.UntypedMultiBtree→redb.tree_store.page_store.page_manager.PageResolverredb.tree_store.multimap_btree.multimap_btree$module→redb.tree_store.page_store.page_manager.PageAllocatorredb.tree_store.multimap_btree.multimap_btree$module→redb.tree_store.page_store.page_manager.PageResolver
- Direction
- redb.tree_store.multimap_btree uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.tree_store.multimap_btree, while a change to redb.tree_store.multimap_btree can't break redb.tree_store.page_store.page_manager.
- Position
- Below the diagonal: redb.tree_store.multimap_btree uses a module listed above it, which is the healthy direction.
33→1 redb.db uses redb.sealed✕
- Connections
- 9 pairs of types, where a type in redb.db uses a type in redb.sealed.
- The types involved
redb.db.Database→redb.sealed.Sealedredb.db.MultimapTableDefinition→redb.sealed.Sealedredb.db.MultimapTableHandle→redb.sealed.Sealedredb.db.ReadOnlyDatabase→redb.sealed.Sealedredb.db.ReadableDatabase→redb.sealed.SealedInApi5redb.db.TableDefinition→redb.sealed.Sealedredb.db.TableHandle→redb.sealed.Sealedredb.db.UntypedMultimapTableHandle→redb.sealed.Sealedredb.db.UntypedTableHandle→redb.sealed.Sealed
- Direction
- redb.db uses redb.sealed, so a change to redb.sealed can break redb.db, while a change to redb.db can't break redb.sealed.
- Position
- Below the diagonal: redb.db uses a module listed above it, which is the healthy direction.
33→23 redb.db uses redb.tree_store.table_tree✕
- Connections
- 1 pair of types, where a type in redb.db uses a type in redb.tree_store.table_tree.
- The types involved
redb.db.Database→redb.tree_store.table_tree.TableTree
- Direction
- redb.db uses redb.tree_store.table_tree, so a change to redb.tree_store.table_tree can break redb.db, while a change to redb.db can't break redb.tree_store.table_tree.
- Position
- Below the diagonal: redb.db uses a module listed above it, which is the healthy direction.
33→24 redb.db uses redb.transactions✕
- Connections
- 2 pairs of types, where a type in redb.db uses a type in redb.transactions.
- The types involved
redb.db.Database→redb.transactions.SystemTableDefinitionredb.db.db$module→redb.transactions.WriteTransaction
- Direction
- redb.db uses redb.transactions, so a change to redb.transactions can break redb.db, while a change to redb.db can't break redb.transactions.
- Position
- Below the diagonal: redb.db uses a module listed above it, which is the healthy direction.
33→26 redb.db uses redb.tree_store.btree_base✕
- Connections
- 1 pair of types, where a type in redb.db uses a type in redb.tree_store.btree_base.
- The types involved
redb.db.Database→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.db uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.db, while a change to redb.db can't break redb.tree_store.btree_base.
- Position
- Below the diagonal: redb.db uses a module listed above it, which is the healthy direction.
33→30 redb.db uses redb.tree_store.page_store.page_manager✕
- Connections
- 12 pairs of types, where a type in redb.db uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.db.Database→redb.tree_store.page_store.page_manager.HeaderGuardredb.db.Database→redb.tree_store.page_store.page_manager.PageResolverredb.db.Database→redb.tree_store.page_store.page_manager.ShrinkPolicyredb.db.Database→redb.tree_store.page_store.page_manager.TransactionalMemoryredb.db.Database→redb.tree_store.page_store.page_manager.WriterLockredb.db.ReadOnlyDatabase→redb.tree_store.page_store.page_manager.TransactionalMemoryredb.db.TransactionGuard→redb.tree_store.page_store.page_manager.TransactionalMemoryredb.db.TransactionGuard→redb.tree_store.page_store.page_manager.WriterLockredb.db.db$module→redb.tree_store.page_store.page_manager.AllocationPolicyredb.db.db$module→redb.tree_store.page_store.page_manager.HeaderGuardredb.db.db$module→redb.tree_store.page_store.page_manager.TransactionalMemoryredb.db.db$module→redb.tree_store.page_store.page_manager.WriterLock
- Direction
- redb.db uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.db, while a change to redb.db can't break redb.tree_store.page_store.page_manager.
- Position
- Below the diagonal: redb.db uses a module listed above it, which is the healthy direction.
33→31 redb.db uses redb.transaction_tracker✕
- Connections
- 6 pairs of types, where a type in redb.db uses a type in redb.transaction_tracker.
- The types involved
redb.db.Database→redb.transaction_tracker.TransactionTrackerredb.db.ReadOnlyDatabase→redb.transaction_tracker.TransactionTrackerredb.db.TransactionGuard→redb.transaction_tracker.TransactionIdredb.db.TransactionGuard→redb.transaction_tracker.TransactionTrackerredb.db.WriteSlot→redb.transaction_tracker.TransactionTrackerredb.db.db$module→redb.transaction_tracker.TransactionTracker
- Direction
- redb.db uses redb.transaction_tracker, so a change to redb.transaction_tracker can break redb.db, while a change to redb.db can't break redb.transaction_tracker.
- Position
- Below the diagonal: redb.db uses a module listed above it, which is the healthy direction.
34→1 redb.multimap_table uses redb.sealed✕
- Connections
- 3 pairs of types, where a type in redb.multimap_table uses a type in redb.sealed.
- The types involved
redb.multimap_table.MultimapTable→redb.sealed.Sealedredb.multimap_table.ReadOnlyMultimapTable→redb.sealed.Sealedredb.multimap_table.ReadOnlyUntypedMultimapTable→redb.sealed.Sealed
- Direction
- redb.multimap_table uses redb.sealed, so a change to redb.sealed can break redb.multimap_table, while a change to redb.multimap_table can't break redb.sealed.
- Position
- Below the diagonal: redb.multimap_table uses a module listed above it, which is the healthy direction.
34→13 redb.multimap_table uses redb.tree_store.page_store.base✕
- Connections
- 6 pairs of types, where a type in redb.multimap_table uses a type in redb.tree_store.page_store.base.
- The types involved
redb.multimap_table.MultimapTable→redb.tree_store.page_store.base.PageNumberredb.multimap_table.MultimapTable→redb.tree_store.page_store.base.PageTrackerredb.multimap_table.MultimapValue→redb.tree_store.page_store.base.PageNumberredb.multimap_table.MultimapValue→redb.tree_store.page_store.base.PageTrackerredb.multimap_table.ReadOnlyMultimapTable→redb.tree_store.page_store.base.PageHintredb.multimap_table.ReadOnlyUntypedMultimapTable→redb.tree_store.page_store.base.PageHint
- Direction
- redb.multimap_table uses redb.tree_store.page_store.base, so a change to redb.tree_store.page_store.base can break redb.multimap_table, while a change to redb.multimap_table can't break redb.tree_store.page_store.base.
- Position
- Below the diagonal: redb.multimap_table uses a module listed above it, which is the healthy direction.
34→20 redb.multimap_table uses redb.tree_store.btree_cursor_range✕
- Connections
- 2 pairs of types, where a type in redb.multimap_table uses a type in redb.tree_store.btree_cursor_range.
- The types involved
redb.multimap_table.MultimapRange→redb.tree_store.btree_cursor_range.BtreeCursorRangeredb.multimap_table.MultimapValue→redb.tree_store.btree_cursor_range.BtreeCursorRange
- Direction
- redb.multimap_table uses redb.tree_store.btree_cursor_range, so a change to redb.tree_store.btree_cursor_range can break redb.multimap_table, while a change to redb.multimap_table can't break redb.tree_store.btree_cursor_range.
- Position
- Below the diagonal: redb.multimap_table uses a module listed above it, which is the healthy direction.
34→21 redb.multimap_table uses redb.tree_store.btree✕
- Connections
- 3 pairs of types, where a type in redb.multimap_table uses a type in redb.tree_store.btree.
- The types involved
redb.multimap_table.MultimapTable→redb.tree_store.btree.BtreeMutredb.multimap_table.ReadOnlyMultimapTable→redb.tree_store.btree.Btreeredb.multimap_table.ReadOnlyUntypedMultimapTable→redb.tree_store.btree.RawBtree
- Direction
- redb.multimap_table uses redb.tree_store.btree, so a change to redb.tree_store.btree can break redb.multimap_table, while a change to redb.multimap_table can't break redb.tree_store.btree.
- Position
- Below the diagonal: redb.multimap_table uses a module listed above it, which is the healthy direction.
34→24 redb.multimap_table uses redb.transactions✕
- Connections
- 1 pair of types, where a type in redb.multimap_table uses a type in redb.transactions.
- The types involved
redb.multimap_table.MultimapTable→redb.transactions.WriteTransaction
- Direction
- redb.multimap_table uses redb.transactions, so a change to redb.transactions can break redb.multimap_table, while a change to redb.multimap_table can't break redb.transactions.
- Position
- Below the diagonal: redb.multimap_table uses a module listed above it, which is the healthy direction.
34→25 redb.multimap_table uses redb.table✕
- Connections
- 5 pairs of types, where a type in redb.multimap_table uses a type in redb.table.
- The types involved
redb.multimap_table.LeafKeyIter→redb.table.Rangeredb.multimap_table.MultimapTable→redb.table.ReadableTableMetadataredb.multimap_table.ReadOnlyMultimapTable→redb.table.ReadableTableMetadataredb.multimap_table.ReadOnlyUntypedMultimapTable→redb.table.ReadableTableMetadataredb.multimap_table.ReadableMultimapTable→redb.table.ReadableTableMetadata
- Direction
- redb.multimap_table uses redb.table, so a change to redb.table can break redb.multimap_table, while a change to redb.multimap_table can't break redb.table.
- Position
- Below the diagonal: redb.multimap_table uses a module listed above it, which is the healthy direction.
34→26 redb.multimap_table uses redb.tree_store.btree_base✕
- Connections
- 5 pairs of types, where a type in redb.multimap_table uses a type in redb.tree_store.btree_base.
- The types involved
redb.multimap_table.LeafKeyIter→redb.tree_store.btree_base.AccessGuardredb.multimap_table.MultimapTable→redb.tree_store.btree_base.BtreeHeaderredb.multimap_table.MultimapValue→redb.tree_store.btree_base.AccessGuardredb.multimap_table.ReadOnlyMultimapTable→redb.tree_store.btree_base.BtreeHeaderredb.multimap_table.ReadOnlyUntypedMultimapTable→redb.tree_store.btree_base.BtreeHeader
- Direction
- redb.multimap_table uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb.multimap_table, while a change to redb.multimap_table can't break redb.tree_store.btree_base.
- Position
- Below the diagonal: redb.multimap_table uses a module listed above it, which is the healthy direction.
34→30 redb.multimap_table uses redb.tree_store.page_store.page_manager✕
- Connections
- 6 pairs of types, where a type in redb.multimap_table uses a type in redb.tree_store.page_store.page_manager.
- The types involved
redb.multimap_table.MultimapRange→redb.tree_store.page_store.page_manager.PageResolverredb.multimap_table.MultimapTable→redb.tree_store.page_store.page_manager.PageAllocatorredb.multimap_table.MultimapValue→redb.tree_store.page_store.page_manager.PageAllocatorredb.multimap_table.MultimapValue→redb.tree_store.page_store.page_manager.PageResolverredb.multimap_table.ReadOnlyMultimapTable→redb.tree_store.page_store.page_manager.PageResolverredb.multimap_table.ReadOnlyUntypedMultimapTable→redb.tree_store.page_store.page_manager.PageResolver
- Direction
- redb.multimap_table uses redb.tree_store.page_store.page_manager, so a change to redb.tree_store.page_store.page_manager can break redb.multimap_table, while a change to redb.multimap_table can't break redb.tree_store.page_store.page_manager.
- Position
- Below the diagonal: redb.multimap_table uses a module listed above it, which is the healthy direction.
34→33 redb.multimap_table uses redb.db✕
- Connections
- 9 pairs of types, where a type in redb.multimap_table uses a type in redb.db.
- The types involved
redb.multimap_table.MultimapRange→redb.db.TransactionGuardredb.multimap_table.MultimapTable→redb.db.MultimapTableHandleredb.multimap_table.MultimapValue→redb.db.TransactionGuardredb.multimap_table.OwnedMultimapRange→redb.db.TransactionGuardredb.multimap_table.OwnedMultimapValue→redb.db.TransactionGuardredb.multimap_table.ReadOnlyMultimapTable→redb.db.MultimapTableHandleredb.multimap_table.ReadOnlyMultimapTable→redb.db.TransactionGuardredb.multimap_table.ReadOnlyUntypedMultimapTable→redb.db.MultimapTableHandleredb.multimap_table.ReadOnlyUntypedMultimapTable→redb.db.TransactionGuard
- Direction
- redb.multimap_table uses redb.db, so a change to redb.db can break redb.multimap_table, while a change to redb.multimap_table can't break redb.db.
- Position
- Below the diagonal: redb.multimap_table uses a module listed above it, which is the healthy direction.
35→5 redb.tree_store.page_store.backends uses redb.error✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.backends uses a type in redb.error.
- The types involved
redb.tree_store.page_store.backends.InMemoryBackend→redb.error.BackendError
- Direction
- redb.tree_store.page_store.backends uses redb.error, so a change to redb.error can break redb.tree_store.page_store.backends, while a change to redb.tree_store.page_store.backends can't break redb.error.
- Position
- Below the diagonal: redb.tree_store.page_store.backends uses a module listed above it, which is the healthy direction.
35→33 redb.tree_store.page_store.backends uses redb.db✕
- Connections
- 2 pairs of types, where a type in redb.tree_store.page_store.backends uses a type in redb.db.
- The types involved
redb.tree_store.page_store.backends.InMemoryBackend→redb.db.StorageBackendredb.tree_store.page_store.backends.ReadOnlyBackend→redb.db.StorageBackend
- Direction
- redb.tree_store.page_store.backends uses redb.db, so a change to redb.db can break redb.tree_store.page_store.backends, while a change to redb.tree_store.page_store.backends can't break redb.db.
- Position
- Below the diagonal: redb.tree_store.page_store.backends uses a module listed above it, which is the healthy direction.
36→33 redb.tree_store.page_store.file_backend.fallback uses redb.db✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.file_backend.fallback uses a type in redb.db.
- The types involved
redb.tree_store.page_store.file_backend.fallback.FileBackend→redb.db.StorageBackend
- Direction
- redb.tree_store.page_store.file_backend.fallback uses redb.db, so a change to redb.db can break redb.tree_store.page_store.file_backend.fallback, while a change to redb.tree_store.page_store.file_backend.fallback can't break redb.db.
- Position
- Below the diagonal: redb.tree_store.page_store.file_backend.fallback uses a module listed above it, which is the healthy direction.
37→33 redb.tree_store.page_store.file_backend.optimized uses redb.db✕
- Connections
- 1 pair of types, where a type in redb.tree_store.page_store.file_backend.optimized uses a type in redb.db.
- The types involved
redb.tree_store.page_store.file_backend.optimized.FileBackend→redb.db.StorageBackend
- Direction
- redb.tree_store.page_store.file_backend.optimized uses redb.db, so a change to redb.db can break redb.tree_store.page_store.file_backend.optimized, while a change to redb.tree_store.page_store.file_backend.optimized can't break redb.db.
- Position
- Below the diagonal: redb.tree_store.page_store.file_backend.optimized uses a module listed above it, which is the healthy direction.
38→24 redb_bench uses redb.transactions✕
- Connections
- 2 pairs of types, where a type in redb_bench uses a type in redb.transactions.
- The types involved
redb_bench.RedbBenchReadTransaction→redb.transactions.ReadTransactionredb_bench.RedbBenchWriteTransaction→redb.transactions.WriteTransaction
- Direction
- redb_bench uses redb.transactions, so a change to redb.transactions can break redb_bench, while a change to redb_bench can't break redb.transactions.
- Position
- Below the diagonal: redb_bench uses a module listed above it, which is the healthy direction.
38→25 redb_bench uses redb.table✕
- Connections
- 4 pairs of types, where a type in redb_bench uses a type in redb.table.
- The types involved
redb_bench.RedbBenchInserter→redb.table.Tableredb_bench.RedbBenchIterator→redb.table.Rangeredb_bench.RedbBenchReader→redb.table.ReadOnlyTableredb_bench.RedbExtractIfIterator→redb.table.ExtractIf
- Direction
- redb_bench uses redb.table, so a change to redb.table can break redb_bench, while a change to redb_bench can't break redb.table.
- Position
- Below the diagonal: redb_bench uses a module listed above it, which is the healthy direction.
38→26 redb_bench uses redb.tree_store.btree_base✕
- Connections
- 1 pair of types, where a type in redb_bench uses a type in redb.tree_store.btree_base.
- The types involved
redb_bench.RedbAccessGuard→redb.tree_store.btree_base.AccessGuard
- Direction
- redb_bench uses redb.tree_store.btree_base, so a change to redb.tree_store.btree_base can break redb_bench, while a change to redb_bench can't break redb.tree_store.btree_base.
- Position
- Below the diagonal: redb_bench uses a module listed above it, which is the healthy direction.
38→33 redb_bench uses redb.db✕
- Connections
- 2 pairs of types, where a type in redb_bench uses a type in redb.db.
- The types involved
redb_bench.RedbBenchDatabase→redb.db.Databaseredb_bench.RedbBenchDatabaseConnection→redb.db.Database
- Direction
- redb_bench uses redb.db, so a change to redb.db can break redb_bench, while a change to redb_bench can't break redb.db.
- Position
- Below the diagonal: redb_bench uses a module listed above it, which is the healthy direction.
39→4 redb_python.database uses redb_python.fork✕
- Connections
- 2 pairs of types, where a type in redb_python.database uses a type in redb_python.fork.
- The types involved
redb_python.database.PyDatabase→redb_python.fork.ProcessLocalredb_python.database.PyReadOnlyDatabase→redb_python.fork.ProcessLocal
- Direction
- redb_python.database uses redb_python.fork, so a change to redb_python.fork can break redb_python.database, while a change to redb_python.database can't break redb_python.fork.
- Position
- Below the diagonal: redb_python.database uses a module listed above it, which is the healthy direction.
39→33 redb_python.database uses redb.db✕
- Connections
- 2 pairs of types, where a type in redb_python.database uses a type in redb.db.
- The types involved
redb_python.database.ConcurrencyMode→redb.db.Builderredb_python.database.PyDatabase→redb.db.Database
- Direction
- redb_python.database uses redb.db, so a change to redb.db can break redb_python.database, while a change to redb_python.database can't break redb.db.
- Position
- Below the diagonal: redb_python.database uses a module listed above it, which is the healthy direction.
40→4 redb_python.transaction uses redb_python.fork✕
- Connections
- 2 pairs of types, where a type in redb_python.transaction uses a type in redb_python.fork.
- The types involved
redb_python.transaction.PyReadTransaction→redb_python.fork.ProcessLocalredb_python.transaction.PyWriteTransaction→redb_python.fork.ProcessLocal
- Direction
- redb_python.transaction uses redb_python.fork, so a change to redb_python.fork can break redb_python.transaction, while a change to redb_python.transaction can't break redb_python.fork.
- Position
- Below the diagonal: redb_python.transaction uses a module listed above it, which is the healthy direction.
40→24 redb_python.transaction uses redb.transactions✕
- Connections
- 4 pairs of types, where a type in redb_python.transaction uses a type in redb.transactions.
- The types involved
redb_python.transaction.PyReadTransaction→redb.transactions.ReadTransactionredb_python.transaction.PyWriteTransaction→redb.transactions.WriteTransactionredb_python.transaction.ReadActive→redb.transactions.ReadTransactionredb_python.transaction.transaction$module→redb.transactions.WriteTransaction
- Direction
- redb_python.transaction uses redb.transactions, so a change to redb.transactions can break redb_python.transaction, while a change to redb_python.transaction can't break redb.transactions.
- Position
- Below the diagonal: redb_python.transaction uses a module listed above it, which is the healthy direction.
40→29 redb_python.transaction uses redb_python.table✕
- Connections
- 2 pairs of types, where a type in redb_python.transaction uses a type in redb_python.table.
- The types involved
redb_python.transaction.PyReadTransaction→redb_python.table.PyTableDefinitionredb_python.transaction.PyWriteTransaction→redb_python.table.PyTableDefinition
- Direction
- redb_python.transaction uses redb_python.table, so a change to redb_python.table can break redb_python.transaction, while a change to redb_python.transaction can't break redb_python.table.
- Position
- Below the diagonal: redb_python.transaction uses a module listed above it, which is the healthy direction.
40→33 redb_python.transaction uses redb.db✕
- Connections
- 1 pair of types, where a type in redb_python.transaction uses a type in redb.db.
- The types involved
redb_python.transaction.transaction$module→redb.db.TableDefinition
- Direction
- redb_python.transaction uses redb.db, so a change to redb.db can break redb_python.transaction, while a change to redb_python.transaction can't break redb.db.
- Position
- Below the diagonal: redb_python.transaction 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 |
|---|---|---|
| A02:2025 — Security Misconfiguration | 9 | High / Critical |
| A05:2025 — Injection | 7 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +4.9 pts | Low | ADR Quality |
| 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. | +4.5 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.0 pts | Medium | Documentation (README) |
| 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. | +2.0 pts | Medium | Deployment & Rollback |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +1.6 pts | Medium | Observability |
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain. | +0.5 pts | Low | Platform End-of-Life |
| Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with db.rs, page_manager.rs, cached_file.rs. | +1.0 pts | High | Churn × Complexity Hotspots |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.3 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/tree_store/page_store/page_manager.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/tree_store/page_store/file_backend/optimized.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/tree_store/btree_mutator.rs | 7.0 | Mixed | Cyclomatic Complexity: MutateHelper::apply_child_deletion_result (cyclomatic 44) |
| src/db.rs | 7.0 | Mixed | Cyclomatic Complexity: Database::check_integrity_inner (cyclomatic 17) |
| src/multimap_table.rs | 7.0 | Mixed | Cognitive Complexity: MultimapTable::insert_inner (cognitive 32) |
| src/transactions.rs | 7.0 | Mixed | Cognitive Complexity: WriteTransaction::process_freed_pages_nondurable_helper (cognitive 30) |
| src/table.rs | 7.0 | Mixed | Cognitive Complexity: redb::table::debug_helper (cognitive 21) |
| src/tree_store/btree.rs | 7.0 | Mixed | Cognitive Complexity: RawBtree::verify_checksum_helper (cognitive 17) |
| src/tree_store/btree_base.rs | 7.0 | Mixed | God Classes: FileTooLong: tree_store/btree_base.rs |
| crates/redb-bench/src/lib.rs | 7.0 | Mixed | Cyclomatic Complexity: redb_bench::benchmark (cyclomatic 30) |
| src/tree_store/btree_cursor.rs | 7.0 | Mixed | God Classes: FileTooLong: tree_store/btree_cursor.rs |
| src/tree_store/page_store/xxh3.rs | 7.0 | Mixed | God Classes: FileTooLong: page_store/xxh3.rs |
| src/tree_store/table_tree.rs | 7.0 | Mixed | God Classes: FileTooLong: tree_store/table_tree.rs |
| fuzz/fuzz_targets/fuzz_redb.rs | 7.0 | Mixed | Code Duplication: Edited copy of a member (20 corresponding lines) |
| src/tree_store/page_store/cached_file.rs | 7.0 | Mixed | Cyclomatic Complexity: PagedCachedFile::read (cyclomatic 17) |
| fuzz/fuzz_targets/fuzz_corruption.rs | 7.1 | Mixed | Code Duplication: Edited copies of one member (3 members, 9+ corresponding lines) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 38 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, 219 of 222 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 48 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (47 contributor(s) across 1927 commit(s) sampled, automation and bot accounts excluded). One of them holds 93% of the history; the other 46 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via Dockerfile (REDACTED). docker build failed (exit 1) — 0.287 /bin/sh: 1: cargo: not found ------ REDACTED:15 -------------------- 13 | ADD . /code/redb/ 14 | 15 | >>> RUN cd /code/redb && cargo bench --no-run -p redb-bench -p redb-bench-compare 16 | -------------------- ERROR: failed to solve: process "/bin/sh -c cd /code/redb && cargo bench --no-run -p redb-bench -p redb-bench-compare" did not complete successfully: exit code: 127; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'redb' is imported (crates/redb-python/src/database.rs:115), 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'redb' is imported (crates/redb-python/src/database.rs:115), 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'redb' is imported (crates/redb-python/src/database.rs:115), 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'redb' is imported (crates/redb-python/src/database.rs:115), 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.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 Python, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 Python, 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.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 Python, 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
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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").
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was MutateHelper::apply_child_deletion_result at 44. A further 2 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 Error::fmt at 33 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/error.rs (Error::fmt at 33), crates/redb-python/src/error.rs (redb_python::error::into_py_err at 31). 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 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MutateHelper::apply_child_deletion_result (cyclomatic 44), MutateHelper::insert_helper (cyclomatic 39), redb_bench::benchmark (cyclomatic 30). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
23 function(s) exceeded the cognitive complexity threshold of 15; the worst was MutateHelper::apply_child_deletion_result at 138.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with MutateHelper::apply_child_deletion_result (cognitive 138), MutateHelper::insert_helper (cognitive 98). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.8 to about 6.7/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
34 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 15 FileTooLong finding(s) in God Classes — start with transactions.rs, btree_base.rs, page_manager.rs. — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 7 ClassTooLong finding(s) in God Classes — start with btree_mutator.rs, page_manager.rs, transactions.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 TooManyMethods finding(s) in God Classes — start with page_manager.rs, transactions.rs, btree_cursor.rs. — One of this dimension's main actionable groups (6 warning-level).
D4 · Code Duplication
66 duplicated block group(s) detected. 6.8 % of the production lines (3,064 of 44,887) are in a reported copy. A further 62 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 12 of the 128 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 7 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with db.rs, multimap_table.rs, table.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 7 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with table.rs (2), db.rs, multimap_table.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with table.rs, extract_if.rs, fallback.rs. — One of this dimension's main actionable groups (6 warning-level).
D5 · Coupling
5 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, with abstractness counted on 3 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 114 classes have LCOM4 above 3.
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. 14 of 18 direct crates were graded against crates.io (0 not published there, 4 not resolved by a committed Cargo.lock). 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 Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 65 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 1 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/db.rs (87×17=1479); src/tree_store/page_store/page_manager.rs (74×18=1332); src/tree_store/page_store/cached_file.rs (21×17=357)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with db.rs, page_manager.rs, cached_file.rs. — One of this dimension's main actionable groups (4 warning-level).
D17 · Explicit Debt
4 deducted task-comment markers across 44887 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with base.rs, page_manager.rs, optimized.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 XxxComment finding(s) in Explicit Debt — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 5 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)
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `src/types.rs` (lines 159–161, lines 163–165) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 6 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 (6 issue-level, 0 of them charged here).
D31 · IaC & Container Security
9 finding(s): 0 critical, 3 high, 4 medium, 2 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 51 of the 64 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/redb-no-std-test`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
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
PF1 · Benchmark discipline
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 85% | Strong | Solid. |
| Architecture | 99% | Exemplary | Strongest area. |
| Maturity | 66% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68% | Adequate | Acceptable, with room to improve. |
| Security | 82% | Strong | Solid. |
| Performance | 80% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'redb' (crates/redb-python/src/database.rs:115) 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 'redb' (crates/redb-python/src/database.rs:115) 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 'redb' (crates/redb-python/src/database.rs:115) 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 — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- 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
- 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) — 0.287 /bin/sh: 1: cargo: not found ------ REDACTED:15 -------------------- 13 | ADD . /code/redb/ 14 | 15 | >>> RUN cd /code/redb && cargo bench --no-run -p redb-bench -p redb-bench-compare 16 | -------------------- ERROR: failed to solve: process "/bin/sh -c cd /code/redb && cargo bench --no-run -p redb-bench -p redb-bench-compare" did not complete successfully: exit code: 127; 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 'redb' (crates/redb-python/src/database.rs:115) 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.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- D10 Test Quality — ~19913 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.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (4979 declarations, no unit with a dominant convention).
- 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .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.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- 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 measured — Rust suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (15 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 — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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 Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 56 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 207 finding(s)
- FileTooLong: src/transactions.rs src/transactions.rs
- FileTooLong: tree_store/btree_base.rs src/tree_store/btree_base.rs
- FileTooLong: page_store/page_manager.rs src/tree_store/page_store/page_manager.rs
- FileTooLong: tree_store/btree_cursor.rs src/tree_store/btree_cursor.rs
- FileTooLong: src/db.rs src/db.rs
- FileTooLong: tree_store/btree_mutator.rs src/tree_store/btree_mutator.rs
- FileTooLong: src/table.rs src/table.rs
- FileTooLong: tree_store/btree.rs src/tree_store/btree.rs
- FileTooLong: src/multimap_table.rs src/multimap_table.rs
- FileTooLong: src/lib.rs crates/redb-bench/src/lib.rs
- FileTooLong: src/error.rs src/error.rs
- FileTooLong: page_store/xxh3.rs src/tree_store/page_store/xxh3.rs
- FileTooLong: src/types.rs src/types.rs
- FileTooLong: page_store/cached_file.rs src/tree_store/page_store/cached_file.rs
- FileTooLong: tree_store/table_tree.rs src/tree_store/table_tree.rs
- ClassTooLong: MutateHelper src/tree_store/btree_mutator.rs:96
- ClassTooLong: TransactionalMemory src/tree_store/page_store/page_manager.rs:661
- ClassTooLong: WriteTransaction src/transactions.rs:930
- ClassTooLong: Database src/db.rs:811
- ClassTooLong: CursorMut src/tree_store/btree_cursor.rs:701
- ClassTooLong: PagedCachedFile src/tree_store/page_store/cached_file.rs:302
- ClassTooLong: TableTreeMut src/tree_store/table_tree.rs:228
- Duplicated block (12 lines × 2) src/db.rs:1509
- Duplicated block (12 lines × 2) src/multimap_table.rs:266
- Duplicated block (12 lines × 2) src/table.rs:498
- Duplicated block (12 lines × 2) src/transactions.rs:1901
- Duplicated block (12 lines × 2) src/tree_store/btree.rs:1327
- Duplicated block (12 lines × 2) crates/redb-bench/src/lib.rs:382
- Duplicated block (12 lines × 2) fuzz/fuzz_targets/fuzz_corruption.rs:317
- Duplicated block (8 lines × 2) src/db.rs:1432
- Duplicated block (8 lines × 2) src/multimap_table.rs:185
- Duplicated block (8 lines × 2) src/table.rs:1225
- Duplicated block (8 lines × 2) src/table.rs:1563
- Duplicated block (8 lines × 2) src/transactions.rs:1096
- Duplicated block (8 lines × 2) src/tree_store/table_tree.rs:205
- Duplicated block (8 lines × 2) src/tree_store/btree_base.rs:1751
- TooManyMethods: TransactionalMemory src/tree_store/page_store/page_manager.rs:661
- TooManyMethods: WriteTransaction src/transactions.rs:930
- TooManyMethods: CursorMut src/tree_store/btree_cursor.rs:701
- TooManyMethods: PagedCachedFile src/tree_store/page_store/cached_file.rs:302
- TooManyMethods: TransactionTracker src/transaction_tracker.rs:248
- TooManyMethods: BtreeMut src/tree_store/btree.rs:356
- Duplicated block (11 lines × 2) src/table.rs:1402
- Duplicated block (11 lines × 2) src/tree_store/extract_if.rs:113
- Duplicated block (11 lines × 2) src/tree_store/page_store/file_backend/fallback.rs:47
- Duplicated block (11 lines × 2) src/tree_store/table_tree.rs:450
- Duplicated block (11 lines × 2) src/transactions.rs:2682
- Duplicated block (11 lines × 2) crates/redb-derive/src/lib.rs:276
- Duplicated block (9 lines × 2) crates/redb-bench/src/lib.rs:399
- Duplicated block (9 lines × 2) src/tree_store/btree_mutator.rs:1111
- Duplicated block (9 lines × 2) src/tree_store/page_store/xxh3.rs:899
- Duplicated block (9 lines × 2) src/transactions.rs:1120
- Duplicated block (9 lines × 2) crates/redb-derive/src/lib.rs:69
- Duplicated block (9 lines × 2) fuzz/fuzz_targets/fuzz_redb.rs:402
- Duplicated block (6 lines × 2) crates/redb-bench/src/lib.rs:240
- Duplicated block (6 lines × 2) src/tree_store/btree.rs:1147
- Duplicated block (6 lines × 2) src/tree_store/btree_base.rs:1446
- Duplicated block (6 lines × 2) src/tree_store/table_tree_base.rs:487
- Duplicated block (6 lines × 2) fuzz/fuzz_targets/fuzz_redb.rs:394
- Duplicated block (6 lines × 2) fuzz/fuzz_targets/fuzz_redb.rs:694
- MutateHelper::apply_child_deletion_result (cognitive 138) src/tree_store/btree_mutator.rs:1504
- MutateHelper::insert_helper (cognitive 98) src/tree_store/btree_mutator.rs:743
- MutateHelper::splice_insert_run (cognitive 27) src/tree_store/btree_mutator.rs:484
- MutateHelper::replace_leaf_children (cognitive 24) src/tree_store/btree_mutator.rs:260
- MutateHelper::build_branch_nodes (cognitive 16) src/tree_store/btree_mutator.rs:600
- MethodTooLong: MutateHelper.insert_helper src/tree_store/btree_mutator.rs:743
- MethodTooLong: MutateHelper.apply_child_deletion_result src/tree_store/btree_mutator.rs:1504
- MethodTooLong: MultimapTable.insert_inner src/multimap_table.rs:595
- MethodTooLong: TransactionalMemory.new src/tree_store/page_store/page_manager.rs:1145
- MethodTooLong: MultimapTable.remove_inner src/multimap_table.rs:780
- Edited copy of a member (17 corresponding lines) src/transactions.rs:2778
- Edited copy of a member (17 corresponding lines) src/tree_store/btree_base.rs:593
- Edited copy of a member (17 corresponding lines) src/tree_store/table_tree.rs:521
- Edited copy of a member (17 corresponding lines) src/transactions.rs:534
- Edited copy of a member (17 corresponding lines) fuzz/fuzz_targets/fuzz_corruption.rs:312
- Duplicated block (10 lines × 2) src/db.rs:1625
- Duplicated block (10 lines × 2) src/transactions.rs:1062
- Duplicated block (10 lines × 2) src/tree_store/btree_base.rs:96
- Duplicated block (10 lines × 2) fuzz/fuzz_targets/fuzz_corruption.rs:262
- Duplicated block (10 lines × 2) fuzz/fuzz_targets/fuzz_redb.rs:168
- Duplicated block (7 lines × 2) src/transactions.rs:2362
- Duplicated block (7 lines × 2) src/tree_store/page_store/cached_file.rs:705
- Duplicated block (7 lines × 2) src/multimap_table.rs:1077
- Duplicated block (7 lines × 2) src/multimap_table.rs:1272
- Duplicated block (7 lines × 2) src/multimap_table.rs:1290
- Hotspot: src/db.rs src/db.rs:1045
- Hotspot: src/tree_store/page_store/page_manager.rs src/tree_store/page_store/page_manager.rs:713
- Hotspot: src/tree_store/page_store/cached_file.rs src/tree_store/page_store/cached_file.rs:696
- Hotspot: src/tree_store/btree_mutator.rs src/tree_store/btree_mutator.rs:743
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (4 corresponding lines) src/multimap_table.rs:1031
- Edited copy of a member (4 corresponding lines) src/multimap_table.rs:1250
- Edited copy of a member (4 corresponding lines) src/multimap_table.rs:1361
- Edited copy of a member (4 corresponding lines) src/tree_store/btree.rs:726
- Duplicated block (13 lines × 2) src/tree_store/page_store/page_manager.rs:2019
- Duplicated block (13 lines × 2) src/tree_store/table_tree.rs:763
- Duplicated block (13 lines × 2) src/tree_store/table_tree_base.rs:395
- Duplicated block (13 lines × 2) src/table.rs:329
- TodoComment src/tree_store/page_store/base.rs:24
- TodoComment src/tree_store/page_store/page_manager.rs:682
- TodoComment src/tree_store/page_store/file_backend/optimized.rs:451
- redb::table::debug_helper (cognitive 21) src/table.rs:592
- redb::tree_store::multimap_btree::relocate_subtrees (cognitive 18) src/tree_store/multimap_btree.rs:201
- redb::tree_store::multimap_btree::multimap_stats_helper (cognitive 17) src/tree_store/multimap_btree.rs:43
- Edited copy of a member (23 corresponding lines) src/tree_store/page_store/xxh3.rs:885
- Edited copy of a member (23 corresponding lines) src/tree_store/btree.rs:1136
- Edited copy of a member (23 corresponding lines) src/tree_store/table_tree.rs:203
- Edited copy of a member (22 corresponding lines) src/tree_store/page_store/xxh3.rs:374
- Edited copy of a member (22 corresponding lines) src/tree_store/btree_cursor.rs:1444
- Edited copy of a member (22 corresponding lines) src/multimap_table.rs:184
- Edited copy of a member (19 corresponding lines) src/tree_store/page_store/xxh3.rs:515
- Edited copy of a member (19 corresponding lines) src/tree_store/btree.rs:452
- Edited copy of a member (19 corresponding lines) src/tree_store/btree_cursor.rs:802
- Edited copy of a member (24 corresponding lines) src/tree_store/extract_if.rs:107
- Edited copy of a member (24 corresponding lines) src/tree_store/btree_base.rs:1145
- Edited copy of a member (24 corresponding lines) src/transactions.rs:2800
- Edited copy of a member (8 corresponding lines) src/tree_store/btree_base.rs:2182
- Edited copy of a member (8 corresponding lines) crates/redb-python/src/table.rs:316
- Edited copy of a member (8 corresponding lines) src/tree_store/page_store/page_manager.rs:1519
- Edited copy of a member (11 corresponding lines) src/tree_store/btree_cursor.rs:1918
- Edited copy of a member (11 corresponding lines) src/tree_store/page_store/page_manager.rs:994
- Edited copy of a member (11 corresponding lines) src/tree_store/btree.rs:390
- Duplicated block (16 lines × 2) src/multimap_table.rs:392
- Duplicated block (16 lines × 2) src/table.rs:444
- Duplicated block (16 lines × 2) src/tree_store/btree_mutator.rs:1669
- Duplicated block (14 lines × 2) src/tree_store/btree_mutator.rs:759
- Duplicated block (14 lines × 2) src/tree_store/btree.rs:1291
- Duplicated block (14 lines × 2) fuzz/fuzz_targets/fuzz_redb.rs:272
- MutateHelper::apply_child_deletion_result (cyclomatic 44) src/tree_store/btree_mutator.rs:1504
- MutateHelper::insert_helper (cyclomatic 39) src/tree_store/btree_mutator.rs:743
- Database::check_integrity_inner (cyclomatic 17) src/db.rs:1045
- Database::compact (cyclomatic 17) src/db.rs:1250
- redb_bench::benchmark (cognitive 51) crates/redb-bench/src/lib.rs:113
- redb_bench::print_results_table (cognitive 19) crates/redb-bench/src/lib.rs:782
- MultimapTable::insert_inner (cognitive 32) src/multimap_table.rs:595
- MultimapTable::remove_inner (cognitive 32) src/multimap_table.rs:780
- WriteTransaction::process_freed_pages_nondurable_helper (cognitive 30) src/transactions.rs:2470
- WriteTransaction::print_allocated_page_debug (cognitive 17) src/transactions.rs:1054
- BuddyAllocator::resize (cognitive 30) src/tree_store/page_store/buddy_allocator.rs:224
- BuddyAllocator::debug_check_consistency (cognitive 19) src/tree_store/page_store/buddy_allocator.rs:293
- PagedCachedFile::read (cognitive 30) src/tree_store/page_store/cached_file.rs:696
- PagedCachedFile::write (cognitive 30) src/tree_store/page_store/cached_file.rs:931
- Database::check_integrity_inner (cognitive 22) src/db.rs:1045
- Database::compact (cognitive 20) src/db.rs:1250
- Edited copy of a member (20 corresponding lines) src/tree_store/page_store/xxh3.rs:564
- Edited copy of a member (20 corresponding lines) fuzz/fuzz_targets/fuzz_redb.rs:167
- Edited copy of a member (21 corresponding lines) src/multimap_table.rs:258
- Edited copy of a member (21 corresponding lines) src/tree_store/btree_base.rs:544
- Edited copy of a member (15 corresponding lines) src/table.rs:1562
- Edited copy of a member (15 corresponding lines) src/transactions.rs:680
- Edited copy of a member (14 corresponding lines) src/table.rs:1903
- Edited copy of a member (14 corresponding lines) src/tree_store/btree_cursor.rs:909
- Edited copy of a member (18 corresponding lines) src/multimap_table.rs:390
- Edited copy of a member (18 corresponding lines) src/tree_store/page_store/file_backend/optimized.rs:388
- Edited copy of a member (13 corresponding lines) src/tree_store/btree.rs:529
- Edited copy of a member (13 corresponding lines) src/tree_store/btree_cursor.rs:1001
- Edited copy of a member (16 corresponding lines) src/tree_store/page_store/file_backend/fallback.rs:41
- Edited copy of a member (16 corresponding lines) src/db.rs:2373
- Edited copy of a member (12 corresponding lines) src/tree_store/btree_base.rs:1933
- Edited copy of a member (12 corresponding lines) src/multimap_table.rs:132
- Edited copy of a member (7 corresponding lines) src/db.rs:687
- Edited copy of a member (7 corresponding lines) src/table.rs:583
- Duplicated block (21 lines × 2) src/multimap_table.rs:1209
- Duplicated block (21 lines × 2) src/tree_store/btree.rs:1341
- Duplicated block (19–20 lines × 2) src/tree_store/btree_mutator.rs:944
- Duplicated block (19–20 lines × 2) fuzz/fuzz_targets/fuzz_redb.rs:895
- redb_bench::benchmark (cyclomatic 30) crates/redb-bench/src/lib.rs:113
- TransactionalMemory::lock_whole_storage (cyclomatic 18) src/tree_store/page_store/page_manager.rs:713
- PagedCachedFile::read (cyclomatic 17) src/tree_store/page_store/cached_file.rs:696
- XxxComment crates/redb-bench-compare/benches/common/mod.rs:19
- Allocators::resize_to (cognitive 23) src/tree_store/page_store/region.rs:141
- TransactionalMemory::lock_whole_storage (cognitive 22) src/tree_store/page_store/page_manager.rs:713
- RawBtree::verify_checksum_helper (cognitive 17) src/tree_store/btree.rs:953
- FunctionTooLong: redb_bench::benchmark crates/redb-bench/src/lib.rs:113
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/table.rs:328
- Edited copy of a member (32 corresponding lines) src/tree_store/table_tree.rs:421
- Edited copy of a member (28 corresponding lines) src/error.rs:333
- Edited copy of a member (26 corresponding lines) src/tree_store/btree_base.rs:80
- Edited copy of a member (31 corresponding lines) src/tree_store/page_store/file_backend/optimized.rs:454
- Edited copy of a member (25 corresponding lines) src/tree_store/page_store/xxh3.rs:187
- Edited copies of one member (3 members, 18+ corresponding lines) src/multimap_table.rs:975
- Edited copies of one member (3 members, 11+ corresponding lines) src/tree_store/btree_base.rs:1172
- Edited copy of a member (10 corresponding lines) src/table.rs:1223
- Edited copies of one member (4 members, 16+ corresponding lines) src/table.rs:1835
- Edited copies of one member (3 members, 9+ corresponding lines) fuzz/fuzz_targets/fuzz_corruption.rs:53
- Edited copies of one member (4 members, 10+ corresponding lines) src/multimap_table.rs:499
- Edited copies of one member (6 members, 6+ corresponding lines) src/table.rs:371
- Edited copy of a member (9 corresponding lines) src/tree_store/page_store/page_manager.rs:2504
- Edited copies of one member (4 members, 11+ corresponding lines) src/transactions.rs:738
- Edited copy of a member (6 corresponding lines) src/tree_store/btree_cursor.rs:230
- Edited copy of a member (5 corresponding lines) src/table.rs:967
- Duplicated block (26–28 lines × 3) src/tree_store/btree_mutator.rs:1640
- Duplicated block (10 lines × 4) src/table.rs:330
- Duplicated block (9–10 lines × 2) src/tree_store/btree.rs:1137
- Duplicated block (8 lines × 3) crates/redb-bench/src/lib.rs:399
- Duplicated block (5 lines × 3) src/tree_store/table_tree.rs:677
- Duplicated block (9 lines × 3) src/db.rs:346
- Duplicated block (6 lines × 3) src/table.rs:604
- Duplicated block (5 lines × 2) src/tree_store/page_store/xxh3.rs:657
- Duplicated block (12–14 lines × 2) fuzz/fuzz_targets/fuzz_corruption.rs:126
- Duplicated block (7–8 lines × 3) fuzz/fuzz_targets/fuzz_redb.rs:906
- End-of-life runtime: Rust 1.90 rust-toolchain:1
- Off the main sequence: redb
Minor — 5 finding(s)
- REDACTED
- REDACTED
- No ADRs found crates/redb-no-std-test/src/main.rs:1
- No ADRs
- Logging is not universal
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-06e5d0fb9f054a75934bcd4e90081b95/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-06e5d0fb9f054a75934bcd4e90081b95/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 9 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |