Executive summary
awslabs/mountpoint-s3 falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 66 out of 100 and is rated Adequate, and 25 of its 33 critical findings are security problems in its servers and containers and in the build pipeline.
Accessibility, at 57, is the weakest lens and counts most in the score. The best first steps are automating accessibility checks and structuring the pages, each worth about 6 points. Raising Accessibility to 70 would lift the score to about 71.
Fourteen settings leave the servers or containers unsafe. Five secrets can leak from the build pipeline, and four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Correcting the unsafe settings, limiting each secret to its own step and pinning each tool to an exact version would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and the pipeline step that runs a download without checking it needs each download checked against a known checksum first. The seven parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 57,525 lines, about €100,000 to rebuild.
If Accessibility rose from 57 to 70, the lowest score rated Strong, the score would rise from 66 to about 71.
New since the last survey: 6 findings
- Cognitive Complexity · MockBucket::list_objects_ordered (cognitive 19) mountpoint-s3-client/src/mock_client.rs
- Cognitive Complexity · MockBucket::append_object (cognitive 16) mountpoint-s3-client/src/mock_client.rs
- Explicit Debt · TodoComment mountpoint-s3-fs/src/superblock.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Knowledge Freshness · Orphaned knowledge mountpoint-s3-fs/src/metrics/data.rs
Fixed since the last survey: 6 findings
- Cyclomatic Complexity · Superblock::rename (cyclomatic 16) mountpoint-s3-fs/src/superblock.rs
- Cognitive Complexity · MockClient::list_objects_ordered (cognitive 19) mountpoint-s3-client/src/mock_client.rs
- God Classes · ClassTooLong: MockClient mountpoint-s3-client/src/mock_client.rs
- Explicit Debt · TodoComment mountpoint-s3-fs/src/superblock.rs
- Explicit Debt · TodoComment mountpoint-s3-fs/src/superblock.rs
- Change Coupling · Change coupling: throughput_client.rs ↔ get_object.rs mountpoint-s3-client/src/mock_client/throughput_client.rs
Rebuild cost: about €100,000 · Estimate
| Cost to rebuild | €35,000 to €170,000, for 576 to 1,826 hours of work, about 0.7 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 | ×0.9 at a score of 66. 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: 57,525 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 mountpoint_s3_client.object_client.etag | 2 mountpoint_s3_crt.checksums.crc32c | 3 mountpoint_s3_crt.common.allocator | 4 mountpoint_s3_crt.common.error | 5 mountpoint_s3_fs.async_util | 6 mountpoint_s3_fs.s3.path | 7 mountpoint_s3_fs.checksums | 8 mountpoint_s3_fs.memory.buffers | 9 mountpoint_s3_fs.metablock.stat | 10 mountpoint_s3_fs.object | 11 mountpoint_s3_fs.upload.atomic | 12 mountpoint_s3_fuser.ll.reply | 13 mountpoint_s3_fs.memory.pool | 14 mountpoint_s3_fs.metablock.path | 15 mountpoint_s3_fuser.ll.request | 16 mountpoint_s3_fs.memory.limiter | 17 mountpoint_s3_fs.metablock | 18 mountpoint_s3_fs.upload.incremental | 19 mountpoint_s3_fuser | 20 mountpoint_s3_fs.manifest.metablock | 21 mountpoint_s3_fs.prefetch.cursor | 22 mountpoint_s3_fs.prefetch.part_stream | 23 mountpoint_s3_fs.prefetch | 24 mountpoint_s3_fs.fs.config | 25 mountpoint_s3_fs.fs.error | 26 mountpoint_s3_fs.superblock | 27 mountpoint_s3_fs.upload | 28 mountpoint_s3_fs.fs | 29 mountpoint_s3_fs.fs.handles | 30 mountpoint_s3_fuser.ll.request.op | 31 mountpoint_s3_crt.io.event_loop | 32 mountpoint_s3_crt.s3.pool | 33 mountpoint_s3_crt.s3.client | 34 mountpoint_s3_client.object_client | 35 mountpoint_s3_fs.prefetch.caching_stream | 36 mountpoint_s3_client.s3_crt_client | 37 mountpoint_s3_fs.data_cache.express_data_cache | 38 mountpoint_s3_fs.data_cache | 39 mountpoint_s3_fs.data_cache.disk_data_cache | 40 mountpoint_s3.cli |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 mountpoint_s3_client.object_client.etag | ||||||||||||||||||||||||||||||||||||||||
| 2 mountpoint_s3_crt.checksums.crc32c | ||||||||||||||||||||||||||||||||||||||||
| 3 mountpoint_s3_crt.common.allocator | ||||||||||||||||||||||||||||||||||||||||
| 4 mountpoint_s3_crt.common.error | ||||||||||||||||||||||||||||||||||||||||
| 5 mountpoint_s3_fs.async_util | ||||||||||||||||||||||||||||||||||||||||
| 6 mountpoint_s3_fs.s3.path | ||||||||||||||||||||||||||||||||||||||||
| 7 mountpoint_s3_fs.checksums | 4 | |||||||||||||||||||||||||||||||||||||||
| 8 mountpoint_s3_fs.memory.buffers | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 mountpoint_s3_fs.metablock.stat | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 mountpoint_s3_fs.object | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 mountpoint_s3_fs.upload.atomic | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 mountpoint_s3_fuser.ll.reply | 5 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 mountpoint_s3_fs.memory.pool | 3 | 3 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 14 mountpoint_s3_fs.metablock.path | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 mountpoint_s3_fuser.ll.request | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 mountpoint_s3_fs.memory.limiter | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 17 mountpoint_s3_fs.metablock | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 mountpoint_s3_fs.upload.incremental | 2 | 2 | 1 | 2 | 5 | 1 | ||||||||||||||||||||||||||||||||||
| 19 mountpoint_s3_fuser | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 mountpoint_s3_fs.manifest.metablock | 1 | 1 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 21 mountpoint_s3_fs.prefetch.cursor | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 mountpoint_s3_fs.prefetch.part_stream | 1 | 3 | 3 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 23 mountpoint_s3_fs.prefetch | 2 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 24 mountpoint_s3_fs.fs.config | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 mountpoint_s3_fs.fs.error | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 mountpoint_s3_fs.superblock | 1 | 3 | 5 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 27 mountpoint_s3_fs.upload | 1 | 1 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 28 mountpoint_s3_fs.fs | 1 | 1 | 1 | 5 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 29 mountpoint_s3_fs.fs.handles | 1 | 1 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 30 mountpoint_s3_fuser.ll.request.op | 2 | 164 | 1 | 19 | ||||||||||||||||||||||||||||||||||||
| 31 mountpoint_s3_crt.io.event_loop | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 mountpoint_s3_crt.s3.pool | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 33 mountpoint_s3_crt.s3.client | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 mountpoint_s3_client.object_client | 5 | 5 | ||||||||||||||||||||||||||||||||||||||
| 35 mountpoint_s3_fs.prefetch.caching_stream | 3 | 2 | 2 | 1 | 6 | 2 | ||||||||||||||||||||||||||||||||||
| 36 mountpoint_s3_client.s3_crt_client | 2 | 1 | 2 | 1 | 9 | 8 | ||||||||||||||||||||||||||||||||||
| 37 mountpoint_s3_fs.data_cache.express_data_cache | 1 | 1 | 3 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 38 mountpoint_s3_fs.data_cache | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 39 mountpoint_s3_fs.data_cache.disk_data_cache | 1 | 2 | 4 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 40 mountpoint_s3.cli | 1 | 3 | 1 | 1 |
7→2 mountpoint_s3_fs.checksums uses mountpoint_s3_crt.checksums.crc32c✕
- Connections
- 4 pairs of types, where a type in mountpoint_s3_fs.checksums uses a type in mountpoint_s3_crt.checksums.crc32c.
- The types involved
mountpoint_s3_fs.checksums.ChecksummedBytes→mountpoint_s3_crt.checksums.crc32c.Crc32cmountpoint_s3_fs.checksums.ChecksummedBytesBuilder→mountpoint_s3_crt.checksums.crc32c.Crc32cmountpoint_s3_fs.checksums.Crc32cBase64→mountpoint_s3_crt.checksums.crc32c.Crc32cmountpoint_s3_fs.checksums.checksums$module→mountpoint_s3_crt.checksums.crc32c.Crc32c
- Direction
- mountpoint_s3_fs.checksums uses mountpoint_s3_crt.checksums.crc32c, so a change to mountpoint_s3_crt.checksums.crc32c can break mountpoint_s3_fs.checksums, while a change to mountpoint_s3_fs.checksums can't break mountpoint_s3_crt.checksums.crc32c.
- Position
- Below the diagonal: mountpoint_s3_fs.checksums uses a module listed above it, which is the healthy direction.
8→16 mountpoint_s3_fs.memory.buffers uses mountpoint_s3_fs.memory.limiter part of a loop✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.memory.buffers uses a type in mountpoint_s3_fs.memory.limiter.
- The types involved
mountpoint_s3_fs.memory.buffers.ManagedBuffer→mountpoint_s3_fs.memory.limiter.MemoryLimitermountpoint_s3_fs.memory.buffers.PoolBuffer→mountpoint_s3_fs.memory.limiter.MemoryLimiter
- Direction
- mountpoint_s3_fs.memory.buffers uses mountpoint_s3_fs.memory.limiter, so a change to mountpoint_s3_fs.memory.limiter can break mountpoint_s3_fs.memory.buffers, while a change to mountpoint_s3_fs.memory.buffers can't break mountpoint_s3_fs.memory.limiter.
- 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→34 mountpoint_s3_fs.metablock.stat uses mountpoint_s3_client.object_client part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.metablock.stat uses a type in mountpoint_s3_client.object_client.
- The types involved
mountpoint_s3_fs.metablock.stat.InodeStat→mountpoint_s3_client.object_client.RestoreStatus
- Direction
- mountpoint_s3_fs.metablock.stat uses mountpoint_s3_client.object_client, so a change to mountpoint_s3_client.object_client can break mountpoint_s3_fs.metablock.stat, while a change to mountpoint_s3_fs.metablock.stat can't break mountpoint_s3_client.object_client.
- 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→1 mountpoint_s3_fs.object uses mountpoint_s3_client.object_client.etag✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.object uses a type in mountpoint_s3_client.object_client.etag.
- The types involved
mountpoint_s3_fs.object.InnerObjectId→mountpoint_s3_client.object_client.etag.ETagmountpoint_s3_fs.object.ObjectId→mountpoint_s3_client.object_client.etag.ETag
- Direction
- mountpoint_s3_fs.object uses mountpoint_s3_client.object_client.etag, so a change to mountpoint_s3_client.object_client.etag can break mountpoint_s3_fs.object, while a change to mountpoint_s3_fs.object can't break mountpoint_s3_client.object_client.etag.
- Position
- Below the diagonal: mountpoint_s3_fs.object uses a module listed above it, which is the healthy direction.
11→2 mountpoint_s3_fs.upload.atomic uses mountpoint_s3_crt.checksums.crc32c✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.upload.atomic uses a type in mountpoint_s3_crt.checksums.crc32c.
- The types involved
mountpoint_s3_fs.upload.atomic.atomic$module→mountpoint_s3_crt.checksums.crc32c.Crc32c
- Direction
- mountpoint_s3_fs.upload.atomic uses mountpoint_s3_crt.checksums.crc32c, so a change to mountpoint_s3_crt.checksums.crc32c can break mountpoint_s3_fs.upload.atomic, while a change to mountpoint_s3_fs.upload.atomic can't break mountpoint_s3_crt.checksums.crc32c.
- Position
- Below the diagonal: mountpoint_s3_fs.upload.atomic uses a module listed above it, which is the healthy direction.
11→5 mountpoint_s3_fs.upload.atomic uses mountpoint_s3_fs.async_util✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.upload.atomic uses a type in mountpoint_s3_fs.async_util.
- The types involved
mountpoint_s3_fs.upload.atomic.UploadRequest→mountpoint_s3_fs.async_util.RemoteResultmountpoint_s3_fs.upload.atomic.UploadRequest→mountpoint_s3_fs.async_util.Runtime
- Direction
- mountpoint_s3_fs.upload.atomic uses mountpoint_s3_fs.async_util, so a change to mountpoint_s3_fs.async_util can break mountpoint_s3_fs.upload.atomic, while a change to mountpoint_s3_fs.upload.atomic can't break mountpoint_s3_fs.async_util.
- Position
- Below the diagonal: mountpoint_s3_fs.upload.atomic uses a module listed above it, which is the healthy direction.
11→33 mountpoint_s3_fs.upload.atomic uses mountpoint_s3_crt.s3.client part of a loop✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.upload.atomic uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_fs.upload.atomic.UploadRequest→mountpoint_s3_crt.s3.client.Clientmountpoint_s3_fs.upload.atomic.UploadRequestParams→mountpoint_s3_crt.s3.client.ChecksumAlgorithmmountpoint_s3_fs.upload.atomic.atomic$module→mountpoint_s3_crt.s3.client.UploadReview
- Direction
- mountpoint_s3_fs.upload.atomic uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_fs.upload.atomic, while a change to mountpoint_s3_fs.upload.atomic can't break mountpoint_s3_crt.s3.client.
- 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→34 mountpoint_s3_fs.upload.atomic uses mountpoint_s3_client.object_client part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.upload.atomic uses a type in mountpoint_s3_client.object_client.
- The types involved
mountpoint_s3_fs.upload.atomic.atomic$module→mountpoint_s3_client.object_client.UploadChecksum
- Direction
- mountpoint_s3_fs.upload.atomic uses mountpoint_s3_client.object_client, so a change to mountpoint_s3_client.object_client can break mountpoint_s3_fs.upload.atomic, while a change to mountpoint_s3_fs.upload.atomic can't break mountpoint_s3_client.object_client.
- 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→15 mountpoint_s3_fuser.ll.reply uses mountpoint_s3_fuser.ll.request part of a loop✕
- Connections
- 5 pairs of types, where a type in mountpoint_s3_fuser.ll.reply uses a type in mountpoint_s3_fuser.ll.request.
- The types involved
mountpoint_s3_fuser.ll.reply.DirEntry→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.reply.DirEntryPlus→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.reply.Response→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.reply.Response→mountpoint_s3_fuser.ll.request.Lockmountpoint_s3_fuser.ll.reply.Response→mountpoint_s3_fuser.ll.request.RequestId
- Direction
- mountpoint_s3_fuser.ll.reply uses mountpoint_s3_fuser.ll.request, so a change to mountpoint_s3_fuser.ll.request can break mountpoint_s3_fuser.ll.reply, while a change to mountpoint_s3_fuser.ll.reply can't break mountpoint_s3_fuser.ll.request.
- 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→19 mountpoint_s3_fuser.ll.reply uses mountpoint_s3_fuser part of a loop✕
- Connections
- 4 pairs of types, where a type in mountpoint_s3_fuser.ll.reply uses a type in mountpoint_s3_fuser.
- The types involved
mountpoint_s3_fuser.ll.reply.Attr→mountpoint_s3_fuser.FileAttrmountpoint_s3_fuser.ll.reply.DirEntry→mountpoint_s3_fuser.FileTypemountpoint_s3_fuser.ll.reply.reply$module→mountpoint_s3_fuser.FileAttrmountpoint_s3_fuser.ll.reply.reply$module→mountpoint_s3_fuser.FileType
- Direction
- mountpoint_s3_fuser.ll.reply uses mountpoint_s3_fuser, so a change to mountpoint_s3_fuser can break mountpoint_s3_fuser.ll.reply, while a change to mountpoint_s3_fuser.ll.reply can't break mountpoint_s3_fuser.
- 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→28 mountpoint_s3_fuser.ll.reply uses mountpoint_s3_fs.fs part of a loop✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fuser.ll.reply uses a type in mountpoint_s3_fs.fs.
- The types involved
mountpoint_s3_fuser.ll.reply.DirEntryPlus→mountpoint_s3_fs.fs.Attrmountpoint_s3_fuser.ll.reply.Response→mountpoint_s3_fs.fs.Attr
- Direction
- mountpoint_s3_fuser.ll.reply uses mountpoint_s3_fs.fs, so a change to mountpoint_s3_fs.fs can break mountpoint_s3_fuser.ll.reply, while a change to mountpoint_s3_fuser.ll.reply can't break mountpoint_s3_fs.fs.
- 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→29 mountpoint_s3_fuser.ll.reply uses mountpoint_s3_fs.fs.handles part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fuser.ll.reply uses a type in mountpoint_s3_fs.fs.handles.
- The types involved
mountpoint_s3_fuser.ll.reply.Response→mountpoint_s3_fs.fs.handles.FileHandle
- Direction
- mountpoint_s3_fuser.ll.reply uses mountpoint_s3_fs.fs.handles, so a change to mountpoint_s3_fs.fs.handles can break mountpoint_s3_fuser.ll.reply, while a change to mountpoint_s3_fuser.ll.reply can't break mountpoint_s3_fs.fs.handles.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→8 mountpoint_s3_fs.memory.pool uses mountpoint_s3_fs.memory.buffers✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.memory.pool uses a type in mountpoint_s3_fs.memory.buffers.
- The types involved
mountpoint_s3_fs.memory.pool.PagedPool→mountpoint_s3_fs.memory.buffers.PoolBuffermountpoint_s3_fs.memory.pool.PagedPool→mountpoint_s3_fs.memory.buffers.PoolBufferMutmountpoint_s3_fs.memory.pool.PagedPoolInner→mountpoint_s3_fs.memory.buffers.PoolBuffer
- Direction
- mountpoint_s3_fs.memory.pool uses mountpoint_s3_fs.memory.buffers, so a change to mountpoint_s3_fs.memory.buffers can break mountpoint_s3_fs.memory.pool, while a change to mountpoint_s3_fs.memory.pool can't break mountpoint_s3_fs.memory.buffers.
- Position
- Below the diagonal: mountpoint_s3_fs.memory.pool uses a module listed above it, which is the healthy direction.
13→16 mountpoint_s3_fs.memory.pool uses mountpoint_s3_fs.memory.limiter part of a loop✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.memory.pool uses a type in mountpoint_s3_fs.memory.limiter.
- The types involved
mountpoint_s3_fs.memory.pool.PagedPool→mountpoint_s3_fs.memory.limiter.CursorHandlemountpoint_s3_fs.memory.pool.PagedPool→mountpoint_s3_fs.memory.limiter.MemoryLimitermountpoint_s3_fs.memory.pool.PagedPoolInner→mountpoint_s3_fs.memory.limiter.MemoryLimiter
- Direction
- mountpoint_s3_fs.memory.pool uses mountpoint_s3_fs.memory.limiter, so a change to mountpoint_s3_fs.memory.limiter can break mountpoint_s3_fs.memory.pool, while a change to mountpoint_s3_fs.memory.pool can't break mountpoint_s3_fs.memory.limiter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→21 mountpoint_s3_fs.memory.pool uses mountpoint_s3_fs.prefetch.cursor part of a loop✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.memory.pool uses a type in mountpoint_s3_fs.prefetch.cursor.
- The types involved
mountpoint_s3_fs.memory.pool.PagedPool→mountpoint_s3_fs.prefetch.cursor.CursorIdmountpoint_s3_fs.memory.pool.PagedPoolInner→mountpoint_s3_fs.prefetch.cursor.CursorId
- Direction
- mountpoint_s3_fs.memory.pool uses mountpoint_s3_fs.prefetch.cursor, so a change to mountpoint_s3_fs.prefetch.cursor can break mountpoint_s3_fs.memory.pool, while a change to mountpoint_s3_fs.memory.pool can't break mountpoint_s3_fs.prefetch.cursor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→32 mountpoint_s3_fs.memory.pool uses mountpoint_s3_crt.s3.pool part of a loop✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.memory.pool uses a type in mountpoint_s3_crt.s3.pool.
- The types involved
mountpoint_s3_fs.memory.pool.PagedPool→mountpoint_s3_crt.s3.pool.CancellationTokenmountpoint_s3_fs.memory.pool.PagedPool→mountpoint_s3_crt.s3.pool.MemoryPoolmountpoint_s3_fs.memory.pool.PagedPoolInner→mountpoint_s3_crt.s3.pool.CancellationToken
- Direction
- mountpoint_s3_fs.memory.pool uses mountpoint_s3_crt.s3.pool, so a change to mountpoint_s3_crt.s3.pool can break mountpoint_s3_fs.memory.pool, while a change to mountpoint_s3_fs.memory.pool can't break mountpoint_s3_crt.s3.pool.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→33 mountpoint_s3_fs.memory.pool uses mountpoint_s3_crt.s3.client part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.memory.pool uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_fs.memory.pool.PagedPool→mountpoint_s3_crt.s3.client.MetaRequest
- Direction
- mountpoint_s3_fs.memory.pool uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_fs.memory.pool, while a change to mountpoint_s3_fs.memory.pool can't break mountpoint_s3_crt.s3.client.
- 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→6 mountpoint_s3_fs.metablock.path uses mountpoint_s3_fs.s3.path✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.metablock.path uses a type in mountpoint_s3_fs.s3.path.
- The types involved
mountpoint_s3_fs.metablock.path.S3Location→mountpoint_s3_fs.s3.path.S3Path
- Direction
- mountpoint_s3_fs.metablock.path uses mountpoint_s3_fs.s3.path, so a change to mountpoint_s3_fs.s3.path can break mountpoint_s3_fs.metablock.path, while a change to mountpoint_s3_fs.metablock.path can't break mountpoint_s3_fs.s3.path.
- Position
- Below the diagonal: mountpoint_s3_fs.metablock.path uses a module listed above it, which is the healthy direction.
14→9 mountpoint_s3_fs.metablock.path uses mountpoint_s3_fs.metablock.stat✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.metablock.path uses a type in mountpoint_s3_fs.metablock.stat.
- The types involved
mountpoint_s3_fs.metablock.path.ValidKey→mountpoint_s3_fs.metablock.stat.InodeKind
- Direction
- mountpoint_s3_fs.metablock.path uses mountpoint_s3_fs.metablock.stat, so a change to mountpoint_s3_fs.metablock.stat can break mountpoint_s3_fs.metablock.path, while a change to mountpoint_s3_fs.metablock.path can't break mountpoint_s3_fs.metablock.stat.
- Position
- Below the diagonal: mountpoint_s3_fs.metablock.path uses a module listed above it, which is the healthy direction.
15→4 mountpoint_s3_fuser.ll.request uses mountpoint_s3_crt.common.error✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fuser.ll.request uses a type in mountpoint_s3_crt.common.error.
- The types involved
mountpoint_s3_fuser.ll.request.RequestError→mountpoint_s3_crt.common.error.Error
- Direction
- mountpoint_s3_fuser.ll.request uses mountpoint_s3_crt.common.error, so a change to mountpoint_s3_crt.common.error can break mountpoint_s3_fuser.ll.request, while a change to mountpoint_s3_fuser.ll.request can't break mountpoint_s3_crt.common.error.
- Position
- Below the diagonal: mountpoint_s3_fuser.ll.request uses a module listed above it, which is the healthy direction.
15→12 mountpoint_s3_fuser.ll.request uses mountpoint_s3_fuser.ll.reply✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fuser.ll.request uses a type in mountpoint_s3_fuser.ll.reply.
- The types involved
mountpoint_s3_fuser.ll.request.Request→mountpoint_s3_fuser.ll.reply.Response
- Direction
- mountpoint_s3_fuser.ll.request uses mountpoint_s3_fuser.ll.reply, so a change to mountpoint_s3_fuser.ll.reply can break mountpoint_s3_fuser.ll.request, while a change to mountpoint_s3_fuser.ll.request can't break mountpoint_s3_fuser.ll.reply.
- Position
- Below the diagonal: mountpoint_s3_fuser.ll.request uses a module listed above it, which is the healthy direction.
16→8 mountpoint_s3_fs.memory.limiter uses mountpoint_s3_fs.memory.buffers✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.memory.limiter uses a type in mountpoint_s3_fs.memory.buffers.
- The types involved
mountpoint_s3_fs.memory.limiter.MemoryLimiter→mountpoint_s3_fs.memory.buffers.BufferPtrmountpoint_s3_fs.memory.limiter.MemoryLimiter→mountpoint_s3_fs.memory.buffers.ManagedBuffer
- Direction
- mountpoint_s3_fs.memory.limiter uses mountpoint_s3_fs.memory.buffers, so a change to mountpoint_s3_fs.memory.buffers can break mountpoint_s3_fs.memory.limiter, while a change to mountpoint_s3_fs.memory.limiter can't break mountpoint_s3_fs.memory.buffers.
- Position
- Below the diagonal: mountpoint_s3_fs.memory.limiter uses a module listed above it, which is the healthy direction.
16→13 mountpoint_s3_fs.memory.limiter uses mountpoint_s3_fs.memory.pool✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.memory.limiter uses a type in mountpoint_s3_fs.memory.pool.
- The types involved
mountpoint_s3_fs.memory.limiter.CursorState→mountpoint_s3_fs.memory.pool.PagedPoolmountpoint_s3_fs.memory.limiter.MemoryLimiter→mountpoint_s3_fs.memory.pool.PagedPool
- Direction
- mountpoint_s3_fs.memory.limiter uses mountpoint_s3_fs.memory.pool, so a change to mountpoint_s3_fs.memory.pool can break mountpoint_s3_fs.memory.limiter, while a change to mountpoint_s3_fs.memory.limiter can't break mountpoint_s3_fs.memory.pool.
- Position
- Below the diagonal: mountpoint_s3_fs.memory.limiter uses a module listed above it, which is the healthy direction.
16→21 mountpoint_s3_fs.memory.limiter uses mountpoint_s3_fs.prefetch.cursor part of a loop✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.memory.limiter uses a type in mountpoint_s3_fs.prefetch.cursor.
- The types involved
mountpoint_s3_fs.memory.limiter.CursorHandle→mountpoint_s3_fs.prefetch.cursor.CursorIdmountpoint_s3_fs.memory.limiter.CursorState→mountpoint_s3_fs.prefetch.cursor.CursorIdmountpoint_s3_fs.memory.limiter.MemoryLimiter→mountpoint_s3_fs.prefetch.cursor.CursorId
- Direction
- mountpoint_s3_fs.memory.limiter uses mountpoint_s3_fs.prefetch.cursor, so a change to mountpoint_s3_fs.prefetch.cursor can break mountpoint_s3_fs.memory.limiter, while a change to mountpoint_s3_fs.memory.limiter can't break mountpoint_s3_fs.prefetch.cursor.
- 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→1 mountpoint_s3_fs.metablock uses mountpoint_s3_client.object_client.etag✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.metablock uses a type in mountpoint_s3_client.object_client.etag.
- The types involved
mountpoint_s3_fs.metablock.Metablock→mountpoint_s3_client.object_client.etag.ETag
- Direction
- mountpoint_s3_fs.metablock uses mountpoint_s3_client.object_client.etag, so a change to mountpoint_s3_client.object_client.etag can break mountpoint_s3_fs.metablock, while a change to mountpoint_s3_fs.metablock can't break mountpoint_s3_client.object_client.etag.
- Position
- Below the diagonal: mountpoint_s3_fs.metablock uses a module listed above it, which is the healthy direction.
17→9 mountpoint_s3_fs.metablock uses mountpoint_s3_fs.metablock.stat✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.metablock uses a type in mountpoint_s3_fs.metablock.stat.
- The types involved
mountpoint_s3_fs.metablock.Metablock→mountpoint_s3_fs.metablock.stat.InodeKind
- Direction
- mountpoint_s3_fs.metablock uses mountpoint_s3_fs.metablock.stat, so a change to mountpoint_s3_fs.metablock.stat can break mountpoint_s3_fs.metablock, while a change to mountpoint_s3_fs.metablock can't break mountpoint_s3_fs.metablock.stat.
- Position
- Below the diagonal: mountpoint_s3_fs.metablock uses a module listed above it, which is the healthy direction.
17→14 mountpoint_s3_fs.metablock uses mountpoint_s3_fs.metablock.path✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.metablock uses a type in mountpoint_s3_fs.metablock.path.
- The types involved
mountpoint_s3_fs.metablock.Metablock→mountpoint_s3_fs.metablock.path.S3Location
- Direction
- mountpoint_s3_fs.metablock uses mountpoint_s3_fs.metablock.path, so a change to mountpoint_s3_fs.metablock.path can break mountpoint_s3_fs.metablock, while a change to mountpoint_s3_fs.metablock can't break mountpoint_s3_fs.metablock.path.
- Position
- Below the diagonal: mountpoint_s3_fs.metablock uses a module listed above it, which is the healthy direction.
18→1 mountpoint_s3_fs.upload.incremental uses mountpoint_s3_client.object_client.etag✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.upload.incremental uses a type in mountpoint_s3_client.object_client.etag.
- The types involved
mountpoint_s3_fs.upload.incremental.AppendUploadQueueParams→mountpoint_s3_client.object_client.etag.ETagmountpoint_s3_fs.upload.incremental.incremental$module→mountpoint_s3_client.object_client.etag.ETag
- Direction
- mountpoint_s3_fs.upload.incremental uses mountpoint_s3_client.object_client.etag, so a change to mountpoint_s3_client.object_client.etag can break mountpoint_s3_fs.upload.incremental, while a change to mountpoint_s3_fs.upload.incremental can't break mountpoint_s3_client.object_client.etag.
- Position
- Below the diagonal: mountpoint_s3_fs.upload.incremental uses a module listed above it, which is the healthy direction.
18→5 mountpoint_s3_fs.upload.incremental uses mountpoint_s3_fs.async_util✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.upload.incremental uses a type in mountpoint_s3_fs.async_util.
- The types involved
mountpoint_s3_fs.upload.incremental.AppendUploadQueue→mountpoint_s3_fs.async_util.Runtimemountpoint_s3_fs.upload.incremental.AppendUploadRequest→mountpoint_s3_fs.async_util.Runtime
- Direction
- mountpoint_s3_fs.upload.incremental uses mountpoint_s3_fs.async_util, so a change to mountpoint_s3_fs.async_util can break mountpoint_s3_fs.upload.incremental, while a change to mountpoint_s3_fs.upload.incremental can't break mountpoint_s3_fs.async_util.
- Position
- Below the diagonal: mountpoint_s3_fs.upload.incremental uses a module listed above it, which is the healthy direction.
18→8 mountpoint_s3_fs.upload.incremental uses mountpoint_s3_fs.memory.buffers✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.upload.incremental uses a type in mountpoint_s3_fs.memory.buffers.
- The types involved
mountpoint_s3_fs.upload.incremental.UploadBuffer→mountpoint_s3_fs.memory.buffers.PoolBufferMut
- Direction
- mountpoint_s3_fs.upload.incremental uses mountpoint_s3_fs.memory.buffers, so a change to mountpoint_s3_fs.memory.buffers can break mountpoint_s3_fs.upload.incremental, while a change to mountpoint_s3_fs.upload.incremental can't break mountpoint_s3_fs.memory.buffers.
- Position
- Below the diagonal: mountpoint_s3_fs.upload.incremental uses a module listed above it, which is the healthy direction.
18→13 mountpoint_s3_fs.upload.incremental uses mountpoint_s3_fs.memory.pool✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.upload.incremental uses a type in mountpoint_s3_fs.memory.pool.
- The types involved
mountpoint_s3_fs.upload.incremental.AppendUploadQueue→mountpoint_s3_fs.memory.pool.PagedPoolmountpoint_s3_fs.upload.incremental.AppendUploadRequest→mountpoint_s3_fs.memory.pool.PagedPool
- Direction
- mountpoint_s3_fs.upload.incremental uses mountpoint_s3_fs.memory.pool, so a change to mountpoint_s3_fs.memory.pool can break mountpoint_s3_fs.upload.incremental, while a change to mountpoint_s3_fs.upload.incremental can't break mountpoint_s3_fs.memory.pool.
- Position
- Below the diagonal: mountpoint_s3_fs.upload.incremental uses a module listed above it, which is the healthy direction.
18→33 mountpoint_s3_fs.upload.incremental uses mountpoint_s3_crt.s3.client part of a loop✕
- Connections
- 5 pairs of types, where a type in mountpoint_s3_fs.upload.incremental uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_fs.upload.incremental.AppendUploadQueue→mountpoint_s3_crt.s3.client.ChecksumAlgorithmmountpoint_s3_fs.upload.incremental.AppendUploadQueue→mountpoint_s3_crt.s3.client.Clientmountpoint_s3_fs.upload.incremental.AppendUploadQueueParams→mountpoint_s3_crt.s3.client.ChecksumAlgorithmmountpoint_s3_fs.upload.incremental.AppendUploadRequest→mountpoint_s3_crt.s3.client.Clientmountpoint_s3_fs.upload.incremental.incremental$module→mountpoint_s3_crt.s3.client.Client
- Direction
- mountpoint_s3_fs.upload.incremental uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_fs.upload.incremental, while a change to mountpoint_s3_fs.upload.incremental can't break mountpoint_s3_crt.s3.client.
- 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→34 mountpoint_s3_fs.upload.incremental uses mountpoint_s3_client.object_client part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.upload.incremental uses a type in mountpoint_s3_client.object_client.
- The types involved
mountpoint_s3_fs.upload.incremental.AppendUploadQueue→mountpoint_s3_client.object_client.PutObjectResult
- Direction
- mountpoint_s3_fs.upload.incremental uses mountpoint_s3_client.object_client, so a change to mountpoint_s3_client.object_client can break mountpoint_s3_fs.upload.incremental, while a change to mountpoint_s3_fs.upload.incremental can't break mountpoint_s3_client.object_client.
- 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→9 mountpoint_s3_fuser uses mountpoint_s3_fs.metablock.stat✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fuser uses a type in mountpoint_s3_fs.metablock.stat.
- The types involved
mountpoint_s3_fuser.FileType→mountpoint_s3_fs.metablock.stat.InodeKind
- Direction
- mountpoint_s3_fuser uses mountpoint_s3_fs.metablock.stat, so a change to mountpoint_s3_fs.metablock.stat can break mountpoint_s3_fuser, while a change to mountpoint_s3_fuser can't break mountpoint_s3_fs.metablock.stat.
- Position
- Below the diagonal: mountpoint_s3_fuser uses a module listed above it, which is the healthy direction.
19→15 mountpoint_s3_fuser uses mountpoint_s3_fuser.ll.request✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fuser uses a type in mountpoint_s3_fuser.ll.request.
- The types involved
mountpoint_s3_fuser.Filesystem→mountpoint_s3_fuser.ll.request.Request
- Direction
- mountpoint_s3_fuser uses mountpoint_s3_fuser.ll.request, so a change to mountpoint_s3_fuser.ll.request can break mountpoint_s3_fuser, while a change to mountpoint_s3_fuser can't break mountpoint_s3_fuser.ll.request.
- Position
- Below the diagonal: mountpoint_s3_fuser uses a module listed above it, which is the healthy direction.
20→1 mountpoint_s3_fs.manifest.metablock uses mountpoint_s3_client.object_client.etag✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.manifest.metablock uses a type in mountpoint_s3_client.object_client.etag.
- The types involved
mountpoint_s3_fs.manifest.metablock.ManifestMetablock→mountpoint_s3_client.object_client.etag.ETag
- Direction
- mountpoint_s3_fs.manifest.metablock uses mountpoint_s3_client.object_client.etag, so a change to mountpoint_s3_client.object_client.etag can break mountpoint_s3_fs.manifest.metablock, while a change to mountpoint_s3_fs.manifest.metablock can't break mountpoint_s3_client.object_client.etag.
- Position
- Below the diagonal: mountpoint_s3_fs.manifest.metablock uses a module listed above it, which is the healthy direction.
20→6 mountpoint_s3_fs.manifest.metablock uses mountpoint_s3_fs.s3.path✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.manifest.metablock uses a type in mountpoint_s3_fs.s3.path.
- The types involved
mountpoint_s3_fs.manifest.metablock.ManifestMetablock→mountpoint_s3_fs.s3.path.S3Path
- Direction
- mountpoint_s3_fs.manifest.metablock uses mountpoint_s3_fs.s3.path, so a change to mountpoint_s3_fs.s3.path can break mountpoint_s3_fs.manifest.metablock, while a change to mountpoint_s3_fs.manifest.metablock can't break mountpoint_s3_fs.s3.path.
- Position
- Below the diagonal: mountpoint_s3_fs.manifest.metablock uses a module listed above it, which is the healthy direction.
20→9 mountpoint_s3_fs.manifest.metablock uses mountpoint_s3_fs.metablock.stat✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.manifest.metablock uses a type in mountpoint_s3_fs.metablock.stat.
- The types involved
mountpoint_s3_fs.manifest.metablock.ManifestMetablock→mountpoint_s3_fs.metablock.stat.InodeKindmountpoint_s3_fs.manifest.metablock.ManifestMetablock→mountpoint_s3_fs.metablock.stat.InodeStat
- Direction
- mountpoint_s3_fs.manifest.metablock uses mountpoint_s3_fs.metablock.stat, so a change to mountpoint_s3_fs.metablock.stat can break mountpoint_s3_fs.manifest.metablock, while a change to mountpoint_s3_fs.manifest.metablock can't break mountpoint_s3_fs.metablock.stat.
- Position
- Below the diagonal: mountpoint_s3_fs.manifest.metablock uses a module listed above it, which is the healthy direction.
20→14 mountpoint_s3_fs.manifest.metablock uses mountpoint_s3_fs.metablock.path✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.manifest.metablock uses a type in mountpoint_s3_fs.metablock.path.
- The types involved
mountpoint_s3_fs.manifest.metablock.ManifestMetablock→mountpoint_s3_fs.metablock.path.S3Location
- Direction
- mountpoint_s3_fs.manifest.metablock uses mountpoint_s3_fs.metablock.path, so a change to mountpoint_s3_fs.metablock.path can break mountpoint_s3_fs.manifest.metablock, while a change to mountpoint_s3_fs.manifest.metablock can't break mountpoint_s3_fs.metablock.path.
- Position
- Below the diagonal: mountpoint_s3_fs.manifest.metablock uses a module listed above it, which is the healthy direction.
20→17 mountpoint_s3_fs.manifest.metablock uses mountpoint_s3_fs.metablock✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.manifest.metablock uses a type in mountpoint_s3_fs.metablock.
- The types involved
mountpoint_s3_fs.manifest.metablock.ManifestMetablock→mountpoint_s3_fs.metablock.Metablockmountpoint_s3_fs.manifest.metablock.ManifestMetablock→mountpoint_s3_fs.metablock.ReadWriteModemountpoint_s3_fs.manifest.metablock.ManifestMetablock→mountpoint_s3_fs.metablock.WriteMode
- Direction
- mountpoint_s3_fs.manifest.metablock uses mountpoint_s3_fs.metablock, so a change to mountpoint_s3_fs.metablock can break mountpoint_s3_fs.manifest.metablock, while a change to mountpoint_s3_fs.manifest.metablock can't break mountpoint_s3_fs.metablock.
- Position
- Below the diagonal: mountpoint_s3_fs.manifest.metablock uses a module listed above it, which is the healthy direction.
21→10 mountpoint_s3_fs.prefetch.cursor uses mountpoint_s3_fs.object✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.prefetch.cursor uses a type in mountpoint_s3_fs.object.
- The types involved
mountpoint_s3_fs.prefetch.cursor.Cursor→mountpoint_s3_fs.object.ObjectId
- Direction
- mountpoint_s3_fs.prefetch.cursor uses mountpoint_s3_fs.object, so a change to mountpoint_s3_fs.object can break mountpoint_s3_fs.prefetch.cursor, while a change to mountpoint_s3_fs.prefetch.cursor can't break mountpoint_s3_fs.object.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.cursor uses a module listed above it, which is the healthy direction.
21→16 mountpoint_s3_fs.prefetch.cursor uses mountpoint_s3_fs.memory.limiter✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.prefetch.cursor uses a type in mountpoint_s3_fs.memory.limiter.
- The types involved
mountpoint_s3_fs.prefetch.cursor.Cursor→mountpoint_s3_fs.memory.limiter.CursorHandlemountpoint_s3_fs.prefetch.cursor.CursorInner→mountpoint_s3_fs.memory.limiter.CursorHandle
- Direction
- mountpoint_s3_fs.prefetch.cursor uses mountpoint_s3_fs.memory.limiter, so a change to mountpoint_s3_fs.memory.limiter can break mountpoint_s3_fs.prefetch.cursor, while a change to mountpoint_s3_fs.prefetch.cursor can't break mountpoint_s3_fs.memory.limiter.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.cursor uses a module listed above it, which is the healthy direction.
21→23 mountpoint_s3_fs.prefetch.cursor uses mountpoint_s3_fs.prefetch part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.prefetch.cursor uses a type in mountpoint_s3_fs.prefetch.
- The types involved
mountpoint_s3_fs.prefetch.cursor.Cursor→mountpoint_s3_fs.prefetch.PrefetcherConfig
- Direction
- mountpoint_s3_fs.prefetch.cursor uses mountpoint_s3_fs.prefetch, so a change to mountpoint_s3_fs.prefetch can break mountpoint_s3_fs.prefetch.cursor, while a change to mountpoint_s3_fs.prefetch.cursor can't break mountpoint_s3_fs.prefetch.
- 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→5 mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_fs.async_util✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.prefetch.part_stream uses a type in mountpoint_s3_fs.async_util.
- The types involved
mountpoint_s3_fs.prefetch.part_stream.ClientPartStream→mountpoint_s3_fs.async_util.Runtime
- Direction
- mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_fs.async_util, so a change to mountpoint_s3_fs.async_util can break mountpoint_s3_fs.prefetch.part_stream, while a change to mountpoint_s3_fs.prefetch.part_stream can't break mountpoint_s3_fs.async_util.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.part_stream uses a module listed above it, which is the healthy direction.
22→10 mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_fs.object✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.prefetch.part_stream uses a type in mountpoint_s3_fs.object.
- The types involved
mountpoint_s3_fs.prefetch.part_stream.ClientPartComposer→mountpoint_s3_fs.object.ObjectIdmountpoint_s3_fs.prefetch.part_stream.RequestTaskConfig→mountpoint_s3_fs.object.ObjectIdmountpoint_s3_fs.prefetch.part_stream.part_stream$module→mountpoint_s3_fs.object.ObjectId
- Direction
- mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_fs.object, so a change to mountpoint_s3_fs.object can break mountpoint_s3_fs.prefetch.part_stream, while a change to mountpoint_s3_fs.prefetch.part_stream can't break mountpoint_s3_fs.object.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.part_stream uses a module listed above it, which is the healthy direction.
22→13 mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_fs.memory.pool✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.prefetch.part_stream uses a type in mountpoint_s3_fs.memory.pool.
- The types involved
mountpoint_s3_fs.prefetch.part_stream.ClientPartStream→mountpoint_s3_fs.memory.pool.PagedPoolmountpoint_s3_fs.prefetch.part_stream.ObjectPartStream→mountpoint_s3_fs.memory.pool.PagedPoolmountpoint_s3_fs.prefetch.part_stream.PartStream→mountpoint_s3_fs.memory.pool.PagedPool
- Direction
- mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_fs.memory.pool, so a change to mountpoint_s3_fs.memory.pool can break mountpoint_s3_fs.prefetch.part_stream, while a change to mountpoint_s3_fs.prefetch.part_stream can't break mountpoint_s3_fs.memory.pool.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.part_stream uses a module listed above it, which is the healthy direction.
22→16 mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_fs.memory.limiter✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.prefetch.part_stream uses a type in mountpoint_s3_fs.memory.limiter.
- The types involved
mountpoint_s3_fs.prefetch.part_stream.RequestTaskConfig→mountpoint_s3_fs.memory.limiter.CursorState
- Direction
- mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_fs.memory.limiter, so a change to mountpoint_s3_fs.memory.limiter can break mountpoint_s3_fs.prefetch.part_stream, while a change to mountpoint_s3_fs.prefetch.part_stream can't break mountpoint_s3_fs.memory.limiter.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.part_stream uses a module listed above it, which is the healthy direction.
22→21 mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_fs.prefetch.cursor✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.prefetch.part_stream uses a type in mountpoint_s3_fs.prefetch.cursor.
- The types involved
mountpoint_s3_fs.prefetch.part_stream.part_stream$module→mountpoint_s3_fs.prefetch.cursor.CursorId
- Direction
- mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_fs.prefetch.cursor, so a change to mountpoint_s3_fs.prefetch.cursor can break mountpoint_s3_fs.prefetch.part_stream, while a change to mountpoint_s3_fs.prefetch.part_stream can't break mountpoint_s3_fs.prefetch.cursor.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.part_stream uses a module listed above it, which is the healthy direction.
22→33 mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_crt.s3.client part of a loop✕
- Connections
- 4 pairs of types, where a type in mountpoint_s3_fs.prefetch.part_stream uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_fs.prefetch.part_stream.ClientPartStream→mountpoint_s3_crt.s3.client.Clientmountpoint_s3_fs.prefetch.part_stream.ObjectPartStream→mountpoint_s3_crt.s3.client.Clientmountpoint_s3_fs.prefetch.part_stream.PartStream→mountpoint_s3_crt.s3.client.Clientmountpoint_s3_fs.prefetch.part_stream.part_stream$module→mountpoint_s3_crt.s3.client.Client
- Direction
- mountpoint_s3_fs.prefetch.part_stream uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_fs.prefetch.part_stream, while a change to mountpoint_s3_fs.prefetch.part_stream can't break mountpoint_s3_crt.s3.client.
- 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→10 mountpoint_s3_fs.prefetch uses mountpoint_s3_fs.object✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.prefetch uses a type in mountpoint_s3_fs.object.
- The types involved
mountpoint_s3_fs.prefetch.PrefetchGetObject→mountpoint_s3_fs.object.ObjectIdmountpoint_s3_fs.prefetch.Prefetcher→mountpoint_s3_fs.object.ObjectId
- Direction
- mountpoint_s3_fs.prefetch uses mountpoint_s3_fs.object, so a change to mountpoint_s3_fs.object can break mountpoint_s3_fs.prefetch, while a change to mountpoint_s3_fs.prefetch can't break mountpoint_s3_fs.object.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch uses a module listed above it, which is the healthy direction.
23→21 mountpoint_s3_fs.prefetch uses mountpoint_s3_fs.prefetch.cursor✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.prefetch uses a type in mountpoint_s3_fs.prefetch.cursor.
- The types involved
mountpoint_s3_fs.prefetch.PrefetchGetObject→mountpoint_s3_fs.prefetch.cursor.Cursor
- Direction
- mountpoint_s3_fs.prefetch uses mountpoint_s3_fs.prefetch.cursor, so a change to mountpoint_s3_fs.prefetch.cursor can break mountpoint_s3_fs.prefetch, while a change to mountpoint_s3_fs.prefetch can't break mountpoint_s3_fs.prefetch.cursor.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch uses a module listed above it, which is the healthy direction.
23→22 mountpoint_s3_fs.prefetch uses mountpoint_s3_fs.prefetch.part_stream✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.prefetch uses a type in mountpoint_s3_fs.prefetch.part_stream.
- The types involved
mountpoint_s3_fs.prefetch.PrefetchGetObject→mountpoint_s3_fs.prefetch.part_stream.PartStreammountpoint_s3_fs.prefetch.Prefetcher→mountpoint_s3_fs.prefetch.part_stream.PartStream
- Direction
- mountpoint_s3_fs.prefetch uses mountpoint_s3_fs.prefetch.part_stream, so a change to mountpoint_s3_fs.prefetch.part_stream can break mountpoint_s3_fs.prefetch, while a change to mountpoint_s3_fs.prefetch can't break mountpoint_s3_fs.prefetch.part_stream.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch uses a module listed above it, which is the healthy direction.
23→33 mountpoint_s3_fs.prefetch uses mountpoint_s3_crt.s3.client part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.prefetch uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_fs.prefetch.Prefetcher→mountpoint_s3_crt.s3.client.Client
- Direction
- mountpoint_s3_fs.prefetch uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_fs.prefetch, while a change to mountpoint_s3_fs.prefetch can't break mountpoint_s3_crt.s3.client.
- 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→34 mountpoint_s3_fs.prefetch uses mountpoint_s3_client.object_client part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.prefetch uses a type in mountpoint_s3_client.object_client.
- The types involved
mountpoint_s3_fs.prefetch.PrefetchReadError→mountpoint_s3_client.object_client.ObjectClientError
- Direction
- mountpoint_s3_fs.prefetch uses mountpoint_s3_client.object_client, so a change to mountpoint_s3_client.object_client can break mountpoint_s3_fs.prefetch, while a change to mountpoint_s3_fs.prefetch can't break mountpoint_s3_client.object_client.
- 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→17 mountpoint_s3_fs.fs.config uses mountpoint_s3_fs.metablock✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs.config uses a type in mountpoint_s3_fs.metablock.
- The types involved
mountpoint_s3_fs.fs.config.S3FilesystemConfig→mountpoint_s3_fs.metablock.WriteMode
- Direction
- mountpoint_s3_fs.fs.config uses mountpoint_s3_fs.metablock, so a change to mountpoint_s3_fs.metablock can break mountpoint_s3_fs.fs.config, while a change to mountpoint_s3_fs.fs.config can't break mountpoint_s3_fs.metablock.
- Position
- Below the diagonal: mountpoint_s3_fs.fs.config uses a module listed above it, which is the healthy direction.
24→23 mountpoint_s3_fs.fs.config uses mountpoint_s3_fs.prefetch✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs.config uses a type in mountpoint_s3_fs.prefetch.
- The types involved
mountpoint_s3_fs.fs.config.S3FilesystemConfig→mountpoint_s3_fs.prefetch.PrefetcherConfig
- Direction
- mountpoint_s3_fs.fs.config uses mountpoint_s3_fs.prefetch, so a change to mountpoint_s3_fs.prefetch can break mountpoint_s3_fs.fs.config, while a change to mountpoint_s3_fs.fs.config can't break mountpoint_s3_fs.prefetch.
- Position
- Below the diagonal: mountpoint_s3_fs.fs.config uses a module listed above it, which is the healthy direction.
25→4 mountpoint_s3_fs.fs.error uses mountpoint_s3_crt.common.error✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs.error uses a type in mountpoint_s3_crt.common.error.
- The types involved
mountpoint_s3_fs.fs.error.Error→mountpoint_s3_crt.common.error.Error
- Direction
- mountpoint_s3_fs.fs.error uses mountpoint_s3_crt.common.error, so a change to mountpoint_s3_crt.common.error can break mountpoint_s3_fs.fs.error, while a change to mountpoint_s3_fs.fs.error can't break mountpoint_s3_crt.common.error.
- Position
- Below the diagonal: mountpoint_s3_fs.fs.error uses a module listed above it, which is the healthy direction.
25→23 mountpoint_s3_fs.fs.error uses mountpoint_s3_fs.prefetch✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs.error uses a type in mountpoint_s3_fs.prefetch.
- The types involved
mountpoint_s3_fs.fs.error.Error→mountpoint_s3_fs.prefetch.PrefetchReadError
- Direction
- mountpoint_s3_fs.fs.error uses mountpoint_s3_fs.prefetch, so a change to mountpoint_s3_fs.prefetch can break mountpoint_s3_fs.fs.error, while a change to mountpoint_s3_fs.fs.error can't break mountpoint_s3_fs.prefetch.
- Position
- Below the diagonal: mountpoint_s3_fs.fs.error uses a module listed above it, which is the healthy direction.
25→27 mountpoint_s3_fs.fs.error uses mountpoint_s3_fs.upload part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs.error uses a type in mountpoint_s3_fs.upload.
- The types involved
mountpoint_s3_fs.fs.error.Error→mountpoint_s3_fs.upload.UploadError
- Direction
- mountpoint_s3_fs.fs.error uses mountpoint_s3_fs.upload, so a change to mountpoint_s3_fs.upload can break mountpoint_s3_fs.fs.error, while a change to mountpoint_s3_fs.fs.error can't break mountpoint_s3_fs.upload.
- 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→1 mountpoint_s3_fs.superblock uses mountpoint_s3_client.object_client.etag✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.superblock uses a type in mountpoint_s3_client.object_client.etag.
- The types involved
mountpoint_s3_fs.superblock.Superblock→mountpoint_s3_client.object_client.etag.ETag
- Direction
- mountpoint_s3_fs.superblock uses mountpoint_s3_client.object_client.etag, so a change to mountpoint_s3_client.object_client.etag can break mountpoint_s3_fs.superblock, while a change to mountpoint_s3_fs.superblock can't break mountpoint_s3_client.object_client.etag.
- Position
- Below the diagonal: mountpoint_s3_fs.superblock uses a module listed above it, which is the healthy direction.
26→6 mountpoint_s3_fs.superblock uses mountpoint_s3_fs.s3.path✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.superblock uses a type in mountpoint_s3_fs.s3.path.
- The types involved
mountpoint_s3_fs.superblock.LookedUpInode→mountpoint_s3_fs.s3.path.S3Pathmountpoint_s3_fs.superblock.Superblock→mountpoint_s3_fs.s3.path.S3Pathmountpoint_s3_fs.superblock.SuperblockInner→mountpoint_s3_fs.s3.path.S3Path
- Direction
- mountpoint_s3_fs.superblock uses mountpoint_s3_fs.s3.path, so a change to mountpoint_s3_fs.s3.path can break mountpoint_s3_fs.superblock, while a change to mountpoint_s3_fs.superblock can't break mountpoint_s3_fs.s3.path.
- Position
- Below the diagonal: mountpoint_s3_fs.superblock uses a module listed above it, which is the healthy direction.
26→9 mountpoint_s3_fs.superblock uses mountpoint_s3_fs.metablock.stat✕
- Connections
- 5 pairs of types, where a type in mountpoint_s3_fs.superblock uses a type in mountpoint_s3_fs.metablock.stat.
- The types involved
mountpoint_s3_fs.superblock.LookedUpInode→mountpoint_s3_fs.metablock.stat.InodeStatmountpoint_s3_fs.superblock.RemoteLookup→mountpoint_s3_fs.metablock.stat.InodeKindmountpoint_s3_fs.superblock.RemoteLookup→mountpoint_s3_fs.metablock.stat.InodeStatmountpoint_s3_fs.superblock.Superblock→mountpoint_s3_fs.metablock.stat.InodeKindmountpoint_s3_fs.superblock.SuperblockInner→mountpoint_s3_fs.metablock.stat.InodeKind
- Direction
- mountpoint_s3_fs.superblock uses mountpoint_s3_fs.metablock.stat, so a change to mountpoint_s3_fs.metablock.stat can break mountpoint_s3_fs.superblock, while a change to mountpoint_s3_fs.superblock can't break mountpoint_s3_fs.metablock.stat.
- Position
- Below the diagonal: mountpoint_s3_fs.superblock uses a module listed above it, which is the healthy direction.
26→14 mountpoint_s3_fs.superblock uses mountpoint_s3_fs.metablock.path✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.superblock uses a type in mountpoint_s3_fs.metablock.path.
- The types involved
mountpoint_s3_fs.superblock.Superblock→mountpoint_s3_fs.metablock.path.S3Locationmountpoint_s3_fs.superblock.SuperblockInner→mountpoint_s3_fs.metablock.path.ValidKeymountpoint_s3_fs.superblock.SuperblockInner→mountpoint_s3_fs.metablock.path.ValidName
- Direction
- mountpoint_s3_fs.superblock uses mountpoint_s3_fs.metablock.path, so a change to mountpoint_s3_fs.metablock.path can break mountpoint_s3_fs.superblock, while a change to mountpoint_s3_fs.superblock can't break mountpoint_s3_fs.metablock.path.
- Position
- Below the diagonal: mountpoint_s3_fs.superblock uses a module listed above it, which is the healthy direction.
26→17 mountpoint_s3_fs.superblock uses mountpoint_s3_fs.metablock✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.superblock uses a type in mountpoint_s3_fs.metablock.
- The types involved
mountpoint_s3_fs.superblock.Superblock→mountpoint_s3_fs.metablock.Metablockmountpoint_s3_fs.superblock.Superblock→mountpoint_s3_fs.metablock.ReadWriteModemountpoint_s3_fs.superblock.Superblock→mountpoint_s3_fs.metablock.WriteMode
- Direction
- mountpoint_s3_fs.superblock uses mountpoint_s3_fs.metablock, so a change to mountpoint_s3_fs.metablock can break mountpoint_s3_fs.superblock, while a change to mountpoint_s3_fs.superblock can't break mountpoint_s3_fs.metablock.
- Position
- Below the diagonal: mountpoint_s3_fs.superblock uses a module listed above it, which is the healthy direction.
26→24 mountpoint_s3_fs.superblock uses mountpoint_s3_fs.fs.config✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.superblock uses a type in mountpoint_s3_fs.fs.config.
- The types involved
mountpoint_s3_fs.superblock.SuperblockConfig→mountpoint_s3_fs.fs.config.CacheConfig
- Direction
- mountpoint_s3_fs.superblock uses mountpoint_s3_fs.fs.config, so a change to mountpoint_s3_fs.fs.config can break mountpoint_s3_fs.superblock, while a change to mountpoint_s3_fs.superblock can't break mountpoint_s3_fs.fs.config.
- Position
- Below the diagonal: mountpoint_s3_fs.superblock uses a module listed above it, which is the healthy direction.
27→1 mountpoint_s3_fs.upload uses mountpoint_s3_client.object_client.etag✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.upload uses a type in mountpoint_s3_client.object_client.etag.
- The types involved
mountpoint_s3_fs.upload.Uploader→mountpoint_s3_client.object_client.etag.ETag
- Direction
- mountpoint_s3_fs.upload uses mountpoint_s3_client.object_client.etag, so a change to mountpoint_s3_client.object_client.etag can break mountpoint_s3_fs.upload, while a change to mountpoint_s3_fs.upload can't break mountpoint_s3_client.object_client.etag.
- Position
- Below the diagonal: mountpoint_s3_fs.upload uses a module listed above it, which is the healthy direction.
27→5 mountpoint_s3_fs.upload uses mountpoint_s3_fs.async_util✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.upload uses a type in mountpoint_s3_fs.async_util.
- The types involved
mountpoint_s3_fs.upload.Uploader→mountpoint_s3_fs.async_util.Runtime
- Direction
- mountpoint_s3_fs.upload uses mountpoint_s3_fs.async_util, so a change to mountpoint_s3_fs.async_util can break mountpoint_s3_fs.upload, while a change to mountpoint_s3_fs.upload can't break mountpoint_s3_fs.async_util.
- Position
- Below the diagonal: mountpoint_s3_fs.upload uses a module listed above it, which is the healthy direction.
27→13 mountpoint_s3_fs.upload uses mountpoint_s3_fs.memory.pool✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.upload uses a type in mountpoint_s3_fs.memory.pool.
- The types involved
mountpoint_s3_fs.upload.Uploader→mountpoint_s3_fs.memory.pool.PagedPool
- Direction
- mountpoint_s3_fs.upload uses mountpoint_s3_fs.memory.pool, so a change to mountpoint_s3_fs.memory.pool can break mountpoint_s3_fs.upload, while a change to mountpoint_s3_fs.upload can't break mountpoint_s3_fs.memory.pool.
- Position
- Below the diagonal: mountpoint_s3_fs.upload uses a module listed above it, which is the healthy direction.
27→18 mountpoint_s3_fs.upload uses mountpoint_s3_fs.upload.incremental✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.upload uses a type in mountpoint_s3_fs.upload.incremental.
- The types involved
mountpoint_s3_fs.upload.Uploader→mountpoint_s3_fs.upload.incremental.AppendUploadRequest
- Direction
- mountpoint_s3_fs.upload uses mountpoint_s3_fs.upload.incremental, so a change to mountpoint_s3_fs.upload.incremental can break mountpoint_s3_fs.upload, while a change to mountpoint_s3_fs.upload can't break mountpoint_s3_fs.upload.incremental.
- Position
- Below the diagonal: mountpoint_s3_fs.upload uses a module listed above it, which is the healthy direction.
27→25 mountpoint_s3_fs.upload uses mountpoint_s3_fs.fs.error✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.upload uses a type in mountpoint_s3_fs.fs.error.
- The types involved
mountpoint_s3_fs.upload.UploadError→mountpoint_s3_fs.fs.error.ToErrno
- Direction
- mountpoint_s3_fs.upload uses mountpoint_s3_fs.fs.error, so a change to mountpoint_s3_fs.fs.error can break mountpoint_s3_fs.upload, while a change to mountpoint_s3_fs.upload can't break mountpoint_s3_fs.fs.error.
- Position
- Below the diagonal: mountpoint_s3_fs.upload uses a module listed above it, which is the healthy direction.
27→33 mountpoint_s3_fs.upload uses mountpoint_s3_crt.s3.client part of a loop✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.upload uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_fs.upload.Uploader→mountpoint_s3_crt.s3.client.ChecksumAlgorithmmountpoint_s3_fs.upload.Uploader→mountpoint_s3_crt.s3.client.Clientmountpoint_s3_fs.upload.UploaderConfig→mountpoint_s3_crt.s3.client.ChecksumAlgorithm
- Direction
- mountpoint_s3_fs.upload uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_fs.upload, while a change to mountpoint_s3_fs.upload can't break mountpoint_s3_crt.s3.client.
- 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.
28→4 mountpoint_s3_fs.fs uses mountpoint_s3_crt.common.error✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs uses a type in mountpoint_s3_crt.common.error.
- The types involved
mountpoint_s3_fs.fs.S3Filesystem→mountpoint_s3_crt.common.error.Error
- Direction
- mountpoint_s3_fs.fs uses mountpoint_s3_crt.common.error, so a change to mountpoint_s3_crt.common.error can break mountpoint_s3_fs.fs, while a change to mountpoint_s3_fs.fs can't break mountpoint_s3_crt.common.error.
- Position
- Below the diagonal: mountpoint_s3_fs.fs uses a module listed above it, which is the healthy direction.
28→5 mountpoint_s3_fs.fs uses mountpoint_s3_fs.async_util✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs uses a type in mountpoint_s3_fs.async_util.
- The types involved
mountpoint_s3_fs.fs.S3Filesystem→mountpoint_s3_fs.async_util.Runtime
- Direction
- mountpoint_s3_fs.fs uses mountpoint_s3_fs.async_util, so a change to mountpoint_s3_fs.async_util can break mountpoint_s3_fs.fs, while a change to mountpoint_s3_fs.fs can't break mountpoint_s3_fs.async_util.
- Position
- Below the diagonal: mountpoint_s3_fs.fs uses a module listed above it, which is the healthy direction.
28→13 mountpoint_s3_fs.fs uses mountpoint_s3_fs.memory.pool✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs uses a type in mountpoint_s3_fs.memory.pool.
- The types involved
mountpoint_s3_fs.fs.S3Filesystem→mountpoint_s3_fs.memory.pool.PagedPool
- Direction
- mountpoint_s3_fs.fs uses mountpoint_s3_fs.memory.pool, so a change to mountpoint_s3_fs.memory.pool can break mountpoint_s3_fs.fs, while a change to mountpoint_s3_fs.fs can't break mountpoint_s3_fs.memory.pool.
- Position
- Below the diagonal: mountpoint_s3_fs.fs uses a module listed above it, which is the healthy direction.
28→19 mountpoint_s3_fs.fs uses mountpoint_s3_fuser✕
- Connections
- 5 pairs of types, where a type in mountpoint_s3_fs.fs uses a type in mountpoint_s3_fuser.
- The types involved
mountpoint_s3_fs.fs.Attr→mountpoint_s3_fuser.FileAttrmountpoint_s3_fs.fs.DirectoryEntry→mountpoint_s3_fuser.FileAttrmountpoint_s3_fs.fs.Entry→mountpoint_s3_fuser.FileAttrmountpoint_s3_fs.fs.S3Filesystem→mountpoint_s3_fuser.FileAttrmountpoint_s3_fs.fs.S3Filesystem→mountpoint_s3_fuser.KernelConfig
- Direction
- mountpoint_s3_fs.fs uses mountpoint_s3_fuser, so a change to mountpoint_s3_fuser can break mountpoint_s3_fs.fs, while a change to mountpoint_s3_fs.fs can't break mountpoint_s3_fuser.
- Position
- Below the diagonal: mountpoint_s3_fs.fs uses a module listed above it, which is the healthy direction.
28→23 mountpoint_s3_fs.fs uses mountpoint_s3_fs.prefetch✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs uses a type in mountpoint_s3_fs.prefetch.
- The types involved
mountpoint_s3_fs.fs.S3Filesystem→mountpoint_s3_fs.prefetch.Prefetcher
- Direction
- mountpoint_s3_fs.fs uses mountpoint_s3_fs.prefetch, so a change to mountpoint_s3_fs.prefetch can break mountpoint_s3_fs.fs, while a change to mountpoint_s3_fs.fs can't break mountpoint_s3_fs.prefetch.
- Position
- Below the diagonal: mountpoint_s3_fs.fs uses a module listed above it, which is the healthy direction.
28→24 mountpoint_s3_fs.fs uses mountpoint_s3_fs.fs.config✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs uses a type in mountpoint_s3_fs.fs.config.
- The types involved
mountpoint_s3_fs.fs.S3Filesystem→mountpoint_s3_fs.fs.config.S3FilesystemConfig
- Direction
- mountpoint_s3_fs.fs uses mountpoint_s3_fs.fs.config, so a change to mountpoint_s3_fs.fs.config can break mountpoint_s3_fs.fs, while a change to mountpoint_s3_fs.fs can't break mountpoint_s3_fs.fs.config.
- Position
- Below the diagonal: mountpoint_s3_fs.fs uses a module listed above it, which is the healthy direction.
28→27 mountpoint_s3_fs.fs uses mountpoint_s3_fs.upload✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs uses a type in mountpoint_s3_fs.upload.
- The types involved
mountpoint_s3_fs.fs.S3Filesystem→mountpoint_s3_fs.upload.Uploader
- Direction
- mountpoint_s3_fs.fs uses mountpoint_s3_fs.upload, so a change to mountpoint_s3_fs.upload can break mountpoint_s3_fs.fs, while a change to mountpoint_s3_fs.fs can't break mountpoint_s3_fs.upload.
- Position
- Below the diagonal: mountpoint_s3_fs.fs uses a module listed above it, which is the healthy direction.
28→33 mountpoint_s3_fs.fs uses mountpoint_s3_crt.s3.client part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_fs.fs.S3Filesystem→mountpoint_s3_crt.s3.client.Client
- Direction
- mountpoint_s3_fs.fs uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_fs.fs, while a change to mountpoint_s3_fs.fs can't break mountpoint_s3_crt.s3.client.
- 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→1 mountpoint_s3_fs.fs.handles uses mountpoint_s3_client.object_client.etag✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs.handles uses a type in mountpoint_s3_client.object_client.etag.
- The types involved
mountpoint_s3_fs.fs.handles.UploadState→mountpoint_s3_client.object_client.etag.ETag
- Direction
- mountpoint_s3_fs.fs.handles uses mountpoint_s3_client.object_client.etag, so a change to mountpoint_s3_client.object_client.etag can break mountpoint_s3_fs.fs.handles, while a change to mountpoint_s3_fs.fs.handles can't break mountpoint_s3_client.object_client.etag.
- Position
- Below the diagonal: mountpoint_s3_fs.fs.handles uses a module listed above it, which is the healthy direction.
29→11 mountpoint_s3_fs.fs.handles uses mountpoint_s3_fs.upload.atomic✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs.handles uses a type in mountpoint_s3_fs.upload.atomic.
- The types involved
mountpoint_s3_fs.fs.handles.UploadState→mountpoint_s3_fs.upload.atomic.UploadRequest
- Direction
- mountpoint_s3_fs.fs.handles uses mountpoint_s3_fs.upload.atomic, so a change to mountpoint_s3_fs.upload.atomic can break mountpoint_s3_fs.fs.handles, while a change to mountpoint_s3_fs.fs.handles can't break mountpoint_s3_fs.upload.atomic.
- Position
- Below the diagonal: mountpoint_s3_fs.fs.handles uses a module listed above it, which is the healthy direction.
29→14 mountpoint_s3_fs.fs.handles uses mountpoint_s3_fs.metablock.path✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.fs.handles uses a type in mountpoint_s3_fs.metablock.path.
- The types involved
mountpoint_s3_fs.fs.handles.FileHandle→mountpoint_s3_fs.metablock.path.S3Locationmountpoint_s3_fs.fs.handles.UploadState→mountpoint_s3_fs.metablock.path.S3Location
- Direction
- mountpoint_s3_fs.fs.handles uses mountpoint_s3_fs.metablock.path, so a change to mountpoint_s3_fs.metablock.path can break mountpoint_s3_fs.fs.handles, while a change to mountpoint_s3_fs.fs.handles can't break mountpoint_s3_fs.metablock.path.
- Position
- Below the diagonal: mountpoint_s3_fs.fs.handles uses a module listed above it, which is the healthy direction.
29→17 mountpoint_s3_fs.fs.handles uses mountpoint_s3_fs.metablock✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs.handles uses a type in mountpoint_s3_fs.metablock.
- The types involved
mountpoint_s3_fs.fs.handles.FileHandleState→mountpoint_s3_fs.metablock.ReadWriteMode
- Direction
- mountpoint_s3_fs.fs.handles uses mountpoint_s3_fs.metablock, so a change to mountpoint_s3_fs.metablock can break mountpoint_s3_fs.fs.handles, while a change to mountpoint_s3_fs.fs.handles can't break mountpoint_s3_fs.metablock.
- Position
- Below the diagonal: mountpoint_s3_fs.fs.handles uses a module listed above it, which is the healthy direction.
29→18 mountpoint_s3_fs.fs.handles uses mountpoint_s3_fs.upload.incremental✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.fs.handles uses a type in mountpoint_s3_fs.upload.incremental.
- The types involved
mountpoint_s3_fs.fs.handles.UploadState→mountpoint_s3_fs.upload.incremental.AppendUploadRequest
- Direction
- mountpoint_s3_fs.fs.handles uses mountpoint_s3_fs.upload.incremental, so a change to mountpoint_s3_fs.upload.incremental can break mountpoint_s3_fs.fs.handles, while a change to mountpoint_s3_fs.fs.handles can't break mountpoint_s3_fs.upload.incremental.
- Position
- Below the diagonal: mountpoint_s3_fs.fs.handles uses a module listed above it, which is the healthy direction.
29→28 mountpoint_s3_fs.fs.handles uses mountpoint_s3_fs.fs✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.fs.handles uses a type in mountpoint_s3_fs.fs.
- The types involved
mountpoint_s3_fs.fs.handles.FileHandleState→mountpoint_s3_fs.fs.S3Filesystemmountpoint_s3_fs.fs.handles.UploadState→mountpoint_s3_fs.fs.S3Filesystem
- Direction
- mountpoint_s3_fs.fs.handles uses mountpoint_s3_fs.fs, so a change to mountpoint_s3_fs.fs can break mountpoint_s3_fs.fs.handles, while a change to mountpoint_s3_fs.fs.handles can't break mountpoint_s3_fs.fs.
- Position
- Below the diagonal: mountpoint_s3_fs.fs.handles uses a module listed above it, which is the healthy direction.
30→12 mountpoint_s3_fuser.ll.request.op uses mountpoint_s3_fuser.ll.reply✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fuser.ll.request.op uses a type in mountpoint_s3_fuser.ll.reply.
- The types involved
mountpoint_s3_fuser.ll.request.op.Destroy→mountpoint_s3_fuser.ll.reply.Responsemountpoint_s3_fuser.ll.request.op.Init→mountpoint_s3_fuser.ll.reply.Response
- Direction
- mountpoint_s3_fuser.ll.request.op uses mountpoint_s3_fuser.ll.reply, so a change to mountpoint_s3_fuser.ll.reply can break mountpoint_s3_fuser.ll.request.op, while a change to mountpoint_s3_fuser.ll.request.op can't break mountpoint_s3_fuser.ll.reply.
- Position
- Below the diagonal: mountpoint_s3_fuser.ll.request.op uses a module listed above it, which is the healthy direction.
30→15 mountpoint_s3_fuser.ll.request.op uses mountpoint_s3_fuser.ll.request✕
- Connections
- 164 pairs of types, where a type in mountpoint_s3_fuser.ll.request.op uses a type in mountpoint_s3_fuser.ll.request. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
mountpoint_s3_fuser.ll.request.op.Access→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.request.op.Access→mountpoint_s3_fuser.ll.request.Requestmountpoint_s3_fuser.ll.request.op.Access→mountpoint_s3_fuser.ll.request.RequestIdmountpoint_s3_fuser.ll.request.op.BMap→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.request.op.BMap→mountpoint_s3_fuser.ll.request.Requestmountpoint_s3_fuser.ll.request.op.BMap→mountpoint_s3_fuser.ll.request.RequestIdmountpoint_s3_fuser.ll.request.op.BatchForget→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.request.op.BatchForget→mountpoint_s3_fuser.ll.request.Requestmountpoint_s3_fuser.ll.request.op.BatchForget→mountpoint_s3_fuser.ll.request.RequestIdmountpoint_s3_fuser.ll.request.op.CopyFileRange→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.request.op.CopyFileRange→mountpoint_s3_fuser.ll.request.Requestmountpoint_s3_fuser.ll.request.op.CopyFileRange→mountpoint_s3_fuser.ll.request.RequestIdmountpoint_s3_fuser.ll.request.op.CopyFileRangeFile→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.request.op.Create→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.request.op.Create→mountpoint_s3_fuser.ll.request.Requestmountpoint_s3_fuser.ll.request.op.Create→mountpoint_s3_fuser.ll.request.RequestIdmountpoint_s3_fuser.ll.request.op.CuseInit→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.request.op.CuseInit→mountpoint_s3_fuser.ll.request.Requestmountpoint_s3_fuser.ll.request.op.CuseInit→mountpoint_s3_fuser.ll.request.RequestIdmountpoint_s3_fuser.ll.request.op.Destroy→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.request.op.Destroy→mountpoint_s3_fuser.ll.request.Requestmountpoint_s3_fuser.ll.request.op.Destroy→mountpoint_s3_fuser.ll.request.RequestIdmountpoint_s3_fuser.ll.request.op.Exchange→mountpoint_s3_fuser.ll.request.FilenameInDirmountpoint_s3_fuser.ll.request.op.Exchange→mountpoint_s3_fuser.ll.request.INodeNomountpoint_s3_fuser.ll.request.op.Exchange→mountpoint_s3_fuser.ll.request.Request
- Direction
- mountpoint_s3_fuser.ll.request.op uses mountpoint_s3_fuser.ll.request, so a change to mountpoint_s3_fuser.ll.request can break mountpoint_s3_fuser.ll.request.op, while a change to mountpoint_s3_fuser.ll.request.op can't break mountpoint_s3_fuser.ll.request.
- Position
- Below the diagonal: mountpoint_s3_fuser.ll.request.op uses a module listed above it, which is the healthy direction.
30→19 mountpoint_s3_fuser.ll.request.op uses mountpoint_s3_fuser✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fuser.ll.request.op uses a type in mountpoint_s3_fuser.
- The types involved
mountpoint_s3_fuser.ll.request.op.Init→mountpoint_s3_fuser.KernelConfig
- Direction
- mountpoint_s3_fuser.ll.request.op uses mountpoint_s3_fuser, so a change to mountpoint_s3_fuser can break mountpoint_s3_fuser.ll.request.op, while a change to mountpoint_s3_fuser.ll.request.op can't break mountpoint_s3_fuser.
- Position
- Below the diagonal: mountpoint_s3_fuser.ll.request.op uses a module listed above it, which is the healthy direction.
30→29 mountpoint_s3_fuser.ll.request.op uses mountpoint_s3_fs.fs.handles✕
- Connections
- 19 pairs of types, where a type in mountpoint_s3_fuser.ll.request.op uses a type in mountpoint_s3_fs.fs.handles.
- The types involved
mountpoint_s3_fuser.ll.request.op.CopyFileRangeFile→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.FAllocate→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.FSync→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.FSyncDir→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.Flush→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.GetAttr→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.GetLk→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.IoCtl→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.Lseek→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.Poll→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.Read→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.ReadDir→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.ReadDirPlus→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.Release→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.ReleaseDir→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.SetAttr→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.SetLk→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.SetLkW→mountpoint_s3_fs.fs.handles.FileHandlemountpoint_s3_fuser.ll.request.op.Write→mountpoint_s3_fs.fs.handles.FileHandle
- Direction
- mountpoint_s3_fuser.ll.request.op uses mountpoint_s3_fs.fs.handles, so a change to mountpoint_s3_fs.fs.handles can break mountpoint_s3_fuser.ll.request.op, while a change to mountpoint_s3_fuser.ll.request.op can't break mountpoint_s3_fs.fs.handles.
- Position
- Below the diagonal: mountpoint_s3_fuser.ll.request.op uses a module listed above it, which is the healthy direction.
31→3 mountpoint_s3_crt.io.event_loop uses mountpoint_s3_crt.common.allocator✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_crt.io.event_loop uses a type in mountpoint_s3_crt.common.allocator.
- The types involved
mountpoint_s3_crt.io.event_loop.EventLoopGroup→mountpoint_s3_crt.common.allocator.Allocator
- Direction
- mountpoint_s3_crt.io.event_loop uses mountpoint_s3_crt.common.allocator, so a change to mountpoint_s3_crt.common.allocator can break mountpoint_s3_crt.io.event_loop, while a change to mountpoint_s3_crt.io.event_loop can't break mountpoint_s3_crt.common.allocator.
- Position
- Below the diagonal: mountpoint_s3_crt.io.event_loop uses a module listed above it, which is the healthy direction.
31→30 mountpoint_s3_crt.io.event_loop uses mountpoint_s3_fuser.ll.request.op✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_crt.io.event_loop uses a type in mountpoint_s3_fuser.ll.request.op.
- The types involved
mountpoint_s3_crt.io.event_loop.EventLoopTimer→mountpoint_s3_fuser.ll.request.op.Poll
- Direction
- mountpoint_s3_crt.io.event_loop uses mountpoint_s3_fuser.ll.request.op, so a change to mountpoint_s3_fuser.ll.request.op can break mountpoint_s3_crt.io.event_loop, while a change to mountpoint_s3_crt.io.event_loop can't break mountpoint_s3_fuser.ll.request.op.
- Position
- Below the diagonal: mountpoint_s3_crt.io.event_loop uses a module listed above it, which is the healthy direction.
32→3 mountpoint_s3_crt.s3.pool uses mountpoint_s3_crt.common.allocator✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_crt.s3.pool uses a type in mountpoint_s3_crt.common.allocator.
- The types involved
mountpoint_s3_crt.s3.pool.CrtBufferPool→mountpoint_s3_crt.common.allocator.Allocatormountpoint_s3_crt.s3.pool.CrtTicketFuture→mountpoint_s3_crt.common.allocator.Allocator
- Direction
- mountpoint_s3_crt.s3.pool uses mountpoint_s3_crt.common.allocator, so a change to mountpoint_s3_crt.common.allocator can break mountpoint_s3_crt.s3.pool, while a change to mountpoint_s3_crt.s3.pool can't break mountpoint_s3_crt.common.allocator.
- Position
- Below the diagonal: mountpoint_s3_crt.s3.pool uses a module listed above it, which is the healthy direction.
32→31 mountpoint_s3_crt.s3.pool uses mountpoint_s3_crt.io.event_loop✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_crt.s3.pool uses a type in mountpoint_s3_crt.io.event_loop.
- The types involved
mountpoint_s3_crt.s3.pool.CrtBufferPool→mountpoint_s3_crt.io.event_loop.EventLoopGroupmountpoint_s3_crt.s3.pool.CrtBufferPoolFactory→mountpoint_s3_crt.io.event_loop.EventLoopGroupmountpoint_s3_crt.s3.pool.CrtBufferPoolFactoryInner→mountpoint_s3_crt.io.event_loop.EventLoopGroup
- Direction
- mountpoint_s3_crt.s3.pool uses mountpoint_s3_crt.io.event_loop, so a change to mountpoint_s3_crt.io.event_loop can break mountpoint_s3_crt.s3.pool, while a change to mountpoint_s3_crt.s3.pool can't break mountpoint_s3_crt.io.event_loop.
- Position
- Below the diagonal: mountpoint_s3_crt.s3.pool uses a module listed above it, which is the healthy direction.
32→33 mountpoint_s3_crt.s3.pool uses mountpoint_s3_crt.s3.client part of a loop✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_crt.s3.pool uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_crt.s3.pool.CrtBufferPool→mountpoint_s3_crt.s3.client.MetaRequestmountpoint_s3_crt.s3.pool.MemoryPool→mountpoint_s3_crt.s3.client.MetaRequest
- Direction
- mountpoint_s3_crt.s3.pool uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_crt.s3.pool, while a change to mountpoint_s3_crt.s3.pool can't break mountpoint_s3_crt.s3.client.
- 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.
33→3 mountpoint_s3_crt.s3.client uses mountpoint_s3_crt.common.allocator✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_crt.s3.client uses a type in mountpoint_s3_crt.common.allocator.
- The types involved
mountpoint_s3_crt.s3.client.Client→mountpoint_s3_crt.common.allocator.Allocator
- Direction
- mountpoint_s3_crt.s3.client uses mountpoint_s3_crt.common.allocator, so a change to mountpoint_s3_crt.common.allocator can break mountpoint_s3_crt.s3.client, while a change to mountpoint_s3_crt.s3.client can't break mountpoint_s3_crt.common.allocator.
- Position
- Below the diagonal: mountpoint_s3_crt.s3.client uses a module listed above it, which is the healthy direction.
33→4 mountpoint_s3_crt.s3.client uses mountpoint_s3_crt.common.error✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_crt.s3.client uses a type in mountpoint_s3_crt.common.error.
- The types involved
mountpoint_s3_crt.s3.client.MetaRequestResult→mountpoint_s3_crt.common.error.Errormountpoint_s3_crt.s3.client.RequestMetrics→mountpoint_s3_crt.common.error.Error
- Direction
- mountpoint_s3_crt.s3.client uses mountpoint_s3_crt.common.error, so a change to mountpoint_s3_crt.common.error can break mountpoint_s3_crt.s3.client, while a change to mountpoint_s3_crt.s3.client can't break mountpoint_s3_crt.common.error.
- Position
- Below the diagonal: mountpoint_s3_crt.s3.client uses a module listed above it, which is the healthy direction.
33→24 mountpoint_s3_crt.s3.client uses mountpoint_s3_fs.fs.config✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_crt.s3.client uses a type in mountpoint_s3_fs.fs.config.
- The types involved
mountpoint_s3_crt.s3.client.ChecksumAlgorithm→mountpoint_s3_fs.fs.config.UploadChecksumAlgorithm
- Direction
- mountpoint_s3_crt.s3.client uses mountpoint_s3_fs.fs.config, so a change to mountpoint_s3_fs.fs.config can break mountpoint_s3_crt.s3.client, while a change to mountpoint_s3_crt.s3.client can't break mountpoint_s3_fs.fs.config.
- Position
- Below the diagonal: mountpoint_s3_crt.s3.client uses a module listed above it, which is the healthy direction.
33→30 mountpoint_s3_crt.s3.client uses mountpoint_s3_fuser.ll.request.op✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_crt.s3.client uses a type in mountpoint_s3_fuser.ll.request.op.
- The types involved
mountpoint_s3_crt.s3.client.MetaRequestWrite→mountpoint_s3_fuser.ll.request.op.Poll
- Direction
- mountpoint_s3_crt.s3.client uses mountpoint_s3_fuser.ll.request.op, so a change to mountpoint_s3_fuser.ll.request.op can break mountpoint_s3_crt.s3.client, while a change to mountpoint_s3_crt.s3.client can't break mountpoint_s3_fuser.ll.request.op.
- Position
- Below the diagonal: mountpoint_s3_crt.s3.client uses a module listed above it, which is the healthy direction.
33→32 mountpoint_s3_crt.s3.client uses mountpoint_s3_crt.s3.pool✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_crt.s3.client uses a type in mountpoint_s3_crt.s3.pool.
- The types involved
mountpoint_s3_crt.s3.client.ClientConfig→mountpoint_s3_crt.s3.pool.CrtBufferPoolFactory
- Direction
- mountpoint_s3_crt.s3.client uses mountpoint_s3_crt.s3.pool, so a change to mountpoint_s3_crt.s3.pool can break mountpoint_s3_crt.s3.client, while a change to mountpoint_s3_crt.s3.client can't break mountpoint_s3_crt.s3.pool.
- Position
- Below the diagonal: mountpoint_s3_crt.s3.client uses a module listed above it, which is the healthy direction.
34→1 mountpoint_s3_client.object_client uses mountpoint_s3_client.object_client.etag✕
- Connections
- 5 pairs of types, where a type in mountpoint_s3_client.object_client uses a type in mountpoint_s3_client.object_client.etag.
- The types involved
mountpoint_s3_client.object_client.GetObjectParams→mountpoint_s3_client.object_client.etag.ETagmountpoint_s3_client.object_client.HeadObjectResult→mountpoint_s3_client.object_client.etag.ETagmountpoint_s3_client.object_client.PutObjectResult→mountpoint_s3_client.object_client.etag.ETagmountpoint_s3_client.object_client.PutObjectSingleParams→mountpoint_s3_client.object_client.etag.ETagmountpoint_s3_client.object_client.RenameObjectParams→mountpoint_s3_client.object_client.etag.ETag
- Direction
- mountpoint_s3_client.object_client uses mountpoint_s3_client.object_client.etag, so a change to mountpoint_s3_client.object_client.etag can break mountpoint_s3_client.object_client, while a change to mountpoint_s3_client.object_client can't break mountpoint_s3_client.object_client.etag.
- Position
- Below the diagonal: mountpoint_s3_client.object_client uses a module listed above it, which is the healthy direction.
34→33 mountpoint_s3_client.object_client uses mountpoint_s3_crt.s3.client✕
- Connections
- 5 pairs of types, where a type in mountpoint_s3_client.object_client uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_client.object_client.Checksum→mountpoint_s3_crt.s3.client.ChecksumAlgorithmmountpoint_s3_client.object_client.ObjectClient→mountpoint_s3_crt.s3.client.BufferPoolUsageStatsmountpoint_s3_client.object_client.ObjectInfo→mountpoint_s3_crt.s3.client.ChecksumAlgorithmmountpoint_s3_client.object_client.PutObjectTrailingChecksums→mountpoint_s3_crt.s3.client.ChecksumAlgorithmmountpoint_s3_client.object_client.UploadChecksum→mountpoint_s3_crt.s3.client.ChecksumAlgorithm
- Direction
- mountpoint_s3_client.object_client uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_client.object_client, while a change to mountpoint_s3_client.object_client can't break mountpoint_s3_crt.s3.client.
- Position
- Below the diagonal: mountpoint_s3_client.object_client uses a module listed above it, which is the healthy direction.
35→5 mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_fs.async_util✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.prefetch.caching_stream uses a type in mountpoint_s3_fs.async_util.
- The types involved
mountpoint_s3_fs.prefetch.caching_stream.CachingPartComposer→mountpoint_s3_fs.async_util.Runtimemountpoint_s3_fs.prefetch.caching_stream.CachingPartStream→mountpoint_s3_fs.async_util.Runtimemountpoint_s3_fs.prefetch.caching_stream.CachingRequest→mountpoint_s3_fs.async_util.Runtime
- Direction
- mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_fs.async_util, so a change to mountpoint_s3_fs.async_util can break mountpoint_s3_fs.prefetch.caching_stream, while a change to mountpoint_s3_fs.prefetch.caching_stream can't break mountpoint_s3_fs.async_util.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.caching_stream uses a module listed above it, which is the healthy direction.
35→7 mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_fs.checksums✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.prefetch.caching_stream uses a type in mountpoint_s3_fs.checksums.
- The types involved
mountpoint_s3_fs.prefetch.caching_stream.CachingPartComposer→mountpoint_s3_fs.checksums.ChecksummedBytesmountpoint_s3_fs.prefetch.caching_stream.caching_stream$module→mountpoint_s3_fs.checksums.ChecksummedBytes
- Direction
- mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_fs.checksums, so a change to mountpoint_s3_fs.checksums can break mountpoint_s3_fs.prefetch.caching_stream, while a change to mountpoint_s3_fs.prefetch.caching_stream can't break mountpoint_s3_fs.checksums.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.caching_stream uses a module listed above it, which is the healthy direction.
35→10 mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_fs.object✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.prefetch.caching_stream uses a type in mountpoint_s3_fs.object.
- The types involved
mountpoint_s3_fs.prefetch.caching_stream.CachingPartComposer→mountpoint_s3_fs.object.ObjectIdmountpoint_s3_fs.prefetch.caching_stream.caching_stream$module→mountpoint_s3_fs.object.ObjectId
- Direction
- mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_fs.object, so a change to mountpoint_s3_fs.object can break mountpoint_s3_fs.prefetch.caching_stream, while a change to mountpoint_s3_fs.prefetch.caching_stream can't break mountpoint_s3_fs.object.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.caching_stream uses a module listed above it, which is the healthy direction.
35→13 mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_fs.memory.pool✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.prefetch.caching_stream uses a type in mountpoint_s3_fs.memory.pool.
- The types involved
mountpoint_s3_fs.prefetch.caching_stream.CachingPartStream→mountpoint_s3_fs.memory.pool.PagedPool
- Direction
- mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_fs.memory.pool, so a change to mountpoint_s3_fs.memory.pool can break mountpoint_s3_fs.prefetch.caching_stream, while a change to mountpoint_s3_fs.prefetch.caching_stream can't break mountpoint_s3_fs.memory.pool.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.caching_stream uses a module listed above it, which is the healthy direction.
35→22 mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_fs.prefetch.part_stream✕
- Connections
- 6 pairs of types, where a type in mountpoint_s3_fs.prefetch.caching_stream uses a type in mountpoint_s3_fs.prefetch.part_stream.
- The types involved
mountpoint_s3_fs.prefetch.caching_stream.CachingPartComposer→mountpoint_s3_fs.prefetch.part_stream.RequestRangemountpoint_s3_fs.prefetch.caching_stream.CachingPartStream→mountpoint_s3_fs.prefetch.part_stream.ObjectPartStreammountpoint_s3_fs.prefetch.caching_stream.CachingPartStream→mountpoint_s3_fs.prefetch.part_stream.RequestTaskConfigmountpoint_s3_fs.prefetch.caching_stream.CachingRequest→mountpoint_s3_fs.prefetch.part_stream.RequestRangemountpoint_s3_fs.prefetch.caching_stream.CachingRequest→mountpoint_s3_fs.prefetch.part_stream.RequestTaskConfigmountpoint_s3_fs.prefetch.caching_stream.caching_stream$module→mountpoint_s3_fs.prefetch.part_stream.RequestRange
- Direction
- mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_fs.prefetch.part_stream, so a change to mountpoint_s3_fs.prefetch.part_stream can break mountpoint_s3_fs.prefetch.caching_stream, while a change to mountpoint_s3_fs.prefetch.caching_stream can't break mountpoint_s3_fs.prefetch.part_stream.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.caching_stream uses a module listed above it, which is the healthy direction.
35→33 mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_crt.s3.client✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.prefetch.caching_stream uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_fs.prefetch.caching_stream.CachingPartStream→mountpoint_s3_crt.s3.client.Clientmountpoint_s3_fs.prefetch.caching_stream.CachingRequest→mountpoint_s3_crt.s3.client.Client
- Direction
- mountpoint_s3_fs.prefetch.caching_stream uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_fs.prefetch.caching_stream, while a change to mountpoint_s3_fs.prefetch.caching_stream can't break mountpoint_s3_crt.s3.client.
- Position
- Below the diagonal: mountpoint_s3_fs.prefetch.caching_stream uses a module listed above it, which is the healthy direction.
36→3 mountpoint_s3_client.s3_crt_client uses mountpoint_s3_crt.common.allocator✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_client.s3_crt_client uses a type in mountpoint_s3_crt.common.allocator.
- The types involved
mountpoint_s3_client.s3_crt_client.S3CrtClientInner→mountpoint_s3_crt.common.allocator.Allocatormountpoint_s3_client.s3_crt_client.s3_crt_client$module→mountpoint_s3_crt.common.allocator.Allocator
- Direction
- mountpoint_s3_client.s3_crt_client uses mountpoint_s3_crt.common.allocator, so a change to mountpoint_s3_crt.common.allocator can break mountpoint_s3_client.s3_crt_client, while a change to mountpoint_s3_client.s3_crt_client can't break mountpoint_s3_crt.common.allocator.
- Position
- Below the diagonal: mountpoint_s3_client.s3_crt_client uses a module listed above it, which is the healthy direction.
36→30 mountpoint_s3_client.s3_crt_client uses mountpoint_s3_fuser.ll.request.op✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_client.s3_crt_client uses a type in mountpoint_s3_fuser.ll.request.op.
- The types involved
mountpoint_s3_client.s3_crt_client.S3MetaRequest→mountpoint_s3_fuser.ll.request.op.Poll
- Direction
- mountpoint_s3_client.s3_crt_client uses mountpoint_s3_fuser.ll.request.op, so a change to mountpoint_s3_fuser.ll.request.op can break mountpoint_s3_client.s3_crt_client, while a change to mountpoint_s3_client.s3_crt_client can't break mountpoint_s3_fuser.ll.request.op.
- Position
- Below the diagonal: mountpoint_s3_client.s3_crt_client uses a module listed above it, which is the healthy direction.
36→31 mountpoint_s3_client.s3_crt_client uses mountpoint_s3_crt.io.event_loop✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_client.s3_crt_client uses a type in mountpoint_s3_crt.io.event_loop.
- The types involved
mountpoint_s3_client.s3_crt_client.S3CrtClient→mountpoint_s3_crt.io.event_loop.EventLoopGroupmountpoint_s3_client.s3_crt_client.S3CrtClientInner→mountpoint_s3_crt.io.event_loop.EventLoopGroup
- Direction
- mountpoint_s3_client.s3_crt_client uses mountpoint_s3_crt.io.event_loop, so a change to mountpoint_s3_crt.io.event_loop can break mountpoint_s3_client.s3_crt_client, while a change to mountpoint_s3_client.s3_crt_client can't break mountpoint_s3_crt.io.event_loop.
- Position
- Below the diagonal: mountpoint_s3_client.s3_crt_client uses a module listed above it, which is the healthy direction.
36→32 mountpoint_s3_client.s3_crt_client uses mountpoint_s3_crt.s3.pool✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_client.s3_crt_client uses a type in mountpoint_s3_crt.s3.pool.
- The types involved
mountpoint_s3_client.s3_crt_client.S3ClientConfig→mountpoint_s3_crt.s3.pool.MemoryPoolFactoryWrapper
- Direction
- mountpoint_s3_client.s3_crt_client uses mountpoint_s3_crt.s3.pool, so a change to mountpoint_s3_crt.s3.pool can break mountpoint_s3_client.s3_crt_client, while a change to mountpoint_s3_client.s3_crt_client can't break mountpoint_s3_crt.s3.pool.
- Position
- Below the diagonal: mountpoint_s3_client.s3_crt_client uses a module listed above it, which is the healthy direction.
36→33 mountpoint_s3_client.s3_crt_client uses mountpoint_s3_crt.s3.client✕
- Connections
- 9 pairs of types, where a type in mountpoint_s3_client.s3_crt_client uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_client.s3_crt_client.CancellingMetaRequest→mountpoint_s3_crt.s3.client.MetaRequestmountpoint_s3_client.s3_crt_client.OnTelemetry→mountpoint_s3_crt.s3.client.RequestMetricsmountpoint_s3_client.s3_crt_client.S3CrtClient→mountpoint_s3_crt.s3.client.BufferPoolUsageStatsmountpoint_s3_client.s3_crt_client.S3CrtClientInner→mountpoint_s3_crt.s3.client.Clientmountpoint_s3_client.s3_crt_client.S3CrtClientInner→mountpoint_s3_crt.s3.client.MetaRequestOptionsmountpoint_s3_client.s3_crt_client.S3Message→mountpoint_s3_crt.s3.client.ChecksumConfigmountpoint_s3_client.s3_crt_client.S3Message→mountpoint_s3_crt.s3.client.MetaRequestOptionsmountpoint_s3_client.s3_crt_client.S3Operation→mountpoint_s3_crt.s3.client.MetaRequestTypemountpoint_s3_client.s3_crt_client.s3_crt_client$module→mountpoint_s3_crt.s3.client.MetaRequestResult
- Direction
- mountpoint_s3_client.s3_crt_client uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_client.s3_crt_client, while a change to mountpoint_s3_client.s3_crt_client can't break mountpoint_s3_crt.s3.client.
- Position
- Below the diagonal: mountpoint_s3_client.s3_crt_client uses a module listed above it, which is the healthy direction.
36→34 mountpoint_s3_client.s3_crt_client uses mountpoint_s3_client.object_client✕
- Connections
- 8 pairs of types, where a type in mountpoint_s3_client.s3_crt_client uses a type in mountpoint_s3_client.object_client.
- The types involved
mountpoint_s3_client.s3_crt_client.S3CrtClient→mountpoint_s3_client.object_client.CopyObjectParamsmountpoint_s3_client.s3_crt_client.S3CrtClient→mountpoint_s3_client.object_client.GetObjectParamsmountpoint_s3_client.s3_crt_client.S3CrtClient→mountpoint_s3_client.object_client.HeadObjectParamsmountpoint_s3_client.s3_crt_client.S3CrtClient→mountpoint_s3_client.object_client.ObjectClientmountpoint_s3_client.s3_crt_client.S3CrtClient→mountpoint_s3_client.object_client.PutObjectParamsmountpoint_s3_client.s3_crt_client.S3CrtClient→mountpoint_s3_client.object_client.PutObjectSingleParamsmountpoint_s3_client.s3_crt_client.S3CrtClient→mountpoint_s3_client.object_client.RenameObjectParamsmountpoint_s3_client.s3_crt_client.S3Message→mountpoint_s3_client.object_client.UploadChecksum
- Direction
- mountpoint_s3_client.s3_crt_client uses mountpoint_s3_client.object_client, so a change to mountpoint_s3_client.object_client can break mountpoint_s3_client.s3_crt_client, while a change to mountpoint_s3_client.s3_crt_client can't break mountpoint_s3_client.object_client.
- Position
- Below the diagonal: mountpoint_s3_client.s3_crt_client uses a module listed above it, which is the healthy direction.
37→2 mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_crt.checksums.crc32c✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache.express_data_cache uses a type in mountpoint_s3_crt.checksums.crc32c.
- The types involved
mountpoint_s3_fs.data_cache.express_data_cache.BlockMetadata→mountpoint_s3_crt.checksums.crc32c.Crc32c
- Direction
- mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_crt.checksums.crc32c, so a change to mountpoint_s3_crt.checksums.crc32c can break mountpoint_s3_fs.data_cache.express_data_cache, while a change to mountpoint_s3_fs.data_cache.express_data_cache can't break mountpoint_s3_crt.checksums.crc32c.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.express_data_cache uses a module listed above it, which is the healthy direction.
37→7 mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_fs.checksums✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache.express_data_cache uses a type in mountpoint_s3_fs.checksums.
- The types involved
mountpoint_s3_fs.data_cache.express_data_cache.ExpressDataCache→mountpoint_s3_fs.checksums.ChecksummedBytes
- Direction
- mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_fs.checksums, so a change to mountpoint_s3_fs.checksums can break mountpoint_s3_fs.data_cache.express_data_cache, while a change to mountpoint_s3_fs.data_cache.express_data_cache can't break mountpoint_s3_fs.checksums.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.express_data_cache uses a module listed above it, which is the healthy direction.
37→10 mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_fs.object✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3_fs.data_cache.express_data_cache uses a type in mountpoint_s3_fs.object.
- The types involved
mountpoint_s3_fs.data_cache.express_data_cache.BlockMetadata→mountpoint_s3_fs.object.ObjectIdmountpoint_s3_fs.data_cache.express_data_cache.ExpressDataCache→mountpoint_s3_fs.object.ObjectIdmountpoint_s3_fs.data_cache.express_data_cache.express_data_cache$module→mountpoint_s3_fs.object.ObjectId
- Direction
- mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_fs.object, so a change to mountpoint_s3_fs.object can break mountpoint_s3_fs.data_cache.express_data_cache, while a change to mountpoint_s3_fs.data_cache.express_data_cache can't break mountpoint_s3_fs.object.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.express_data_cache uses a module listed above it, which is the healthy direction.
37→21 mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_fs.prefetch.cursor✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache.express_data_cache uses a type in mountpoint_s3_fs.prefetch.cursor.
- The types involved
mountpoint_s3_fs.data_cache.express_data_cache.ExpressDataCache→mountpoint_s3_fs.prefetch.cursor.CursorId
- Direction
- mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_fs.prefetch.cursor, so a change to mountpoint_s3_fs.prefetch.cursor can break mountpoint_s3_fs.data_cache.express_data_cache, while a change to mountpoint_s3_fs.data_cache.express_data_cache can't break mountpoint_s3_fs.prefetch.cursor.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.express_data_cache uses a module listed above it, which is the healthy direction.
37→33 mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_crt.s3.client✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache.express_data_cache uses a type in mountpoint_s3_crt.s3.client.
- The types involved
mountpoint_s3_fs.data_cache.express_data_cache.ExpressDataCache→mountpoint_s3_crt.s3.client.Client
- Direction
- mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_crt.s3.client, so a change to mountpoint_s3_crt.s3.client can break mountpoint_s3_fs.data_cache.express_data_cache, while a change to mountpoint_s3_fs.data_cache.express_data_cache can't break mountpoint_s3_crt.s3.client.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.express_data_cache uses a module listed above it, which is the healthy direction.
37→34 mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_client.object_client✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.data_cache.express_data_cache uses a type in mountpoint_s3_client.object_client.
- The types involved
mountpoint_s3_fs.data_cache.express_data_cache.BlockMetadata→mountpoint_s3_client.object_client.PutObjectSingleParamsmountpoint_s3_fs.data_cache.express_data_cache.ExpressDataCache→mountpoint_s3_client.object_client.PutObjectSingleParams
- Direction
- mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_client.object_client, so a change to mountpoint_s3_client.object_client can break mountpoint_s3_fs.data_cache.express_data_cache, while a change to mountpoint_s3_fs.data_cache.express_data_cache can't break mountpoint_s3_client.object_client.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.express_data_cache uses a module listed above it, which is the healthy direction.
37→38 mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_fs.data_cache part of a loop✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache.express_data_cache uses a type in mountpoint_s3_fs.data_cache.
- The types involved
mountpoint_s3_fs.data_cache.express_data_cache.ExpressDataCache→mountpoint_s3_fs.data_cache.DataCache
- Direction
- mountpoint_s3_fs.data_cache.express_data_cache uses mountpoint_s3_fs.data_cache, so a change to mountpoint_s3_fs.data_cache can break mountpoint_s3_fs.data_cache.express_data_cache, while a change to mountpoint_s3_fs.data_cache.express_data_cache can't break mountpoint_s3_fs.data_cache.
- 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.
38→4 mountpoint_s3_fs.data_cache uses mountpoint_s3_crt.common.error✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache uses a type in mountpoint_s3_crt.common.error.
- The types involved
mountpoint_s3_fs.data_cache.DataCacheError→mountpoint_s3_crt.common.error.Error
- Direction
- mountpoint_s3_fs.data_cache uses mountpoint_s3_crt.common.error, so a change to mountpoint_s3_crt.common.error can break mountpoint_s3_fs.data_cache, while a change to mountpoint_s3_fs.data_cache can't break mountpoint_s3_crt.common.error.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache uses a module listed above it, which is the healthy direction.
38→7 mountpoint_s3_fs.data_cache uses mountpoint_s3_fs.checksums✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache uses a type in mountpoint_s3_fs.checksums.
- The types involved
mountpoint_s3_fs.data_cache.DataCache→mountpoint_s3_fs.checksums.ChecksummedBytes
- Direction
- mountpoint_s3_fs.data_cache uses mountpoint_s3_fs.checksums, so a change to mountpoint_s3_fs.checksums can break mountpoint_s3_fs.data_cache, while a change to mountpoint_s3_fs.data_cache can't break mountpoint_s3_fs.checksums.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache uses a module listed above it, which is the healthy direction.
38→10 mountpoint_s3_fs.data_cache uses mountpoint_s3_fs.object✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache uses a type in mountpoint_s3_fs.object.
- The types involved
mountpoint_s3_fs.data_cache.DataCache→mountpoint_s3_fs.object.ObjectId
- Direction
- mountpoint_s3_fs.data_cache uses mountpoint_s3_fs.object, so a change to mountpoint_s3_fs.object can break mountpoint_s3_fs.data_cache, while a change to mountpoint_s3_fs.data_cache can't break mountpoint_s3_fs.object.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache uses a module listed above it, which is the healthy direction.
38→21 mountpoint_s3_fs.data_cache uses mountpoint_s3_fs.prefetch.cursor✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache uses a type in mountpoint_s3_fs.prefetch.cursor.
- The types involved
mountpoint_s3_fs.data_cache.DataCache→mountpoint_s3_fs.prefetch.cursor.CursorId
- Direction
- mountpoint_s3_fs.data_cache uses mountpoint_s3_fs.prefetch.cursor, so a change to mountpoint_s3_fs.prefetch.cursor can break mountpoint_s3_fs.data_cache, while a change to mountpoint_s3_fs.data_cache can't break mountpoint_s3_fs.prefetch.cursor.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache uses a module listed above it, which is the healthy direction.
38→34 mountpoint_s3_fs.data_cache uses mountpoint_s3_client.object_client✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache uses a type in mountpoint_s3_client.object_client.
- The types involved
mountpoint_s3_fs.data_cache.DataCacheError→mountpoint_s3_client.object_client.ObjectClientError
- Direction
- mountpoint_s3_fs.data_cache uses mountpoint_s3_client.object_client, so a change to mountpoint_s3_client.object_client can break mountpoint_s3_fs.data_cache, while a change to mountpoint_s3_fs.data_cache can't break mountpoint_s3_client.object_client.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache uses a module listed above it, which is the healthy direction.
38→37 mountpoint_s3_fs.data_cache uses mountpoint_s3_fs.data_cache.express_data_cache✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache uses a type in mountpoint_s3_fs.data_cache.express_data_cache.
- The types involved
mountpoint_s3_fs.data_cache.DataCacheConfig→mountpoint_s3_fs.data_cache.express_data_cache.ExpressDataCacheConfig
- Direction
- mountpoint_s3_fs.data_cache uses mountpoint_s3_fs.data_cache.express_data_cache, so a change to mountpoint_s3_fs.data_cache.express_data_cache can break mountpoint_s3_fs.data_cache, while a change to mountpoint_s3_fs.data_cache can't break mountpoint_s3_fs.data_cache.express_data_cache.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache uses a module listed above it, which is the healthy direction.
38→39 mountpoint_s3_fs.data_cache uses mountpoint_s3_fs.data_cache.disk_data_cache part of a loop✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.data_cache uses a type in mountpoint_s3_fs.data_cache.disk_data_cache.
- The types involved
mountpoint_s3_fs.data_cache.DataCacheConfig→mountpoint_s3_fs.data_cache.disk_data_cache.DiskDataCacheConfigmountpoint_s3_fs.data_cache.DataCacheError→mountpoint_s3_fs.data_cache.disk_data_cache.DiskBlockReadWriteError
- Direction
- mountpoint_s3_fs.data_cache uses mountpoint_s3_fs.data_cache.disk_data_cache, so a change to mountpoint_s3_fs.data_cache.disk_data_cache can break mountpoint_s3_fs.data_cache, while a change to mountpoint_s3_fs.data_cache can't break mountpoint_s3_fs.data_cache.disk_data_cache.
- 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.
39→2 mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_crt.checksums.crc32c✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache.disk_data_cache uses a type in mountpoint_s3_crt.checksums.crc32c.
- The types involved
mountpoint_s3_fs.data_cache.disk_data_cache.DiskBlockHeader→mountpoint_s3_crt.checksums.crc32c.Crc32c
- Direction
- mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_crt.checksums.crc32c, so a change to mountpoint_s3_crt.checksums.crc32c can break mountpoint_s3_fs.data_cache.disk_data_cache, while a change to mountpoint_s3_fs.data_cache.disk_data_cache can't break mountpoint_s3_crt.checksums.crc32c.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.disk_data_cache uses a module listed above it, which is the healthy direction.
39→7 mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_fs.checksums✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.data_cache.disk_data_cache uses a type in mountpoint_s3_fs.checksums.
- The types involved
mountpoint_s3_fs.data_cache.disk_data_cache.DiskBlock→mountpoint_s3_fs.checksums.ChecksummedBytesmountpoint_s3_fs.data_cache.disk_data_cache.DiskDataCache→mountpoint_s3_fs.checksums.ChecksummedBytes
- Direction
- mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_fs.checksums, so a change to mountpoint_s3_fs.checksums can break mountpoint_s3_fs.data_cache.disk_data_cache, while a change to mountpoint_s3_fs.data_cache.disk_data_cache can't break mountpoint_s3_fs.checksums.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.disk_data_cache uses a module listed above it, which is the healthy direction.
39→10 mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_fs.object✕
- Connections
- 4 pairs of types, where a type in mountpoint_s3_fs.data_cache.disk_data_cache uses a type in mountpoint_s3_fs.object.
- The types involved
mountpoint_s3_fs.data_cache.disk_data_cache.DiskBlock→mountpoint_s3_fs.object.ObjectIdmountpoint_s3_fs.data_cache.disk_data_cache.DiskBlockKey→mountpoint_s3_fs.object.ObjectIdmountpoint_s3_fs.data_cache.disk_data_cache.DiskDataCache→mountpoint_s3_fs.object.ObjectIdmountpoint_s3_fs.data_cache.disk_data_cache.disk_data_cache$module→mountpoint_s3_fs.object.ObjectId
- Direction
- mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_fs.object, so a change to mountpoint_s3_fs.object can break mountpoint_s3_fs.data_cache.disk_data_cache, while a change to mountpoint_s3_fs.data_cache.disk_data_cache can't break mountpoint_s3_fs.object.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.disk_data_cache uses a module listed above it, which is the healthy direction.
39→13 mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_fs.memory.pool✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.data_cache.disk_data_cache uses a type in mountpoint_s3_fs.memory.pool.
- The types involved
mountpoint_s3_fs.data_cache.disk_data_cache.DiskBlock→mountpoint_s3_fs.memory.pool.PagedPoolmountpoint_s3_fs.data_cache.disk_data_cache.DiskDataCache→mountpoint_s3_fs.memory.pool.PagedPool
- Direction
- mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_fs.memory.pool, so a change to mountpoint_s3_fs.memory.pool can break mountpoint_s3_fs.data_cache.disk_data_cache, while a change to mountpoint_s3_fs.data_cache.disk_data_cache can't break mountpoint_s3_fs.memory.pool.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.disk_data_cache uses a module listed above it, which is the healthy direction.
39→21 mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_fs.prefetch.cursor✕
- Connections
- 2 pairs of types, where a type in mountpoint_s3_fs.data_cache.disk_data_cache uses a type in mountpoint_s3_fs.prefetch.cursor.
- The types involved
mountpoint_s3_fs.data_cache.disk_data_cache.DiskBlock→mountpoint_s3_fs.prefetch.cursor.CursorIdmountpoint_s3_fs.data_cache.disk_data_cache.DiskDataCache→mountpoint_s3_fs.prefetch.cursor.CursorId
- Direction
- mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_fs.prefetch.cursor, so a change to mountpoint_s3_fs.prefetch.cursor can break mountpoint_s3_fs.data_cache.disk_data_cache, while a change to mountpoint_s3_fs.data_cache.disk_data_cache can't break mountpoint_s3_fs.prefetch.cursor.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.disk_data_cache uses a module listed above it, which is the healthy direction.
39→38 mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_fs.data_cache✕
- Connections
- 1 pair of types, where a type in mountpoint_s3_fs.data_cache.disk_data_cache uses a type in mountpoint_s3_fs.data_cache.
- The types involved
mountpoint_s3_fs.data_cache.disk_data_cache.DiskDataCache→mountpoint_s3_fs.data_cache.DataCache
- Direction
- mountpoint_s3_fs.data_cache.disk_data_cache uses mountpoint_s3_fs.data_cache, so a change to mountpoint_s3_fs.data_cache can break mountpoint_s3_fs.data_cache.disk_data_cache, while a change to mountpoint_s3_fs.data_cache.disk_data_cache can't break mountpoint_s3_fs.data_cache.
- Position
- Below the diagonal: mountpoint_s3_fs.data_cache.disk_data_cache uses a module listed above it, which is the healthy direction.
40→6 mountpoint_s3.cli uses mountpoint_s3_fs.s3.path✕
- Connections
- 1 pair of types, where a type in mountpoint_s3.cli uses a type in mountpoint_s3_fs.s3.path.
- The types involved
mountpoint_s3.cli.CliArgs→mountpoint_s3_fs.s3.path.S3Path
- Direction
- mountpoint_s3.cli uses mountpoint_s3_fs.s3.path, so a change to mountpoint_s3_fs.s3.path can break mountpoint_s3.cli, while a change to mountpoint_s3.cli can't break mountpoint_s3_fs.s3.path.
- Position
- Below the diagonal: mountpoint_s3.cli uses a module listed above it, which is the healthy direction.
40→24 mountpoint_s3.cli uses mountpoint_s3_fs.fs.config✕
- Connections
- 3 pairs of types, where a type in mountpoint_s3.cli uses a type in mountpoint_s3_fs.fs.config.
- The types involved
mountpoint_s3.cli.CliArgs→mountpoint_s3_fs.fs.config.CacheConfigmountpoint_s3.cli.CliArgs→mountpoint_s3_fs.fs.config.S3FilesystemConfigmountpoint_s3.cli.CliArgs→mountpoint_s3_fs.fs.config.UploadChecksumAlgorithm
- Direction
- mountpoint_s3.cli uses mountpoint_s3_fs.fs.config, so a change to mountpoint_s3_fs.fs.config can break mountpoint_s3.cli, while a change to mountpoint_s3.cli can't break mountpoint_s3_fs.fs.config.
- Position
- Below the diagonal: mountpoint_s3.cli uses a module listed above it, which is the healthy direction.
40→36 mountpoint_s3.cli uses mountpoint_s3_client.s3_crt_client✕
- Connections
- 1 pair of types, where a type in mountpoint_s3.cli uses a type in mountpoint_s3_client.s3_crt_client.
- The types involved
mountpoint_s3.cli.CliArgs→mountpoint_s3_client.s3_crt_client.S3ClientAuthConfig
- Direction
- mountpoint_s3.cli uses mountpoint_s3_client.s3_crt_client, so a change to mountpoint_s3_client.s3_crt_client can break mountpoint_s3.cli, while a change to mountpoint_s3.cli can't break mountpoint_s3_client.s3_crt_client.
- Position
- Below the diagonal: mountpoint_s3.cli uses a module listed above it, which is the healthy direction.
40→39 mountpoint_s3.cli uses mountpoint_s3_fs.data_cache.disk_data_cache✕
- Connections
- 1 pair of types, where a type in mountpoint_s3.cli uses a type in mountpoint_s3_fs.data_cache.disk_data_cache.
- The types involved
mountpoint_s3.cli.CliArgs→mountpoint_s3_fs.data_cache.disk_data_cache.DiskDataCacheConfig
- Direction
- mountpoint_s3.cli uses mountpoint_s3_fs.data_cache.disk_data_cache, so a change to mountpoint_s3_fs.data_cache.disk_data_cache can break mountpoint_s3.cli, while a change to mountpoint_s3.cli can't break mountpoint_s3_fs.data_cache.disk_data_cache.
- Position
- Below the diagonal: mountpoint_s3.cli 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 41 | High / Critical |
| A05:2025 — Injection | 13 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | Medium |
Roadmap
First, enforce accessibility in the test suite by asserting invariants on rendered HTML and gating the test in CI to prevent regressions. Second, fix page structure issues by adding required semantic elements like language attributes and main landmarks, while ensuring headings are ordered correctly. Third, address the lack of architectural documentation by creating a dedicated folder for Architecture Decision Records that capture key design choices and their consequences. Finally, resolve the significant number of orphaned files by cleaning up unused modules such as mod.rs and notify.rs to improve codebase freshness.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +6.5 pts | Medium | A11y enforcement |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +6.0 pts | Medium | Page structure |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.8 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. | +2.7 pts | Medium | Architecture documentation |
| Resolve the 7 Orphaned knowledge finding(s) in Knowledge Freshness — start with request.rs (2), reply.rs (2), lib.rs. | +1.2 pts | Low | Knowledge Freshness |
| Resolve the 45 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (2), notify.rs (2), builder.rs. | +1.7 pts | Medium | Knowledge Freshness |
| Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2). | +0.7 pts | Low | Static Analysis (SAST) |
| Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. | +1.2 pts | Medium | Web-Security Posture |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| mountpoint-s3-fuser/src/request.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| mountpoint-s3-fs/src/superblock.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| mountpoint-s3-client/src/s3_crt_client.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| mountpoint-s3-client/src/mock_client.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| mountpoint-s3-fuser/src/ll/request.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| mountpoint-s3-crt/src/s3/client.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| mountpoint-s3-fs/src/fs.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| mountpoint-s3-client/src/object_client.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| mountpoint-s3-fuser/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| mountpoint-s3-fuser/src/ll/argument.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 67 of 67 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 67 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, 348 of 369 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 135 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.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 2 | 3 | # Need this because of Centos 7 reached EOL on July 1, 2024 and mirrorlist.centos.org does not exist anymore. -------------------- ERROR: failed to solve: public.ecr.aws/docker/library/centos:7: failed to resolve source metadata for public.ecr.aws/docker/library/centos:7: failed to do request: Head "https://public.ecr.aws/v2/docker/library/centos/manifests/7": Forbidden; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Rust, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 29 further occurrence(s) are not listed individually; the score already reflects all 69.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Request::dispatch_req at 60. A further 9 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being fuse_opcode::try_from at 50 — they are counted neither in the figure above nor in this dimension's score. 6 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: mountpoint-s3-fuser/src/ll/fuse_abi.rs (fuse_opcode::try_from at 50), mountpoint-s3-fuser/src/ll/request.rs (Operation::fmt at 49), mountpoint-s3-fs/src/fs/error.rs (InodeError::to_errno at 30), mountpoint-s3-fs/src/metrics/defs.rs (mountpoint_s3_fs::metrics::defs::lookup_config at 24), mountpoint-s3-fuser/src/mnt/fuse_pure.rs (mountpoint_s3_fuser::mnt::fuse_pure::option_group at 20), and 1 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with Request::dispatch_req (cyclomatic 60). — Refactoring it lifts Cyclomatic Complexity from 8.2 to about 9.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
17 method(s) exceeded the cognitive complexity threshold of 15; the worst was mountpoint_s3::bin::mount-s3-log-analyzer::main at 38.
What to do
- Bring the 17 bodies over 15 down to 15 or less in Cognitive Complexity — start with mountpoint_s3::bin::mount-s3-log-analyzer::main (cognitive 38), Superblock::readdir (cognitive 38), S3CrtClientInner::meta_request_with_callbacks (cognitive 31). — 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 17 together lifts Cognitive Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
24 god class(es) detected.
What to do
- Resolve the 10 FileTooLong finding(s) in God Classes — start with request.rs, superblock.rs, s3_crt_client.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 6 MethodTooLong finding(s) in God Classes — start with request.rs (2), superblock.rs (2), s3_crt_client.rs (2). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 ClassTooLong finding(s) in God Classes — start with superblock.rs, cli.rs, fs.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
28 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 1 of the 30 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 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with client.rs, fuse_pure.rs, request.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with handles_map.rs, get_object_attributes.rs, sha1.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with defs.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
6 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 5 of the 6 (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).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 175 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
831 test methods: 477 unit, 354 integration, 0 BDD, 0 e2e. The Rust suite contributes 823 `#[test]` function(s) across 135 file(s) declaring at least one; its unit/integration split is Cargo's own — 56 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Python suite contributes 8 test function(s) across 2 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D12 · Dependency Hygiene
5 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 345 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: mountpoint-s3-fs/src/fs/error.rs (3×30=90); benchmark/benchmarks/mountpoint.py (2×29=58); benchmark/benchmark.py (2×17=34)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with error.rs, mountpoint.py, benchmark.py. — One of this dimension's main actionable groups (3 warning-level).
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is mountpoint-s3-fs/src/fs/sse.rs. Counted over 150 of the 191 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
111 deducted task-comment markers across 57525 LoC (0.2/KLoC) → score 9.6. 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 102 TodoComment finding(s) in Explicit Debt — start with request.rs (26), harness.rs (6), reply.rs (5). — One of this dimension's main actionable groups (102 warning-level).
- Resolve the 8 FixmeComment finding(s) in Explicit Debt — start with direct_io.rs, consistency_test.rs, prefetch_test.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 XxxComment finding(s) in Explicit Debt — start with simple.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 24 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 7 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
13 finding(s): 0 critical, 11 high, 2 medium, 0 low. 1 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 3 file(s) — `mountpoint-s3-crt/src/s3/pool.rs` (line 329, line 349, line 467, …), `package/generate_amzn_srpm.sh` (line 4), `vendor-fuser.sh` (line 10) — 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. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
41 finding(s): 0 critical, 14 high, 20 medium, 7 low.
What to do
- Resolve the 20 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (20 warning-level).
- Resolve the 14 High IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 7 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (7 recommendation-level).
D34 · Knowledge Freshness
52 of 150 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is mountpoint-s3-fuser/src/ll/request.rs. Counted over 150 of the 191 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 45 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (2), notify.rs (2), builder.rs. — One of this dimension's main actionable groups (45 recommendation-level).
- Resolve the 7 Orphaned knowledge finding(s) in Knowledge Freshness — start with request.rs (2), reply.rs (2), lib.rs. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: atomic.rs↔incremental.rs 67%; failure_client.rs↔throughput_client.rs 64%; disk_data_cache.rs↔in_memory_data_cache.rs 60%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with atomic.rs, failure_client.rs, disk_data_cache.rs. — One of this dimension's main actionable groups (4 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — benchmark_website/index.html:0
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 1 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 7 project(s) that lack one — worth up to 0.3 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 5/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
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
- Dependabot is configured but does not watch `cargo`, `pip`, `gitsubmodule` — add those `package-ecosystem` entries to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — mountpoint-s3-client/src/object_client/etag.rs:33
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `name` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — package/attribution.hbs:4
- `crate.name` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — package/attribution.hbs:8
- `text` is text this program did not author, and it is written into the text of an element through Handlebars' raw `{{{ }}}` output with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — package/attribution.hbs:11
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug!` at line 46 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/autoconfigure.rs:46
- `debug!` at line 52 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/autoconfigure.rs:52
- `info!` at line 202 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:202
- `info!` at line 223 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:223
- `trace!` at line 285 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:285
- `trace!` at line 308 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:308
- `debug!` at line 325 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:325
- `trace!` at line 357 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:357
- `trace!` at line 362 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:362
- `debug!` at line 398 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:398
- `trace!` at line 414 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:414
- `trace!` at line 519 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:519
- `trace!` at line 567 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:567
- `trace!` at line 584 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:584
- `trace!` at line 595 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:595
- `trace!` at line 714 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:714
- `trace!` at line 800 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/fs.rs:800
- `error!` at line 118 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/logging.rs:118
- `error!` at line 119 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/logging.rs:119
- `warn!` at line 231 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/logging.rs:231
- `warn!` at line 234 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/logging.rs:234
- `warn!` at line 166 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/prefetch.rs:166
- `trace!` at line 347 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/superblock.rs:347
- `warn!` at line 598 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/superblock.rs:598
- `debug!` at line 710 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/superblock.rs:710
- `debug!` at line 1070 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/superblock.rs:1070
- `debug!` at line 1357 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/superblock.rs:1357
- `error!` at line 1366 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/superblock.rs:1366
- `trace!` at line 1502 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/superblock.rs:1502
- `warn!` at line 1597 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/superblock.rs:1597
- `warn!` at line 146 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/superblock/readdir.rs:146
- `warn!` at line 510 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/superblock/readdir.rs:510
- `warn!` at line 108 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/s3/config.rs:108
- `warn!` at line 251 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/s3/config.rs:251
- `warn!` at line 290 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/s3/config.rs:290
- `debug!` at line 120 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/memory/limiter.rs:120
- `info!` at line 90 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/memory/write_handle_limiter.rs:90
- `warn!` at line 295 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/manifest/builder.rs:295
- `error!` at line 95 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/manifest/core.rs:95
- `error!` at line 167 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — mountpoint-s3-fs/src/manifest/core.rs:167
What to do
- Interpolated log message defeats structured logging
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 79% | Strong | Solid. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 68% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 85% | Strong | Solid. |
| Security | 70% | Adequate — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 57% | Adequate | Largest drag on the score — prioritise here. |
| Performance | 94% | Exemplary | Strongest area. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AC6 Visual & motion safety — No styled element found in the parsed markup — AC6 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's 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 Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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) — 2 | 3 | # Need this because of Centos 7 reached EOL on July 1, 2024 and mirrorlist.centos.org does not exist anymore. -------------------- ERROR: failed to solve: public.ecr.aws/docker/library/centos:7: failed to resolve source metadata for public.ecr.aws/docker/library/centos:7: failed to do request: Head "https://public.ecr.aws/v2/docker/library/centos/manifests/7": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~29733 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
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Go, JavaScript, Python, Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .go, .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.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 54 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 JavaScript/TypeScript, Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 33 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge mountpoint-s3-fuser/src/ll/request.rs:1
- Orphaned knowledge mountpoint-s3-fuser/src/lib.rs:1
- Orphaned knowledge mountpoint-s3-fuser/src/reply.rs:1
- Orphaned knowledge mountpoint-s3-fuser/src/ll/fuse_abi.rs:1
- Orphaned knowledge mountpoint-s3-fuser/src/ll/reply.rs:1
- Orphaned knowledge mountpoint-s3-fuser/src/request.rs:1
- Orphaned knowledge mountpoint-s3-fs/src/metrics/data.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang benchmark_website/index.html
- REDACTED
- REDACTED
- REDACTED
Serious — 227 finding(s)
- TodoComment mountpoint-s3-fuser/src/lib.rs:60
- TodoComment mountpoint-s3-fuser/src/lib.rs:63
- TodoComment mountpoint-s3-fuser/src/lib.rs:66
- TodoComment mountpoint-s3-fuser/src/request.rs:6
- TodoComment mountpoint-s3-fuser/src/request.rs:176
- TodoComment mountpoint-s3-fuser/src/request.rs:514
- TodoComment mountpoint-s3-fuser/src/request.rs:608
- TodoComment mountpoint-s3-fuser/src/mnt/mount_options.rs:7
- TodoComment mountpoint-s3-fuser/src/ll/argument.rs:37
- TodoComment mountpoint-s3-fuser/src/ll/argument.rs:59
- TodoComment mountpoint-s3-fuser/src/ll/fuse_abi.rs:857
- TodoComment mountpoint-s3-fuser/src/ll/reply.rs:121
- TodoComment mountpoint-s3-fuser/src/ll/reply.rs:190
- TodoComment mountpoint-s3-fuser/src/ll/reply.rs:224
- TodoComment mountpoint-s3-fuser/src/ll/reply.rs:233
- TodoComment mountpoint-s3-fuser/src/ll/reply.rs:330
- TodoComment mountpoint-s3-fuser/src/ll/request.rs:127
- TodoComment mountpoint-s3-fuser/src/ll/request.rs:149
- TodoComment mountpoint-s3-fuser/src/ll/request.rs:472
- TodoComment mountpoint-s3-fuser/src/ll/request.rs:724
- TodoComment mountpoint-s3-fuser/src/ll/request.rs:737
- TodoComment mountpoint-s3-fuser/src/ll/request.rs:772
- TodoComment mountpoint-s3-fuser/src/ll/request.rs:819
- TodoComment mountpoint-s3-fuser/src/ll/request.rs:1014
- TodoComment mountpoint-s3-fuser/src/ll/request.rs:1072
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: ll/request.rs mountpoint-s3-fuser/src/ll/request.rs
- FileTooLong: src/superblock.rs mountpoint-s3-fs/src/superblock.rs
- FileTooLong: src/s3_crt_client.rs mountpoint-s3-client/src/s3_crt_client.rs
- FileTooLong: src/mock_client.rs mountpoint-s3-client/src/mock_client.rs
- FileTooLong: s3/client.rs mountpoint-s3-crt/src/s3/client.rs
- FileTooLong: ll/fuse_abi.rs mountpoint-s3-fuser/src/ll/fuse_abi.rs
- FileTooLong: src/cli.rs mountpoint-s3/src/cli.rs
- FileTooLong: src/object_client.rs mountpoint-s3-client/src/object_client.rs
- FileTooLong: src/lib.rs mountpoint-s3-fuser/src/lib.rs
- FileTooLong: src/fs.rs mountpoint-s3-fs/src/fs.rs
- FixmeComment mountpoint-s3-fs/tests/direct_io.rs:33
- FixmeComment mountpoint-s3-fs/tests/fuse_tests/consistency_test.rs:16
- FixmeComment mountpoint-s3-fs/tests/fuse_tests/prefetch_test.rs:82
- FixmeComment mountpoint-s3-fs/tests/fuse_tests/metrics_test.rs:152
- FixmeComment mountpoint-s3-fs/src/prefetch.rs:287
- FixmeComment mountpoint-s3-fs/src/superblock/inode.rs:780
- FixmeComment benchmark/benchmarks/crt_benchmark.py:106
- FixmeComment benchmark/analysis-scripts/autogroup.py:116
- MethodTooLong: Request.dispatch_req mountpoint-s3-fuser/src/request.rs:71
- MethodTooLong: Operation.fmt mountpoint-s3-fuser/src/ll/request.rs:1921
- MethodTooLong: Superblock.rename mountpoint-s3-fs/src/superblock.rs:440
- MethodTooLong: S3CrtClientInner.meta_request_with_callbacks mountpoint-s3-client/src/s3_crt_client.rs:680
- MethodTooLong: S3CrtClientInner.new mountpoint-s3-client/src/s3_crt_client.rs:452
- MethodTooLong: Superblock.readdir mountpoint-s3-fs/src/superblock.rs:1080
- Superblock::readdir (cognitive 38) mountpoint-s3-fs/src/superblock.rs:1080
- Superblock::open_handle (cognitive 20) mountpoint-s3-fs/src/superblock.rs:805
- Superblock::forget (cognitive 17) mountpoint-s3-fs/src/superblock.rs:1314
- Superblock::rename (cognitive 16) mountpoint-s3-fs/src/superblock.rs:440
- Superblock::finish_writing (cognitive 16) mountpoint-s3-fs/src/superblock.rs:916
- ClassTooLong: Superblock mountpoint-s3-fs/src/superblock.rs:70
- ClassTooLong: CliArgs mountpoint-s3/src/cli.rs:58
- ClassTooLong: S3Filesystem mountpoint-s3-fs/src/fs.rs:52
- ClassTooLong: Request mountpoint-s3-fuser/src/request.rs:28
- ClassTooLong: S3FuseFilesystem mountpoint-s3-fs/src/fuse.rs:83
- Change coupling: atomic.rs ↔ incremental.rs mountpoint-s3-fs/src/upload/atomic.rs:1
- Change coupling: failure_client.rs ↔ throughput_client.rs mountpoint-s3-client/src/failure_client.rs:1
- Change coupling: disk_data_cache.rs ↔ in_memory_data_cache.rs mountpoint-s3-fs/src/data_cache/disk_data_cache.rs:1
- Change coupling: fs.rs ↔ part_queue.rs mountpoint-s3-fs/src/fs.rs:1
- Hotspot: mountpoint-s3-fs/src/fs/error.rs mountpoint-s3-fs/src/fs/error.rs:159
- Hotspot: benchmark/benchmarks/mountpoint.py benchmark/benchmarks/mountpoint.py:24
- Hotspot: benchmark/benchmark.py benchmark/benchmark.py:100
- Duplicated block (12 lines × 2) mountpoint-s3-crt/src/s3/client.rs:1449
- Duplicated block (12 lines × 2) mountpoint-s3-fuser/src/mnt/fuse_pure.rs:288
- Duplicated block (12 lines × 2) mountpoint-s3-fuser/src/request.rs:91
- Duplicated block (5 lines × 2) mountpoint-s3-fs/src/superblock/handles_map.rs:116
- Duplicated block (5 lines × 2) mountpoint-s3-client/src/s3_crt_client/get_object_attributes.rs:192
- Duplicated block (5 lines × 2) mountpoint-s3-crt/src/checksums/sha1.rs:52
- Untrusted text written into markup unescaped package/attribution.hbs:4
- Untrusted text written into markup unescaped package/attribution.hbs:8
- Untrusted text written into markup unescaped package/attribution.hbs:11
- mountpoint_s3::bin::mount-s3-log-analyzer::main (cognitive 38) mountpoint-s3/src/bin/mount-s3-log-analyzer.rs:82
- mountpoint_s3::run::run (cognitive 20) mountpoint-s3/src/run.rs:45
- SuperblockInner::update_slow_path (cognitive 26) mountpoint-s3-fs/src/superblock.rs:1709
- SuperblockInner::remote_lookup (cognitive 25) mountpoint-s3-fs/src/superblock.rs:1512
- MockBucket::list_objects_ordered (cognitive 19) mountpoint-s3-client/src/mock_client.rs:586
- MockBucket::append_object (cognitive 16) mountpoint-s3-client/src/mock_client.rs:747
- TooManyFields: CliArgs mountpoint-s3/src/cli.rs:58
- TooManyFields: fuse_lowlevel_ops mountpoint-s3-fuser/src/mnt/fuse3_sys.rs:50
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2) mountpoint-s3-fs/src/metrics/defs.rs:75
- Duplicated block (13 lines × 2) mountpoint-s3-fs/src/metrics/defs.rs:109
- Duplicated block (11 lines × 2) mountpoint-s3-client/src/imds_crt_client.rs:29
- Duplicated block (11 lines × 2) mountpoint-s3-crt/src/s3/client.rs:1253
- Duplicated block (10 lines × 2) mountpoint-s3-fs/src/fs.rs:629
- Duplicated block (10 lines × 2) mountpoint-s3-fs/src/superblock.rs:1186
- Duplicated block (6 lines × 2) mountpoint-s3-fuser/src/request.rs:447
- Duplicated block (6 lines × 2) mountpoint-s3-crt/src/checksums/sha1.rs:34
- Accessibility enforcement below the top rung
- Request::dispatch_req (cyclomatic 60) mountpoint-s3-fuser/src/request.rs:71
- Superblock::readdir (cyclomatic 20) mountpoint-s3-fs/src/superblock.rs:1080
- S3CrtClientInner::meta_request_with_callbacks (cyclomatic 19) mountpoint-s3-client/src/s3_crt_client.rs:680
- SuperblockInner::update_slow_path (cyclomatic 17) mountpoint-s3-fs/src/superblock.rs:1709
- XxxComment mountpoint-s3-fuser/examples/simple.rs:1469
- S3CrtClientInner::meta_request_with_callbacks (cognitive 31) mountpoint-s3-client/src/s3_crt_client.rs:680
- CachingPartComposer::compose_parts (cognitive 18) mountpoint-s3-fs/src/prefetch/caching_stream.rs:287
- MockClient::get_object (cognitive 17) mountpoint-s3-client/src/mock_client.rs:1258
- ReaddirIter::next (cognitive 17) mountpoint-s3-fs/src/superblock/readdir.rs:480
- mountpoint_s3_fuser::mnt::fuse_pure::fuse_mount_fusermount (cognitive 17) mountpoint-s3-fuser/src/mnt/fuse_pure.rs:238
- Request::dispatch_req (cognitive 16) mountpoint-s3-fuser/src/request.rs:71
- REDACTED
- REDACTED
- FunctionTooLong: mountpoint_s3_fuser::ll::request::op::parse mountpoint-s3-fuser/src/ll/request.rs:1614
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (7 members, 50+ identical tokens) mountpoint-s3-client/src/s3_crt_client/copy_object.rs:65
- Members sharing a duplicated core (4 members, 50+ identical tokens) mountpoint-s3-fs/src/fs.rs:413
- Duplicated block (14 lines × 2) mountpoint-s3-fuser/src/ll/argument.rs:36
- Duplicated block (12 lines × 3) mountpoint-s3-fs/src/metrics/defs.rs:75
- Duplicated block (9–10 lines × 2) mountpoint-s3-fs/src/superblock.rs:788
- Duplicated block (8 lines × 4) mountpoint-s3-fs/src/fs.rs:426
- Duplicated block (6 lines × 7) mountpoint-s3-client/src/s3_crt_client/copy_object.rs:66
- Duplicated block (5 lines × 8) mountpoint-s3-client/src/s3_crt_client/copy_object.rs:67
- Duplicated block (5 lines × 3) mountpoint-s3-fs/src/manifest/db.rs:168
- Duplicated block (7 lines × 2) mountpoint-s3-fuser/src/mnt/fuse2.rs:13
- Duplicated block (9 lines × 5) mountpoint-s3-crt/src/auth.rs:18
- Duplicated block (11 lines × 3) mountpoint-s3-crt/src/checksums/crc32.rs:54
- Duplicated block (7 lines × 3) mountpoint-s3-crt/src/http/request_response.rs:312
- Duplicated block (8 lines × 2) mountpoint-s3-fs/src/logging/syslog.rs:178
- Duplicated block (5 lines × 9) mountpoint-s3-client/src/s3_crt_client/copy_object.rs:67
- Duplicated block (6–10 lines × 2) examples/pytorch/resnet.py:51
- Off the main sequence: mountpoint-s3-fuser
- Low cohesion: KernelConfig (LCOM4 5) mountpoint-s3-fuser/src/lib.rs:142
- Weak hash algorithm mountpoint-s3-client/src/object_client/etag.rs:33
Minor — 104 finding(s)
- Orphaned file mountpoint-s3-fs/src/manifest/builder.rs:1
- Orphaned file mountpoint-s3-crt/src/s3/endpoint_resolver.rs:1
- Orphaned file mountpoint-s3-fuser/src/mnt/fuse_pure.rs:1
- Orphaned file mountpoint-s3-client/src/endpoint_config.rs:1
- Orphaned file mountpoint-s3-crt/src/io/event_loop.rs:1
- Orphaned file mountpoint-s3-fs/src/manifest/core.rs:1
- Orphaned file mountpoint-s3-fs/src/manifest/db.rs:1
- Orphaned file mountpoint-s3-fuser/src/session.rs:1
- Orphaned file mountpoint-s3-client/src/s3_crt_client/get_object_attributes.rs:1
- Orphaned file mountpoint-s3-fuser/src/ll/mod.rs:1
- Orphaned file mountpoint-s3-fs/src/logging/syslog.rs:1
- Orphaned file mountpoint-s3-crt/src/common/logging.rs:1
- Orphaned file mountpoint-s3-fs/src/manifest/csv_reader.rs:1
- Orphaned file mountpoint-s3-crt/src/common/task_scheduler.rs:1
- Orphaned file mountpoint-s3-fuser/src/mnt/mount_options.rs:1
- Orphaned file mountpoint-s3-crt/src/common/uri.rs:1
- Orphaned file mountpoint-s3-fs/src/metrics/defs.rs:1
- Orphaned file mountpoint-s3-client/src/user_agent.rs:1
- Orphaned file mountpoint-s3-fuser/src/ll/notify.rs:1
- Orphaned file mountpoint-s3-client/src/mock_client/leaky_bucket.rs:1
- Orphaned file mountpoint-s3-fs/src/metrics_otel.rs:1
- Orphaned file mountpoint-s3-fs/src/superblock/handles_map.rs:1
- Orphaned file mountpoint-s3-fuser/src/mnt/mod.rs:1
- Orphaned file mountpoint-s3-fs/src/data_cache/in_memory_data_cache.rs:1
- Orphaned file mountpoint-s3-fuser/src/ll/argument.rs:1
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/autoconfigure.rs:46
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/autoconfigure.rs:52
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:202
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:223
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:285
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:308
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:325
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:357
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:362
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:398
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:414
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:519
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:567
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:584
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:595
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:714
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/fs.rs:800
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/logging.rs:118
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/logging.rs:119
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/logging.rs:231
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/logging.rs:234
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/prefetch.rs:166
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/superblock.rs:347
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/superblock.rs:598
- Interpolated log message defeats structured logging mountpoint-s3-fs/src/superblock.rs:710
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
Minor — 5 finding(s)
- Outdated: cc
- Outdated: const_format
- Outdated: libc
- Outdated: smallvec
- Outdated: uuid
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fba74fc197d143258d0e6e08729ca218/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fba74fc197d143258d0e6e08729ca218/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude mountpoint-s3-fs/src/autoconfigure . | 13 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 3 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 41 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |