Executive summary
hyperium/hyper meets our standard for production, though it has pipeline tools referenced by a changeable name. It scores 79 out of 100 and is rated Strong, and 60 of its 61 critical findings are security problems.
Security and Compliance, at 69, is the weakest lens and counts most in the score. The best first step is restricting the build's access tokens, worth about 3 points. Stopping the two pipeline steps that hand secrets to unpinned tools comes next, worth about 2 points.
Fifty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two passwords or keys are open to anyone who can read the repository, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 20,569 lines, about €54,000 to rebuild.
If Security and Compliance rose from 69 to 70, the lowest score rated Strong, the score would rise from 79 to about 79.
New since the last survey: 8 findings
- Code Duplication · Edited copy of a member (27 corresponding lines) src/proto/h1/decode.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/client/conn/http1.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) src/proto/h1/conn.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/ffi/io.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/error.rs
- Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) src/client/dispatch.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/client/conn/http1.rs
- Code Duplication · Duplicated block (11 lines × 2) src/proto/h1/role.rs
Fixed since the last survey: 3 findings
- Code Duplication · Duplicated block (11 lines × 2) src/proto/h1/role.rs
- Churn × Complexity Hotspots · Hotspot: src/proto/h1/conn.rs src/proto/h1/conn.rs
- Documentation (README) · README may be stale
Rebuild cost: about €54,000 · Estimate
| Cost to rebuild | €18,000 to €89,000, for 297 to 941 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.3 at a score of 79. 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: 20,569 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 body.length | 2 common.buf | 3 common.time | 4 ext | 5 ffi | 6 rt.bounds.h2_client.sealed_client | 7 rt.io | 8 client.conn.http1.upgrades | 9 client.dispatch | 10 common.date | 11 common.io.rewind | 12 ffi.task | 13 proto.h2 | 14 ffi.body | 15 upgrade | 16 upgrade.sealed | 17 ext.informational | 18 ffi.http_types | 19 proto | 20 proto.h1 | 21 proto.h1.io | 22 proto.h1.encode | 23 proto.h1.conn | 24 proto.h1.dispatch | 25 client.conn.http1 | 26 proto.h2.client | 27 server.conn.http1 | 28 client.conn.http2 | 29 proto.h2.ping | 30 body.incoming | 31 error | 32 proto.h1.decode | 33 body.chan | 34 proto.h1.role | 35 proto.h2.server | 36 proto.h2.upgrade | 37 server.conn.http2 | 38 rt.bounds.h2_common | 39 rt.bounds.h2_client | 40 rt.bounds.h2_server |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 body.length | ||||||||||||||||||||||||||||||||||||||||
| 2 common.buf | ||||||||||||||||||||||||||||||||||||||||
| 3 common.time | ||||||||||||||||||||||||||||||||||||||||
| 4 ext | ||||||||||||||||||||||||||||||||||||||||
| 5 ffi | ||||||||||||||||||||||||||||||||||||||||
| 6 rt.bounds.h2_client.sealed_client | ||||||||||||||||||||||||||||||||||||||||
| 7 rt.io | ||||||||||||||||||||||||||||||||||||||||
| 8 client.conn.http1.upgrades | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 client.dispatch | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 common.date | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 common.io.rewind | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 ffi.task | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 proto.h2 | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 ffi.body | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 upgrade | 5 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 16 upgrade.sealed | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 ext.informational | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 ffi.http_types | 2 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 19 proto | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 proto.h1 | 1 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 proto.h1.io | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 proto.h1.encode | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 proto.h1.conn | 2 | 4 | 1 | 2 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 24 proto.h1.dispatch | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 client.conn.http1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 proto.h2.client | 1 | 1 | 1 | 3 | 4 | 5 | ||||||||||||||||||||||||||||||||||
| 27 server.conn.http1 | 2 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 28 client.conn.http2 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 proto.h2.ping | 3 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 30 body.incoming | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 error | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 32 proto.h1.decode | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 body.chan | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 proto.h1.role | 2 | 1 | 3 | 8 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 35 proto.h2.server | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 36 proto.h2.upgrade | 3 | 1 | 2 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 37 server.conn.http2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 rt.bounds.h2_common | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 rt.bounds.h2_client | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 rt.bounds.h2_server | 1 | 1 | 1 |
8→25 client.conn.http1.upgrades uses client.conn.http1 part of a loop✕
- Connections
- 1 pair of types, where a type in client.conn.http1.upgrades uses a type in client.conn.http1.
- The types involved
hyper.client.conn.http1.upgrades.UpgradeableConnection→hyper.client.conn.http1.Connection
- Direction
- client.conn.http1.upgrades uses client.conn.http1, so a change to client.conn.http1 can break client.conn.http1.upgrades, while a change to client.conn.http1.upgrades can't break client.conn.http1.
- 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→26 client.dispatch uses proto.h2.client part of a loop✕
- Connections
- 1 pair of types, where a type in client.dispatch uses a type in proto.h2.client.
- The types involved
hyper.client.dispatch.SendWhen→hyper.proto.h2.client.ResponseFutMap
- Direction
- client.dispatch uses proto.h2.client, so a change to proto.h2.client can break client.dispatch, while a change to client.dispatch can't break proto.h2.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.
9→31 client.dispatch uses error part of a loop✕
- Connections
- 2 pairs of types, where a type in client.dispatch uses a type in error.
- The types involved
hyper.client.dispatch.TrySendError→hyper.error.Errorhyper.client.dispatch.dispatch$module→hyper.error.Error
- Direction
- client.dispatch uses error, so a change to error can break client.dispatch, while a change to client.dispatch can't break error.
- 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→7 common.date uses rt.io✕
- Connections
- 1 pair of types, where a type in common.date uses a type in rt.io.
- The types involved
hyper.common.date.CachedDate→hyper.rt.io.Write
- Direction
- common.date uses rt.io, so a change to rt.io can break common.date, while a change to common.date can't break rt.io.
- Position
- Below the diagonal: common.date uses a module listed above it, which is the healthy direction.
11→7 common.io.rewind uses rt.io✕
- Connections
- 3 pairs of types, where a type in common.io.rewind uses a type in rt.io.
- The types involved
hyper.common.io.rewind.Rewind→hyper.rt.io.Readhyper.common.io.rewind.Rewind→hyper.rt.io.ReadBufCursorhyper.common.io.rewind.Rewind→hyper.rt.io.Write
- Direction
- common.io.rewind uses rt.io, so a change to rt.io can break common.io.rewind, while a change to common.io.rewind can't break rt.io.
- Position
- Below the diagonal: common.io.rewind uses a module listed above it, which is the healthy direction.
12→5 ffi.task uses ffi✕
- Connections
- 1 pair of types, where a type in ffi.task uses a type in ffi.
- The types involved
hyper.ffi.task.hyper_task→hyper.ffi.UserDataPointer
- Direction
- ffi.task uses ffi, so a change to ffi can break ffi.task, while a change to ffi.task can't break ffi.
- Position
- Below the diagonal: ffi.task uses a module listed above it, which is the healthy direction.
13→31 proto.h2 uses error part of a loop✕
- Connections
- 1 pair of types, where a type in proto.h2 uses a type in error.
- The types involved
hyper.proto.h2.SendStreamExt→hyper.error.Error
- Direction
- proto.h2 uses error, so a change to error can break proto.h2, while a change to proto.h2 can't break error.
- 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→12 ffi.body uses ffi.task✕
- Connections
- 2 pairs of types, where a type in ffi.body uses a type in ffi.task.
- The types involved
hyper.ffi.body.hyper_buf→hyper.ffi.task.AsTaskTypehyper.ffi.body.hyper_buf→hyper.ffi.task.hyper_task_return_type
- Direction
- ffi.body uses ffi.task, so a change to ffi.task can break ffi.body, while a change to ffi.body can't break ffi.task.
- Position
- Below the diagonal: ffi.body uses a module listed above it, which is the healthy direction.
15→7 upgrade uses rt.io✕
- Connections
- 5 pairs of types, where a type in upgrade uses a type in rt.io.
- The types involved
hyper.upgrade.Io→hyper.rt.io.Readhyper.upgrade.Io→hyper.rt.io.Writehyper.upgrade.Upgraded→hyper.rt.io.Readhyper.upgrade.Upgraded→hyper.rt.io.ReadBufCursorhyper.upgrade.Upgraded→hyper.rt.io.Write
- Direction
- upgrade uses rt.io, so a change to rt.io can break upgrade, while a change to upgrade can't break rt.io.
- Position
- Below the diagonal: upgrade uses a module listed above it, which is the healthy direction.
15→11 upgrade uses common.io.rewind✕
- Connections
- 1 pair of types, where a type in upgrade uses a type in common.io.rewind.
- The types involved
hyper.upgrade.Upgraded→hyper.common.io.rewind.Rewind
- Direction
- upgrade uses common.io.rewind, so a change to common.io.rewind can break upgrade, while a change to upgrade can't break common.io.rewind.
- Position
- Below the diagonal: upgrade uses a module listed above it, which is the healthy direction.
15→33 upgrade uses body.chan part of a loop✕
- Connections
- 2 pairs of types, where a type in upgrade uses a type in body.chan.
- The types involved
hyper.upgrade.OnUpgrade→hyper.body.chan.Receiverhyper.upgrade.Pending→hyper.body.chan.Sender
- Direction
- upgrade uses body.chan, so a change to body.chan can break upgrade, while a change to upgrade can't break body.chan.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→15 upgrade.sealed uses upgrade✕
- Connections
- 1 pair of types, where a type in upgrade.sealed uses a type in upgrade.
- The types involved
hyper.upgrade.sealed.CanUpgrade→hyper.upgrade.OnUpgrade
- Direction
- upgrade.sealed uses upgrade, so a change to upgrade can break upgrade.sealed, while a change to upgrade.sealed can't break upgrade.
- Position
- Below the diagonal: upgrade.sealed uses a module listed above it, which is the healthy direction.
17→15 ext.informational uses upgrade✕
- Connections
- 1 pair of types, where a type in ext.informational uses a type in upgrade.
- The types involved
hyper.ext.informational.Response→hyper.upgrade.OnUpgrade
- Direction
- ext.informational uses upgrade, so a change to upgrade can break ext.informational, while a change to ext.informational can't break upgrade.
- Position
- Below the diagonal: ext.informational uses a module listed above it, which is the healthy direction.
17→16 ext.informational uses upgrade.sealed✕
- Connections
- 1 pair of types, where a type in ext.informational uses a type in upgrade.sealed.
- The types involved
hyper.ext.informational.Response→hyper.upgrade.sealed.CanUpgrade
- Direction
- ext.informational uses upgrade.sealed, so a change to upgrade.sealed can break ext.informational, while a change to ext.informational can't break upgrade.sealed.
- Position
- Below the diagonal: ext.informational uses a module listed above it, which is the healthy direction.
18→4 ffi.http_types uses ext✕
- Connections
- 2 pairs of types, where a type in ffi.http_types uses a type in ext.
- The types involved
hyper.ffi.http_types.hyper_headers→hyper.ext.HeaderCaseMaphyper.ffi.http_types.hyper_headers→hyper.ext.OriginalHeaderOrder
- Direction
- ffi.http_types uses ext, so a change to ext can break ffi.http_types, while a change to ffi.http_types can't break ext.
- Position
- Below the diagonal: ffi.http_types uses a module listed above it, which is the healthy direction.
18→5 ffi.http_types uses ffi✕
- Connections
- 1 pair of types, where a type in ffi.http_types uses a type in ffi.
- The types involved
hyper.ffi.http_types.OnInformational→hyper.ffi.UserDataPointer
- Direction
- ffi.http_types uses ffi, so a change to ffi can break ffi.http_types, while a change to ffi.http_types can't break ffi.
- Position
- Below the diagonal: ffi.http_types uses a module listed above it, which is the healthy direction.
18→12 ffi.http_types uses ffi.task✕
- Connections
- 2 pairs of types, where a type in ffi.http_types uses a type in ffi.task.
- The types involved
hyper.ffi.http_types.hyper_response→hyper.ffi.task.AsTaskTypehyper.ffi.http_types.hyper_response→hyper.ffi.task.hyper_task_return_type
- Direction
- ffi.http_types uses ffi.task, so a change to ffi.task can break ffi.http_types, while a change to ffi.http_types can't break ffi.task.
- Position
- Below the diagonal: ffi.http_types uses a module listed above it, which is the healthy direction.
18→17 ffi.http_types uses ext.informational✕
- Connections
- 3 pairs of types, where a type in ffi.http_types uses a type in ext.informational.
- The types involved
hyper.ffi.http_types.OnInformational→hyper.ext.informational.OnInformationalCallbackhyper.ffi.http_types.OnInformational→hyper.ext.informational.Responsehyper.ffi.http_types.hyper_response→hyper.ext.informational.Response
- Direction
- ffi.http_types uses ext.informational, so a change to ext.informational can break ffi.http_types, while a change to ffi.http_types can't break ext.informational.
- Position
- Below the diagonal: ffi.http_types uses a module listed above it, which is the healthy direction.
19→17 proto uses ext.informational✕
- Connections
- 1 pair of types, where a type in proto uses a type in ext.informational.
- The types involved
hyper.proto.MessageHead→hyper.ext.informational.Response
- Direction
- proto uses ext.informational, so a change to ext.informational can break proto, while a change to proto can't break ext.informational.
- Position
- Below the diagonal: proto uses a module listed above it, which is the healthy direction.
20→1 proto.h1 uses body.length✕
- Connections
- 1 pair of types, where a type in proto.h1 uses a type in body.length.
- The types involved
hyper.proto.h1.ParsedMessage→hyper.body.length.DecodedLength
- Direction
- proto.h1 uses body.length, so a change to body.length can break proto.h1, while a change to proto.h1 can't break body.length.
- Position
- Below the diagonal: proto.h1 uses a module listed above it, which is the healthy direction.
20→17 proto.h1 uses ext.informational✕
- Connections
- 1 pair of types, where a type in proto.h1 uses a type in ext.informational.
- The types involved
hyper.proto.h1.ParseContext→hyper.ext.informational.OnInformational
- Direction
- proto.h1 uses ext.informational, so a change to ext.informational can break proto.h1, while a change to proto.h1 can't break ext.informational.
- Position
- Below the diagonal: proto.h1 uses a module listed above it, which is the healthy direction.
20→19 proto.h1 uses proto✕
- Connections
- 4 pairs of types, where a type in proto.h1 uses a type in proto.
- The types involved
hyper.proto.h1.Encode→hyper.proto.BodyLengthhyper.proto.h1.Encode→hyper.proto.MessageHeadhyper.proto.h1.Http1Transaction→hyper.proto.MessageHeadhyper.proto.h1.ParsedMessage→hyper.proto.MessageHead
- Direction
- proto.h1 uses proto, so a change to proto can break proto.h1, while a change to proto.h1 can't break proto.
- Position
- Below the diagonal: proto.h1 uses a module listed above it, which is the healthy direction.
20→31 proto.h1 uses error part of a loop✕
- Connections
- 1 pair of types, where a type in proto.h1 uses a type in error.
- The types involved
hyper.proto.h1.Http1Transaction→hyper.error.Error
- Direction
- proto.h1 uses error, so a change to error can break proto.h1, while a change to proto.h1 can't break error.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→2 proto.h1.io uses common.buf✕
- Connections
- 1 pair of types, where a type in proto.h1.io uses a type in common.buf.
- The types involved
hyper.proto.h1.io.WriteBuf→hyper.common.buf.BufList
- Direction
- proto.h1.io uses common.buf, so a change to common.buf can break proto.h1.io, while a change to proto.h1.io can't break common.buf.
- Position
- Below the diagonal: proto.h1.io uses a module listed above it, which is the healthy direction.
21→20 proto.h1.io uses proto.h1✕
- Connections
- 1 pair of types, where a type in proto.h1.io uses a type in proto.h1.
- The types involved
hyper.proto.h1.io.Buffered→hyper.proto.h1.ParseContext
- Direction
- proto.h1.io uses proto.h1, so a change to proto.h1 can break proto.h1.io, while a change to proto.h1.io can't break proto.h1.
- Position
- Below the diagonal: proto.h1.io uses a module listed above it, which is the healthy direction.
22→7 proto.h1.encode uses rt.io✕
- Connections
- 1 pair of types, where a type in proto.h1.encode uses a type in rt.io.
- The types involved
hyper.proto.h1.encode.ChunkSize→hyper.rt.io.Write
- Direction
- proto.h1.encode uses rt.io, so a change to rt.io can break proto.h1.encode, while a change to proto.h1.encode can't break rt.io.
- Position
- Below the diagonal: proto.h1.encode uses a module listed above it, which is the healthy direction.
22→21 proto.h1.encode uses proto.h1.io✕
- Connections
- 1 pair of types, where a type in proto.h1.encode uses a type in proto.h1.io.
- The types involved
hyper.proto.h1.encode.Encoder→hyper.proto.h1.io.WriteBuf
- Direction
- proto.h1.encode uses proto.h1.io, so a change to proto.h1.io can break proto.h1.encode, while a change to proto.h1.encode can't break proto.h1.io.
- Position
- Below the diagonal: proto.h1.encode uses a module listed above it, which is the healthy direction.
22→30 proto.h1.encode uses body.incoming part of a loop✕
- Connections
- 1 pair of types, where a type in proto.h1.encode uses a type in body.incoming.
- The types involved
hyper.proto.h1.encode.Encoder→hyper.body.incoming.Kind
- Direction
- proto.h1.encode uses body.incoming, so a change to body.incoming can break proto.h1.encode, while a change to proto.h1.encode can't break body.incoming.
- 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→31 proto.h1.encode uses error part of a loop✕
- Connections
- 1 pair of types, where a type in proto.h1.encode uses a type in error.
- The types involved
hyper.proto.h1.encode.NotEof→hyper.error.Error
- Direction
- proto.h1.encode uses error, so a change to error can break proto.h1.encode, while a change to proto.h1.encode can't break error.
- 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→3 proto.h1.conn uses common.time✕
- Connections
- 2 pairs of types, where a type in proto.h1.conn uses a type in common.time.
- The types involved
hyper.proto.h1.conn.Conn→hyper.common.time.Timehyper.proto.h1.conn.State→hyper.common.time.Time
- Direction
- proto.h1.conn uses common.time, so a change to common.time can break proto.h1.conn, while a change to proto.h1.conn can't break common.time.
- Position
- Below the diagonal: proto.h1.conn uses a module listed above it, which is the healthy direction.
23→15 proto.h1.conn uses upgrade✕
- Connections
- 4 pairs of types, where a type in proto.h1.conn uses a type in upgrade.
- The types involved
hyper.proto.h1.conn.Conn→hyper.upgrade.OnUpgradehyper.proto.h1.conn.Conn→hyper.upgrade.Pendinghyper.proto.h1.conn.State→hyper.upgrade.OnUpgradehyper.proto.h1.conn.State→hyper.upgrade.Pending
- Direction
- proto.h1.conn uses upgrade, so a change to upgrade can break proto.h1.conn, while a change to proto.h1.conn can't break upgrade.
- Position
- Below the diagonal: proto.h1.conn uses a module listed above it, which is the healthy direction.
23→17 proto.h1.conn uses ext.informational✕
- Connections
- 1 pair of types, where a type in proto.h1.conn uses a type in ext.informational.
- The types involved
hyper.proto.h1.conn.State→hyper.ext.informational.OnInformational
- Direction
- proto.h1.conn uses ext.informational, so a change to ext.informational can break proto.h1.conn, while a change to proto.h1.conn can't break ext.informational.
- Position
- Below the diagonal: proto.h1.conn uses a module listed above it, which is the healthy direction.
23→19 proto.h1.conn uses proto✕
- Connections
- 2 pairs of types, where a type in proto.h1.conn uses a type in proto.
- The types involved
hyper.proto.h1.conn.Conn→hyper.proto.BodyLengthhyper.proto.h1.conn.Conn→hyper.proto.MessageHead
- Direction
- proto.h1.conn uses proto, so a change to proto can break proto.h1.conn, while a change to proto.h1.conn can't break proto.
- Position
- Below the diagonal: proto.h1.conn uses a module listed above it, which is the healthy direction.
23→21 proto.h1.conn uses proto.h1.io✕
- Connections
- 1 pair of types, where a type in proto.h1.conn uses a type in proto.h1.io.
- The types involved
hyper.proto.h1.conn.Conn→hyper.proto.h1.io.Buffered
- Direction
- proto.h1.conn uses proto.h1.io, so a change to proto.h1.io can break proto.h1.conn, while a change to proto.h1.conn can't break proto.h1.io.
- Position
- Below the diagonal: proto.h1.conn uses a module listed above it, which is the healthy direction.
23→22 proto.h1.conn uses proto.h1.encode✕
- Connections
- 1 pair of types, where a type in proto.h1.conn uses a type in proto.h1.encode.
- The types involved
hyper.proto.h1.conn.Conn→hyper.proto.h1.encode.Encoder
- Direction
- proto.h1.conn uses proto.h1.encode, so a change to proto.h1.encode can break proto.h1.conn, while a change to proto.h1.conn can't break proto.h1.encode.
- Position
- Below the diagonal: proto.h1.conn uses a module listed above it, which is the healthy direction.
23→31 proto.h1.conn uses error part of a loop✕
- Connections
- 2 pairs of types, where a type in proto.h1.conn uses a type in error.
- The types involved
hyper.proto.h1.conn.Conn→hyper.error.Errorhyper.proto.h1.conn.State→hyper.error.Error
- Direction
- proto.h1.conn uses error, so a change to error can break proto.h1.conn, while a change to proto.h1.conn can't break error.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→33 proto.h1.conn uses body.chan part of a loop✕
- Connections
- 1 pair of types, where a type in proto.h1.conn uses a type in body.chan.
- The types involved
hyper.proto.h1.conn.Conn→hyper.body.chan.State
- Direction
- proto.h1.conn uses body.chan, so a change to body.chan can break proto.h1.conn, while a change to proto.h1.conn can't break body.chan.
- 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→23 proto.h1.dispatch uses proto.h1.conn✕
- Connections
- 1 pair of types, where a type in proto.h1.dispatch uses a type in proto.h1.conn.
- The types involved
hyper.proto.h1.dispatch.Dispatcher→hyper.proto.h1.conn.Conn
- Direction
- proto.h1.dispatch uses proto.h1.conn, so a change to proto.h1.conn can break proto.h1.dispatch, while a change to proto.h1.dispatch can't break proto.h1.conn.
- Position
- Below the diagonal: proto.h1.dispatch uses a module listed above it, which is the healthy direction.
24→33 proto.h1.dispatch uses body.chan part of a loop✕
- Connections
- 1 pair of types, where a type in proto.h1.dispatch uses a type in body.chan.
- The types involved
hyper.proto.h1.dispatch.SenderDropGuard→hyper.body.chan.Sender
- Direction
- proto.h1.dispatch uses body.chan, so a change to body.chan can break proto.h1.dispatch, while a change to proto.h1.dispatch can't break body.chan.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→8 client.conn.http1 uses client.conn.http1.upgrades✕
- Connections
- 1 pair of types, where a type in client.conn.http1 uses a type in client.conn.http1.upgrades.
- The types involved
hyper.client.conn.http1.Connection→hyper.client.conn.http1.upgrades.UpgradeableConnection
- Direction
- client.conn.http1 uses client.conn.http1.upgrades, so a change to client.conn.http1.upgrades can break client.conn.http1, while a change to client.conn.http1 can't break client.conn.http1.upgrades.
- Position
- Below the diagonal: client.conn.http1 uses a module listed above it, which is the healthy direction.
25→24 client.conn.http1 uses proto.h1.dispatch✕
- Connections
- 1 pair of types, where a type in client.conn.http1 uses a type in proto.h1.dispatch.
- The types involved
hyper.client.conn.http1.Connection→hyper.proto.h1.dispatch.Dispatcher
- Direction
- client.conn.http1 uses proto.h1.dispatch, so a change to proto.h1.dispatch can break client.conn.http1, while a change to client.conn.http1 can't break proto.h1.dispatch.
- Position
- Below the diagonal: client.conn.http1 uses a module listed above it, which is the healthy direction.
25→33 client.conn.http1 uses body.chan part of a loop✕
- Connections
- 1 pair of types, where a type in client.conn.http1 uses a type in body.chan.
- The types involved
hyper.client.conn.http1.SendRequest→hyper.body.chan.Sender
- Direction
- client.conn.http1 uses body.chan, so a change to body.chan can break client.conn.http1, while a change to client.conn.http1 can't break body.chan.
- 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→3 proto.h2.client uses common.time✕
- Connections
- 1 pair of types, where a type in proto.h2.client uses a type in common.time.
- The types involved
hyper.proto.h2.client.client$module→hyper.common.time.Time
- Direction
- proto.h2.client uses common.time, so a change to common.time can break proto.h2.client, while a change to proto.h2.client can't break common.time.
- Position
- Below the diagonal: proto.h2.client uses a module listed above it, which is the healthy direction.
26→9 proto.h2.client uses client.dispatch✕
- Connections
- 1 pair of types, where a type in proto.h2.client uses a type in client.dispatch.
- The types involved
hyper.proto.h2.client.FutCtx→hyper.client.dispatch.Callback
- Direction
- proto.h2.client uses client.dispatch, so a change to client.dispatch can break proto.h2.client, while a change to proto.h2.client can't break client.dispatch.
- Position
- Below the diagonal: proto.h2.client uses a module listed above it, which is the healthy direction.
26→13 proto.h2.client uses proto.h2✕
- Connections
- 1 pair of types, where a type in proto.h2.client uses a type in proto.h2.
- The types involved
hyper.proto.h2.client.PipeMap→hyper.proto.h2.PipeToSendStream
- Direction
- proto.h2.client uses proto.h2, so a change to proto.h2 can break proto.h2.client, while a change to proto.h2.client can't break proto.h2.
- Position
- Below the diagonal: proto.h2.client uses a module listed above it, which is the healthy direction.
26→25 proto.h2.client uses client.conn.http1✕
- Connections
- 3 pairs of types, where a type in proto.h2.client uses a type in client.conn.http1.
- The types involved
hyper.proto.h2.client.ClientTask→hyper.client.conn.http1.SendRequesthyper.proto.h2.client.Conn→hyper.client.conn.http1.Connectionhyper.proto.h2.client.client$module→hyper.client.conn.http1.Builder
- Direction
- proto.h2.client uses client.conn.http1, so a change to client.conn.http1 can break proto.h2.client, while a change to proto.h2.client can't break client.conn.http1.
- Position
- Below the diagonal: proto.h2.client uses a module listed above it, which is the healthy direction.
26→29 proto.h2.client uses proto.h2.ping part of a loop✕
- Connections
- 4 pairs of types, where a type in proto.h2.client uses a type in proto.h2.ping.
- The types involved
hyper.proto.h2.client.ClientTask→hyper.proto.h2.ping.Recorderhyper.proto.h2.client.Conn→hyper.proto.h2.ping.Pongerhyper.proto.h2.client.PipeMap→hyper.proto.h2.ping.Recorderhyper.proto.h2.client.ResponseFutMap→hyper.proto.h2.ping.Recorder
- Direction
- proto.h2.client uses proto.h2.ping, so a change to proto.h2.ping can break proto.h2.client, while a change to proto.h2.client can't break proto.h2.ping.
- 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→33 proto.h2.client uses body.chan part of a loop✕
- Connections
- 5 pairs of types, where a type in proto.h2.client uses a type in body.chan.
- The types involved
hyper.proto.h2.client.ConnTask→hyper.body.chan.Receiverhyper.proto.h2.client.ConnTask→hyper.body.chan.Senderhyper.proto.h2.client.PipeMap→hyper.body.chan.Receiverhyper.proto.h2.client.PipeMap→hyper.body.chan.Senderhyper.proto.h2.client.ResponseFutMap→hyper.body.chan.Sender
- Direction
- proto.h2.client uses body.chan, so a change to body.chan can break proto.h2.client, while a change to proto.h2.client can't break body.chan.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→3 server.conn.http1 uses common.time✕
- Connections
- 2 pairs of types, where a type in server.conn.http1 uses a type in common.time.
- The types involved
hyper.server.conn.http1.Builder→hyper.common.time.Durhyper.server.conn.http1.Builder→hyper.common.time.Time
- Direction
- server.conn.http1 uses common.time, so a change to common.time can break server.conn.http1, while a change to server.conn.http1 can't break common.time.
- Position
- Below the diagonal: server.conn.http1 uses a module listed above it, which is the healthy direction.
27→8 server.conn.http1 uses client.conn.http1.upgrades✕
- Connections
- 1 pair of types, where a type in server.conn.http1 uses a type in client.conn.http1.upgrades.
- The types involved
hyper.server.conn.http1.Connection→hyper.client.conn.http1.upgrades.UpgradeableConnection
- Direction
- server.conn.http1 uses client.conn.http1.upgrades, so a change to client.conn.http1.upgrades can break server.conn.http1, while a change to server.conn.http1 can't break client.conn.http1.upgrades.
- Position
- Below the diagonal: server.conn.http1 uses a module listed above it, which is the healthy direction.
27→25 server.conn.http1 uses client.conn.http1✕
- Connections
- 5 pairs of types, where a type in server.conn.http1 uses a type in client.conn.http1.
- The types involved
hyper.server.conn.http1.Builder→hyper.client.conn.http1.Builderhyper.server.conn.http1.Builder→hyper.client.conn.http1.Connectionhyper.server.conn.http1.Connection→hyper.client.conn.http1.Partshyper.server.conn.http1.UpgradeableConnection→hyper.client.conn.http1.Connectionhyper.server.conn.http1.UpgradeableConnection→hyper.client.conn.http1.Parts
- Direction
- server.conn.http1 uses client.conn.http1, so a change to client.conn.http1 can break server.conn.http1, while a change to server.conn.http1 can't break client.conn.http1.
- Position
- Below the diagonal: server.conn.http1 uses a module listed above it, which is the healthy direction.
28→3 client.conn.http2 uses common.time✕
- Connections
- 1 pair of types, where a type in client.conn.http2 uses a type in common.time.
- The types involved
hyper.client.conn.http2.Builder→hyper.common.time.Time
- Direction
- client.conn.http2 uses common.time, so a change to common.time can break client.conn.http2, while a change to client.conn.http2 can't break common.time.
- Position
- Below the diagonal: client.conn.http2 uses a module listed above it, which is the healthy direction.
28→9 client.conn.http2 uses client.dispatch✕
- Connections
- 1 pair of types, where a type in client.conn.http2 uses a type in client.dispatch.
- The types involved
hyper.client.conn.http2.SendRequest→hyper.client.dispatch.UnboundedSender
- Direction
- client.conn.http2 uses client.dispatch, so a change to client.dispatch can break client.conn.http2, while a change to client.conn.http2 can't break client.dispatch.
- Position
- Below the diagonal: client.conn.http2 uses a module listed above it, which is the healthy direction.
28→25 client.conn.http2 uses client.conn.http1✕
- Connections
- 2 pairs of types, where a type in client.conn.http2 uses a type in client.conn.http1.
- The types involved
hyper.client.conn.http2.Builder→hyper.client.conn.http1.Builderhyper.client.conn.http2.SendRequest→hyper.client.conn.http1.SendRequest
- Direction
- client.conn.http2 uses client.conn.http1, so a change to client.conn.http1 can break client.conn.http2, while a change to client.conn.http2 can't break client.conn.http1.
- Position
- Below the diagonal: client.conn.http2 uses a module listed above it, which is the healthy direction.
28→26 client.conn.http2 uses proto.h2.client✕
- Connections
- 1 pair of types, where a type in client.conn.http2 uses a type in proto.h2.client.
- The types involved
hyper.client.conn.http2.Builder→hyper.proto.h2.client.Config
- Direction
- client.conn.http2 uses proto.h2.client, so a change to proto.h2.client can break client.conn.http2, while a change to client.conn.http2 can't break proto.h2.client.
- Position
- Below the diagonal: client.conn.http2 uses a module listed above it, which is the healthy direction.
29→3 proto.h2.ping uses common.time✕
- Connections
- 3 pairs of types, where a type in proto.h2.ping uses a type in common.time.
- The types involved
hyper.proto.h2.ping.KeepAlive→hyper.common.time.Timehyper.proto.h2.ping.Shared→hyper.common.time.Timehyper.proto.h2.ping.ping$module→hyper.common.time.Time
- Direction
- proto.h2.ping uses common.time, so a change to common.time can break proto.h2.ping, while a change to proto.h2.ping can't break common.time.
- Position
- Below the diagonal: proto.h2.ping uses a module listed above it, which is the healthy direction.
29→26 proto.h2.ping uses proto.h2.client✕
- Connections
- 1 pair of types, where a type in proto.h2.ping uses a type in proto.h2.client.
- The types involved
hyper.proto.h2.ping.ping$module→hyper.proto.h2.client.Config
- Direction
- proto.h2.ping uses proto.h2.client, so a change to proto.h2.client can break proto.h2.ping, while a change to proto.h2.ping can't break proto.h2.client.
- Position
- Below the diagonal: proto.h2.ping uses a module listed above it, which is the healthy direction.
29→31 proto.h2.ping uses error part of a loop✕
- Connections
- 1 pair of types, where a type in proto.h2.ping uses a type in error.
- The types involved
hyper.proto.h2.ping.KeepAliveTimedOut→hyper.error.Error
- Direction
- proto.h2.ping uses error, so a change to error can break proto.h2.ping, while a change to proto.h2.ping can't break error.
- 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→33 proto.h2.ping uses body.chan part of a loop✕
- Connections
- 3 pairs of types, where a type in proto.h2.ping uses a type in body.chan.
- The types involved
hyper.proto.h2.ping.KeepAlive→hyper.body.chan.Sharedhyper.proto.h2.ping.Ponger→hyper.body.chan.Sharedhyper.proto.h2.ping.Recorder→hyper.body.chan.Shared
- Direction
- proto.h2.ping uses body.chan, so a change to body.chan can break proto.h2.ping, while a change to proto.h2.ping can't break body.chan.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→1 body.incoming uses body.length✕
- Connections
- 1 pair of types, where a type in body.incoming uses a type in body.length.
- The types involved
hyper.body.incoming.Incoming→hyper.body.length.DecodedLength
- Direction
- body.incoming uses body.length, so a change to body.length can break body.incoming, while a change to body.incoming can't break body.length.
- Position
- Below the diagonal: body.incoming uses a module listed above it, which is the healthy direction.
30→14 body.incoming uses ffi.body✕
- Connections
- 1 pair of types, where a type in body.incoming uses a type in ffi.body.
- The types involved
hyper.body.incoming.Incoming→hyper.ffi.body.UserBody
- Direction
- body.incoming uses ffi.body, so a change to ffi.body can break body.incoming, while a change to body.incoming can't break ffi.body.
- Position
- Below the diagonal: body.incoming uses a module listed above it, which is the healthy direction.
30→29 body.incoming uses proto.h2.ping✕
- Connections
- 1 pair of types, where a type in body.incoming uses a type in proto.h2.ping.
- The types involved
hyper.body.incoming.Incoming→hyper.proto.h2.ping.Recorder
- Direction
- body.incoming uses proto.h2.ping, so a change to proto.h2.ping can break body.incoming, while a change to body.incoming can't break proto.h2.ping.
- Position
- Below the diagonal: body.incoming uses a module listed above it, which is the healthy direction.
31→12 error uses ffi.task✕
- Connections
- 2 pairs of types, where a type in error uses a type in ffi.task.
- The types involved
hyper.error.Error→hyper.ffi.task.AsTaskTypehyper.error.Error→hyper.ffi.task.hyper_task_return_type
- Direction
- error uses ffi.task, so a change to ffi.task can break error, while a change to error can't break ffi.task.
- Position
- Below the diagonal: error uses a module listed above it, which is the healthy direction.
31→30 error uses body.incoming✕
- Connections
- 2 pairs of types, where a type in error uses a type in body.incoming.
- The types involved
hyper.error.Error→hyper.body.incoming.Kindhyper.error.ErrorImpl→hyper.body.incoming.Kind
- Direction
- error uses body.incoming, so a change to body.incoming can break error, while a change to error can't break body.incoming.
- Position
- Below the diagonal: error uses a module listed above it, which is the healthy direction.
32→1 proto.h1.decode uses body.length✕
- Connections
- 1 pair of types, where a type in proto.h1.decode uses a type in body.length.
- The types involved
hyper.proto.h1.decode.Decoder→hyper.body.length.DecodedLength
- Direction
- proto.h1.decode uses body.length, so a change to body.length can break proto.h1.decode, while a change to proto.h1.decode can't break body.length.
- Position
- Below the diagonal: proto.h1.decode uses a module listed above it, which is the healthy direction.
32→30 proto.h1.decode uses body.incoming✕
- Connections
- 1 pair of types, where a type in proto.h1.decode uses a type in body.incoming.
- The types involved
hyper.proto.h1.decode.Decoder→hyper.body.incoming.Kind
- Direction
- proto.h1.decode uses body.incoming, so a change to body.incoming can break proto.h1.decode, while a change to proto.h1.decode can't break body.incoming.
- Position
- Below the diagonal: proto.h1.decode uses a module listed above it, which is the healthy direction.
33→31 body.chan uses error✕
- Connections
- 2 pairs of types, where a type in body.chan uses a type in error.
- The types involved
hyper.body.chan.Sender→hyper.error.Errorhyper.body.chan.State→hyper.error.Error
- Direction
- body.chan uses error, so a change to error can break body.chan, while a change to body.chan can't break error.
- Position
- Below the diagonal: body.chan uses a module listed above it, which is the healthy direction.
34→4 proto.h1.role uses ext✕
- Connections
- 2 pairs of types, where a type in proto.h1.role uses a type in ext.
- The types involved
hyper.proto.h1.role.Server→hyper.ext.HeaderCaseMaphyper.proto.h1.role.role$module→hyper.ext.HeaderCaseMap
- Direction
- proto.h1.role uses ext, so a change to ext can break proto.h1.role, while a change to proto.h1.role can't break ext.
- Position
- Below the diagonal: proto.h1.role uses a module listed above it, which is the healthy direction.
34→7 proto.h1.role uses rt.io✕
- Connections
- 1 pair of types, where a type in proto.h1.role uses a type in rt.io.
- The types involved
hyper.proto.h1.role.FastWrite→hyper.rt.io.Write
- Direction
- proto.h1.role uses rt.io, so a change to rt.io can break proto.h1.role, while a change to proto.h1.role can't break rt.io.
- Position
- Below the diagonal: proto.h1.role uses a module listed above it, which is the healthy direction.
34→19 proto.h1.role uses proto✕
- Connections
- 3 pairs of types, where a type in proto.h1.role uses a type in proto.
- The types involved
hyper.proto.h1.role.Client→hyper.proto.BodyLengthhyper.proto.h1.role.Client→hyper.proto.MessageHeadhyper.proto.h1.role.Server→hyper.proto.MessageHead
- Direction
- proto.h1.role uses proto, so a change to proto can break proto.h1.role, while a change to proto.h1.role can't break proto.
- Position
- Below the diagonal: proto.h1.role uses a module listed above it, which is the healthy direction.
34→20 proto.h1.role uses proto.h1✕
- Connections
- 8 pairs of types, where a type in proto.h1.role uses a type in proto.h1.
- The types involved
hyper.proto.h1.role.Client→hyper.proto.h1.Encodehyper.proto.h1.role.Client→hyper.proto.h1.Http1Transactionhyper.proto.h1.role.Client→hyper.proto.h1.ParseContexthyper.proto.h1.role.Server→hyper.proto.h1.Encodehyper.proto.h1.role.Server→hyper.proto.h1.Http1Transactionhyper.proto.h1.role.Server→hyper.proto.h1.ParseContexthyper.proto.h1.role.role$module→hyper.proto.h1.Encodehyper.proto.h1.role.role$module→hyper.proto.h1.ParseContext
- Direction
- proto.h1.role uses proto.h1, so a change to proto.h1 can break proto.h1.role, while a change to proto.h1.role can't break proto.h1.
- Position
- Below the diagonal: proto.h1.role uses a module listed above it, which is the healthy direction.
34→22 proto.h1.role uses proto.h1.encode✕
- Connections
- 2 pairs of types, where a type in proto.h1.role uses a type in proto.h1.encode.
- The types involved
hyper.proto.h1.role.Client→hyper.proto.h1.encode.Encoderhyper.proto.h1.role.role$module→hyper.proto.h1.encode.Encoder
- Direction
- proto.h1.role uses proto.h1.encode, so a change to proto.h1.encode can break proto.h1.role, while a change to proto.h1.role can't break proto.h1.encode.
- Position
- Below the diagonal: proto.h1.role uses a module listed above it, which is the healthy direction.
34→31 proto.h1.role uses error✕
- Connections
- 2 pairs of types, where a type in proto.h1.role uses a type in error.
- The types involved
hyper.proto.h1.role.Client→hyper.error.Errorhyper.proto.h1.role.Server→hyper.error.Error
- Direction
- proto.h1.role uses error, so a change to error can break proto.h1.role, while a change to proto.h1.role can't break error.
- Position
- Below the diagonal: proto.h1.role uses a module listed above it, which is the healthy direction.
35→3 proto.h2.server uses common.time✕
- Connections
- 1 pair of types, where a type in proto.h2.server uses a type in common.time.
- The types involved
hyper.proto.h2.server.Server→hyper.common.time.Time
- Direction
- proto.h2.server uses common.time, so a change to common.time can break proto.h2.server, while a change to proto.h2.server can't break common.time.
- Position
- Below the diagonal: proto.h2.server uses a module listed above it, which is the healthy direction.
35→15 proto.h2.server uses upgrade✕
- Connections
- 1 pair of types, where a type in proto.h2.server uses a type in upgrade.
- The types involved
hyper.proto.h2.server.ConnectParts→hyper.upgrade.Pending
- Direction
- proto.h2.server uses upgrade, so a change to upgrade can break proto.h2.server, while a change to proto.h2.server can't break upgrade.
- Position
- Below the diagonal: proto.h2.server uses a module listed above it, which is the healthy direction.
35→25 proto.h2.server uses client.conn.http1✕
- Connections
- 1 pair of types, where a type in proto.h2.server uses a type in client.conn.http1.
- The types involved
hyper.proto.h2.server.Serving→hyper.client.conn.http1.Connection
- Direction
- proto.h2.server uses client.conn.http1, so a change to client.conn.http1 can break proto.h2.server, while a change to proto.h2.server can't break client.conn.http1.
- Position
- Below the diagonal: proto.h2.server uses a module listed above it, which is the healthy direction.
35→26 proto.h2.server uses proto.h2.client✕
- Connections
- 2 pairs of types, where a type in proto.h2.server uses a type in proto.h2.client.
- The types involved
hyper.proto.h2.server.Config→hyper.proto.h2.client.Confighyper.proto.h2.server.Server→hyper.proto.h2.client.Config
- Direction
- proto.h2.server uses proto.h2.client, so a change to proto.h2.client can break proto.h2.server, while a change to proto.h2.server can't break proto.h2.client.
- Position
- Below the diagonal: proto.h2.server uses a module listed above it, which is the healthy direction.
35→29 proto.h2.server uses proto.h2.ping✕
- Connections
- 1 pair of types, where a type in proto.h2.server uses a type in proto.h2.ping.
- The types involved
hyper.proto.h2.server.ConnectParts→hyper.proto.h2.ping.Recorder
- Direction
- proto.h2.server uses proto.h2.ping, so a change to proto.h2.ping can break proto.h2.server, while a change to proto.h2.server can't break proto.h2.ping.
- Position
- Below the diagonal: proto.h2.server uses a module listed above it, which is the healthy direction.
35→31 proto.h2.server uses error✕
- Connections
- 1 pair of types, where a type in proto.h2.server uses a type in error.
- The types involved
hyper.proto.h2.server.Serving→hyper.error.Error
- Direction
- proto.h2.server uses error, so a change to error can break proto.h2.server, while a change to proto.h2.server can't break error.
- Position
- Below the diagonal: proto.h2.server uses a module listed above it, which is the healthy direction.
35→33 proto.h2.server uses body.chan✕
- Connections
- 1 pair of types, where a type in proto.h2.server uses a type in body.chan.
- The types involved
hyper.proto.h2.server.Server→hyper.body.chan.State
- Direction
- proto.h2.server uses body.chan, so a change to body.chan can break proto.h2.server, while a change to proto.h2.server can't break body.chan.
- Position
- Below the diagonal: proto.h2.server uses a module listed above it, which is the healthy direction.
35→34 proto.h2.server uses proto.h1.role✕
- Connections
- 1 pair of types, where a type in proto.h2.server uses a type in proto.h1.role.
- The types involved
hyper.proto.h2.server.Server→hyper.proto.h1.role.Server
- Direction
- proto.h2.server uses proto.h1.role, so a change to proto.h1.role can break proto.h2.server, while a change to proto.h2.server can't break proto.h1.role.
- Position
- Below the diagonal: proto.h2.server uses a module listed above it, which is the healthy direction.
36→7 proto.h2.upgrade uses rt.io✕
- Connections
- 3 pairs of types, where a type in proto.h2.upgrade uses a type in rt.io.
- The types involved
hyper.proto.h2.upgrade.H2Upgraded→hyper.rt.io.Readhyper.proto.h2.upgrade.H2Upgraded→hyper.rt.io.ReadBufCursorhyper.proto.h2.upgrade.H2Upgraded→hyper.rt.io.Write
- Direction
- proto.h2.upgrade uses rt.io, so a change to rt.io can break proto.h2.upgrade, while a change to proto.h2.upgrade can't break rt.io.
- Position
- Below the diagonal: proto.h2.upgrade uses a module listed above it, which is the healthy direction.
36→21 proto.h2.upgrade uses proto.h1.io✕
- Connections
- 1 pair of types, where a type in proto.h2.upgrade uses a type in proto.h1.io.
- The types involved
hyper.proto.h2.upgrade.UpgradedSendStreamTask→hyper.proto.h1.io.Cursor
- Direction
- proto.h2.upgrade uses proto.h1.io, so a change to proto.h1.io can break proto.h2.upgrade, while a change to proto.h2.upgrade can't break proto.h1.io.
- Position
- Below the diagonal: proto.h2.upgrade uses a module listed above it, which is the healthy direction.
36→29 proto.h2.upgrade uses proto.h2.ping✕
- Connections
- 2 pairs of types, where a type in proto.h2.upgrade uses a type in proto.h2.ping.
- The types involved
hyper.proto.h2.upgrade.H2Upgraded→hyper.proto.h2.ping.Recorderhyper.proto.h2.upgrade.upgrade$module→hyper.proto.h2.ping.Recorder
- Direction
- proto.h2.upgrade uses proto.h2.ping, so a change to proto.h2.ping can break proto.h2.upgrade, while a change to proto.h2.upgrade can't break proto.h2.ping.
- Position
- Below the diagonal: proto.h2.upgrade uses a module listed above it, which is the healthy direction.
36→31 proto.h2.upgrade uses error✕
- Connections
- 1 pair of types, where a type in proto.h2.upgrade uses a type in error.
- The types involved
hyper.proto.h2.upgrade.upgrade$module→hyper.error.Error
- Direction
- proto.h2.upgrade uses error, so a change to error can break proto.h2.upgrade, while a change to proto.h2.upgrade can't break error.
- Position
- Below the diagonal: proto.h2.upgrade uses a module listed above it, which is the healthy direction.
36→33 proto.h2.upgrade uses body.chan✕
- Connections
- 4 pairs of types, where a type in proto.h2.upgrade uses a type in body.chan.
- The types involved
hyper.proto.h2.upgrade.UpgradedSendStreamBridge→hyper.body.chan.Receiverhyper.proto.h2.upgrade.UpgradedSendStreamBridge→hyper.body.chan.Senderhyper.proto.h2.upgrade.UpgradedSendStreamTask→hyper.body.chan.Receiverhyper.proto.h2.upgrade.UpgradedSendStreamTask→hyper.body.chan.Sender
- Direction
- proto.h2.upgrade uses body.chan, so a change to body.chan can break proto.h2.upgrade, while a change to proto.h2.upgrade can't break body.chan.
- Position
- Below the diagonal: proto.h2.upgrade uses a module listed above it, which is the healthy direction.
37→3 server.conn.http2 uses common.time✕
- Connections
- 1 pair of types, where a type in server.conn.http2 uses a type in common.time.
- The types involved
hyper.server.conn.http2.Builder→hyper.common.time.Time
- Direction
- server.conn.http2 uses common.time, so a change to common.time can break server.conn.http2, while a change to server.conn.http2 can't break common.time.
- Position
- Below the diagonal: server.conn.http2 uses a module listed above it, which is the healthy direction.
37→25 server.conn.http2 uses client.conn.http1✕
- Connections
- 1 pair of types, where a type in server.conn.http2 uses a type in client.conn.http1.
- The types involved
hyper.server.conn.http2.Builder→hyper.client.conn.http1.Connection
- Direction
- server.conn.http2 uses client.conn.http1, so a change to client.conn.http1 can break server.conn.http2, while a change to server.conn.http2 can't break client.conn.http1.
- Position
- Below the diagonal: server.conn.http2 uses a module listed above it, which is the healthy direction.
37→26 server.conn.http2 uses proto.h2.client✕
- Connections
- 1 pair of types, where a type in server.conn.http2 uses a type in proto.h2.client.
- The types involved
hyper.server.conn.http2.Builder→hyper.proto.h2.client.Config
- Direction
- server.conn.http2 uses proto.h2.client, so a change to proto.h2.client can break server.conn.http2, while a change to server.conn.http2 can't break proto.h2.client.
- Position
- Below the diagonal: server.conn.http2 uses a module listed above it, which is the healthy direction.
37→34 server.conn.http2 uses proto.h1.role✕
- Connections
- 1 pair of types, where a type in server.conn.http2 uses a type in proto.h1.role.
- The types involved
hyper.server.conn.http2.Connection→hyper.proto.h1.role.Server
- Direction
- server.conn.http2 uses proto.h1.role, so a change to proto.h1.role can break server.conn.http2, while a change to server.conn.http2 can't break proto.h1.role.
- Position
- Below the diagonal: server.conn.http2 uses a module listed above it, which is the healthy direction.
38→36 rt.bounds.h2_common uses proto.h2.upgrade✕
- Connections
- 1 pair of types, where a type in rt.bounds.h2_common uses a type in proto.h2.upgrade.
- The types involved
hyper.rt.bounds.h2_common.Http2UpgradedExec→hyper.proto.h2.upgrade.UpgradedSendStreamTask
- Direction
- rt.bounds.h2_common uses proto.h2.upgrade, so a change to proto.h2.upgrade can break rt.bounds.h2_common, while a change to rt.bounds.h2_common can't break proto.h2.upgrade.
- Position
- Below the diagonal: rt.bounds.h2_common uses a module listed above it, which is the healthy direction.
39→6 rt.bounds.h2_client uses rt.bounds.h2_client.sealed_client✕
- Connections
- 1 pair of types, where a type in rt.bounds.h2_client uses a type in rt.bounds.h2_client.sealed_client.
- The types involved
hyper.rt.bounds.h2_client.Http2ClientConnExec→hyper.rt.bounds.h2_client.sealed_client.Sealed
- Direction
- rt.bounds.h2_client uses rt.bounds.h2_client.sealed_client, so a change to rt.bounds.h2_client.sealed_client can break rt.bounds.h2_client, while a change to rt.bounds.h2_client can't break rt.bounds.h2_client.sealed_client.
- Position
- Below the diagonal: rt.bounds.h2_client uses a module listed above it, which is the healthy direction.
39→26 rt.bounds.h2_client uses proto.h2.client✕
- Connections
- 1 pair of types, where a type in rt.bounds.h2_client uses a type in proto.h2.client.
- The types involved
hyper.rt.bounds.h2_client.Http2ClientConnExec→hyper.proto.h2.client.H2ClientFuture
- Direction
- rt.bounds.h2_client uses proto.h2.client, so a change to proto.h2.client can break rt.bounds.h2_client, while a change to rt.bounds.h2_client can't break proto.h2.client.
- Position
- Below the diagonal: rt.bounds.h2_client uses a module listed above it, which is the healthy direction.
39→38 rt.bounds.h2_client uses rt.bounds.h2_common✕
- Connections
- 1 pair of types, where a type in rt.bounds.h2_client uses a type in rt.bounds.h2_common.
- The types involved
hyper.rt.bounds.h2_client.Http2ClientConnExec→hyper.rt.bounds.h2_common.Http2UpgradedExec
- Direction
- rt.bounds.h2_client uses rt.bounds.h2_common, so a change to rt.bounds.h2_common can break rt.bounds.h2_client, while a change to rt.bounds.h2_client can't break rt.bounds.h2_common.
- Position
- Below the diagonal: rt.bounds.h2_client uses a module listed above it, which is the healthy direction.
40→6 rt.bounds.h2_server uses rt.bounds.h2_client.sealed_client✕
- Connections
- 1 pair of types, where a type in rt.bounds.h2_server uses a type in rt.bounds.h2_client.sealed_client.
- The types involved
hyper.rt.bounds.h2_server.Http2ServerConnExec→hyper.rt.bounds.h2_client.sealed_client.Sealed
- Direction
- rt.bounds.h2_server uses rt.bounds.h2_client.sealed_client, so a change to rt.bounds.h2_client.sealed_client can break rt.bounds.h2_server, while a change to rt.bounds.h2_server can't break rt.bounds.h2_client.sealed_client.
- Position
- Below the diagonal: rt.bounds.h2_server uses a module listed above it, which is the healthy direction.
40→35 rt.bounds.h2_server uses proto.h2.server✕
- Connections
- 1 pair of types, where a type in rt.bounds.h2_server uses a type in proto.h2.server.
- The types involved
hyper.rt.bounds.h2_server.Http2ServerConnExec→hyper.proto.h2.server.H2Stream
- Direction
- rt.bounds.h2_server uses proto.h2.server, so a change to proto.h2.server can break rt.bounds.h2_server, while a change to rt.bounds.h2_server can't break proto.h2.server.
- Position
- Below the diagonal: rt.bounds.h2_server uses a module listed above it, which is the healthy direction.
40→38 rt.bounds.h2_server uses rt.bounds.h2_common✕
- Connections
- 1 pair of types, where a type in rt.bounds.h2_server uses a type in rt.bounds.h2_common.
- The types involved
hyper.rt.bounds.h2_server.Http2ServerConnExec→hyper.rt.bounds.h2_common.Http2UpgradedExec
- Direction
- rt.bounds.h2_server uses rt.bounds.h2_common, so a change to rt.bounds.h2_common can break rt.bounds.h2_server, while a change to rt.bounds.h2_server can't break rt.bounds.h2_common.
- Position
- Below the diagonal: rt.bounds.h2_server uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 59 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
| A07:2025 — Authentication Failures | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED; Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED; Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +3.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +2.0 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. | +1.9 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.5 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.5 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +1.5 pts | Low | Documentation Quality |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +1.4 pts | Medium | Documentation (README) |
| Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). | +0.6 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/client/conn/http1.rs | 5.7 | Mixed | Code Duplication: Edited copy of a member (21 corresponding lines) |
| src/proto/h1/role.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/proto/h1/decode.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/proto/h1/conn.rs | 6.0 | Mixed | Explicit Debt: XxxComment |
| src/proto/h1/io.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/client/dispatch.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/ffi/http_types.rs | 6.2 | Mixed | Change Coupling: Boundary-crossing change coupling: http_types.rs ↔ role.rs |
| src/proto/h1/dispatch.rs | 7.1 | Mixed | Cyclomatic Complexity: Dispatcher::poll_read (cyclomatic 17) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/proto/h2/ping.rs | 7.3 | Mixed | Explicit Debt: XxxComment |
| src/common/task.rs | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/proto/h2/client.rs | 7.4 | Mixed | Cyclomatic Complexity: ClientTask::poll (cyclomatic 19) |
| src/client/conn/http2.rs | 7.4 | Mixed | Code Duplication: Duplicated block (7 lines × 2) |
| src/proto/h2/server.rs | 7.8 | Mixed | Cognitive Complexity: H2Stream::poll2 (cognitive 38) |
| src/proto/h2/mod.rs | 7.8 | Mixed | Cognitive Complexity: PipeToSendStream::poll (cognitive 31) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 39 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 39 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, 156 of 162 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 35 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (20569 LoC, 88 module-visible types across 12 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was Server::encode_headers at 50. A further 1 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Error::description at 32 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/error.rs (Error::description at 32). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Server::encode_headers (cyclomatic 50), Server::parse (cyclomatic 37), Client::parse (cyclomatic 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 7 together lifts Cyclomatic Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
19 function(s) exceeded the cognitive complexity threshold of 15; the worst was Server::encode_headers at 122.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with Server::encode_headers (cognitive 122), Client::parse (cognitive 67), Dispatcher::poll_write (cognitive 63). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.0 to about 6.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
10 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with role.rs (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with role.rs, conn.rs, client.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with conn.rs, error.rs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
15 duplicated block group(s) detected. 2.3 % of the production lines (470 of 20,569) are in a reported copy. A further 7 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with role.rs (2), io.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with dispatch.rs (2), upgrade.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with io.rs, error.rs. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
1 of 56 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with http1.rs. — One of this dimension's main actionable groups (1 warning-level).
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D12 · Dependency Hygiene
0 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 Cargo.lock there.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 36 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/proto/h1/role.rs (8×37=296)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with role.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/trace.rs. Counted over 46 of the 64 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
31 deducted task-comment markers across 20569 LoC (0.1/KLoC) → score 9.7. 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 24 TodoComment finding(s) in Explicit Debt — start with role.rs (6), io.rs (4), decode.rs (2). — One of this dimension's main actionable groups (24 warning-level).
- Resolve the 4 FixmeComment finding(s) in Explicit Debt — start with mock.rs, tests.rs, dispatch.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 XxxComment finding(s) in Explicit Debt — start with ping.rs (2), conn.rs. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 16 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
59 finding(s): 0 critical, 58 high, 1 medium, 0 low. 56 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `.github/ISSUE_TEMPLATE/bug_report.yml` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 55 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (55 issue-level, 0 of them charged here).
- No action in Static Analysis (SAST) — all 1 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (1 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 46 of the 64 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: http_types.rs↔role.rs 69%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with http_types.rs. — One of this dimension's main actionable groups (1 issue-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 92% | Exemplary | Solid. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 84% | Strong | Solid. |
| Readiness | 85% | Strong | Solid. |
| Security | 69% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94% | Exemplary | Solid. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — 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 — ~11098 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 — N/A — too few peers to establish a naming convention (1848 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (23 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'.
- P2 Observability — This repository's Rust source (1 module(s), 64 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface: 63 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 61 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: http_types.rs ↔ role.rs src/ffi/http_types.rs:1
Serious — 95 finding(s)
- TodoComment tests/server.rs:1105
- TodoComment src/upgrade.rs:391
- TodoComment src/server/conn/http2.rs:97
- TodoComment src/rt/io.rs:544
- TodoComment src/proto/h1/decode.rs:24
- TodoComment src/proto/h1/decode.rs:641
- TodoComment src/proto/h1/io.rs:295
- TodoComment src/proto/h1/io.rs:351
- TodoComment src/proto/h1/io.rs:665
- TodoComment src/proto/h1/mod.rs:12
- TodoComment src/proto/h1/role.rs:228
- TodoComment src/proto/h1/role.rs:911
- TodoComment src/proto/h1/role.rs:1237
- TodoComment src/proto/h1/role.rs:1266
- TodoComment src/proto/h1/role.rs:1533
- TodoComment src/proto/h1/role.rs:1656
- TodoComment src/ffi/http_types.rs:458
- TodoComment src/ffi/error.rs:49
- TodoComment src/common/future.rs:7
- TodoComment src/common/task.rs:13
- TodoComment src/common/task.rs:39
- TodoComment src/common/io/rewind.rs:64
- TodoComment benches/connect.rs:6
- TodoComment benches/end_to_end.rs:7
- FixmeComment src/mock.rs:1
- FixmeComment src/client/tests.rs:2
- FixmeComment src/client/dispatch.rs:273
- FixmeComment examples/params.rs:1
- XxxComment src/proto/h2/ping.rs:277
- XxxComment src/proto/h2/ping.rs:322
- XxxComment src/proto/h1/conn.rs:355
- Server::encode_headers (cognitive 122) src/proto/h1/role.rs:661
- Server::parse (cognitive 59) src/proto/h1/role.rs:146
- Server::encode (cognitive 16) src/proto/h1/role.rs:390
- Dispatcher::poll_write (cognitive 63) src/proto/h1/dispatch.rs:375
- Dispatcher::poll_read (cognitive 51) src/proto/h1/dispatch.rs:244
- Dispatcher::poll_loop (cognitive 17) src/proto/h1/dispatch.rs:185
- Conn::poll_read_head (cognitive 26) src/proto/h1/conn.rs:216
- Conn::poll_read_body (cognitive 22) src/proto/h1/conn.rs:365
- Conn::maybe_notify (cognitive 18) src/proto/h1/conn.rs:523
- MethodTooLong: Server.encode_headers src/proto/h1/role.rs:661
- MethodTooLong: Server.parse src/proto/h1/role.rs:146
- MethodTooLong: Client.parse src/proto/h1/role.rs:1036
- FileTooLong: h1/role.rs src/proto/h1/role.rs
- FileTooLong: h1/conn.rs src/proto/h1/conn.rs
- FileTooLong: h2/client.rs src/proto/h2/client.rs
- Duplicated block (11 lines × 2) src/proto/h1/io.rs:301
- Duplicated block (11 lines × 2) src/proto/h1/role.rs:342
- Duplicated block (11 lines × 2) src/proto/h1/role.rs:177
- Duplicated block (6 lines × 2) src/proto/h2/upgrade.rs:252
- Duplicated block (6 lines × 2) src/client/dispatch.rs:111
- Duplicated block (6 lines × 2) src/client/dispatch.rs:123
- Server::encode_headers (cyclomatic 50) src/proto/h1/role.rs:661
- Server::parse (cyclomatic 37) src/proto/h1/role.rs:146
- Client::parse (cyclomatic 31) src/proto/h1/role.rs:1036
- Client::set_length (cyclomatic 16) src/proto/h1/role.rs:1349
- Dispatcher::poll_read (cyclomatic 17) src/proto/h1/dispatch.rs:244
- Dispatcher::poll_write (cyclomatic 17) src/proto/h1/dispatch.rs:375
- Client::parse (cognitive 67) src/proto/h1/role.rs:1036
- Client::set_length (cognitive 28) src/proto/h1/role.rs:1349
- TooManyMethods: Conn src/proto/h1/conn.rs:38
- TooManyMethods: Error src/error.rs:31
- ClassTooLong: Server src/proto/h1/role.rs:137
- ClassTooLong: Conn src/proto/h1/conn.rs:38
- REDACTED
- REDACTED
- Edited copy of a member (13 corresponding lines) src/ffi/io.rs:149
- Edited copy of a member (13 corresponding lines) src/error.rs:240
- Duplicated block (5 lines × 2) src/proto/h1/role.rs:266
- Duplicated block (5 lines × 2) src/proto/h1/role.rs:169
- Duplicated block (7 lines × 2) src/client/conn/http2.rs:339
- Duplicated block (7 lines × 2) src/client/conn/http2.rs:352
- ClientTask::poll (cyclomatic 19) src/proto/h2/client.rs:678
- Hotspot: src/proto/h1/role.rs src/proto/h1/role.rs:146
- ClientTask::poll (cognitive 43) src/proto/h2/client.rs:678
- H2Stream::poll2 (cognitive 38) src/proto/h2/server.rs:441
- PipeToSendStream::poll (cognitive 31) src/proto/h2/mod.rs:142
- Decoder::decode (cognitive 29) src/proto/h1/decode.rs:144
- Serving::poll_server (cognitive 24) src/proto/h2/server.rs:248
- Encoder::encode_trailers (cognitive 20) src/proto/h1/encode.rs:168
- Buffered::parse (cognitive 20) src/proto/h1/io.rs:174
- Incoming::poll_frame (cognitive 19) src/body/incoming.rs:147
- REDACTED
- REDACTED
- Edited copy of a member (27 corresponding lines) src/proto/h1/decode.rs:349
- Edited copy of a member (21 corresponding lines) src/client/conn/http1.rs:663
- Edited copy of a member (19 corresponding lines) src/proto/h1/conn.rs:731
- Edited copies of one member (4 members, 7+ corresponding lines) src/client/dispatch.rs:107
- Edited copy of a member (14 corresponding lines) src/client/conn/http1.rs:105
- Duplicated block (20 lines × 2) src/client/conn/http1.rs:265
- Duplicated block (17–18 lines × 2) src/client/conn/http1.rs:234
- Duplicated block (14 lines × 2) src/proto/h1/decode.rs:352
- Duplicated block (12 lines × 2) src/proto/h2/mod.rs:164
- Duplicated block (10 lines × 2) src/client/conn/http2.rs:382
- Low cohesion: Builder (LCOM4 10) src/client/conn/http1.rs:128
Minor — 6 finding(s)
- Off-boarding risk: anonymized user #1
- Documentation: no build, run or usage example README.md:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f1a5ec36b0e44a699492e5a34ca67d6f/history.json --exit-code 0 --source . | 7 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f1a5ec36b0e44a699492e5a34ca67d6f/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude capi/include . | 59 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |