Executive summary
salvo-rs/salvo falls short of our standard for production, held back most by its Event-Driven lens, the way the code's parts exchange events. It scores 43 out of 100 and is rated Weak, and 82 of its 83 critical findings are security problems.
Event-Driven, at 10, is the weakest lens and counts most in the score. The best first step is stopping the event handlers from waiting on other services, worth about 28 points. Raising Event-Driven to 70 would lift the score to about 70.
Forty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-six passwords or keys in the code's history and 11 in the code are open to anyone who can read the repository, and three pipeline steps install packages that can change without warning. Pinning each tool to an exact version, replacing each exposed password or key and pinning what the pipeline installs would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed. Letting the handler publish a message instead of waiting for the reply would take care of the message handler that waits for another service.
The product code is 96,415 lines, about €96,000 to rebuild.
If Event-Driven rose from 10 to 70, the lowest score rated Strong, the score would rise from 43 to about 70.
New since the last survey: 37 findings
- Cyclomatic Complexity · ReadSeeker::send_inner (cyclomatic 26) crates/core/src/writing/seek.rs
- Cyclomatic Complexity · NormNode::with_method (cyclomatic 20) crates/oapi/src/routing.rs
- Cyclomatic Complexity · salvo_serve_static::embed::render_embedded_data (cyclomatic 18) crates/serve-static/src/embed.rs
- Cyclomatic Complexity · Tracing::handle (cyclomatic 16) crates/otel/src/tracing.rs
- Cognitive Complexity · ReadSeeker::send_inner (cognitive 33) crates/core/src/writing/seek.rs
- Cognitive Complexity · FormData::read_with_directory (cognitive 29) crates/core/src/http/form.rs
- Cognitive Complexity · NormNode::with_method (cognitive 25) crates/oapi/src/routing.rs
- Cognitive Complexity · SessionHandler::handle (cognitive 23) crates/session/src/lib.rs
- Cognitive Complexity · Router::detect_with_method (cognitive 19) crates/core/src/routing/router.rs
- Cognitive Complexity · DiskStore::try_finalize_if_complete (cognitive 16) crates/tus/src/stores/disk.rs
- God Classes · FunctionTooLong: salvo_serve_static::embed::render_embedded_data crates/serve-static/src/embed.rs
- Code Duplication · Duplicated block (10–11 lines × 2) crates/extra/src/tower_compat.rs
- Code Duplication · Duplicated block (9 lines × 2) crates/tus/src/handlers/patch.rs
- Code Duplication · Duplicated block (7 lines × 2) crates/core/src/fs/named_file.rs
- Code Duplication · Duplicated block (7 lines × 2) crates/session/src/lib.rs
- Code Duplication · Duplicated block (5 lines × 2) crates/tus/src/handlers/patch.rs
- Code Duplication · Duplicated block (8 lines × 2) crates/tus/src/handlers/post.rs
- Churn × Complexity Hotspots · Hotspot: crates/core/src/fs/named_file.rs crates/core/src/fs/named_file.rs
- Churn × Complexity Hotspots · Hotspot: crates/compression/src/lib.rs crates/compression/src/lib.rs
- Churn × Complexity Hotspots · Hotspot: crates/core/src/service.rs crates/core/src/service.rs
- Churn × Complexity Hotspots · Hotspot: crates/tus/src/handlers/post.rs crates/tus/src/handlers/post.rs
- Churn × Complexity Hotspots · Hotspot: crates/core/src/writing/seek.rs crates/core/src/writing/seek.rs
- Churn × Complexity Hotspots · Hotspot: crates/core/src/conn/quinn/builder.rs crates/core/src/conn/quinn/builder.rs
- Churn × Complexity Hotspots · Hotspot: crates/serve-static/src/embed.rs crates/serve-static/src/embed.rs
- Churn × Complexity Hotspots · Hotspot: crates/otel/src/tracing.rs crates/otel/src/tracing.rs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
Fixed since the last survey: 14 findings
- Cyclomatic Complexity · NormNode::new (cyclomatic 18) crates/oapi/src/routing.rs
- Cyclomatic Complexity · ReadSeeker::send (cyclomatic 17) crates/core/src/writing/seek.rs
- Cognitive Complexity · FormData::read (cognitive 26) crates/core/src/http/form.rs
- Cognitive Complexity · Compression::negotiate (cognitive 22) crates/compression/src/lib.rs
- Cognitive Complexity · ReadSeeker::send (cognitive 22) crates/core/src/writing/seek.rs
- Cognitive Complexity · Router::detect (cognitive 19) crates/core/src/routing/router.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) crates/tus/src/handlers/delete.rs
- Code Duplication · Duplicated block (12 lines × 2) crates/tus/src/handlers/patch.rs
- Code Duplication · Duplicated block (10–11 lines × 2) crates/core/src/fs/named_file.rs
- Code Duplication · Duplicated block (6–7 lines × 4) crates/tus/src/handlers/delete.rs
- Code Duplication · Duplicated block (7 lines × 2) crates/session/src/lib.rs
- Code Duplication · Duplicated block (5 lines × 2) crates/tus/src/handlers/patch.rs
- Static Analysis (SAST) · High: REDACTED REDACTED
- Supply-chain Provenance & Signing · REDACTED exported as workflow-level env
Rebuild cost: about €96,000 · Estimate
| Cost to rebuild | €32,000 to €160,000, for 532 to 1,688 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 43. 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: 96,415 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 salvo_core.extract.metadata | 2 salvo_core.http.response | 3 salvo_oapi.openapi.schema.object | 4 salvo_core.routing.flow_ctrl | 5 salvo_core.routing.router | 6 salvo_oapi.openapi.schema.array | 7 salvo_oapi.openapi.schema | 8 salvo_oapi.openapi.components | 9 salvo_oapi.openapi | 10 salvo_oapi.openapi.parameter | 11 salvo_oapi_macros.shared | 12 salvo_oapi.openapi.operation | 13 salvo_oapi_macros.feature | 14 salvo_oapi.endpoint | 15 salvo_oapi_macros.schema_type | 16 salvo_oapi_macros.feature.attributes | 17 salvo_core.conn.ctrl | 18 salvo_core.http.form | 19 salvo_oapi_macros.operation | 20 salvo_core.fuse | 21 salvo_core.conn.proto | 22 salvo_core.http.request | 23 salvo_core.handler | 24 salvo_csrf | 25 salvo_flash | 26 salvo_core.depot | 27 salvo_cache | 28 salvo_core.extract | 29 salvo_core.writing | 30 salvo_cors | 31 salvo_cors.inner | 32 salvo_oapi | 33 salvo_core.extract.payload.form | 34 salvo_core.extract.payload.json | 35 salvo_core.http.errors.status_error | 36 salvo_core.writing.json | 37 salvo_core.catcher | 38 salvo_core.error | 39 salvo_core.service | 40 salvo_core.conn |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 salvo_core.extract.metadata | ||||||||||||||||||||||||||||||||||||||||
| 2 salvo_core.http.response | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 3 salvo_oapi.openapi.schema.object | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 4 salvo_core.routing.flow_ctrl | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 5 salvo_core.routing.router | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 6 salvo_oapi.openapi.schema.array | 1 | 3 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 7 salvo_oapi.openapi.schema | 2 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 8 salvo_oapi.openapi.components | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 salvo_oapi.openapi | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 10 salvo_oapi.openapi.parameter | 4 | |||||||||||||||||||||||||||||||||||||||
| 11 salvo_oapi_macros.shared | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 12 salvo_oapi.openapi.operation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 salvo_oapi_macros.feature | 3 | 2 | 1 | 1 | 29 | |||||||||||||||||||||||||||||||||||
| 14 salvo_oapi.endpoint | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 15 salvo_oapi_macros.schema_type | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 salvo_oapi_macros.feature.attributes | 1 | 1 | 4 | 5 | 71 | 2 | ||||||||||||||||||||||||||||||||||
| 17 salvo_core.conn.ctrl | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 salvo_core.http.form | 1 | 1 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 19 salvo_oapi_macros.operation | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 20 salvo_core.fuse | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 salvo_core.conn.proto | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 salvo_core.http.request | 1 | 2 | 1 | 2 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 23 salvo_core.handler | 5 | 5 | 7 | 7 | ||||||||||||||||||||||||||||||||||||
| 24 salvo_csrf | 2 | 1 | 3 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 25 salvo_flash | 2 | 1 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 26 salvo_core.depot | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 salvo_cache | 2 | 2 | 2 | 4 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 28 salvo_core.extract | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 salvo_core.writing | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 salvo_cors | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 31 salvo_cors.inner | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 32 salvo_oapi | 8 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 salvo_core.extract.payload.form | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 34 salvo_core.extract.payload.json | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 35 salvo_core.http.errors.status_error | 1 | 1 | 1 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 36 salvo_core.writing.json | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 37 salvo_core.catcher | 4 | 2 | 1 | 1 | 4 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 38 salvo_core.error | 1 | 1 | 1 | 1 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 39 salvo_core.service | 2 | 1 | 2 | 2 | 2 | 3 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 40 salvo_core.conn | 1 | 1 | 1 | 1 |
2→16 salvo_core.http.response uses salvo_oapi_macros.feature.attributes part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.http.response uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_core.http.response.Response→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_core.http.response uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_core.http.response, while a change to salvo_core.http.response can't break salvo_oapi_macros.feature.attributes.
- 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.
2→20 salvo_core.http.response uses salvo_core.fuse part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.http.response uses a type in salvo_core.fuse.
- The types involved
salvo_core.http.response.Response→salvo_core.fuse.TransProto
- Direction
- salvo_core.http.response uses salvo_core.fuse, so a change to salvo_core.fuse can break salvo_core.http.response, while a change to salvo_core.http.response can't break salvo_core.fuse.
- 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.
3→6 salvo_oapi.openapi.schema.object uses salvo_oapi.openapi.schema.array part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi.schema.object uses a type in salvo_oapi.openapi.schema.array.
- The types involved
salvo_oapi.openapi.schema.object.Object→salvo_oapi.openapi.schema.array.Array
- Direction
- salvo_oapi.openapi.schema.object uses salvo_oapi.openapi.schema.array, so a change to salvo_oapi.openapi.schema.array can break salvo_oapi.openapi.schema.object, while a change to salvo_oapi.openapi.schema.object can't break salvo_oapi.openapi.schema.array.
- 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.
3→7 salvo_oapi.openapi.schema.object uses salvo_oapi.openapi.schema part of a loop✕
- Connections
- 3 pairs of types, where a type in salvo_oapi.openapi.schema.object uses a type in salvo_oapi.openapi.schema.
- The types involved
salvo_oapi.openapi.schema.object.Object→salvo_oapi.openapi.schema.AdditionalPropertiessalvo_oapi.openapi.schema.object.Object→salvo_oapi.openapi.schema.SchemaFormatsalvo_oapi.openapi.schema.object.Object→salvo_oapi.openapi.schema.SchemaType
- Direction
- salvo_oapi.openapi.schema.object uses salvo_oapi.openapi.schema, so a change to salvo_oapi.openapi.schema can break salvo_oapi.openapi.schema.object, while a change to salvo_oapi.openapi.schema.object can't break salvo_oapi.openapi.schema.
- 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.
3→9 salvo_oapi.openapi.schema.object uses salvo_oapi.openapi part of a loop✕
- Connections
- 2 pairs of types, where a type in salvo_oapi.openapi.schema.object uses a type in salvo_oapi.openapi.
- The types involved
salvo_oapi.openapi.schema.object.Object→salvo_oapi.openapi.Deprecatedsalvo_oapi.openapi.schema.object.Object→salvo_oapi.openapi.RefOr
- Direction
- salvo_oapi.openapi.schema.object uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi.openapi.schema.object, while a change to salvo_oapi.openapi.schema.object can't break salvo_oapi.openapi.
- 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.
4→2 salvo_core.routing.flow_ctrl uses salvo_core.http.response✕
- Connections
- 1 pair of types, where a type in salvo_core.routing.flow_ctrl uses a type in salvo_core.http.response.
- The types involved
salvo_core.routing.flow_ctrl.FlowCtrl→salvo_core.http.response.Response
- Direction
- salvo_core.routing.flow_ctrl uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.routing.flow_ctrl, while a change to salvo_core.routing.flow_ctrl can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.routing.flow_ctrl uses a module listed above it, which is the healthy direction.
4→17 salvo_core.routing.flow_ctrl uses salvo_core.conn.ctrl part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.routing.flow_ctrl uses a type in salvo_core.conn.ctrl.
- The types involved
salvo_core.routing.flow_ctrl.FlowCtrl→salvo_core.conn.ctrl.ConnCtrl
- Direction
- salvo_core.routing.flow_ctrl uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.routing.flow_ctrl, while a change to salvo_core.routing.flow_ctrl can't break salvo_core.conn.ctrl.
- 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.
4→22 salvo_core.routing.flow_ctrl uses salvo_core.http.request part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.routing.flow_ctrl uses a type in salvo_core.http.request.
- The types involved
salvo_core.routing.flow_ctrl.FlowCtrl→salvo_core.http.request.Request
- Direction
- salvo_core.routing.flow_ctrl uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.routing.flow_ctrl, while a change to salvo_core.routing.flow_ctrl can't break salvo_core.http.request.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→26 salvo_core.routing.flow_ctrl uses salvo_core.depot part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.routing.flow_ctrl uses a type in salvo_core.depot.
- The types involved
salvo_core.routing.flow_ctrl.FlowCtrl→salvo_core.depot.Depot
- Direction
- salvo_core.routing.flow_ctrl uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.routing.flow_ctrl, while a change to salvo_core.routing.flow_ctrl can't break salvo_core.depot.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→2 salvo_core.routing.router uses salvo_core.http.response✕
- Connections
- 1 pair of types, where a type in salvo_core.routing.router uses a type in salvo_core.http.response.
- The types involved
salvo_core.routing.router.Router→salvo_core.http.response.Response
- Direction
- salvo_core.routing.router uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.routing.router, while a change to salvo_core.routing.router can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.routing.router uses a module listed above it, which is the healthy direction.
5→16 salvo_core.routing.router uses salvo_oapi_macros.feature.attributes part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.routing.router uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_core.routing.router.Router→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_core.routing.router uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_core.routing.router, while a change to salvo_core.routing.router can't break salvo_oapi_macros.feature.attributes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→22 salvo_core.routing.router uses salvo_core.http.request part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.routing.router uses a type in salvo_core.http.request.
- The types involved
salvo_core.routing.router.Router→salvo_core.http.request.Request
- Direction
- salvo_core.routing.router uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.routing.router, while a change to salvo_core.routing.router can't break salvo_core.http.request.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→3 salvo_oapi.openapi.schema.array uses salvo_oapi.openapi.schema.object✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi.schema.array uses a type in salvo_oapi.openapi.schema.object.
- The types involved
salvo_oapi.openapi.schema.array.ArrayItems→salvo_oapi.openapi.schema.object.Object
- Direction
- salvo_oapi.openapi.schema.array uses salvo_oapi.openapi.schema.object, so a change to salvo_oapi.openapi.schema.object can break salvo_oapi.openapi.schema.array, while a change to salvo_oapi.openapi.schema.array can't break salvo_oapi.openapi.schema.object.
- Position
- Below the diagonal: salvo_oapi.openapi.schema.array uses a module listed above it, which is the healthy direction.
6→7 salvo_oapi.openapi.schema.array uses salvo_oapi.openapi.schema part of a loop✕
- Connections
- 3 pairs of types, where a type in salvo_oapi.openapi.schema.array uses a type in salvo_oapi.openapi.schema.
- The types involved
salvo_oapi.openapi.schema.array.Array→salvo_oapi.openapi.schema.SchemaTypesalvo_oapi.openapi.schema.array.ArrayItems→salvo_oapi.openapi.schema.Refsalvo_oapi.openapi.schema.array.ArrayItems→salvo_oapi.openapi.schema.Schema
- Direction
- salvo_oapi.openapi.schema.array uses salvo_oapi.openapi.schema, so a change to salvo_oapi.openapi.schema can break salvo_oapi.openapi.schema.array, while a change to salvo_oapi.openapi.schema.array can't break salvo_oapi.openapi.schema.
- 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.
6→9 salvo_oapi.openapi.schema.array uses salvo_oapi.openapi part of a loop✕
- Connections
- 3 pairs of types, where a type in salvo_oapi.openapi.schema.array uses a type in salvo_oapi.openapi.
- The types involved
salvo_oapi.openapi.schema.array.Array→salvo_oapi.openapi.Deprecatedsalvo_oapi.openapi.schema.array.Array→salvo_oapi.openapi.RefOrsalvo_oapi.openapi.schema.array.ArrayItems→salvo_oapi.openapi.RefOr
- Direction
- salvo_oapi.openapi.schema.array uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi.openapi.schema.array, while a change to salvo_oapi.openapi.schema.array can't break salvo_oapi.openapi.
- 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.
6→16 salvo_oapi.openapi.schema.array uses salvo_oapi_macros.feature.attributes part of a loop✕
- Connections
- 2 pairs of types, where a type in salvo_oapi.openapi.schema.array uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_oapi.openapi.schema.array.Array→salvo_oapi_macros.feature.attributes.Defaultsalvo_oapi.openapi.schema.array.ArrayItems→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_oapi.openapi.schema.array uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi.openapi.schema.array, while a change to salvo_oapi.openapi.schema.array can't break salvo_oapi_macros.feature.attributes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→3 salvo_oapi.openapi.schema uses salvo_oapi.openapi.schema.object✕
- Connections
- 2 pairs of types, where a type in salvo_oapi.openapi.schema uses a type in salvo_oapi.openapi.schema.object.
- The types involved
salvo_oapi.openapi.schema.AdditionalProperties→salvo_oapi.openapi.schema.object.Objectsalvo_oapi.openapi.schema.Schema→salvo_oapi.openapi.schema.object.Object
- Direction
- salvo_oapi.openapi.schema uses salvo_oapi.openapi.schema.object, so a change to salvo_oapi.openapi.schema.object can break salvo_oapi.openapi.schema, while a change to salvo_oapi.openapi.schema can't break salvo_oapi.openapi.schema.object.
- Position
- Below the diagonal: salvo_oapi.openapi.schema uses a module listed above it, which is the healthy direction.
7→6 salvo_oapi.openapi.schema uses salvo_oapi.openapi.schema.array✕
- Connections
- 3 pairs of types, where a type in salvo_oapi.openapi.schema uses a type in salvo_oapi.openapi.schema.array.
- The types involved
salvo_oapi.openapi.schema.AdditionalProperties→salvo_oapi.openapi.schema.array.Arraysalvo_oapi.openapi.schema.Ref→salvo_oapi.openapi.schema.array.Arraysalvo_oapi.openapi.schema.Schema→salvo_oapi.openapi.schema.array.Array
- Direction
- salvo_oapi.openapi.schema uses salvo_oapi.openapi.schema.array, so a change to salvo_oapi.openapi.schema.array can break salvo_oapi.openapi.schema, while a change to salvo_oapi.openapi.schema can't break salvo_oapi.openapi.schema.array.
- Position
- Below the diagonal: salvo_oapi.openapi.schema uses a module listed above it, which is the healthy direction.
7→9 salvo_oapi.openapi.schema uses salvo_oapi.openapi part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi.schema uses a type in salvo_oapi.openapi.
- The types involved
salvo_oapi.openapi.schema.AdditionalProperties→salvo_oapi.openapi.RefOr
- Direction
- salvo_oapi.openapi.schema uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi.openapi.schema, while a change to salvo_oapi.openapi.schema can't break salvo_oapi.openapi.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→16 salvo_oapi.openapi.schema uses salvo_oapi_macros.feature.attributes part of a loop✕
- Connections
- 2 pairs of types, where a type in salvo_oapi.openapi.schema uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_oapi.openapi.schema.Schema→salvo_oapi_macros.feature.attributes.Defaultsalvo_oapi.openapi.schema.SchemaType→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_oapi.openapi.schema uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi.openapi.schema, while a change to salvo_oapi.openapi.schema can't break salvo_oapi_macros.feature.attributes.
- 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.
8→7 salvo_oapi.openapi.components uses salvo_oapi.openapi.schema✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi.components uses a type in salvo_oapi.openapi.schema.
- The types involved
salvo_oapi.openapi.components.Components→salvo_oapi.openapi.schema.Schemas
- Direction
- salvo_oapi.openapi.components uses salvo_oapi.openapi.schema, so a change to salvo_oapi.openapi.schema can break salvo_oapi.openapi.components, while a change to salvo_oapi.openapi.components can't break salvo_oapi.openapi.schema.
- Position
- Below the diagonal: salvo_oapi.openapi.components uses a module listed above it, which is the healthy direction.
9→2 salvo_oapi.openapi uses salvo_core.http.response✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_core.http.response.
- The types involved
salvo_oapi.openapi.OpenApi→salvo_core.http.response.Response
- Direction
- salvo_oapi.openapi uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
9→3 salvo_oapi.openapi uses salvo_oapi.openapi.schema.object✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_oapi.openapi.schema.object.
- The types involved
salvo_oapi.openapi.RefOr→salvo_oapi.openapi.schema.object.Object
- Direction
- salvo_oapi.openapi uses salvo_oapi.openapi.schema.object, so a change to salvo_oapi.openapi.schema.object can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_oapi.openapi.schema.object.
- Position
- Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
9→4 salvo_oapi.openapi uses salvo_core.routing.flow_ctrl✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_core.routing.flow_ctrl.
- The types involved
salvo_oapi.openapi.OpenApi→salvo_core.routing.flow_ctrl.FlowCtrl
- Direction
- salvo_oapi.openapi uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.routing.flow_ctrl.
- Position
- Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
9→5 salvo_oapi.openapi uses salvo_core.routing.router✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_core.routing.router.
- The types involved
salvo_oapi.openapi.OpenApi→salvo_core.routing.router.Router
- Direction
- salvo_oapi.openapi uses salvo_core.routing.router, so a change to salvo_core.routing.router can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.routing.router.
- Position
- Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
9→6 salvo_oapi.openapi uses salvo_oapi.openapi.schema.array✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_oapi.openapi.schema.array.
- The types involved
salvo_oapi.openapi.RefOr→salvo_oapi.openapi.schema.array.Array
- Direction
- salvo_oapi.openapi uses salvo_oapi.openapi.schema.array, so a change to salvo_oapi.openapi.schema.array can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_oapi.openapi.schema.array.
- Position
- Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
9→7 salvo_oapi.openapi uses salvo_oapi.openapi.schema✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_oapi.openapi.schema.
- The types involved
salvo_oapi.openapi.RefOr→salvo_oapi.openapi.schema.Ref
- Direction
- salvo_oapi.openapi uses salvo_oapi.openapi.schema, so a change to salvo_oapi.openapi.schema can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_oapi.openapi.schema.
- Position
- Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
9→8 salvo_oapi.openapi uses salvo_oapi.openapi.components✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_oapi.openapi.components.
- The types involved
salvo_oapi.openapi.OpenApi→salvo_oapi.openapi.components.Components
- Direction
- salvo_oapi.openapi uses salvo_oapi.openapi.components, so a change to salvo_oapi.openapi.components can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_oapi.openapi.components.
- Position
- Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
9→16 salvo_oapi.openapi uses salvo_oapi_macros.feature.attributes part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_oapi.openapi.RefOr→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_oapi.openapi uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_oapi_macros.feature.attributes.
- 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→22 salvo_oapi.openapi uses salvo_core.http.request part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_core.http.request.
- The types involved
salvo_oapi.openapi.OpenApi→salvo_core.http.request.Request
- Direction
- salvo_oapi.openapi uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.http.request.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→23 salvo_oapi.openapi uses salvo_core.handler part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_core.handler.
- The types involved
salvo_oapi.openapi.OpenApi→salvo_core.handler.Handler
- Direction
- salvo_oapi.openapi uses salvo_core.handler, so a change to salvo_core.handler can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.handler.
- 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 salvo_oapi.openapi uses salvo_core.depot part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi uses a type in salvo_core.depot.
- The types involved
salvo_oapi.openapi.OpenApi→salvo_core.depot.Depot
- Direction
- salvo_oapi.openapi uses salvo_core.depot, so a change to salvo_core.depot can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.depot.
- 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→9 salvo_oapi.openapi.parameter uses salvo_oapi.openapi✕
- Connections
- 4 pairs of types, where a type in salvo_oapi.openapi.parameter uses a type in salvo_oapi.openapi.
- The types involved
salvo_oapi.openapi.parameter.Parameter→salvo_oapi.openapi.Deprecatedsalvo_oapi.openapi.parameter.Parameter→salvo_oapi.openapi.RefOrsalvo_oapi.openapi.parameter.Parameter→salvo_oapi.openapi.Requiredsalvo_oapi.openapi.parameter.parameter$module→salvo_oapi.openapi.Required
- Direction
- salvo_oapi.openapi.parameter uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi.openapi.parameter, while a change to salvo_oapi.openapi.parameter can't break salvo_oapi.openapi.
- Position
- Below the diagonal: salvo_oapi.openapi.parameter uses a module listed above it, which is the healthy direction.
11→9 salvo_oapi_macros.shared uses salvo_oapi.openapi✕
- Connections
- 2 pairs of types, where a type in salvo_oapi_macros.shared uses a type in salvo_oapi.openapi.
- The types involved
salvo_oapi_macros.shared.Required→salvo_oapi.openapi.Requiredsalvo_oapi_macros.shared.shared$module→salvo_oapi.openapi.Deprecated
- Direction
- salvo_oapi_macros.shared uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi_macros.shared, while a change to salvo_oapi_macros.shared can't break salvo_oapi.openapi.
- Position
- Below the diagonal: salvo_oapi_macros.shared uses a module listed above it, which is the healthy direction.
11→13 salvo_oapi_macros.shared uses salvo_oapi_macros.feature part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_oapi_macros.shared uses a type in salvo_oapi_macros.feature.
- The types involved
salvo_oapi_macros.shared.ExternalDocs→salvo_oapi_macros.feature.Parse
- Direction
- salvo_oapi_macros.shared uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.shared, while a change to salvo_oapi_macros.shared can't break salvo_oapi_macros.feature.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 salvo_oapi_macros.shared uses salvo_oapi_macros.feature.attributes part of a loop✕
- Connections
- 2 pairs of types, where a type in salvo_oapi_macros.shared uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_oapi_macros.shared.FieldRename→salvo_oapi_macros.feature.attributes.Renamesalvo_oapi_macros.shared.VariantRename→salvo_oapi_macros.feature.attributes.Rename
- Direction
- salvo_oapi_macros.shared uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi_macros.shared, while a change to salvo_oapi_macros.shared can't break salvo_oapi_macros.feature.attributes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→9 salvo_oapi.openapi.operation uses salvo_oapi.openapi✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi.operation uses a type in salvo_oapi.openapi.
- The types involved
salvo_oapi.openapi.operation.Operation→salvo_oapi.openapi.Deprecated
- Direction
- salvo_oapi.openapi.operation uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi.openapi.operation, while a change to salvo_oapi.openapi.operation can't break salvo_oapi.openapi.
- Position
- Below the diagonal: salvo_oapi.openapi.operation uses a module listed above it, which is the healthy direction.
12→10 salvo_oapi.openapi.operation uses salvo_oapi.openapi.parameter✕
- Connections
- 1 pair of types, where a type in salvo_oapi.openapi.operation uses a type in salvo_oapi.openapi.parameter.
- The types involved
salvo_oapi.openapi.operation.Operation→salvo_oapi.openapi.parameter.Parameters
- Direction
- salvo_oapi.openapi.operation uses salvo_oapi.openapi.parameter, so a change to salvo_oapi.openapi.parameter can break salvo_oapi.openapi.operation, while a change to salvo_oapi.openapi.operation can't break salvo_oapi.openapi.parameter.
- Position
- Below the diagonal: salvo_oapi.openapi.operation uses a module listed above it, which is the healthy direction.
13→7 salvo_oapi_macros.feature uses salvo_oapi.openapi.schema✕
- Connections
- 3 pairs of types, where a type in salvo_oapi_macros.feature uses a type in salvo_oapi.openapi.schema.
- The types involved
salvo_oapi_macros.feature.Feature→salvo_oapi.openapi.schema.AdditionalPropertiessalvo_oapi_macros.feature.Feature→salvo_oapi.openapi.schema.Discriminatorsalvo_oapi_macros.feature.Feature→salvo_oapi.openapi.schema.SchemaType
- Direction
- salvo_oapi_macros.feature uses salvo_oapi.openapi.schema, so a change to salvo_oapi.openapi.schema can break salvo_oapi_macros.feature, while a change to salvo_oapi_macros.feature can't break salvo_oapi.openapi.schema.
- Position
- Below the diagonal: salvo_oapi_macros.feature uses a module listed above it, which is the healthy direction.
13→9 salvo_oapi_macros.feature uses salvo_oapi.openapi✕
- Connections
- 2 pairs of types, where a type in salvo_oapi_macros.feature uses a type in salvo_oapi.openapi.
- The types involved
salvo_oapi_macros.feature.Feature→salvo_oapi.openapi.Deprecatedsalvo_oapi_macros.feature.Feature→salvo_oapi.openapi.Required
- Direction
- salvo_oapi_macros.feature uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi_macros.feature, while a change to salvo_oapi_macros.feature can't break salvo_oapi.openapi.
- Position
- Below the diagonal: salvo_oapi_macros.feature uses a module listed above it, which is the healthy direction.
13→10 salvo_oapi_macros.feature uses salvo_oapi.openapi.parameter✕
- Connections
- 1 pair of types, where a type in salvo_oapi_macros.feature uses a type in salvo_oapi.openapi.parameter.
- The types involved
salvo_oapi_macros.feature.Feature→salvo_oapi.openapi.parameter.ParameterIn
- Direction
- salvo_oapi_macros.feature uses salvo_oapi.openapi.parameter, so a change to salvo_oapi.openapi.parameter can break salvo_oapi_macros.feature, while a change to salvo_oapi_macros.feature can't break salvo_oapi.openapi.parameter.
- Position
- Below the diagonal: salvo_oapi_macros.feature uses a module listed above it, which is the healthy direction.
13→11 salvo_oapi_macros.feature uses salvo_oapi_macros.shared✕
- Connections
- 1 pair of types, where a type in salvo_oapi_macros.feature uses a type in salvo_oapi_macros.shared.
- The types involved
salvo_oapi_macros.feature.Feature→salvo_oapi_macros.shared.TryToTokens
- Direction
- salvo_oapi_macros.feature uses salvo_oapi_macros.shared, so a change to salvo_oapi_macros.shared can break salvo_oapi_macros.feature, while a change to salvo_oapi_macros.feature can't break salvo_oapi_macros.shared.
- Position
- Below the diagonal: salvo_oapi_macros.feature uses a module listed above it, which is the healthy direction.
13→16 salvo_oapi_macros.feature uses salvo_oapi_macros.feature.attributes part of a loop✕
- Connections
- 29 pairs of types, where a type in salvo_oapi_macros.feature uses a type in salvo_oapi_macros.feature.attributes. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
salvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Aliasessalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.AllowReservedsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Boundsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.ContentEncodingsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.ContentMediaTypesalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Defaultsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.DefaultParameterInsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.DefaultStylesalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Descriptionsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Examplessalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Explodesalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Formatsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Ignoresalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Inlinesalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Namesalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.NoRecursionsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Nullablesalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.ReadOnlysalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Renamesalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.RenameAllsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.SchemaWithsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Skipsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.SkipBoundsalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Stylesalvo_oapi_macros.feature.Feature→salvo_oapi_macros.feature.attributes.Title
- Direction
- salvo_oapi_macros.feature uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi_macros.feature, while a change to salvo_oapi_macros.feature can't break salvo_oapi_macros.feature.attributes.
- 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→8 salvo_oapi.endpoint uses salvo_oapi.openapi.components✕
- Connections
- 3 pairs of types, where a type in salvo_oapi.endpoint uses a type in salvo_oapi.openapi.components.
- The types involved
salvo_oapi.endpoint.Endpoint→salvo_oapi.openapi.components.Componentssalvo_oapi.endpoint.EndpointArgRegister→salvo_oapi.openapi.components.Componentssalvo_oapi.endpoint.EndpointOutRegister→salvo_oapi.openapi.components.Components
- Direction
- salvo_oapi.endpoint uses salvo_oapi.openapi.components, so a change to salvo_oapi.openapi.components can break salvo_oapi.endpoint, while a change to salvo_oapi.endpoint can't break salvo_oapi.openapi.components.
- Position
- Below the diagonal: salvo_oapi.endpoint uses a module listed above it, which is the healthy direction.
14→12 salvo_oapi.endpoint uses salvo_oapi.openapi.operation✕
- Connections
- 3 pairs of types, where a type in salvo_oapi.endpoint uses a type in salvo_oapi.openapi.operation.
- The types involved
salvo_oapi.endpoint.Endpoint→salvo_oapi.openapi.operation.Operationsalvo_oapi.endpoint.EndpointArgRegister→salvo_oapi.openapi.operation.Operationsalvo_oapi.endpoint.EndpointOutRegister→salvo_oapi.openapi.operation.Operation
- Direction
- salvo_oapi.endpoint uses salvo_oapi.openapi.operation, so a change to salvo_oapi.openapi.operation can break salvo_oapi.endpoint, while a change to salvo_oapi.endpoint can't break salvo_oapi.openapi.operation.
- Position
- Below the diagonal: salvo_oapi.endpoint uses a module listed above it, which is the healthy direction.
15→11 salvo_oapi_macros.schema_type uses salvo_oapi_macros.shared✕
- Connections
- 3 pairs of types, where a type in salvo_oapi_macros.schema_type uses a type in salvo_oapi_macros.shared.
- The types involved
salvo_oapi_macros.schema_type.SchemaFormat→salvo_oapi_macros.shared.TryToTokenssalvo_oapi_macros.schema_type.SchemaType→salvo_oapi_macros.shared.TryToTokenssalvo_oapi_macros.schema_type.Type→salvo_oapi_macros.shared.TryToTokens
- Direction
- salvo_oapi_macros.schema_type uses salvo_oapi_macros.shared, so a change to salvo_oapi_macros.shared can break salvo_oapi_macros.schema_type, while a change to salvo_oapi_macros.schema_type can't break salvo_oapi_macros.shared.
- Position
- Below the diagonal: salvo_oapi_macros.schema_type uses a module listed above it, which is the healthy direction.
15→13 salvo_oapi_macros.schema_type uses salvo_oapi_macros.feature✕
- Connections
- 2 pairs of types, where a type in salvo_oapi_macros.schema_type uses a type in salvo_oapi_macros.feature.
- The types involved
salvo_oapi_macros.schema_type.SchemaFormat→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.schema_type.Variant→salvo_oapi_macros.feature.Parse
- Direction
- salvo_oapi_macros.schema_type uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.schema_type, while a change to salvo_oapi_macros.schema_type can't break salvo_oapi_macros.feature.
- Position
- Below the diagonal: salvo_oapi_macros.schema_type uses a module listed above it, which is the healthy direction.
16→7 salvo_oapi_macros.feature.attributes uses salvo_oapi.openapi.schema✕
- Connections
- 1 pair of types, where a type in salvo_oapi_macros.feature.attributes uses a type in salvo_oapi.openapi.schema.
- The types involved
salvo_oapi_macros.feature.attributes.Format→salvo_oapi.openapi.schema.SchemaFormat
- Direction
- salvo_oapi_macros.feature.attributes uses salvo_oapi.openapi.schema, so a change to salvo_oapi.openapi.schema can break salvo_oapi_macros.feature.attributes, while a change to salvo_oapi_macros.feature.attributes can't break salvo_oapi.openapi.schema.
- Position
- Below the diagonal: salvo_oapi_macros.feature.attributes uses a module listed above it, which is the healthy direction.
16→9 salvo_oapi_macros.feature.attributes uses salvo_oapi.openapi✕
- Connections
- 1 pair of types, where a type in salvo_oapi_macros.feature.attributes uses a type in salvo_oapi.openapi.
- The types involved
salvo_oapi_macros.feature.attributes.Required→salvo_oapi.openapi.Required
- Direction
- salvo_oapi_macros.feature.attributes uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi_macros.feature.attributes, while a change to salvo_oapi_macros.feature.attributes can't break salvo_oapi.openapi.
- Position
- Below the diagonal: salvo_oapi_macros.feature.attributes uses a module listed above it, which is the healthy direction.
16→10 salvo_oapi_macros.feature.attributes uses salvo_oapi.openapi.parameter✕
- Connections
- 4 pairs of types, where a type in salvo_oapi_macros.feature.attributes uses a type in salvo_oapi.openapi.parameter.
- The types involved
salvo_oapi_macros.feature.attributes.DefaultParameterIn→salvo_oapi.openapi.parameter.ParameterInsalvo_oapi_macros.feature.attributes.DefaultStyle→salvo_oapi.openapi.parameter.ParameterStylesalvo_oapi_macros.feature.attributes.ParameterIn→salvo_oapi.openapi.parameter.ParameterInsalvo_oapi_macros.feature.attributes.Style→salvo_oapi.openapi.parameter.ParameterStyle
- Direction
- salvo_oapi_macros.feature.attributes uses salvo_oapi.openapi.parameter, so a change to salvo_oapi.openapi.parameter can break salvo_oapi_macros.feature.attributes, while a change to salvo_oapi_macros.feature.attributes can't break salvo_oapi.openapi.parameter.
- Position
- Below the diagonal: salvo_oapi_macros.feature.attributes uses a module listed above it, which is the healthy direction.
16→11 salvo_oapi_macros.feature.attributes uses salvo_oapi_macros.shared✕
- Connections
- 5 pairs of types, where a type in salvo_oapi_macros.feature.attributes uses a type in salvo_oapi_macros.shared.
- The types involved
salvo_oapi_macros.feature.attributes.Bound→salvo_oapi_macros.shared.TryToTokenssalvo_oapi_macros.feature.attributes.Default→salvo_oapi_macros.shared.AnyValuesalvo_oapi_macros.feature.attributes.Example→salvo_oapi_macros.shared.AnyValuesalvo_oapi_macros.feature.attributes.Examples→salvo_oapi_macros.shared.AnyValuesalvo_oapi_macros.feature.attributes.Format→salvo_oapi_macros.shared.TryToTokens
- Direction
- salvo_oapi_macros.feature.attributes uses salvo_oapi_macros.shared, so a change to salvo_oapi_macros.shared can break salvo_oapi_macros.feature.attributes, while a change to salvo_oapi_macros.feature.attributes can't break salvo_oapi_macros.shared.
- Position
- Below the diagonal: salvo_oapi_macros.feature.attributes uses a module listed above it, which is the healthy direction.
16→13 salvo_oapi_macros.feature.attributes uses salvo_oapi_macros.feature✕
- Connections
- 71 pairs of types, where a type in salvo_oapi_macros.feature.attributes uses a type in salvo_oapi_macros.feature. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
salvo_oapi_macros.feature.attributes.AdditionalProperties→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.AdditionalProperties→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.Alias→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.Aliases→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.Aliases→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.AllowReserved→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.AllowReserved→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.Bound→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.Bound→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.ContentEncoding→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.ContentEncoding→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.ContentMediaType→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.ContentMediaType→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.Default→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.Default→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.DefaultParameterIn→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.DefaultParameterIn→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.DefaultStyle→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.DefaultStyle→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.Deprecated→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.Deprecated→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.Description→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.Description→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.feature.attributes.Discriminator→salvo_oapi_macros.feature.GetNamesalvo_oapi_macros.feature.attributes.Discriminator→salvo_oapi_macros.feature.Parse
- Direction
- salvo_oapi_macros.feature.attributes uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.feature.attributes, while a change to salvo_oapi_macros.feature.attributes can't break salvo_oapi_macros.feature.
- Position
- Below the diagonal: salvo_oapi_macros.feature.attributes uses a module listed above it, which is the healthy direction.
16→15 salvo_oapi_macros.feature.attributes uses salvo_oapi_macros.schema_type✕
- Connections
- 2 pairs of types, where a type in salvo_oapi_macros.feature.attributes uses a type in salvo_oapi_macros.schema_type.
- The types involved
salvo_oapi_macros.feature.attributes.Alias→salvo_oapi_macros.schema_type.Typesalvo_oapi_macros.feature.attributes.ValueType→salvo_oapi_macros.schema_type.Type
- Direction
- salvo_oapi_macros.feature.attributes uses salvo_oapi_macros.schema_type, so a change to salvo_oapi_macros.schema_type can break salvo_oapi_macros.feature.attributes, while a change to salvo_oapi_macros.feature.attributes can't break salvo_oapi_macros.schema_type.
- Position
- Below the diagonal: salvo_oapi_macros.feature.attributes uses a module listed above it, which is the healthy direction.
17→16 salvo_core.conn.ctrl uses salvo_oapi_macros.feature.attributes✕
- Connections
- 1 pair of types, where a type in salvo_core.conn.ctrl uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_core.conn.ctrl.ConnCtrl→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_core.conn.ctrl uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_core.conn.ctrl, while a change to salvo_core.conn.ctrl can't break salvo_oapi_macros.feature.attributes.
- Position
- Below the diagonal: salvo_core.conn.ctrl uses a module listed above it, which is the healthy direction.
18→1 salvo_core.http.form uses salvo_core.extract.metadata✕
- Connections
- 1 pair of types, where a type in salvo_core.http.form uses a type in salvo_core.extract.metadata.
- The types involved
salvo_core.http.form.FilePart→salvo_core.extract.metadata.Field
- Direction
- salvo_core.http.form uses salvo_core.extract.metadata, so a change to salvo_core.extract.metadata can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.extract.metadata.
- Position
- Below the diagonal: salvo_core.http.form uses a module listed above it, which is the healthy direction.
18→2 salvo_core.http.form uses salvo_core.http.response✕
- Connections
- 1 pair of types, where a type in salvo_core.http.form uses a type in salvo_core.http.response.
- The types involved
salvo_core.http.form.FormLimits→salvo_core.http.response.Response
- Direction
- salvo_core.http.form uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.http.form uses a module listed above it, which is the healthy direction.
18→4 salvo_core.http.form uses salvo_core.routing.flow_ctrl✕
- Connections
- 1 pair of types, where a type in salvo_core.http.form uses a type in salvo_core.routing.flow_ctrl.
- The types involved
salvo_core.http.form.FormLimits→salvo_core.routing.flow_ctrl.FlowCtrl
- Direction
- salvo_core.http.form uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.routing.flow_ctrl.
- Position
- Below the diagonal: salvo_core.http.form uses a module listed above it, which is the healthy direction.
18→16 salvo_core.http.form uses salvo_oapi_macros.feature.attributes✕
- Connections
- 2 pairs of types, where a type in salvo_core.http.form uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_core.http.form.FormData→salvo_oapi_macros.feature.attributes.Defaultsalvo_core.http.form.FormLimits→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_core.http.form uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_oapi_macros.feature.attributes.
- Position
- Below the diagonal: salvo_core.http.form uses a module listed above it, which is the healthy direction.
18→22 salvo_core.http.form uses salvo_core.http.request part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.http.form uses a type in salvo_core.http.request.
- The types involved
salvo_core.http.form.FormLimits→salvo_core.http.request.Request
- Direction
- salvo_core.http.form uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.http.request.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→23 salvo_core.http.form uses salvo_core.handler part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.http.form uses a type in salvo_core.handler.
- The types involved
salvo_core.http.form.FormLimits→salvo_core.handler.Handler
- Direction
- salvo_core.http.form uses salvo_core.handler, so a change to salvo_core.handler can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.handler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→26 salvo_core.http.form uses salvo_core.depot part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.http.form uses a type in salvo_core.depot.
- The types involved
salvo_core.http.form.FormLimits→salvo_core.depot.Depot
- Direction
- salvo_core.http.form uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.depot.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→2 salvo_oapi_macros.operation uses salvo_core.http.response✕
- Connections
- 1 pair of types, where a type in salvo_oapi_macros.operation uses a type in salvo_core.http.response.
- The types involved
salvo_oapi_macros.operation.Operation→salvo_core.http.response.Response
- Direction
- salvo_oapi_macros.operation uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_oapi_macros.operation, while a change to salvo_oapi_macros.operation can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_oapi_macros.operation uses a module listed above it, which is the healthy direction.
19→6 salvo_oapi_macros.operation uses salvo_oapi.openapi.schema.array✕
- Connections
- 1 pair of types, where a type in salvo_oapi_macros.operation uses a type in salvo_oapi.openapi.schema.array.
- The types involved
salvo_oapi_macros.operation.Operation→salvo_oapi.openapi.schema.array.Array
- Direction
- salvo_oapi_macros.operation uses salvo_oapi.openapi.schema.array, so a change to salvo_oapi.openapi.schema.array can break salvo_oapi_macros.operation, while a change to salvo_oapi_macros.operation can't break salvo_oapi.openapi.schema.array.
- Position
- Below the diagonal: salvo_oapi_macros.operation uses a module listed above it, which is the healthy direction.
19→10 salvo_oapi_macros.operation uses salvo_oapi.openapi.parameter✕
- Connections
- 1 pair of types, where a type in salvo_oapi_macros.operation uses a type in salvo_oapi.openapi.parameter.
- The types involved
salvo_oapi_macros.operation.Operation→salvo_oapi.openapi.parameter.Parameter
- Direction
- salvo_oapi_macros.operation uses salvo_oapi.openapi.parameter, so a change to salvo_oapi.openapi.parameter can break salvo_oapi_macros.operation, while a change to salvo_oapi_macros.operation can't break salvo_oapi.openapi.parameter.
- Position
- Below the diagonal: salvo_oapi_macros.operation uses a module listed above it, which is the healthy direction.
19→13 salvo_oapi_macros.operation uses salvo_oapi_macros.feature✕
- Connections
- 2 pairs of types, where a type in salvo_oapi_macros.operation uses a type in salvo_oapi_macros.feature.
- The types involved
salvo_oapi_macros.operation.InlineType→salvo_oapi_macros.feature.Parsesalvo_oapi_macros.operation.PathType→salvo_oapi_macros.feature.Parse
- Direction
- salvo_oapi_macros.operation uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.operation, while a change to salvo_oapi_macros.operation can't break salvo_oapi_macros.feature.
- Position
- Below the diagonal: salvo_oapi_macros.operation uses a module listed above it, which is the healthy direction.
19→16 salvo_oapi_macros.operation uses salvo_oapi_macros.feature.attributes✕
- Connections
- 1 pair of types, where a type in salvo_oapi_macros.operation uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_oapi_macros.operation.Operation→salvo_oapi_macros.feature.attributes.Description
- Direction
- salvo_oapi_macros.operation uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi_macros.operation, while a change to salvo_oapi_macros.operation can't break salvo_oapi_macros.feature.attributes.
- Position
- Below the diagonal: salvo_oapi_macros.operation uses a module listed above it, which is the healthy direction.
20→16 salvo_core.fuse uses salvo_oapi_macros.feature.attributes✕
- Connections
- 1 pair of types, where a type in salvo_core.fuse uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_core.fuse.FuseConfig→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_core.fuse uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_core.fuse, while a change to salvo_core.fuse can't break salvo_oapi_macros.feature.attributes.
- Position
- Below the diagonal: salvo_core.fuse uses a module listed above it, which is the healthy direction.
20→17 salvo_core.fuse uses salvo_core.conn.ctrl✕
- Connections
- 1 pair of types, where a type in salvo_core.fuse uses a type in salvo_core.conn.ctrl.
- The types involved
salvo_core.fuse.FusePolicy→salvo_core.conn.ctrl.ConnCtrl
- Direction
- salvo_core.fuse uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.fuse, while a change to salvo_core.fuse can't break salvo_core.conn.ctrl.
- Position
- Below the diagonal: salvo_core.fuse uses a module listed above it, which is the healthy direction.
21→16 salvo_core.conn.proto uses salvo_oapi_macros.feature.attributes✕
- Connections
- 1 pair of types, where a type in salvo_core.conn.proto uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_core.conn.proto.HttpBuilder→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_core.conn.proto uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_core.conn.proto, while a change to salvo_core.conn.proto can't break salvo_oapi_macros.feature.attributes.
- Position
- Below the diagonal: salvo_core.conn.proto uses a module listed above it, which is the healthy direction.
21→17 salvo_core.conn.proto uses salvo_core.conn.ctrl✕
- Connections
- 1 pair of types, where a type in salvo_core.conn.proto uses a type in salvo_core.conn.ctrl.
- The types involved
salvo_core.conn.proto.HttpBuilder→salvo_core.conn.ctrl.ConnCtrl
- Direction
- salvo_core.conn.proto uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.conn.proto, while a change to salvo_core.conn.proto can't break salvo_core.conn.ctrl.
- Position
- Below the diagonal: salvo_core.conn.proto uses a module listed above it, which is the healthy direction.
21→20 salvo_core.conn.proto uses salvo_core.fuse✕
- Connections
- 1 pair of types, where a type in salvo_core.conn.proto uses a type in salvo_core.fuse.
- The types involved
salvo_core.conn.proto.HttpBuilder→salvo_core.fuse.FuseConfig
- Direction
- salvo_core.conn.proto uses salvo_core.fuse, so a change to salvo_core.fuse can break salvo_core.conn.proto, while a change to salvo_core.conn.proto can't break salvo_core.fuse.
- Position
- Below the diagonal: salvo_core.conn.proto uses a module listed above it, which is the healthy direction.
22→1 salvo_core.http.request uses salvo_core.extract.metadata✕
- Connections
- 1 pair of types, where a type in salvo_core.http.request uses a type in salvo_core.extract.metadata.
- The types involved
salvo_core.http.request.Request→salvo_core.extract.metadata.Metadata
- Direction
- salvo_core.http.request uses salvo_core.extract.metadata, so a change to salvo_core.extract.metadata can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.extract.metadata.
- Position
- Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
22→2 salvo_core.http.request uses salvo_core.http.response✕
- Connections
- 2 pairs of types, where a type in salvo_core.http.request uses a type in salvo_core.http.response.
- The types involved
salvo_core.http.request.ResponseObservers→salvo_core.http.response.Responsesalvo_core.http.request.SecureMaxSize→salvo_core.http.response.Response
- Direction
- salvo_core.http.request uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
22→4 salvo_core.http.request uses salvo_core.routing.flow_ctrl✕
- Connections
- 1 pair of types, where a type in salvo_core.http.request uses a type in salvo_core.routing.flow_ctrl.
- The types involved
salvo_core.http.request.SecureMaxSize→salvo_core.routing.flow_ctrl.FlowCtrl
- Direction
- salvo_core.http.request uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.routing.flow_ctrl.
- Position
- Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
22→16 salvo_core.http.request uses salvo_oapi_macros.feature.attributes✕
- Connections
- 2 pairs of types, where a type in salvo_core.http.request uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_core.http.request.Request→salvo_oapi_macros.feature.attributes.Defaultsalvo_core.http.request.ResponseObservers→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_core.http.request uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_oapi_macros.feature.attributes.
- Position
- Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
22→18 salvo_core.http.request uses salvo_core.http.form✕
- Connections
- 2 pairs of types, where a type in salvo_core.http.request uses a type in salvo_core.http.form.
- The types involved
salvo_core.http.request.Request→salvo_core.http.form.FilePartsalvo_core.http.request.Request→salvo_core.http.form.FormLimits
- Direction
- salvo_core.http.request uses salvo_core.http.form, so a change to salvo_core.http.form can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.http.form.
- Position
- Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
22→20 salvo_core.http.request uses salvo_core.fuse✕
- Connections
- 1 pair of types, where a type in salvo_core.http.request uses a type in salvo_core.fuse.
- The types involved
salvo_core.http.request.Request→salvo_core.fuse.TransProto
- Direction
- salvo_core.http.request uses salvo_core.fuse, so a change to salvo_core.fuse can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.fuse.
- Position
- Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
22→23 salvo_core.http.request uses salvo_core.handler part of a loop✕
- Connections
- 1 pair of types, where a type in salvo_core.http.request uses a type in salvo_core.handler.
- The types involved
salvo_core.http.request.SecureMaxSize→salvo_core.handler.Handler
- Direction
- salvo_core.http.request uses salvo_core.handler, so a change to salvo_core.handler can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.handler.
- 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→26 salvo_core.http.request uses salvo_core.depot part of a loop✕
- Connections
- 2 pairs of types, where a type in salvo_core.http.request uses a type in salvo_core.depot.
- The types involved
salvo_core.http.request.Request→salvo_core.depot.Depotsalvo_core.http.request.SecureMaxSize→salvo_core.depot.Depot
- Direction
- salvo_core.http.request uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.depot.
- 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→2 salvo_core.handler uses salvo_core.http.response✕
- Connections
- 5 pairs of types, where a type in salvo_core.handler uses a type in salvo_core.http.response.
- The types involved
salvo_core.handler.ArcHandler→salvo_core.http.response.Responsesalvo_core.handler.EmptyHandler→salvo_core.http.response.Responsesalvo_core.handler.Handler→salvo_core.http.response.Responsesalvo_core.handler.HoopedHandler→salvo_core.http.response.Responsesalvo_core.handler.WhenHoop→salvo_core.http.response.Response
- Direction
- salvo_core.handler uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.handler, while a change to salvo_core.handler can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.handler uses a module listed above it, which is the healthy direction.
23→4 salvo_core.handler uses salvo_core.routing.flow_ctrl✕
- Connections
- 5 pairs of types, where a type in salvo_core.handler uses a type in salvo_core.routing.flow_ctrl.
- The types involved
salvo_core.handler.ArcHandler→salvo_core.routing.flow_ctrl.FlowCtrlsalvo_core.handler.EmptyHandler→salvo_core.routing.flow_ctrl.FlowCtrlsalvo_core.handler.Handler→salvo_core.routing.flow_ctrl.FlowCtrlsalvo_core.handler.HoopedHandler→salvo_core.routing.flow_ctrl.FlowCtrlsalvo_core.handler.WhenHoop→salvo_core.routing.flow_ctrl.FlowCtrl
- Direction
- salvo_core.handler uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_core.handler, while a change to salvo_core.handler can't break salvo_core.routing.flow_ctrl.
- Position
- Below the diagonal: salvo_core.handler uses a module listed above it, which is the healthy direction.
23→22 salvo_core.handler uses salvo_core.http.request✕
- Connections
- 7 pairs of types, where a type in salvo_core.handler uses a type in salvo_core.http.request.
- The types involved
salvo_core.handler.ArcHandler→salvo_core.http.request.Requestsalvo_core.handler.EmptyHandler→salvo_core.http.request.Requestsalvo_core.handler.Handler→salvo_core.http.request.Requestsalvo_core.handler.HoopedHandler→salvo_core.http.request.Requestsalvo_core.handler.Skipper→salvo_core.http.request.Requestsalvo_core.handler.WhenHoop→salvo_core.http.request.Requestsalvo_core.handler.handler$module→salvo_core.http.request.Request
- Direction
- salvo_core.handler uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.handler, while a change to salvo_core.handler can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_core.handler uses a module listed above it, which is the healthy direction.
23→26 salvo_core.handler uses salvo_core.depot part of a loop✕
- Connections
- 7 pairs of types, where a type in salvo_core.handler uses a type in salvo_core.depot.
- The types involved
salvo_core.handler.ArcHandler→salvo_core.depot.Depotsalvo_core.handler.EmptyHandler→salvo_core.depot.Depotsalvo_core.handler.Handler→salvo_core.depot.Depotsalvo_core.handler.HoopedHandler→salvo_core.depot.Depotsalvo_core.handler.Skipper→salvo_core.depot.Depotsalvo_core.handler.WhenHoop→salvo_core.depot.Depotsalvo_core.handler.handler$module→salvo_core.depot.Depot
- Direction
- salvo_core.handler uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.handler, while a change to salvo_core.handler can't break salvo_core.depot.
- 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→2 salvo_csrf uses salvo_core.http.response✕
- Connections
- 2 pairs of types, where a type in salvo_csrf uses a type in salvo_core.http.response.
- The types involved
salvo_csrf.Csrf→salvo_core.http.response.Responsesalvo_csrf.CsrfStore→salvo_core.http.response.Response
- Direction
- salvo_csrf uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_csrf, while a change to salvo_csrf can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_csrf uses a module listed above it, which is the healthy direction.
24→4 salvo_csrf uses salvo_core.routing.flow_ctrl✕
- Connections
- 1 pair of types, where a type in salvo_csrf uses a type in salvo_core.routing.flow_ctrl.
- The types involved
salvo_csrf.Csrf→salvo_core.routing.flow_ctrl.FlowCtrl
- Direction
- salvo_csrf uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_csrf, while a change to salvo_csrf can't break salvo_core.routing.flow_ctrl.
- Position
- Below the diagonal: salvo_csrf uses a module listed above it, which is the healthy direction.
24→22 salvo_csrf uses salvo_core.http.request✕
- Connections
- 3 pairs of types, where a type in salvo_csrf uses a type in salvo_core.http.request.
- The types involved
salvo_csrf.Csrf→salvo_core.http.request.Requestsalvo_csrf.CsrfStore→salvo_core.http.request.Requestsalvo_csrf.salvo_csrf$module→salvo_core.http.request.Request
- Direction
- salvo_csrf uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_csrf, while a change to salvo_csrf can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_csrf uses a module listed above it, which is the healthy direction.
24→23 salvo_csrf uses salvo_core.handler✕
- Connections
- 1 pair of types, where a type in salvo_csrf uses a type in salvo_core.handler.
- The types involved
salvo_csrf.Csrf→salvo_core.handler.Handler
- Direction
- salvo_csrf uses salvo_core.handler, so a change to salvo_core.handler can break salvo_csrf, while a change to salvo_csrf can't break salvo_core.handler.
- Position
- Below the diagonal: salvo_csrf uses a module listed above it, which is the healthy direction.
24→26 salvo_csrf uses salvo_core.depot part of a loop✕
- Connections
- 3 pairs of types, where a type in salvo_csrf uses a type in salvo_core.depot.
- The types involved
salvo_csrf.Csrf→salvo_core.depot.Depotsalvo_csrf.CsrfStore→salvo_core.depot.Depotsalvo_csrf.salvo_csrf$module→salvo_core.depot.Depot
- Direction
- salvo_csrf uses salvo_core.depot, so a change to salvo_core.depot can break salvo_csrf, while a change to salvo_csrf can't break salvo_core.depot.
- 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→2 salvo_flash uses salvo_core.http.response✕
- Connections
- 2 pairs of types, where a type in salvo_flash uses a type in salvo_core.http.response.
- The types involved
salvo_flash.FlashHandler→salvo_core.http.response.Responsesalvo_flash.FlashStore→salvo_core.http.response.Response
- Direction
- salvo_flash uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_flash, while a change to salvo_flash can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_flash uses a module listed above it, which is the healthy direction.
25→4 salvo_flash uses salvo_core.routing.flow_ctrl✕
- Connections
- 1 pair of types, where a type in salvo_flash uses a type in salvo_core.routing.flow_ctrl.
- The types involved
salvo_flash.FlashHandler→salvo_core.routing.flow_ctrl.FlowCtrl
- Direction
- salvo_flash uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_flash, while a change to salvo_flash can't break salvo_core.routing.flow_ctrl.
- Position
- Below the diagonal: salvo_flash uses a module listed above it, which is the healthy direction.
25→22 salvo_flash uses salvo_core.http.request✕
- Connections
- 2 pairs of types, where a type in salvo_flash uses a type in salvo_core.http.request.
- The types involved
salvo_flash.FlashHandler→salvo_core.http.request.Requestsalvo_flash.FlashStore→salvo_core.http.request.Request
- Direction
- salvo_flash uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_flash, while a change to salvo_flash can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_flash uses a module listed above it, which is the healthy direction.
25→23 salvo_flash uses salvo_core.handler✕
- Connections
- 1 pair of types, where a type in salvo_flash uses a type in salvo_core.handler.
- The types involved
salvo_flash.FlashHandler→salvo_core.handler.Handler
- Direction
- salvo_flash uses salvo_core.handler, so a change to salvo_core.handler can break salvo_flash, while a change to salvo_flash can't break salvo_core.handler.
- Position
- Below the diagonal: salvo_flash uses a module listed above it, which is the healthy direction.
25→26 salvo_flash uses salvo_core.depot part of a loop✕
- Connections
- 2 pairs of types, where a type in salvo_flash uses a type in salvo_core.depot.
- The types involved
salvo_flash.FlashHandler→salvo_core.depot.Depotsalvo_flash.FlashStore→salvo_core.depot.Depot
- Direction
- salvo_flash uses salvo_core.depot, so a change to salvo_core.depot can break salvo_flash, while a change to salvo_flash can't break salvo_core.depot.
- 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→24 salvo_core.depot uses salvo_csrf✕
- Connections
- 1 pair of types, where a type in salvo_core.depot uses a type in salvo_csrf.
- The types involved
salvo_core.depot.Depot→salvo_csrf.CsrfDepotExt
- Direction
- salvo_core.depot uses salvo_csrf, so a change to salvo_csrf can break salvo_core.depot, while a change to salvo_core.depot can't break salvo_csrf.
- Position
- Below the diagonal: salvo_core.depot uses a module listed above it, which is the healthy direction.
26→25 salvo_core.depot uses salvo_flash✕
- Connections
- 2 pairs of types, where a type in salvo_core.depot uses a type in salvo_flash.
- The types involved
salvo_core.depot.Depot→salvo_flash.Flashsalvo_core.depot.Depot→salvo_flash.FlashDepotExt
- Direction
- salvo_core.depot uses salvo_flash, so a change to salvo_flash can break salvo_core.depot, while a change to salvo_core.depot can't break salvo_flash.
- Position
- Below the diagonal: salvo_core.depot uses a module listed above it, which is the healthy direction.
27→2 salvo_cache uses salvo_core.http.response✕
- Connections
- 2 pairs of types, where a type in salvo_cache uses a type in salvo_core.http.response.
- The types involved
salvo_cache.Cache→salvo_core.http.response.Responsesalvo_cache.salvo_cache$module→salvo_core.http.response.Response
- Direction
- salvo_cache uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_cache, while a change to salvo_cache can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_cache uses a module listed above it, which is the healthy direction.
27→4 salvo_cache uses salvo_core.routing.flow_ctrl✕
- Connections
- 2 pairs of types, where a type in salvo_cache uses a type in salvo_core.routing.flow_ctrl.
- The types involved
salvo_cache.Cache→salvo_core.routing.flow_ctrl.FlowCtrlsalvo_cache.salvo_cache$module→salvo_core.routing.flow_ctrl.FlowCtrl
- Direction
- salvo_cache uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_cache, while a change to salvo_cache can't break salvo_core.routing.flow_ctrl.
- Position
- Below the diagonal: salvo_cache uses a module listed above it, which is the healthy direction.
27→16 salvo_cache uses salvo_oapi_macros.feature.attributes✕
- Connections
- 2 pairs of types, where a type in salvo_cache uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_cache.InFlight→salvo_oapi_macros.feature.attributes.Defaultsalvo_cache.RequestIssuer→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_cache uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_cache, while a change to salvo_cache can't break salvo_oapi_macros.feature.attributes.
- Position
- Below the diagonal: salvo_cache uses a module listed above it, which is the healthy direction.
27→22 salvo_cache uses salvo_core.http.request✕
- Connections
- 4 pairs of types, where a type in salvo_cache uses a type in salvo_core.http.request.
- The types involved
salvo_cache.Cache→salvo_core.http.request.Requestsalvo_cache.CacheIssuer→salvo_core.http.request.Requestsalvo_cache.RequestIssuer→salvo_core.http.request.Requestsalvo_cache.salvo_cache$module→salvo_core.http.request.Request
- Direction
- salvo_cache uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_cache, while a change to salvo_cache can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_cache uses a module listed above it, which is the healthy direction.
27→23 salvo_cache uses salvo_core.handler✕
- Connections
- 1 pair of types, where a type in salvo_cache uses a type in salvo_core.handler.
- The types involved
salvo_cache.Cache→salvo_core.handler.Handler
- Direction
- salvo_cache uses salvo_core.handler, so a change to salvo_core.handler can break salvo_cache, while a change to salvo_cache can't break salvo_core.handler.
- Position
- Below the diagonal: salvo_cache uses a module listed above it, which is the healthy direction.
27→26 salvo_cache uses salvo_core.depot✕
- Connections
- 4 pairs of types, where a type in salvo_cache uses a type in salvo_core.depot.
- The types involved
salvo_cache.Cache→salvo_core.depot.Depotsalvo_cache.CacheIssuer→salvo_core.depot.Depotsalvo_cache.RequestIssuer→salvo_core.depot.Depotsalvo_cache.salvo_cache$module→salvo_core.depot.Depot
- Direction
- salvo_cache uses salvo_core.depot, so a change to salvo_core.depot can break salvo_cache, while a change to salvo_cache can't break salvo_core.depot.
- Position
- Below the diagonal: salvo_cache uses a module listed above it, which is the healthy direction.
28→1 salvo_core.extract uses salvo_core.extract.metadata✕
- Connections
- 1 pair of types, where a type in salvo_core.extract uses a type in salvo_core.extract.metadata.
- The types involved
salvo_core.extract.Extractible→salvo_core.extract.metadata.Metadata
- Direction
- salvo_core.extract uses salvo_core.extract.metadata, so a change to salvo_core.extract.metadata can break salvo_core.extract, while a change to salvo_core.extract can't break salvo_core.extract.metadata.
- Position
- Below the diagonal: salvo_core.extract uses a module listed above it, which is the healthy direction.
28→22 salvo_core.extract uses salvo_core.http.request✕
- Connections
- 1 pair of types, where a type in salvo_core.extract uses a type in salvo_core.http.request.
- The types involved
salvo_core.extract.Extractible→salvo_core.http.request.Request
- Direction
- salvo_core.extract uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.extract, while a change to salvo_core.extract can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_core.extract uses a module listed above it, which is the healthy direction.
28→26 salvo_core.extract uses salvo_core.depot✕
- Connections
- 1 pair of types, where a type in salvo_core.extract uses a type in salvo_core.depot.
- The types involved
salvo_core.extract.Extractible→salvo_core.depot.Depot
- Direction
- salvo_core.extract uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.extract, while a change to salvo_core.extract can't break salvo_core.depot.
- Position
- Below the diagonal: salvo_core.extract uses a module listed above it, which is the healthy direction.
29→2 salvo_core.writing uses salvo_core.http.response✕
- Connections
- 2 pairs of types, where a type in salvo_core.writing uses a type in salvo_core.http.response.
- The types involved
salvo_core.writing.Scribe→salvo_core.http.response.Responsesalvo_core.writing.Writer→salvo_core.http.response.Response
- Direction
- salvo_core.writing uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.writing, while a change to salvo_core.writing can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.writing uses a module listed above it, which is the healthy direction.
29→22 salvo_core.writing uses salvo_core.http.request✕
- Connections
- 1 pair of types, where a type in salvo_core.writing uses a type in salvo_core.http.request.
- The types involved
salvo_core.writing.Writer→salvo_core.http.request.Request
- Direction
- salvo_core.writing uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.writing, while a change to salvo_core.writing can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_core.writing uses a module listed above it, which is the healthy direction.
29→26 salvo_core.writing uses salvo_core.depot✕
- Connections
- 1 pair of types, where a type in salvo_core.writing uses a type in salvo_core.depot.
- The types involved
salvo_core.writing.Writer→salvo_core.depot.Depot
- Direction
- salvo_core.writing uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.writing, while a change to salvo_core.writing can't break salvo_core.depot.
- Position
- Below the diagonal: salvo_core.writing uses a module listed above it, which is the healthy direction.
30→2 salvo_cors uses salvo_core.http.response✕
- Connections
- 2 pairs of types, where a type in salvo_cors uses a type in salvo_core.http.response.
- The types involved
salvo_cors.CorsHandler→salvo_core.http.response.Responsesalvo_cors.salvo_cors$module→salvo_core.http.response.Response
- Direction
- salvo_cors uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_cors, while a change to salvo_cors can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_cors uses a module listed above it, which is the healthy direction.
30→4 salvo_cors uses salvo_core.routing.flow_ctrl✕
- Connections
- 1 pair of types, where a type in salvo_cors uses a type in salvo_core.routing.flow_ctrl.
- The types involved
salvo_cors.CorsHandler→salvo_core.routing.flow_ctrl.FlowCtrl
- Direction
- salvo_cors uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_cors, while a change to salvo_cors can't break salvo_core.routing.flow_ctrl.
- Position
- Below the diagonal: salvo_cors uses a module listed above it, which is the healthy direction.
30→16 salvo_cors uses salvo_oapi_macros.feature.attributes✕
- Connections
- 1 pair of types, where a type in salvo_cors uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_cors.Cors→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_cors uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_cors, while a change to salvo_cors can't break salvo_oapi_macros.feature.attributes.
- Position
- Below the diagonal: salvo_cors uses a module listed above it, which is the healthy direction.
30→22 salvo_cors uses salvo_core.http.request✕
- Connections
- 1 pair of types, where a type in salvo_cors uses a type in salvo_core.http.request.
- The types involved
salvo_cors.CorsHandler→salvo_core.http.request.Request
- Direction
- salvo_cors uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_cors, while a change to salvo_cors can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_cors uses a module listed above it, which is the healthy direction.
30→23 salvo_cors uses salvo_core.handler✕
- Connections
- 1 pair of types, where a type in salvo_cors uses a type in salvo_core.handler.
- The types involved
salvo_cors.CorsHandler→salvo_core.handler.Handler
- Direction
- salvo_cors uses salvo_core.handler, so a change to salvo_core.handler can break salvo_cors, while a change to salvo_cors can't break salvo_core.handler.
- Position
- Below the diagonal: salvo_cors uses a module listed above it, which is the healthy direction.
30→26 salvo_cors uses salvo_core.depot✕
- Connections
- 1 pair of types, where a type in salvo_cors uses a type in salvo_core.depot.
- The types involved
salvo_cors.CorsHandler→salvo_core.depot.Depot
- Direction
- salvo_cors uses salvo_core.depot, so a change to salvo_core.depot can break salvo_cors, while a change to salvo_cors can't break salvo_core.depot.
- Position
- Below the diagonal: salvo_cors uses a module listed above it, which is the healthy direction.
31→16 salvo_cors.inner uses salvo_oapi_macros.feature.attributes✕
- Connections
- 1 pair of types, where a type in salvo_cors.inner uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_cors.inner.HeaderValueListInner→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_cors.inner uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_cors.inner, while a change to salvo_cors.inner can't break salvo_oapi_macros.feature.attributes.
- Position
- Below the diagonal: salvo_cors.inner uses a module listed above it, which is the healthy direction.
31→22 salvo_cors.inner uses salvo_core.http.request✕
- Connections
- 3 pairs of types, where a type in salvo_cors.inner uses a type in salvo_core.http.request.
- The types involved
salvo_cors.inner.BoolInner→salvo_core.http.request.Requestsalvo_cors.inner.HeaderInner→salvo_core.http.request.Requestsalvo_cors.inner.HeaderValueInner→salvo_core.http.request.Request
- Direction
- salvo_cors.inner uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_cors.inner, while a change to salvo_cors.inner can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_cors.inner uses a module listed above it, which is the healthy direction.
31→26 salvo_cors.inner uses salvo_core.depot✕
- Connections
- 3 pairs of types, where a type in salvo_cors.inner uses a type in salvo_core.depot.
- The types involved
salvo_cors.inner.BoolInner→salvo_core.depot.Depotsalvo_cors.inner.HeaderInner→salvo_core.depot.Depotsalvo_cors.inner.HeaderValueInner→salvo_core.depot.Depot
- Direction
- salvo_cors.inner uses salvo_core.depot, so a change to salvo_core.depot can break salvo_cors.inner, while a change to salvo_cors.inner can't break salvo_core.depot.
- Position
- Below the diagonal: salvo_cors.inner uses a module listed above it, which is the healthy direction.
32→8 salvo_oapi uses salvo_oapi.openapi.components✕
- Connections
- 8 pairs of types, where a type in salvo_oapi uses a type in salvo_oapi.openapi.components.
- The types involved
salvo_oapi.ComposeSchema→salvo_oapi.openapi.components.Componentssalvo_oapi.ToParameter→salvo_oapi.openapi.components.Componentssalvo_oapi.ToParameters→salvo_oapi.openapi.components.Componentssalvo_oapi.ToRequestBody→salvo_oapi.openapi.components.Componentssalvo_oapi.ToResponse→salvo_oapi.openapi.components.Componentssalvo_oapi.ToResponses→salvo_oapi.openapi.components.Componentssalvo_oapi.ToSchema→salvo_oapi.openapi.components.Componentssalvo_oapi.salvo_oapi$module→salvo_oapi.openapi.components.Components
- Direction
- salvo_oapi uses salvo_oapi.openapi.components, so a change to salvo_oapi.openapi.components can break salvo_oapi, while a change to salvo_oapi can't break salvo_oapi.openapi.components.
- Position
- Below the diagonal: salvo_oapi uses a module listed above it, which is the healthy direction.
32→9 salvo_oapi uses salvo_oapi.openapi✕
- Connections
- 4 pairs of types, where a type in salvo_oapi uses a type in salvo_oapi.openapi.
- The types involved
salvo_oapi.ComposeSchema→salvo_oapi.openapi.RefOrsalvo_oapi.ToResponse→salvo_oapi.openapi.RefOrsalvo_oapi.ToSchema→salvo_oapi.openapi.RefOrsalvo_oapi.salvo_oapi$module→salvo_oapi.openapi.RefOr
- Direction
- salvo_oapi uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi, while a change to salvo_oapi can't break salvo_oapi.openapi.
- Position
- Below the diagonal: salvo_oapi uses a module listed above it, which is the healthy direction.
32→10 salvo_oapi uses salvo_oapi.openapi.parameter✕
- Connections
- 2 pairs of types, where a type in salvo_oapi uses a type in salvo_oapi.openapi.parameter.
- The types involved
salvo_oapi.ToParameter→salvo_oapi.openapi.parameter.Parametersalvo_oapi.ToParameters→salvo_oapi.openapi.parameter.Parameters
- Direction
- salvo_oapi uses salvo_oapi.openapi.parameter, so a change to salvo_oapi.openapi.parameter can break salvo_oapi, while a change to salvo_oapi can't break salvo_oapi.openapi.parameter.
- Position
- Below the diagonal: salvo_oapi uses a module listed above it, which is the healthy direction.
32→28 salvo_oapi uses salvo_core.extract✕
- Connections
- 1 pair of types, where a type in salvo_oapi uses a type in salvo_core.extract.
- The types involved
salvo_oapi.ToParameters→salvo_core.extract.Extractible
- Direction
- salvo_oapi uses salvo_core.extract, so a change to salvo_core.extract can break salvo_oapi, while a change to salvo_oapi can't break salvo_core.extract.
- Position
- Below the diagonal: salvo_oapi uses a module listed above it, which is the healthy direction.
33→1 salvo_core.extract.payload.form uses salvo_core.extract.metadata✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.form uses a type in salvo_core.extract.metadata.
- The types involved
salvo_core.extract.payload.form.FormBody→salvo_core.extract.metadata.Metadata
- Direction
- salvo_core.extract.payload.form uses salvo_core.extract.metadata, so a change to salvo_core.extract.metadata can break salvo_core.extract.payload.form, while a change to salvo_core.extract.payload.form can't break salvo_core.extract.metadata.
- Position
- Below the diagonal: salvo_core.extract.payload.form uses a module listed above it, which is the healthy direction.
33→8 salvo_core.extract.payload.form uses salvo_oapi.openapi.components✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.form uses a type in salvo_oapi.openapi.components.
- The types involved
salvo_core.extract.payload.form.FormBody→salvo_oapi.openapi.components.Components
- Direction
- salvo_core.extract.payload.form uses salvo_oapi.openapi.components, so a change to salvo_oapi.openapi.components can break salvo_core.extract.payload.form, while a change to salvo_core.extract.payload.form can't break salvo_oapi.openapi.components.
- Position
- Below the diagonal: salvo_core.extract.payload.form uses a module listed above it, which is the healthy direction.
33→12 salvo_core.extract.payload.form uses salvo_oapi.openapi.operation✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.form uses a type in salvo_oapi.openapi.operation.
- The types involved
salvo_core.extract.payload.form.FormBody→salvo_oapi.openapi.operation.Operation
- Direction
- salvo_core.extract.payload.form uses salvo_oapi.openapi.operation, so a change to salvo_oapi.openapi.operation can break salvo_core.extract.payload.form, while a change to salvo_core.extract.payload.form can't break salvo_oapi.openapi.operation.
- Position
- Below the diagonal: salvo_core.extract.payload.form uses a module listed above it, which is the healthy direction.
33→14 salvo_core.extract.payload.form uses salvo_oapi.endpoint✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.form uses a type in salvo_oapi.endpoint.
- The types involved
salvo_core.extract.payload.form.FormBody→salvo_oapi.endpoint.EndpointArgRegister
- Direction
- salvo_core.extract.payload.form uses salvo_oapi.endpoint, so a change to salvo_oapi.endpoint can break salvo_core.extract.payload.form, while a change to salvo_core.extract.payload.form can't break salvo_oapi.endpoint.
- Position
- Below the diagonal: salvo_core.extract.payload.form uses a module listed above it, which is the healthy direction.
33→22 salvo_core.extract.payload.form uses salvo_core.http.request✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.form uses a type in salvo_core.http.request.
- The types involved
salvo_core.extract.payload.form.FormBody→salvo_core.http.request.Request
- Direction
- salvo_core.extract.payload.form uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.extract.payload.form, while a change to salvo_core.extract.payload.form can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_core.extract.payload.form uses a module listed above it, which is the healthy direction.
33→26 salvo_core.extract.payload.form uses salvo_core.depot✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.form uses a type in salvo_core.depot.
- The types involved
salvo_core.extract.payload.form.FormBody→salvo_core.depot.Depot
- Direction
- salvo_core.extract.payload.form uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.extract.payload.form, while a change to salvo_core.extract.payload.form can't break salvo_core.depot.
- Position
- Below the diagonal: salvo_core.extract.payload.form uses a module listed above it, which is the healthy direction.
33→28 salvo_core.extract.payload.form uses salvo_core.extract✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.form uses a type in salvo_core.extract.
- The types involved
salvo_core.extract.payload.form.FormBody→salvo_core.extract.Extractible
- Direction
- salvo_core.extract.payload.form uses salvo_core.extract, so a change to salvo_core.extract can break salvo_core.extract.payload.form, while a change to salvo_core.extract.payload.form can't break salvo_core.extract.
- Position
- Below the diagonal: salvo_core.extract.payload.form uses a module listed above it, which is the healthy direction.
33→32 salvo_core.extract.payload.form uses salvo_oapi✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.form uses a type in salvo_oapi.
- The types involved
salvo_core.extract.payload.form.FormBody→salvo_oapi.ToRequestBody
- Direction
- salvo_core.extract.payload.form uses salvo_oapi, so a change to salvo_oapi can break salvo_core.extract.payload.form, while a change to salvo_core.extract.payload.form can't break salvo_oapi.
- Position
- Below the diagonal: salvo_core.extract.payload.form uses a module listed above it, which is the healthy direction.
34→1 salvo_core.extract.payload.json uses salvo_core.extract.metadata✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.json uses a type in salvo_core.extract.metadata.
- The types involved
salvo_core.extract.payload.json.JsonBody→salvo_core.extract.metadata.Metadata
- Direction
- salvo_core.extract.payload.json uses salvo_core.extract.metadata, so a change to salvo_core.extract.metadata can break salvo_core.extract.payload.json, while a change to salvo_core.extract.payload.json can't break salvo_core.extract.metadata.
- Position
- Below the diagonal: salvo_core.extract.payload.json uses a module listed above it, which is the healthy direction.
34→8 salvo_core.extract.payload.json uses salvo_oapi.openapi.components✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.json uses a type in salvo_oapi.openapi.components.
- The types involved
salvo_core.extract.payload.json.JsonBody→salvo_oapi.openapi.components.Components
- Direction
- salvo_core.extract.payload.json uses salvo_oapi.openapi.components, so a change to salvo_oapi.openapi.components can break salvo_core.extract.payload.json, while a change to salvo_core.extract.payload.json can't break salvo_oapi.openapi.components.
- Position
- Below the diagonal: salvo_core.extract.payload.json uses a module listed above it, which is the healthy direction.
34→12 salvo_core.extract.payload.json uses salvo_oapi.openapi.operation✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.json uses a type in salvo_oapi.openapi.operation.
- The types involved
salvo_core.extract.payload.json.JsonBody→salvo_oapi.openapi.operation.Operation
- Direction
- salvo_core.extract.payload.json uses salvo_oapi.openapi.operation, so a change to salvo_oapi.openapi.operation can break salvo_core.extract.payload.json, while a change to salvo_core.extract.payload.json can't break salvo_oapi.openapi.operation.
- Position
- Below the diagonal: salvo_core.extract.payload.json uses a module listed above it, which is the healthy direction.
34→14 salvo_core.extract.payload.json uses salvo_oapi.endpoint✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.json uses a type in salvo_oapi.endpoint.
- The types involved
salvo_core.extract.payload.json.JsonBody→salvo_oapi.endpoint.EndpointArgRegister
- Direction
- salvo_core.extract.payload.json uses salvo_oapi.endpoint, so a change to salvo_oapi.endpoint can break salvo_core.extract.payload.json, while a change to salvo_core.extract.payload.json can't break salvo_oapi.endpoint.
- Position
- Below the diagonal: salvo_core.extract.payload.json uses a module listed above it, which is the healthy direction.
34→22 salvo_core.extract.payload.json uses salvo_core.http.request✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.json uses a type in salvo_core.http.request.
- The types involved
salvo_core.extract.payload.json.JsonBody→salvo_core.http.request.Request
- Direction
- salvo_core.extract.payload.json uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.extract.payload.json, while a change to salvo_core.extract.payload.json can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_core.extract.payload.json uses a module listed above it, which is the healthy direction.
34→26 salvo_core.extract.payload.json uses salvo_core.depot✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.json uses a type in salvo_core.depot.
- The types involved
salvo_core.extract.payload.json.JsonBody→salvo_core.depot.Depot
- Direction
- salvo_core.extract.payload.json uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.extract.payload.json, while a change to salvo_core.extract.payload.json can't break salvo_core.depot.
- Position
- Below the diagonal: salvo_core.extract.payload.json uses a module listed above it, which is the healthy direction.
34→28 salvo_core.extract.payload.json uses salvo_core.extract✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.json uses a type in salvo_core.extract.
- The types involved
salvo_core.extract.payload.json.JsonBody→salvo_core.extract.Extractible
- Direction
- salvo_core.extract.payload.json uses salvo_core.extract, so a change to salvo_core.extract can break salvo_core.extract.payload.json, while a change to salvo_core.extract.payload.json can't break salvo_core.extract.
- Position
- Below the diagonal: salvo_core.extract.payload.json uses a module listed above it, which is the healthy direction.
34→32 salvo_core.extract.payload.json uses salvo_oapi✕
- Connections
- 1 pair of types, where a type in salvo_core.extract.payload.json uses a type in salvo_oapi.
- The types involved
salvo_core.extract.payload.json.JsonBody→salvo_oapi.ToRequestBody
- Direction
- salvo_core.extract.payload.json uses salvo_oapi, so a change to salvo_oapi can break salvo_core.extract.payload.json, while a change to salvo_core.extract.payload.json can't break salvo_oapi.
- Position
- Below the diagonal: salvo_core.extract.payload.json uses a module listed above it, which is the healthy direction.
35→2 salvo_core.http.errors.status_error uses salvo_core.http.response✕
- Connections
- 1 pair of types, where a type in salvo_core.http.errors.status_error uses a type in salvo_core.http.response.
- The types involved
salvo_core.http.errors.status_error.StatusError→salvo_core.http.response.Response
- Direction
- salvo_core.http.errors.status_error uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.http.errors.status_error, while a change to salvo_core.http.errors.status_error can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.http.errors.status_error uses a module listed above it, which is the healthy direction.
35→8 salvo_core.http.errors.status_error uses salvo_oapi.openapi.components✕
- Connections
- 1 pair of types, where a type in salvo_core.http.errors.status_error uses a type in salvo_oapi.openapi.components.
- The types involved
salvo_core.http.errors.status_error.StatusError→salvo_oapi.openapi.components.Components
- Direction
- salvo_core.http.errors.status_error uses salvo_oapi.openapi.components, so a change to salvo_oapi.openapi.components can break salvo_core.http.errors.status_error, while a change to salvo_core.http.errors.status_error can't break salvo_oapi.openapi.components.
- Position
- Below the diagonal: salvo_core.http.errors.status_error uses a module listed above it, which is the healthy direction.
35→9 salvo_core.http.errors.status_error uses salvo_oapi.openapi✕
- Connections
- 1 pair of types, where a type in salvo_core.http.errors.status_error uses a type in salvo_oapi.openapi.
- The types involved
salvo_core.http.errors.status_error.StatusError→salvo_oapi.openapi.RefOr
- Direction
- salvo_core.http.errors.status_error uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_core.http.errors.status_error, while a change to salvo_core.http.errors.status_error can't break salvo_oapi.openapi.
- Position
- Below the diagonal: salvo_core.http.errors.status_error uses a module listed above it, which is the healthy direction.
35→12 salvo_core.http.errors.status_error uses salvo_oapi.openapi.operation✕
- Connections
- 1 pair of types, where a type in salvo_core.http.errors.status_error uses a type in salvo_oapi.openapi.operation.
- The types involved
salvo_core.http.errors.status_error.StatusError→salvo_oapi.openapi.operation.Operation
- Direction
- salvo_core.http.errors.status_error uses salvo_oapi.openapi.operation, so a change to salvo_oapi.openapi.operation can break salvo_core.http.errors.status_error, while a change to salvo_core.http.errors.status_error can't break salvo_oapi.openapi.operation.
- Position
- Below the diagonal: salvo_core.http.errors.status_error uses a module listed above it, which is the healthy direction.
35→14 salvo_core.http.errors.status_error uses salvo_oapi.endpoint✕
- Connections
- 1 pair of types, where a type in salvo_core.http.errors.status_error uses a type in salvo_oapi.endpoint.
- The types involved
salvo_core.http.errors.status_error.StatusError→salvo_oapi.endpoint.EndpointOutRegister
- Direction
- salvo_core.http.errors.status_error uses salvo_oapi.endpoint, so a change to salvo_oapi.endpoint can break salvo_core.http.errors.status_error, while a change to salvo_core.http.errors.status_error can't break salvo_oapi.endpoint.
- Position
- Below the diagonal: salvo_core.http.errors.status_error uses a module listed above it, which is the healthy direction.
35→29 salvo_core.http.errors.status_error uses salvo_core.writing✕
- Connections
- 1 pair of types, where a type in salvo_core.http.errors.status_error uses a type in salvo_core.writing.
- The types involved
salvo_core.http.errors.status_error.StatusError→salvo_core.writing.Scribe
- Direction
- salvo_core.http.errors.status_error uses salvo_core.writing, so a change to salvo_core.writing can break salvo_core.http.errors.status_error, while a change to salvo_core.http.errors.status_error can't break salvo_core.writing.
- Position
- Below the diagonal: salvo_core.http.errors.status_error uses a module listed above it, which is the healthy direction.
35→32 salvo_core.http.errors.status_error uses salvo_oapi✕
- Connections
- 3 pairs of types, where a type in salvo_core.http.errors.status_error uses a type in salvo_oapi.
- The types involved
salvo_core.http.errors.status_error.StatusError→salvo_oapi.ComposeSchemasalvo_core.http.errors.status_error.StatusError→salvo_oapi.ToResponsessalvo_core.http.errors.status_error.StatusError→salvo_oapi.ToSchema
- Direction
- salvo_core.http.errors.status_error uses salvo_oapi, so a change to salvo_oapi can break salvo_core.http.errors.status_error, while a change to salvo_core.http.errors.status_error can't break salvo_oapi.
- Position
- Below the diagonal: salvo_core.http.errors.status_error uses a module listed above it, which is the healthy direction.
36→2 salvo_core.writing.json uses salvo_core.http.response✕
- Connections
- 1 pair of types, where a type in salvo_core.writing.json uses a type in salvo_core.http.response.
- The types involved
salvo_core.writing.json.Json→salvo_core.http.response.Response
- Direction
- salvo_core.writing.json uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.writing.json, while a change to salvo_core.writing.json can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.writing.json uses a module listed above it, which is the healthy direction.
36→8 salvo_core.writing.json uses salvo_oapi.openapi.components✕
- Connections
- 1 pair of types, where a type in salvo_core.writing.json uses a type in salvo_oapi.openapi.components.
- The types involved
salvo_core.writing.json.Json→salvo_oapi.openapi.components.Components
- Direction
- salvo_core.writing.json uses salvo_oapi.openapi.components, so a change to salvo_oapi.openapi.components can break salvo_core.writing.json, while a change to salvo_core.writing.json can't break salvo_oapi.openapi.components.
- Position
- Below the diagonal: salvo_core.writing.json uses a module listed above it, which is the healthy direction.
36→9 salvo_core.writing.json uses salvo_oapi.openapi✕
- Connections
- 1 pair of types, where a type in salvo_core.writing.json uses a type in salvo_oapi.openapi.
- The types involved
salvo_core.writing.json.Json→salvo_oapi.openapi.RefOr
- Direction
- salvo_core.writing.json uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_core.writing.json, while a change to salvo_core.writing.json can't break salvo_oapi.openapi.
- Position
- Below the diagonal: salvo_core.writing.json uses a module listed above it, which is the healthy direction.
36→12 salvo_core.writing.json uses salvo_oapi.openapi.operation✕
- Connections
- 1 pair of types, where a type in salvo_core.writing.json uses a type in salvo_oapi.openapi.operation.
- The types involved
salvo_core.writing.json.Json→salvo_oapi.openapi.operation.Operation
- Direction
- salvo_core.writing.json uses salvo_oapi.openapi.operation, so a change to salvo_oapi.openapi.operation can break salvo_core.writing.json, while a change to salvo_core.writing.json can't break salvo_oapi.openapi.operation.
- Position
- Below the diagonal: salvo_core.writing.json uses a module listed above it, which is the healthy direction.
36→14 salvo_core.writing.json uses salvo_oapi.endpoint✕
- Connections
- 1 pair of types, where a type in salvo_core.writing.json uses a type in salvo_oapi.endpoint.
- The types involved
salvo_core.writing.json.Json→salvo_oapi.endpoint.EndpointOutRegister
- Direction
- salvo_core.writing.json uses salvo_oapi.endpoint, so a change to salvo_oapi.endpoint can break salvo_core.writing.json, while a change to salvo_core.writing.json can't break salvo_oapi.endpoint.
- Position
- Below the diagonal: salvo_core.writing.json uses a module listed above it, which is the healthy direction.
36→29 salvo_core.writing.json uses salvo_core.writing✕
- Connections
- 1 pair of types, where a type in salvo_core.writing.json uses a type in salvo_core.writing.
- The types involved
salvo_core.writing.json.Json→salvo_core.writing.Scribe
- Direction
- salvo_core.writing.json uses salvo_core.writing, so a change to salvo_core.writing can break salvo_core.writing.json, while a change to salvo_core.writing.json can't break salvo_core.writing.
- Position
- Below the diagonal: salvo_core.writing.json uses a module listed above it, which is the healthy direction.
36→32 salvo_core.writing.json uses salvo_oapi✕
- Connections
- 2 pairs of types, where a type in salvo_core.writing.json uses a type in salvo_oapi.
- The types involved
salvo_core.writing.json.Json→salvo_oapi.ToResponsesalvo_core.writing.json.Json→salvo_oapi.ToResponses
- Direction
- salvo_core.writing.json uses salvo_oapi, so a change to salvo_oapi can break salvo_core.writing.json, while a change to salvo_core.writing.json can't break salvo_oapi.
- Position
- Below the diagonal: salvo_core.writing.json uses a module listed above it, which is the healthy direction.
37→2 salvo_core.catcher uses salvo_core.http.response✕
- Connections
- 4 pairs of types, where a type in salvo_core.catcher uses a type in salvo_core.http.response.
- The types involved
salvo_core.catcher.Catcher→salvo_core.http.response.Responsesalvo_core.catcher.DefaultGoal→salvo_core.http.response.Responsesalvo_core.catcher.ProblemGoal→salvo_core.http.response.Responsesalvo_core.catcher.catcher$module→salvo_core.http.response.Response
- Direction
- salvo_core.catcher uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
37→4 salvo_core.catcher uses salvo_core.routing.flow_ctrl✕
- Connections
- 2 pairs of types, where a type in salvo_core.catcher uses a type in salvo_core.routing.flow_ctrl.
- The types involved
salvo_core.catcher.DefaultGoal→salvo_core.routing.flow_ctrl.FlowCtrlsalvo_core.catcher.ProblemGoal→salvo_core.routing.flow_ctrl.FlowCtrl
- Direction
- salvo_core.catcher uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.routing.flow_ctrl.
- Position
- Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
37→16 salvo_core.catcher uses salvo_oapi_macros.feature.attributes✕
- Connections
- 1 pair of types, where a type in salvo_core.catcher uses a type in salvo_oapi_macros.feature.attributes.
- The types involved
salvo_core.catcher.Catcher→salvo_oapi_macros.feature.attributes.Default
- Direction
- salvo_core.catcher uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_oapi_macros.feature.attributes.
- Position
- Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
37→17 salvo_core.catcher uses salvo_core.conn.ctrl✕
- Connections
- 1 pair of types, where a type in salvo_core.catcher uses a type in salvo_core.conn.ctrl.
- The types involved
salvo_core.catcher.Catcher→salvo_core.conn.ctrl.ConnCtrl
- Direction
- salvo_core.catcher uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.conn.ctrl.
- Position
- Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
37→22 salvo_core.catcher uses salvo_core.http.request✕
- Connections
- 4 pairs of types, where a type in salvo_core.catcher uses a type in salvo_core.http.request.
- The types involved
salvo_core.catcher.Catcher→salvo_core.http.request.Requestsalvo_core.catcher.DefaultGoal→salvo_core.http.request.Requestsalvo_core.catcher.ProblemGoal→salvo_core.http.request.Requestsalvo_core.catcher.catcher$module→salvo_core.http.request.Request
- Direction
- salvo_core.catcher uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
37→23 salvo_core.catcher uses salvo_core.handler✕
- Connections
- 2 pairs of types, where a type in salvo_core.catcher uses a type in salvo_core.handler.
- The types involved
salvo_core.catcher.DefaultGoal→salvo_core.handler.Handlersalvo_core.catcher.ProblemGoal→salvo_core.handler.Handler
- Direction
- salvo_core.catcher uses salvo_core.handler, so a change to salvo_core.handler can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.handler.
- Position
- Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
37→26 salvo_core.catcher uses salvo_core.depot✕
- Connections
- 3 pairs of types, where a type in salvo_core.catcher uses a type in salvo_core.depot.
- The types involved
salvo_core.catcher.Catcher→salvo_core.depot.Depotsalvo_core.catcher.DefaultGoal→salvo_core.depot.Depotsalvo_core.catcher.ProblemGoal→salvo_core.depot.Depot
- Direction
- salvo_core.catcher uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.depot.
- Position
- Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
37→35 salvo_core.catcher uses salvo_core.http.errors.status_error✕
- Connections
- 1 pair of types, where a type in salvo_core.catcher uses a type in salvo_core.http.errors.status_error.
- The types involved
salvo_core.catcher.catcher$module→salvo_core.http.errors.status_error.StatusError
- Direction
- salvo_core.catcher uses salvo_core.http.errors.status_error, so a change to salvo_core.http.errors.status_error can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.http.errors.status_error.
- Position
- Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
38→2 salvo_core.error uses salvo_core.http.response✕
- Connections
- 1 pair of types, where a type in salvo_core.error uses a type in salvo_core.http.response.
- The types involved
salvo_core.error.Error→salvo_core.http.response.Response
- Direction
- salvo_core.error uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.error, while a change to salvo_core.error can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.error uses a module listed above it, which is the healthy direction.
38→8 salvo_core.error uses salvo_oapi.openapi.components✕
- Connections
- 1 pair of types, where a type in salvo_core.error uses a type in salvo_oapi.openapi.components.
- The types involved
salvo_core.error.Error→salvo_oapi.openapi.components.Components
- Direction
- salvo_core.error uses salvo_oapi.openapi.components, so a change to salvo_oapi.openapi.components can break salvo_core.error, while a change to salvo_core.error can't break salvo_oapi.openapi.components.
- Position
- Below the diagonal: salvo_core.error uses a module listed above it, which is the healthy direction.
38→9 salvo_core.error uses salvo_oapi.openapi✕
- Connections
- 1 pair of types, where a type in salvo_core.error uses a type in salvo_oapi.openapi.
- The types involved
salvo_core.error.Error→salvo_oapi.openapi.RefOr
- Direction
- salvo_core.error uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_core.error, while a change to salvo_core.error can't break salvo_oapi.openapi.
- Position
- Below the diagonal: salvo_core.error uses a module listed above it, which is the healthy direction.
38→12 salvo_core.error uses salvo_oapi.openapi.operation✕
- Connections
- 1 pair of types, where a type in salvo_core.error uses a type in salvo_oapi.openapi.operation.
- The types involved
salvo_core.error.Error→salvo_oapi.openapi.operation.Operation
- Direction
- salvo_core.error uses salvo_oapi.openapi.operation, so a change to salvo_oapi.openapi.operation can break salvo_core.error, while a change to salvo_core.error can't break salvo_oapi.openapi.operation.
- Position
- Below the diagonal: salvo_core.error uses a module listed above it, which is the healthy direction.
38→14 salvo_core.error uses salvo_oapi.endpoint✕
- Connections
- 1 pair of types, where a type in salvo_core.error uses a type in salvo_oapi.endpoint.
- The types involved
salvo_core.error.Error→salvo_oapi.endpoint.EndpointOutRegister
- Direction
- salvo_core.error uses salvo_oapi.endpoint, so a change to salvo_oapi.endpoint can break salvo_core.error, while a change to salvo_core.error can't break salvo_oapi.endpoint.
- Position
- Below the diagonal: salvo_core.error uses a module listed above it, which is the healthy direction.
38→29 salvo_core.error uses salvo_core.writing✕
- Connections
- 1 pair of types, where a type in salvo_core.error uses a type in salvo_core.writing.
- The types involved
salvo_core.error.Error→salvo_core.writing.Scribe
- Direction
- salvo_core.error uses salvo_core.writing, so a change to salvo_core.writing can break salvo_core.error, while a change to salvo_core.error can't break salvo_core.writing.
- Position
- Below the diagonal: salvo_core.error uses a module listed above it, which is the healthy direction.
38→32 salvo_core.error uses salvo_oapi✕
- Connections
- 3 pairs of types, where a type in salvo_core.error uses a type in salvo_oapi.
- The types involved
salvo_core.error.Error→salvo_oapi.ComposeSchemasalvo_core.error.Error→salvo_oapi.ToResponsessalvo_core.error.Error→salvo_oapi.ToSchema
- Direction
- salvo_core.error uses salvo_oapi, so a change to salvo_oapi can break salvo_core.error, while a change to salvo_core.error can't break salvo_oapi.
- Position
- Below the diagonal: salvo_core.error uses a module listed above it, which is the healthy direction.
38→35 salvo_core.error uses salvo_core.http.errors.status_error✕
- Connections
- 1 pair of types, where a type in salvo_core.error uses a type in salvo_core.http.errors.status_error.
- The types involved
salvo_core.error.Error→salvo_core.http.errors.status_error.StatusError
- Direction
- salvo_core.error uses salvo_core.http.errors.status_error, so a change to salvo_core.http.errors.status_error can break salvo_core.error, while a change to salvo_core.error can't break salvo_core.http.errors.status_error.
- Position
- Below the diagonal: salvo_core.error uses a module listed above it, which is the healthy direction.
39→2 salvo_core.service uses salvo_core.http.response✕
- Connections
- 2 pairs of types, where a type in salvo_core.service uses a type in salvo_core.http.response.
- The types involved
salvo_core.service.DefaultStatusOK→salvo_core.http.response.Responsesalvo_core.service.Service→salvo_core.http.response.Response
- Direction
- salvo_core.service uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.http.response.
- Position
- Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
39→4 salvo_core.service uses salvo_core.routing.flow_ctrl✕
- Connections
- 1 pair of types, where a type in salvo_core.service uses a type in salvo_core.routing.flow_ctrl.
- The types involved
salvo_core.service.DefaultStatusOK→salvo_core.routing.flow_ctrl.FlowCtrl
- Direction
- salvo_core.service uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.routing.flow_ctrl.
- Position
- Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
39→5 salvo_core.service uses salvo_core.routing.router✕
- Connections
- 2 pairs of types, where a type in salvo_core.service uses a type in salvo_core.routing.router.
- The types involved
salvo_core.service.HyperHandlerState→salvo_core.routing.router.Routersalvo_core.service.Service→salvo_core.routing.router.Router
- Direction
- salvo_core.service uses salvo_core.routing.router, so a change to salvo_core.routing.router can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.routing.router.
- Position
- Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
39→17 salvo_core.service uses salvo_core.conn.ctrl✕
- Connections
- 2 pairs of types, where a type in salvo_core.service uses a type in salvo_core.conn.ctrl.
- The types involved
salvo_core.service.HyperHandler→salvo_core.conn.ctrl.ConnCtrlsalvo_core.service.Service→salvo_core.conn.ctrl.ConnCtrl
- Direction
- salvo_core.service uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.conn.ctrl.
- Position
- Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
39→20 salvo_core.service uses salvo_core.fuse✕
- Connections
- 2 pairs of types, where a type in salvo_core.service uses a type in salvo_core.fuse.
- The types involved
salvo_core.service.HyperHandler→salvo_core.fuse.FuseConfigsalvo_core.service.Service→salvo_core.fuse.FuseConfig
- Direction
- salvo_core.service uses salvo_core.fuse, so a change to salvo_core.fuse can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.fuse.
- Position
- Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
39→22 salvo_core.service uses salvo_core.http.request✕
- Connections
- 3 pairs of types, where a type in salvo_core.service uses a type in salvo_core.http.request.
- The types involved
salvo_core.service.DefaultStatusOK→salvo_core.http.request.Requestsalvo_core.service.HyperHandler→salvo_core.http.request.Requestsalvo_core.service.Service→salvo_core.http.request.Request
- Direction
- salvo_core.service uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.http.request.
- Position
- Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
39→23 salvo_core.service uses salvo_core.handler✕
- Connections
- 1 pair of types, where a type in salvo_core.service uses a type in salvo_core.handler.
- The types involved
salvo_core.service.DefaultStatusOK→salvo_core.handler.Handler
- Direction
- salvo_core.service uses salvo_core.handler, so a change to salvo_core.handler can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.handler.
- Position
- Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
39→26 salvo_core.service uses salvo_core.depot✕
- Connections
- 1 pair of types, where a type in salvo_core.service uses a type in salvo_core.depot.
- The types involved
salvo_core.service.DefaultStatusOK→salvo_core.depot.Depot
- Direction
- salvo_core.service uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.depot.
- Position
- Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
39→37 salvo_core.service uses salvo_core.catcher✕
- Connections
- 2 pairs of types, where a type in salvo_core.service uses a type in salvo_core.catcher.
- The types involved
salvo_core.service.HyperHandlerState→salvo_core.catcher.Catchersalvo_core.service.Service→salvo_core.catcher.Catcher
- Direction
- salvo_core.service uses salvo_core.catcher, so a change to salvo_core.catcher can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.catcher.
- Position
- Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
40→17 salvo_core.conn uses salvo_core.conn.ctrl✕
- Connections
- 1 pair of types, where a type in salvo_core.conn uses a type in salvo_core.conn.ctrl.
- The types involved
salvo_core.conn.Accepted→salvo_core.conn.ctrl.ConnCtrl
- Direction
- salvo_core.conn uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.conn, while a change to salvo_core.conn can't break salvo_core.conn.ctrl.
- Position
- Below the diagonal: salvo_core.conn uses a module listed above it, which is the healthy direction.
40→20 salvo_core.conn uses salvo_core.fuse✕
- Connections
- 1 pair of types, where a type in salvo_core.conn uses a type in salvo_core.fuse.
- The types involved
salvo_core.conn.Accepted→salvo_core.fuse.FuseConfig
- Direction
- salvo_core.conn uses salvo_core.fuse, so a change to salvo_core.fuse can break salvo_core.conn, while a change to salvo_core.conn can't break salvo_core.fuse.
- Position
- Below the diagonal: salvo_core.conn uses a module listed above it, which is the healthy direction.
40→21 salvo_core.conn uses salvo_core.conn.proto✕
- Connections
- 1 pair of types, where a type in salvo_core.conn uses a type in salvo_core.conn.proto.
- The types involved
salvo_core.conn.Coupler→salvo_core.conn.proto.HttpBuilder
- Direction
- salvo_core.conn uses salvo_core.conn.proto, so a change to salvo_core.conn.proto can break salvo_core.conn, while a change to salvo_core.conn can't break salvo_core.conn.proto.
- Position
- Below the diagonal: salvo_core.conn uses a module listed above it, which is the healthy direction.
40→39 salvo_core.conn uses salvo_core.service✕
- Connections
- 1 pair of types, where a type in salvo_core.conn uses a type in salvo_core.service.
- The types involved
salvo_core.conn.Coupler→salvo_core.service.HyperHandler
- Direction
- salvo_core.conn uses salvo_core.service, so a change to salvo_core.service can break salvo_core.conn, while a change to salvo_core.conn can't break salvo_core.service.
- Position
- Below the diagonal: salvo_core.conn uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 46 | High / Critical |
| A07:2025 — Authentication Failures | 38 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
| A08:2025 — Software or Data Integrity Failures | 1 | Medium |
Roadmap
First, resolve the handler temporal coupling by moving awaited work off the handler or making the handler async to prevent blocking. Next, address the 22 secrets found in history, starting with REDACTED, and establish a single, reviewable set of access rules for roles and permissions. Finally, document significant design decisions in a dedicated folder and add a clear testing section to the README to explain how to run the test suite.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place. | +28.3 pts | Medium | Handler temporal coupling |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.4 pts | Medium | Architecture documentation |
| 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. | +1.4 pts | Medium | Documentation (README) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +0.6 pts | Low | Static Analysis (SAST) |
| Resolve the 22 REDACTED finding(s) in Secrets (history) — start with REDACTED (15), REDACTED (4), REDACTED. | +1.0 pts | Medium | Secrets (history) |
| Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own. | +0.9 pts | Medium | Access Controls |
| Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED. | +0.4 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.4 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| crates/core/src/conn/native_tls/listener.rs | 4.8 | Mixed | Code Duplication: Duplicated block (17 lines × 3) |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| crates/core/src/fs/named_file.rs | 5.5 | Mixed | Cyclomatic Complexity: NamedFile::send_inner (cyclomatic 34) |
| crates/oapi/src/openapi.rs | 5.6 | Mixed | Cyclomatic Complexity: OpenApi::merge_norm_node (cyclomatic 19) |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 54 of 54 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 54 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, 413 of 431 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`cargo tarpaulin`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs, .js), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 177 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs, .js) and this repository declares a Cargo test suite (repository root, 216 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (6.426 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (97 contributor(s) across 3910 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 96 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; REDACTED was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that REDACTED is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui.js` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D43 Malicious Dependencies — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; REDACTED was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that REDACTED is free of known-vulnerable dependencies.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (examples/db-postgres-sea-orm/docker-compose.yml). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c cargo build --release --target-dir target" did not complete successfully: exit code: 101; runtime evidence skipped.
- ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), 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.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
31 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was salvo_tus::handlers::post::create at 58. A further 9 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Feature::fmt at 47 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/oapi-macros/src/feature.rs (Feature::fmt at 47), crates/core/src/http/errors/status_error.rs (StatusError::from_code at 40), crates/oapi-macros/src/schema_type.rs (Variant::parse at 30), crates/tus/src/error.rs (TusError::status at 20). 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 31 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with salvo_tus::handlers::post::create (cyclomatic 58), StaticDir::handle (cyclomatic 56), RequestDeserializer::fill_value (cyclomatic 52). — 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 31 together lifts Cyclomatic Complexity from 6.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
66 method(s) exceeded the cognitive complexity threshold of 15; the worst was RequestDeserializer::fill_value at 183.
What to do
- Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with RequestDeserializer::fill_value (cognitive 183), StaticDir::handle (cognitive 164). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.4 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
37 god class(es) detected.
What to do
- Resolve the 14 MethodTooLong finding(s) in God Classes — start with enum_schemas.rs (4), struct_schemas.rs (2), named_file.rs (2). — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 11 FileTooLong finding(s) in God Classes — start with enum_schemas.rs, path.rs, request.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 5 FunctionTooLong finding(s) in God Classes — start with post.rs, patch.rs, extract.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
119 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 9 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with handshake.rs, server.rs, enum_variant.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 9 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with path.rs, rapidoc.rs, patch.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 7 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with tcp.rs, req.rs, handler.rs. — One of this dimension's main actionable groups (7 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
22 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 17 of the 22 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
5 of 259 classes have LCOM4 above 3.
What to do
- Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with openapi.rs, stream.rs, router.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
1800 test methods: 1702 unit, 98 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 1 `it`/`test` case(s) across 1 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 1799 `#[test]` function(s) across 216 file(s) declaring at least one; its unit/integration split is Cargo's own — 27 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests. Measured on the JavaScript/TypeScript suite only — at least 177 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. 98 of 130 direct crates were graded against crates.io (0 not published there, 32 not resolved by a committed Cargo.lock). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
What to do
- Maintain Dependency Hygiene — already on the Gold path. — No findings, and enforcement is at this dimension's ceiling.
D13 · REDACTED Scanning
11 secret(s) detected.
What to do
- Resolve the 11 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (7), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (11 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 717 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 Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: crates/serve-static/src/dir.rs (5×56=280); crates/core/src/fs/named_file.rs (5×34=170); crates/compression/src/lib.rs (6×27=162)
What to do
- Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with dir.rs, named_file.rs, lib.rs. — One of this dimension's main actionable groups (11 warning-level).
D17 · Explicit Debt
15 deducted task-comment markers across 96415 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 14 TodoComment finding(s) in Explicit Debt — start with client.rs (4), main.rs, head.rs. — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with enum_schemas.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 29 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 23 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
26 finding(s): 0 critical, 26 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 22 REDACTED finding(s) in Secrets (history) — start with REDACTED (15), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (22 issue-level).
- Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 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)
46 finding(s): 0 critical, 45 high, 0 medium, 1 low. 40 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 4 file(s) — `crates/core/src/extract/parameter/cookie.rs` (line 15), `crates/core/src/http/response.rs` (line 278, lines 278–280, lines 281–282, …), `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-standalone-preset.js`, `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui.js` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 40 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 (40 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. REDACTED was not scanned (REDACTED: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
1 of 232 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/cors/src/inner.rs. Counted over 232 of the 261 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: listener.rs↔listener.rs 94%; cookie.rs↔path.rs 87%; path.rs↔query.rs 87%
What to do
- Resolve the 5 Change coupling finding(s) in Change Coupling — start with listener.rs (2), config.rs, req.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with cookie.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with listener.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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.
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. REDACTED was not scanned (REDACTED: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
ED1 · Handler temporal coupling
- `Timeout.handle` is an event/message handler that blocks the executor on a synchronous wait (`block_on`/`blocking_recv`/`thread::sleep`/a blocking `recv()`) — it stalls the handler and serialises throughput, and on an async runtime can starve the reactor. Either move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`, if the result isn't needed inline) or make the handler itself `async` so it can `.await`. — crates/extra/src/timeout.rs:91
What to do
- Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 89 of 120 project(s) that lack one — worth up to 1.5 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-standalone-preset.js` reports through `console.*` at line 2 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-standalone-preset.js:2
- `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — crates/oapi/src/swagger_ui/v5.34.0/swagger-ui.js:1
What to do
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `github-actions`, `npm` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
P8 · Schema migrations
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- Set: X-Content-Type-Options. Missing: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.5 on this card.) The server: `.serve_connection(` (crates/core/src/conn/proto.rs:161).
What to do
- Add Content-Security-Policy, Strict-Transport-Security, X-Frame-Options beside the headers the Rust server already sets.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn!` at line 196 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:196
- `warn!` at line 237 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:237
- `warn!` at line 371 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:371
- `warn!` at line 404 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:404
- `warn!` at line 417 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:417
- `warn!` at line 426 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:426
- `info!` at line 126 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/handlers/patch.rs:126
- `info!` at line 271 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/handlers/post.rs:271
- `error!` at line 145 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/serve-static/src/embed.rs:145
- `debug!` at line 728 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/proxy/src/lib.rs:728
- `error!` at line 339 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/oapi/src/naming.rs:339
- `warn!` at line 727 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/oapi/src/openapi.rs:727
- `debug!` at line 297 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/jwt-auth/src/oidc.rs:297
- `info!` at line 328 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/jwt-auth/src/oidc.rs:328
- `info!` at line 431 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/jwt-auth/src/oidc.rs:431
- `debug!` at line 287 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/jwt-auth/src/oidc/cache.rs:287
- `error!` at line 99 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/extra/src/concurrency_limiter.rs:99
- `error!` at line 305 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/extra/src/sse.rs:305
- `debug!` at line 542 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/extra/src/websocket.rs:542
- `error!` at line 599 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/cors/src/lib.rs:599
- `warn!` at line 149 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/catcher.rs:149
- `info!` at line 377 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/server.rs:377
- `info!` at line 502 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/server.rs:502
- `info!` at line 545 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/server.rs:545
- `error!` at line 277 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/serde/request.rs:277
- `info!` at line 278 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/conn/proto.rs:278
- `error!` at line 228 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/conn/quinn/builder.rs:228
- `debug!` at line 232 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/conn/quinn/builder.rs:232
- `error!` at line 281 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/conn/quinn/builder.rs:281
- `info!` at line 393 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/conn/quinn/client.rs:393
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 76% | Strong | Solid. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 66% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 77% | Adequate — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 71% | Adequate — gated by D28, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 10% | Critical — gated by ED1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 89% | Strong | Solid. |
Unscored — 4 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c cargo build --release --target-dir target" did not complete successfully: exit code: 101; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- 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.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Python, Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (106 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — Not assessed, and this one is on us: 44 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on. Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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
- 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 — 83 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Blocking wait inside a handler: Timeout.handle crates/extra/src/timeout.rs:91
Serious — 297 finding(s)
- TodoComment examples/todos-utoipa/src/main.rs:241
- TodoComment crates/tus/src/handlers/head.rs:73
- TodoComment crates/tus/src/handlers/patch.rs:118
- TodoComment crates/otel/src/tracing.rs:99
- TodoComment crates/oapi-macros/src/component.rs:631
- TodoComment crates/oapi-macros/src/type_tree.rs:261
- TodoComment crates/oapi-macros/src/schema/enum_schemas.rs:507
- TodoComment crates/oapi/src/openapi/schema.rs:364
- TodoComment crates/core/src/http/body/req.rs:347
- TodoComment crates/core/src/conn/proto.rs:372
- TodoComment crates/core/src/conn/quinn/client.rs:523
- TodoComment crates/core/src/conn/quinn/client.rs:525
- TodoComment crates/core/src/conn/quinn/client.rs:637
- TodoComment crates/core/src/conn/quinn/client.rs:655
- MethodTooLong: NamedStructSchema.try_to_tokens crates/oapi-macros/src/schema/struct_schemas.rs:182
- MethodTooLong: ComponentSchema.non_generic_to_tokens crates/oapi-macros/src/component.rs:393
- MethodTooLong: StaticDir.handle crates/serve-static/src/dir.rs:486
- MethodTooLong: ComplexEnum.tagged_variant_tokens crates/oapi-macros/src/schema/enum_schemas.rs:727
- MethodTooLong: ToParameters.try_to_tokens crates/oapi-macros/src/parameter/derive.rs:66
- MethodTooLong: RequestDeserializer.fill_value crates/core/src/serde/request.rs:267
- MethodTooLong: NamedFile.send_inner crates/core/src/fs/named_file.rs:812
- MethodTooLong: ComplexEnum.adjacently_tagged_variant_tokens crates/oapi-macros/src/schema/enum_schemas.rs:932
- MethodTooLong: EnumSchema.new crates/oapi-macros/src/schema/enum_schemas.rs:44
- MethodTooLong: Builder.serve_connection crates/core/src/conn/quinn/builder.rs:103
- MethodTooLong: ComplexEnum.variant_tokens crates/oapi-macros/src/schema/enum_schemas.rs:499
- MethodTooLong: ToSchema.try_to_tokens crates/oapi-macros/src/schema.rs:75
- MethodTooLong: NamedFileBuilder.build crates/core/src/fs/named_file.rs:325
- MethodTooLong: UnnamedStructSchema.try_to_tokens crates/oapi-macros/src/schema/struct_schemas.rs:531
- Hotspot: crates/serve-static/src/dir.rs crates/serve-static/src/dir.rs:486
- Hotspot: crates/core/src/fs/named_file.rs crates/core/src/fs/named_file.rs:812
- Hotspot: crates/compression/src/lib.rs crates/compression/src/lib.rs:477
- Hotspot: crates/core/src/service.rs crates/core/src/service.rs:268
- Hotspot: crates/tus/src/handlers/post.rs crates/tus/src/handlers/post.rs:21
- Hotspot: crates/core/src/writing/seek.rs crates/core/src/writing/seek.rs:77
- Hotspot: crates/core/src/conn/quinn/builder.rs crates/core/src/conn/quinn/builder.rs:103
- Hotspot: crates/oapi/src/routing.rs crates/oapi/src/routing.rs:105
- Hotspot: crates/serve-static/src/embed.rs crates/serve-static/src/embed.rs:104
- Hotspot: crates/oapi-macros/src/parameter/derive.rs crates/oapi-macros/src/parameter/derive.rs:66
- Hotspot: crates/otel/src/tracing.rs crates/otel/src/tracing.rs:92
- FileTooLong: schema/enum_schemas.rs crates/oapi-macros/src/schema/enum_schemas.rs
- FileTooLong: filters/path.rs crates/core/src/routing/filters/path.rs
- FileTooLong: http/request.rs crates/core/src/http/request.rs
- FileTooLong: src/lib.rs crates/oapi/src/lib.rs
- FileTooLong: fs/named_file.rs crates/core/src/fs/named_file.rs
- FileTooLong: src/dir.rs crates/serve-static/src/dir.rs
- FileTooLong: feature/attributes.rs crates/oapi-macros/src/feature/attributes.rs
- FileTooLong: src/schema_type.rs crates/oapi-macros/src/schema_type.rs
- FileTooLong: src/response.rs crates/oapi-macros/src/response.rs
- FileTooLong: src/component.rs crates/oapi-macros/src/component.rs
- FileTooLong: src/openapi.rs crates/oapi/src/openapi.rs
- Duplicated block (9 lines × 2) crates/core/src/conn/stream/handshake.rs:55
- Duplicated block (9 lines × 2) crates/core/src/server.rs:376
- Duplicated block (9 lines × 2) crates/oapi-macros/src/schema/enum_variant.rs:210
- Duplicated block (9 lines × 2) crates/oapi-macros/src/schema/struct_schemas.rs:94
- Duplicated block (9 lines × 2) crates/oapi/src/openapi.rs:888
- Duplicated block (9 lines × 2) crates/rate-limiter/src/lib.rs:344
- Duplicated block (9 lines × 2) crates/tus/src/handlers/patch.rs:32
- Duplicated block (9 lines × 2) crates/oapi/src/openapi/schema/object.rs:275
- Duplicated block (9 lines × 2) crates/oapi-macros/src/operation/encoding.rs:23
- Duplicated block (5 lines × 2) crates/oapi/src/openapi/path.rs:158
- Duplicated block (5 lines × 2) crates/oapi/src/rapidoc.rs:118
- Duplicated block (5 lines × 2) crates/tus/src/handlers/patch.rs:199
- Duplicated block (5 lines × 2) crates/tus/src/stores/disk.rs:525
- Duplicated block (5 lines × 2) crates/core/src/conn/openssl/config.rs:42
- Duplicated block (5 lines × 2) crates/cors/src/allow_credentials.rs:50
- Duplicated block (5 lines × 2) crates/cors/src/allow_headers.rs:71
- Duplicated block (5 lines × 2) crates/cors/src/expose_headers.rs:70
- Duplicated block (5 lines × 2) crates/macros/src/handler.rs:156
- Duplicated block (8 lines × 2) crates/core/src/conn/tcp.rs:199
- Duplicated block (8 lines × 2) crates/core/src/http/body/req.rs:165
- Duplicated block (8 lines × 2) crates/macros/src/handler.rs:131
- Duplicated block (8 lines × 2) crates/oapi/src/openapi/response.rs:42
- Duplicated block (8 lines × 2) crates/cors/src/allow_headers.rs:98
- Duplicated block (8 lines × 2) crates/tus/src/handlers/post.rs:237
- Duplicated block (8 lines × 2) crates/core/src/routing/filters/others.rs:180
- Duplicated block (7 lines × 2) crates/core/src/fs/named_file.rs:949
- Duplicated block (7 lines × 2) crates/oapi-macros/src/operation/request_body.rs:76
- Duplicated block (7 lines × 2) crates/session/src/lib.rs:162
- Duplicated block (7 lines × 2) crates/core/src/serde/flat_value.rs:121
- Duplicated block (7 lines × 2) crates/cors/src/allow_headers.rs:139
- Duplicated block (7 lines × 2) crates/cors/src/allow_headers.rs:148
- Duplicated block (7 lines × 2) crates/macros/src/handler.rs:107
- Duplicated block (10 lines × 2) crates/core/src/conn/quinn/builder.rs:172
- Duplicated block (10 lines × 2) crates/core/src/extract/case.rs:115
- Duplicated block (10 lines × 2) crates/core/src/http/request.rs:668
- Duplicated block (10 lines × 2) crates/csrf/src/aes_gcm_cipher.rs:82
- Duplicated block (10 lines × 2) crates/extra/src/tower_compat.rs:128
- Duplicated block (10 lines × 2) crates/macros/src/shared.rs:45
- FunctionTooLong: salvo_tus::handlers::post::create crates/tus/src/handlers/post.rs:21
- FunctionTooLong: salvo_tus::handlers::patch::patch crates/tus/src/handlers/patch.rs:17
- FunctionTooLong: salvo_macros::extract::generate crates/macros/src/extract.rs:274
- FunctionTooLong: salvo_oapi_macros::bound::with_bound crates/oapi-macros/src/bound.rs:57
- FunctionTooLong: salvo_serve_static::embed::render_embedded_data crates/serve-static/src/embed.rs:104
- Change coupling: listener.rs ↔ listener.rs crates/core/src/conn/native_tls/listener.rs:1
- Change coupling: listener.rs ↔ config.rs crates/core/src/conn/native_tls/listener.rs:1
- Change coupling: config.rs ↔ listener.rs crates/core/src/conn/openssl/config.rs:1
- Change coupling: req.rs ↔ res.rs crates/core/src/http/body/req.rs:1
- Change coupling: named_file.rs ↔ seek.rs crates/core/src/fs/named_file.rs:1
- Duplicated block (11 lines × 2) crates/macros/src/shared.rs:34
- Duplicated block (11 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:303
- Duplicated block (11 lines × 2) crates/oapi/src/openapi/schema/all_of.rs:58
- Duplicated block (11 lines × 2) crates/oapi/src/rapidoc.rs:105
- Duplicated block (11 lines × 2) crates/core/src/conn/proto.rs:170
- Low cohesion: OpenApi (LCOM4 7) crates/oapi/src/openapi.rs:87
- Low cohesion: EncodeStream (LCOM4 6) crates/compression/src/stream.rs:21
- Low cohesion: Router (LCOM4 6) crates/core/src/routing/router.rs:16
- Low cohesion: DynStream (LCOM4 4) crates/core/src/conn.rs:508
- Low cohesion: Cors (LCOM4 4) crates/cors/src/lib.rs:107
- TooManyMethods: Request crates/core/src/http/request.rs:203
- TooManyMethods: Router crates/core/src/routing/router.rs:16
- TooManyMethods: OpenApi crates/oapi/src/openapi.rs:87
- TooManyMethods: Object crates/oapi/src/openapi/schema/object.rs:19
- Duplicated block (14 lines × 2) crates/macros/src/handler.rs:51
- Duplicated block (14 lines × 2) crates/macros/src/handler.rs:89
- Duplicated block (14 lines × 2) crates/core/src/fs/named_file.rs:1066
- Duplicated block (14 lines × 2) crates/core/src/fs/named_file.rs:1082
- Duplicated block (12 lines × 2) crates/core/src/server.rs:387
- Duplicated block (12 lines × 2) crates/oapi-macros/src/response.rs:259
- Duplicated block (12 lines × 2) crates/oapi-macros/src/schema.rs:288
- Duplicated block (12 lines × 2) crates/oapi-macros/src/schema/struct_schemas.rs:252
- Duplicated block (7 lines × 3) crates/core/src/catcher.rs:345
- Duplicated block (7 lines × 3) crates/core/src/conn/native_tls/listener.rs:154
- Duplicated block (7 lines × 3) crates/oapi/src/openapi.rs:407
- Duplicated block (7 lines × 3) crates/oapi/src/openapi/callback.rs:80
- Duplicated block (6 lines × 2) crates/macros/src/handler.rs:163
- Duplicated block (6 lines × 2) crates/oapi/src/openapi/path.rs:70
- Duplicated block (6 lines × 2) crates/session/src/lib.rs:155
- Duplicated block (6 lines × 2) crates/core/src/conn/native_tls/listener.rs:64
- salvo_tus::handlers::post::create (cyclomatic 58) crates/tus/src/handlers/post.rs:21
- salvo_tus::handlers::patch::patch (cyclomatic 49) crates/tus/src/handlers/patch.rs:17
- salvo_tus::handlers::head::head (cyclomatic 19) crates/tus/src/handlers/head.rs:15
- RequestDeserializer::fill_value (cognitive 183) crates/core/src/serde/request.rs:267
- RequestDeserializer::deserialize_value (cognitive 20) crates/core/src/serde/request.rs:189
- RequestDeserializer::real_parser (cognitive 16) crates/core/src/serde/request.rs:167
- salvo_tus::handlers::post::create (cognitive 74) crates/tus/src/handlers/post.rs:21
- salvo_tus::handlers::patch::patch (cognitive 69) crates/tus/src/handlers/patch.rs:17
- salvo_tus::handlers::head::head (cognitive 26) crates/tus/src/handlers/head.rs:15
- PathParser::scan_wisps (cognitive 73) crates/core/src/routing/filters/path.rs:844
- PathParser::scan_regex (cognitive 17) crates/core/src/routing/filters/path.rs:761
- PathParser::validate (cognitive 16) crates/core/src/routing/filters/path.rs:992
- salvo_oapi_macros::bound::with_bound (cognitive 38) crates/oapi-macros/src/bound.rs:57
- salvo_oapi_macros::shared::parse_input_type (cognitive 18) crates/oapi-macros/src/shared.rs:55
- salvo_oapi_macros::endpoint::generate (cognitive 17) crates/oapi-macros/src/endpoint.rs:133
- StraightStream::poll_write (cognitive 31) crates/core/src/conn/stream/straight.rs:116
- StraightStream::poll_write_vectored (cognitive 31) crates/core/src/conn/stream/straight.rs:181
- StraightStream::poll_read (cognitive 17) crates/core/src/conn/stream/straight.rs:73
- ClassTooLong: Request crates/core/src/http/request.rs:203
- ClassTooLong: ComplexEnum crates/oapi-macros/src/schema/enum_schemas.rs:480
- ClassTooLong: ComponentSchema crates/oapi-macros/src/component.rs:63
- Duplicated block (26 lines × 2) crates/macros/src/shared.rs:80
- Duplicated block (26 lines × 2) crates/macros/src/shared.rs:117
- Duplicated block (26 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:513
- Duplicated block (18 lines × 2) crates/core/src/extract/case.rs:62
- Duplicated block (18 lines × 2) crates/oapi-macros/src/component.rs:139
- Duplicated block (18 lines × 2) crates/oapi-macros/src/response.rs:476
- Duplicated block (15 lines × 2) crates/macros/src/extract.rs:425
- Duplicated block (15 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:983
- Duplicated block (15 lines × 2) crates/oapi-macros/src/schema_type.rs:69
- Duplicated block (10–11 lines × 2) crates/core/src/routing/filters/path.rs:636
- Duplicated block (10–11 lines × 2) crates/extra/src/tower_compat.rs:103
- Duplicated block (10–11 lines × 2) crates/oapi-macros/src/operation/example.rs:25
- StraightStream::poll_write (cyclomatic 16) crates/core/src/conn/stream/straight.rs:116
- StraightStream::poll_write_vectored (cyclomatic 16) crates/core/src/conn/stream/straight.rs:181
- NamedStructSchema::try_to_tokens (cognitive 62) crates/oapi-macros/src/schema/struct_schemas.rs:182
- NamedStructSchema::field_as_schema_property (cognitive 17) crates/oapi-macros/src/schema/struct_schemas.rs:61
- CombWisp::detect (cognitive 44) crates/core/src/routing/filters/path.rs:448
- CombWisp::new (cognitive 24) crates/core/src/routing/filters/path.rs:353
- salvo_macros::extract::generate (cognitive 24) crates/macros/src/extract.rs:274
- salvo_macros::shared::parse_input_type (cognitive 19) crates/macros/src/shared.rs:33
- RequestBodyAttr::parse (cognitive 20) crates/oapi-macros/src/operation/request_body.rs:67
- RequestBodyAttr::try_to_tokens (cognitive 20) crates/oapi-macros/src/operation/request_body.rs:158
- Router::detect_with_method (cognitive 19) crates/core/src/routing/router.rs:253
- Router::fmt::print (cognitive 17) crates/core/src/routing/router.rs:667
- Duplicated block (24 lines × 2) crates/macros/src/handler.rs:16
- Duplicated block (24 lines × 2) crates/oapi-macros/src/response.rs:500
- Duplicated block (23 lines × 2) crates/csrf/src/aes_gcm_cipher.rs:57
- Duplicated block (23 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:812
- Duplicated block (20 lines × 2) crates/core/src/conn/tcp.rs:245
- Duplicated block (20 lines × 2) crates/proxy/src/hyper_client.rs:149
- Duplicated block (17 lines × 3) crates/core/src/conn/native_tls/listener.rs:165
- Duplicated block (17 lines × 3) crates/oapi-macros/src/operation/encoding.rs:42
- Duplicated block (17 lines × 2) crates/core/src/http/body/channel.rs:103
- Duplicated block (17 lines × 2) crates/oapi-macros/src/schema/enum_variant.rs:238
- Duplicated block (16 lines × 2) crates/macros/src/extract.rs:305
- Duplicated block (16 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:766
- Duplicated block (14 lines × 3) crates/craft-macros/src/utils.rs:6
- Duplicated block (14 lines × 3) crates/tus/src/handlers/delete.rs:34
- Duplicated block (13 lines × 2) crates/core/src/extract/case.rs:90
- Duplicated block (13 lines × 2) crates/oapi-macros/src/response/derive.rs:269
- Duplicated block (9 lines × 3) crates/core/src/conn/stream/straight.rs:104
- Duplicated block (9 lines × 3) crates/oapi-macros/src/response/derive.rs:306
- Duplicated block (8 lines × 3) crates/oapi-macros/src/component.rs:432
- Duplicated block (8 lines × 3) crates/oapi/src/openapi/components.rs:182
- Off the main sequence: salvo-serde-util
- Off the main sequence: salvo_core
- StaticDir::handle (cyclomatic 56) crates/serve-static/src/dir.rs:486
- RequestDeserializer::fill_value (cyclomatic 52) crates/core/src/serde/request.rs:267
- salvo_oapi_macros::bound::with_bound (cyclomatic 40) crates/oapi-macros/src/bound.rs:57
- ComponentSchema::non_generic_to_tokens (cyclomatic 35) crates/oapi-macros/src/component.rs:393
- NamedFile::send_inner (cyclomatic 34) crates/core/src/fs/named_file.rs:812
- HyperHandler::handle (cyclomatic 31) crates/core/src/service.rs:268
- NamedStructSchema::try_to_tokens (cyclomatic 31) crates/oapi-macros/src/schema/struct_schemas.rs:182
- Compression::handle (cyclomatic 27) crates/compression/src/lib.rs:477
- Builder::serve_connection (cyclomatic 27) crates/core/src/conn/quinn/builder.rs:103
- ReadSeeker::send_inner (cyclomatic 26) crates/core/src/writing/seek.rs:77
- HttpBuilder::serve_connection (cyclomatic 25) crates/core/src/conn/proto.rs:82
- Proxy::build_proxied_request (cyclomatic 25) crates/proxy/src/lib.rs:506
- PathParser::scan_wisps (cyclomatic 22) crates/core/src/routing/filters/path.rs:844
- UnnamedStructSchema::try_to_tokens (cyclomatic 21) crates/oapi-macros/src/schema/struct_schemas.rs:531
- NormNode::with_method (cyclomatic 20) crates/oapi/src/routing.rs:105
- salvo_macros::extract::generate (cyclomatic 19) crates/macros/src/extract.rs:274
- OpenApi::merge_norm_node (cyclomatic 19) crates/oapi/src/openapi.rs:624
- EndpointAttr::parse (cyclomatic 19) crates/oapi-macros/src/endpoint/attr.rs:29
- ToParameters::try_to_tokens (cyclomatic 19) crates/oapi-macros/src/parameter/derive.rs:66
- CombWisp::detect (cyclomatic 18) crates/core/src/routing/filters/path.rs:448
- Server::try_serve (cyclomatic 18) crates/core/src/server.rs:352
- salvo_serve_static::embed::render_embedded_data (cyclomatic 18) crates/serve-static/src/embed.rs:104
- ResBody::poll_frame (cyclomatic 17) crates/core/src/http/body/res.rs:150
- Operation::modifiers (cyclomatic 16) crates/oapi-macros/src/operation.rs:115
- Tracing::handle (cyclomatic 16) crates/otel/src/tracing.rs:92
- SerdeContainer::parse_attribute (cyclomatic 16) crates/serde-util/src/lib.rs:155
- FixmeComment crates/oapi-macros/src/schema/enum_schemas.rs:930
- StaticDir::handle (cognitive 164) crates/serve-static/src/dir.rs:486
- ComponentSchema::non_generic_to_tokens (cognitive 84) crates/oapi-macros/src/component.rs:393
- HttpBuilder::serve_connection (cognitive 61) crates/core/src/conn/proto.rs:82
- Builder::serve_connection (cognitive 61) crates/core/src/conn/quinn/builder.rs:103
- NamedFile::send_inner (cognitive 48) crates/core/src/fs/named_file.rs:812
- Compression::handle (cognitive 42) crates/compression/src/lib.rs:477
- HyperHandler::handle (cognitive 41) crates/core/src/service.rs:268
- Proxy::build_proxied_request (cognitive 40) crates/proxy/src/lib.rs:506
- salvo_oapi::routing::normalize_oapi_path (cognitive 34) crates/oapi/src/routing.rs:12
- ReadSeeker::send_inner (cognitive 33) crates/core/src/writing/seek.rs:77
- OpenApi::merge_norm_node (cognitive 33) crates/oapi/src/openapi.rs:624
- Server::try_serve (cognitive 32) crates/core/src/server.rs:352
- salvo_serve_static::embed::render_embedded_data (cognitive 32) crates/serve-static/src/embed.rs:104
- CharsWispBuilder::build (cognitive 31) crates/core/src/routing/filters/path.rs:217
- FormData::read_with_directory (cognitive 29) crates/core/src/http/form.rs:131
- HttpRange::parse (cognitive 26) crates/core/src/http/range.rs:46
- Operation::modifiers (cognitive 26) crates/oapi-macros/src/operation.rs:115
- NormNode::with_method (cognitive 25) crates/oapi/src/routing.rs:105
- ResponseTuple::try_to_tokens (cognitive 25) crates/oapi-macros/src/response.rs:297
- FlexNamer::assign_name (cognitive 23) crates/oapi/src/naming.rs:294
- SessionHandler::handle (cognitive 23) crates/session/src/lib.rs:418
- ReqwestClient::execute (cognitive 20) crates/proxy/src/reqwest_client.rs:58
- NamedFileBuilder::build (cognitive 19) crates/core/src/fs/named_file.rs:325
- UnnamedStructSchema::try_to_tokens (cognitive 19) crates/oapi-macros/src/schema/struct_schemas.rs:531
- Tracing::handle (cognitive 19) crates/otel/src/tracing.rs:92
- TusOptions::extract_host_and_proto (cognitive 19) crates/tus/src/options.rs:347
- EncodeStream::poll_next (cognitive 18) crates/compression/src/stream.rs:128
- RegexWisp::detect (cognitive 18) crates/core/src/routing/filters/path.rs:622
- Csrf::handle (cognitive 18) crates/csrf/src/lib.rs:336
- WebSocketUpgrade::upgrade (cognitive 18) crates/extra/src/websocket.rs:377
- FieldInfo::try_from (cognitive 18) crates/macros/src/extract.rs:27
- ComplexEnum::tagged_variant_tokens (cognitive 18) crates/oapi-macros/src/schema/enum_schemas.rs:727
- Parameter::try_to_tokens (cognitive 17) crates/oapi-macros/src/parameter/derive.rs:540
- ToSchema::try_to_tokens (cognitive 17) crates/oapi-macros/src/schema.rs:75
- HyperClient::execute (cognitive 17) crates/proxy/src/hyper_client.rs:123
- AcmeListenerBuilder::build_certon_manager (cognitive 16) crates/acme/src/listener.rs:288
- FlatParser::next (cognitive 16) crates/core/src/serde/flat_value.rs:224
- EndpointAttr::parse (cognitive 16) crates/oapi-macros/src/endpoint/attr.rs:29
- EnumResponse::parse_variant_attributes (cognitive 16) crates/oapi-macros/src/response/derive.rs:583
- StaticEmbed::handle (cognitive 16) crates/serve-static/src/embed.rs:311
- DiskStore::try_finalize_if_complete (cognitive 16) crates/tus/src/stores/disk.rs:357
- Change coupling clique: cookie.rs, header.rs, path.rs, query.rs, json.rs crates/core/src/extract/parameter/cookie.rs
- Change-coupling hub: listener.rs → listener.rs, config.rs, listener.rs, listener.rs crates/core/src/conn/rustls/listener.rs
- REDACTED
- Near-duplicate member pair (100 shared lines) crates/oapi-macros/src/schema/enum_schemas.rs:735
- Duplicated block (41 lines × 2) crates/core/src/conn/stream/straight.rs:128
- Duplicated block (39–40 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:890
- Duplicated block (38 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:736
- Duplicated block (34–37 lines × 2) crates/core/src/conn/quinn/builder.rs:344
- Duplicated block (30–31 lines × 2) crates/tus/src/handlers/get.rs:23
- Duplicated block (21–27 lines × 2) crates/oapi-macros/src/operation/request_body.rs:165
- Duplicated block (20 lines × 3) crates/oapi-macros/src/schema/enum_schemas.rs:508
- Duplicated block (19–20 lines × 2) crates/core/src/fs/named_file.rs:957
- Duplicated block (11–19 lines × 3) crates/oapi-macros/src/operation/request_body.rs:167
- Duplicated block (18–19 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:135
- Duplicated block (18 lines × 3) crates/oapi-macros/src/schema/enum_schemas.rs:558
- Duplicated block (15 lines × 6) crates/oapi-macros/src/schema/enum_schemas.rs:513
- Duplicated block (15 lines × 3) crates/tus/src/handlers/delete.rs:15
- Duplicated block (13–15 lines × 2) crates/oapi-macros/src/component.rs:452
- Duplicated block (12–13 lines × 3) crates/core/src/conn/stream/straight.rs:83
- Duplicated block (10–11 lines × 3) crates/tus/src/handlers/get.rs:67
- Duplicated block (9–11 lines × 2) crates/oapi-macros/src/operation/request_body.rs:193
- Duplicated block (9–10 lines × 3) crates/core/src/conn/native_tls/listener.rs:74
- Duplicated block (8–10 lines × 3) crates/oapi-macros/src/response/derive.rs:411
- Duplicated block (9–10 lines × 2) crates/core/src/catcher.rs:433
- Duplicated block (7–8 lines × 3) crates/oapi-macros/src/component.rs:455
- Duplicated block (7–8 lines × 2) crates/oapi-macros/src/component.rs:232
- Duplicated block (6 lines × 4) crates/oapi-macros/src/component.rs:455
- Duplicated block (4–6 lines × 3) crates/compression/src/lib.rs:557
- Duplicated block (2–5 lines × 4) crates/core/src/http/body/req.rs:208
- Duplicated block (6 lines × 3) crates/core/src/extract/payload/file.rs:57
- Duplicated block (12 lines × 3) crates/core/src/conn/native_tls/listener.rs:218
- Duplicated block (8 lines × 4) crates/core/src/conn/proto.rs:184
- Coverage collected but not gated
- JavaScript dependencies are not locked
Minor — 51 finding(s)
- Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:196
- Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:237
- Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:371
- Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:404
- Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:417
- Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:426
- Interpolated log message defeats structured logging crates/tus/src/handlers/patch.rs:126
- Interpolated log message defeats structured logging crates/tus/src/handlers/post.rs:271
- Interpolated log message defeats structured logging crates/serve-static/src/embed.rs:145
- Interpolated log message defeats structured logging crates/proxy/src/lib.rs:728
- Interpolated log message defeats structured logging crates/oapi/src/naming.rs:339
- Interpolated log message defeats structured logging crates/oapi/src/openapi.rs:727
- Interpolated log message defeats structured logging crates/jwt-auth/src/oidc.rs:297
- Interpolated log message defeats structured logging crates/jwt-auth/src/oidc.rs:328
- Interpolated log message defeats structured logging crates/jwt-auth/src/oidc.rs:431
- Interpolated log message defeats structured logging crates/jwt-auth/src/oidc/cache.rs:287
- Interpolated log message defeats structured logging crates/extra/src/concurrency_limiter.rs:99
- Interpolated log message defeats structured logging crates/extra/src/sse.rs:305
- Interpolated log message defeats structured logging crates/extra/src/websocket.rs:542
- Interpolated log message defeats structured logging crates/cors/src/lib.rs:599
- Interpolated log message defeats structured logging crates/core/src/catcher.rs:149
- Interpolated log message defeats structured logging crates/core/src/server.rs:377
- Interpolated log message defeats structured logging crates/core/src/server.rs:502
- Interpolated log message defeats structured logging crates/core/src/server.rs:545
- Interpolated log message defeats structured logging crates/core/src/serde/request.rs:277
- Console output used as the logging channel crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-standalone-preset.js:2
- Console output used as the logging channel crates/oapi/src/swagger_ui/v5.34.0/swagger-ui.js:1
- Duplicated predicate crates/macros/src/handler.rs:132
- Duplicated predicate crates/macros/src/handler.rs:53
- Hand-rolled JSON/XML parsing via regex crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-bundle.js:2
- Hand-rolled JSON/XML parsing via regex crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-es-bundle.js:2
- No named authorization policies
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- Orphaned file crates/cors/src/inner.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No release approval gate
- Security headers incomplete
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e6d624089d2d49ce8efd96ed8e6b0bd3/history.json --exit-code 0 --source . | 19 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e6d624089d2d49ce8efd96ed8e6b0bd3/tree.json --exit-code 0 --source . | 8 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 46 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui.js` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |