Executive summary
poem-web/poem falls short of our standard for production because we found no recorded design decisions and no architecture document or diagram, and 112 files are no longer known to anyone active in the project. It scores 60 out of 100 and is rated Adequate, and all 28 of its critical findings are security problems.
Maturity, at 54, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5 points. Automating accessibility checks comes next, worth about 4 points. Raising Maturity to 70 would lift the score to about 65.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight passwords or keys in the code's history and three in the code are open to anyone who can read the repository, and six secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once.
The product code is 49,327 lines, about €71,000 to rebuild.
If Maturity rose from 54 to 70, the lowest score rated Strong, the score would rise from 60 to about 65.
New since the last survey: 26 findings
- Cyclomatic Complexity · StaticFilesEndpoint::serve (cyclomatic 19) poem/src/endpoint/static_files.rs
- Cyclomatic Complexity · Node::matches (cyclomatic 16) poem/src/route/internal/radix_tree.rs
- Cyclomatic Complexity · poem_grpc::encoding::decode_single_response_message (cyclomatic 16) poem-grpc/src/encoding.rs
- Cognitive Complexity · StaticFilesEndpoint::serve (cognitive 39) poem/src/endpoint/static_files.rs
- Cognitive Complexity · poem_grpc::encoding::decode_single_response_message (cognitive 31) poem-grpc/src/encoding.rs
- Code Duplication · Near-duplicate member family (4 members, 19 shared lines) poem-grpc-build/src/server.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) poem-grpc/src/client.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) poem-grpc/src/server.rs
- Code Duplication · Duplicated block (28 lines × 2) poem-grpc/src/server.rs
- Code Duplication · Duplicated block (20 lines × 2) poem-grpc/src/client.rs
- Code Duplication · Duplicated block (17 lines × 2) poem-grpc/src/client.rs
- Code Duplication · Duplicated block (16 lines × 2) poem-grpc/src/client.rs
- Code Duplication · Duplicated block (16 lines × 2) poem-grpc/src/client.rs
- Code Duplication · Duplicated block (13 lines × 4) poem-grpc-build/src/server.rs
- Code Duplication · Duplicated block (13 lines × 2) poem-openapi-derive/src/api.rs
- Code Duplication · Duplicated block (8–11 lines × 4) poem-grpc/src/client.rs
- Code Duplication · Duplicated block (6 lines × 2) poem-grpc/src/reflection.rs
- Churn × Complexity Hotspots · Hotspot: poem-openapi-derive/src/api.rs poem-openapi-derive/src/api.rs
- Churn × Complexity Hotspots · Hotspot: poem/src/web/static_file.rs poem/src/web/static_file.rs
- Churn × Complexity Hotspots · Hotspot: poem/src/endpoint/static_files.rs poem/src/endpoint/static_files.rs
- Churn × Complexity Hotspots · Hotspot: poem/src/route/internal/radix_tree.rs poem/src/route/internal/radix_tree.rs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
Fixed since the last survey: 11 findings
- Cyclomatic Complexity · StaticFilesEndpoint::call (cyclomatic 20) poem/src/endpoint/static_files.rs
- Cognitive Complexity · StaticFilesEndpoint::call (cognitive 40) poem/src/endpoint/static_files.rs
- Code Duplication · Near-duplicate member family (4 members, 19 shared lines) poem-grpc-build/src/server.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) poem-grpc/src/client.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) poem-grpc/src/server.rs
- Code Duplication · Duplicated block (31 lines × 2) poem-grpc/src/server.rs
- Code Duplication · Duplicated block (21 lines × 2) poem-grpc/src/client.rs
- Code Duplication · Duplicated block (20 lines × 2) poem-grpc/src/client.rs
- Code Duplication · Duplicated block (20 lines × 2) poem-grpc/src/client.rs
- Code Duplication · Duplicated block (18 lines × 4) poem-grpc/src/client.rs
- Code Duplication · Duplicated block (13 lines × 4) poem-grpc-build/src/server.rs
Rebuild cost: about €71,000 · Estimate
| Cost to rebuild | €24,000 to €120,000, for 395 to 1,252 hours of work, about 0.5 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 60. 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: 49,327 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 poem.listener.acme.auto_cert | 2 poem.middleware | 3 poem_grpc.metadata | 4 poem_openapi_derive.common_args | 5 poem.response | 6 poem_openapi.registry | 7 poem.web | 8 poem_openapi.types | 9 poem_openapi.validation | 10 poem.web.addr | 11 poem_lambda | 12 poem.listener.acme.listener | 13 poem.listener.openssl_tls | 14 poem.request | 15 poem.body | 16 poem.endpoint.endpoint | 17 poem.listener | 18 poem.web.data | 19 poem.web.path | 20 poem_grpc.service | 21 poem_openapi.base | 22 poem_openapi.payload | 23 poem.error | 24 poem.middleware.requestid | 25 poem.web.static_file | 26 poem_grpc.reflection | 27 poem_grpc.server | 28 poem_mcpserver.streamable_http | 29 poem_openapi.auth | 30 poem_openapi.payload.base64_payload | 31 poem_openapi.payload.binary | 32 poem_openapi.payload.html | 33 poem_openapi.payload.json | 34 poem_openapi.payload.plain_text | 35 poem_openapi.payload.xml | 36 poem_openapi.payload.yaml | 37 poem_openapi_derive.api | 38 poem.middleware.tower_compat | 39 poem_mcpserver.server | 40 poem_openapi.payload.attachment |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 poem.listener.acme.auto_cert | ||||||||||||||||||||||||||||||||||||||||
| 2 poem.middleware | ||||||||||||||||||||||||||||||||||||||||
| 3 poem_grpc.metadata | ||||||||||||||||||||||||||||||||||||||||
| 4 poem_openapi_derive.common_args | ||||||||||||||||||||||||||||||||||||||||
| 5 poem.response | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 poem_openapi.registry | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 poem.web | 6 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 8 poem_openapi.types | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 poem_openapi.validation | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 poem.web.addr | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 poem_lambda | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 poem.listener.acme.listener | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 13 poem.listener.openssl_tls | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 poem.request | 2 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 poem.body | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 poem.endpoint.endpoint | 6 | |||||||||||||||||||||||||||||||||||||||
| 17 poem.listener | 1 | 3 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 18 poem.web.data | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 poem.web.path | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 poem_grpc.service | 4 | |||||||||||||||||||||||||||||||||||||||
| 21 poem_openapi.base | 14 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 22 poem_openapi.payload | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 poem.error | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 poem.middleware.requestid | 1 | 1 | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 25 poem.web.static_file | 1 | 1 | 2 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 26 poem_grpc.reflection | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 poem_grpc.server | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 poem_mcpserver.streamable_http | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 29 poem_openapi.auth | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 poem_openapi.payload.base64_payload | 1 | 3 | 3 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 31 poem_openapi.payload.binary | 1 | 3 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 32 poem_openapi.payload.html | 1 | 3 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 33 poem_openapi.payload.json | 1 | 3 | 2 | 3 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 34 poem_openapi.payload.plain_text | 1 | 3 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 35 poem_openapi.payload.xml | 1 | 3 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 36 poem_openapi.payload.yaml | 1 | 3 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 37 poem_openapi_derive.api | 4 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 38 poem.middleware.tower_compat | 1 | 1 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 39 poem_mcpserver.server | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 poem_openapi.payload.attachment | 1 | 3 | 1 | 1 | 1 | 1 |
5→7 poem.response uses poem.web part of a loop✕
- Connections
- 1 pair of types, where a type in poem.response uses a type in poem.web.
- The types involved
poem.response.Response→poem.web.IntoResponse
- Direction
- poem.response uses poem.web, so a change to poem.web can break poem.response, while a change to poem.response can't break poem.web.
- 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→15 poem.response uses poem.body part of a loop✕
- Connections
- 1 pair of types, where a type in poem.response uses a type in poem.body.
- The types involved
poem.response.Response→poem.body.Body
- Direction
- poem.response uses poem.body, so a change to poem.body can break poem.response, while a change to poem.response can't break poem.body.
- 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→21 poem_openapi.registry uses poem_openapi.base part of a loop✕
- Connections
- 1 pair of types, where a type in poem_openapi.registry uses a type in poem_openapi.base.
- The types involved
poem_openapi.registry.MetaOperationParam→poem_openapi.base.ParameterStyle
- Direction
- poem_openapi.registry uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi.registry, while a change to poem_openapi.registry can't break poem_openapi.base.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→5 poem.web uses poem.response✕
- Connections
- 6 pairs of types, where a type in poem.web uses a type in poem.response.
- The types involved
poem.web.Html→poem.response.Responsepoem.web.IntoResponse→poem.response.Responsepoem.web.WithBody→poem.response.Responsepoem.web.WithContentType→poem.response.Responsepoem.web.WithHeader→poem.response.Responsepoem.web.WithStatus→poem.response.Response
- Direction
- poem.web uses poem.response, so a change to poem.response can break poem.web, while a change to poem.web can't break poem.response.
- Position
- Below the diagonal: poem.web uses a module listed above it, which is the healthy direction.
7→14 poem.web uses poem.request part of a loop✕
- Connections
- 1 pair of types, where a type in poem.web uses a type in poem.request.
- The types involved
poem.web.FromRequest→poem.request.Request
- Direction
- poem.web uses poem.request, so a change to poem.request can break poem.web, while a change to poem.web can't break poem.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.
7→15 poem.web uses poem.body part of a loop✕
- Connections
- 2 pairs of types, where a type in poem.web uses a type in poem.body.
- The types involved
poem.web.RequestBody→poem.body.Bodypoem.web.WithBody→poem.body.Body
- Direction
- poem.web uses poem.body, so a change to poem.body can break poem.web, while a change to poem.web can't break poem.body.
- 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→6 poem_openapi.types uses poem_openapi.registry✕
- Connections
- 2 pairs of types, where a type in poem_openapi.types uses a type in poem_openapi.registry.
- The types involved
poem_openapi.types.Type→poem_openapi.registry.MetaSchemaRefpoem_openapi.types.Type→poem_openapi.registry.Registry
- Direction
- poem_openapi.types uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.types, while a change to poem_openapi.types can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.types uses a module listed above it, which is the healthy direction.
9→6 poem_openapi.validation uses poem_openapi.registry✕
- Connections
- 1 pair of types, where a type in poem_openapi.validation uses a type in poem_openapi.registry.
- The types involved
poem_openapi.validation.ValidatorMeta→poem_openapi.registry.MetaSchema
- Direction
- poem_openapi.validation uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.validation, while a change to poem_openapi.validation can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.validation uses a module listed above it, which is the healthy direction.
10→7 poem.web.addr uses poem.web✕
- Connections
- 4 pairs of types, where a type in poem.web.addr uses a type in poem.web.
- The types involved
poem.web.addr.LocalAddr→poem.web.FromRequestpoem.web.addr.LocalAddr→poem.web.RequestBodypoem.web.addr.RemoteAddr→poem.web.FromRequestpoem.web.addr.RemoteAddr→poem.web.RequestBody
- Direction
- poem.web.addr uses poem.web, so a change to poem.web can break poem.web.addr, while a change to poem.web.addr can't break poem.web.
- Position
- Below the diagonal: poem.web.addr uses a module listed above it, which is the healthy direction.
10→14 poem.web.addr uses poem.request part of a loop✕
- Connections
- 2 pairs of types, where a type in poem.web.addr uses a type in poem.request.
- The types involved
poem.web.addr.LocalAddr→poem.request.Requestpoem.web.addr.RemoteAddr→poem.request.Request
- Direction
- poem.web.addr uses poem.request, so a change to poem.request can break poem.web.addr, while a change to poem.web.addr can't break poem.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.
11→7 poem_lambda uses poem.web✕
- Connections
- 2 pairs of types, where a type in poem_lambda uses a type in poem.web.
- The types involved
poem_lambda.Context→poem.web.FromRequestpoem_lambda.Context→poem.web.RequestBody
- Direction
- poem_lambda uses poem.web, so a change to poem.web can break poem_lambda, while a change to poem_lambda can't break poem.web.
- Position
- Below the diagonal: poem_lambda uses a module listed above it, which is the healthy direction.
11→14 poem_lambda uses poem.request part of a loop✕
- Connections
- 2 pairs of types, where a type in poem_lambda uses a type in poem.request.
- The types involved
poem_lambda.Context→poem.request.Requestpoem_lambda.poem_lambda$module→poem.request.Request
- Direction
- poem_lambda uses poem.request, so a change to poem.request can break poem_lambda, while a change to poem_lambda can't break poem.request.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→1 poem.listener.acme.listener uses poem.listener.acme.auto_cert✕
- Connections
- 1 pair of types, where a type in poem.listener.acme.listener uses a type in poem.listener.acme.auto_cert.
- The types involved
poem.listener.acme.listener.AutoCertListener→poem.listener.acme.auto_cert.AutoCert
- Direction
- poem.listener.acme.listener uses poem.listener.acme.auto_cert, so a change to poem.listener.acme.auto_cert can break poem.listener.acme.listener, while a change to poem.listener.acme.listener can't break poem.listener.acme.auto_cert.
- Position
- Below the diagonal: poem.listener.acme.listener uses a module listed above it, which is the healthy direction.
12→10 poem.listener.acme.listener uses poem.web.addr✕
- Connections
- 1 pair of types, where a type in poem.listener.acme.listener uses a type in poem.web.addr.
- The types involved
poem.listener.acme.listener.AutoCertAcceptor→poem.web.addr.LocalAddr
- Direction
- poem.listener.acme.listener uses poem.web.addr, so a change to poem.web.addr can break poem.listener.acme.listener, while a change to poem.listener.acme.listener can't break poem.web.addr.
- Position
- Below the diagonal: poem.listener.acme.listener uses a module listed above it, which is the healthy direction.
12→17 poem.listener.acme.listener uses poem.listener part of a loop✕
- Connections
- 3 pairs of types, where a type in poem.listener.acme.listener uses a type in poem.listener.
- The types involved
poem.listener.acme.listener.AutoCertAcceptor→poem.listener.Acceptorpoem.listener.acme.listener.AutoCertListener→poem.listener.Listenerpoem.listener.acme.listener.ResolvedCertListener→poem.listener.Listener
- Direction
- poem.listener.acme.listener uses poem.listener, so a change to poem.listener can break poem.listener.acme.listener, while a change to poem.listener.acme.listener can't break poem.listener.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→10 poem.listener.openssl_tls uses poem.web.addr✕
- Connections
- 1 pair of types, where a type in poem.listener.openssl_tls uses a type in poem.web.addr.
- The types involved
poem.listener.openssl_tls.OpensslTlsAcceptor→poem.web.addr.LocalAddr
- Direction
- poem.listener.openssl_tls uses poem.web.addr, so a change to poem.web.addr can break poem.listener.openssl_tls, while a change to poem.listener.openssl_tls can't break poem.web.addr.
- Position
- Below the diagonal: poem.listener.openssl_tls uses a module listed above it, which is the healthy direction.
13→17 poem.listener.openssl_tls uses poem.listener part of a loop✕
- Connections
- 2 pairs of types, where a type in poem.listener.openssl_tls uses a type in poem.listener.
- The types involved
poem.listener.openssl_tls.OpensslTlsAcceptor→poem.listener.Acceptorpoem.listener.openssl_tls.OpensslTlsListener→poem.listener.Listener
- Direction
- poem.listener.openssl_tls uses poem.listener, so a change to poem.listener can break poem.listener.openssl_tls, while a change to poem.listener.openssl_tls can't break poem.listener.
- 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→7 poem.request uses poem.web✕
- Connections
- 2 pairs of types, where a type in poem.request uses a type in poem.web.
- The types involved
poem.request.Request→poem.web.FromRequestpoem.request.Request→poem.web.RequestBody
- Direction
- poem.request uses poem.web, so a change to poem.web can break poem.request, while a change to poem.request can't break poem.web.
- Position
- Below the diagonal: poem.request uses a module listed above it, which is the healthy direction.
14→10 poem.request uses poem.web.addr✕
- Connections
- 4 pairs of types, where a type in poem.request uses a type in poem.web.addr.
- The types involved
poem.request.Request→poem.web.addr.LocalAddrpoem.request.Request→poem.web.addr.RemoteAddrpoem.request.RequestState→poem.web.addr.LocalAddrpoem.request.RequestState→poem.web.addr.RemoteAddr
- Direction
- poem.request uses poem.web.addr, so a change to poem.web.addr can break poem.request, while a change to poem.request can't break poem.web.addr.
- Position
- Below the diagonal: poem.request uses a module listed above it, which is the healthy direction.
14→11 poem.request uses poem_lambda✕
- Connections
- 2 pairs of types, where a type in poem.request uses a type in poem_lambda.
- The types involved
poem.request.OnUpgrade→poem_lambda.Contextpoem.request.Upgraded→poem_lambda.Context
- Direction
- poem.request uses poem_lambda, so a change to poem_lambda can break poem.request, while a change to poem.request can't break poem_lambda.
- Position
- Below the diagonal: poem.request uses a module listed above it, which is the healthy direction.
14→15 poem.request uses poem.body part of a loop✕
- Connections
- 1 pair of types, where a type in poem.request uses a type in poem.body.
- The types involved
poem.request.Request→poem.body.Body
- Direction
- poem.request uses poem.body, so a change to poem.body can break poem.request, while a change to poem.request can't break poem.body.
- 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.
15→5 poem.body uses poem.response✕
- Connections
- 1 pair of types, where a type in poem.body uses a type in poem.response.
- The types involved
poem.body.Body→poem.response.Response
- Direction
- poem.body uses poem.response, so a change to poem.response can break poem.body, while a change to poem.body can't break poem.response.
- Position
- Below the diagonal: poem.body uses a module listed above it, which is the healthy direction.
15→7 poem.body uses poem.web✕
- Connections
- 3 pairs of types, where a type in poem.body uses a type in poem.web.
- The types involved
poem.body.Body→poem.web.FromRequestpoem.body.Body→poem.web.IntoResponsepoem.body.Body→poem.web.RequestBody
- Direction
- poem.body uses poem.web, so a change to poem.web can break poem.body, while a change to poem.body can't break poem.web.
- Position
- Below the diagonal: poem.body uses a module listed above it, which is the healthy direction.
15→14 poem.body uses poem.request✕
- Connections
- 1 pair of types, where a type in poem.body uses a type in poem.request.
- The types involved
poem.body.Body→poem.request.Request
- Direction
- poem.body uses poem.request, so a change to poem.request can break poem.body, while a change to poem.body can't break poem.request.
- Position
- Below the diagonal: poem.body uses a module listed above it, which is the healthy direction.
16→14 poem.endpoint.endpoint uses poem.request✕
- Connections
- 6 pairs of types, where a type in poem.endpoint.endpoint uses a type in poem.request.
- The types involved
poem.endpoint.endpoint.AsyncFnEndpoint→poem.request.Requestpoem.endpoint.endpoint.DynEndpoint→poem.request.Requestpoem.endpoint.endpoint.EitherEndpoint→poem.request.Requestpoem.endpoint.endpoint.Endpoint→poem.request.Requestpoem.endpoint.endpoint.SyncFnEndpoint→poem.request.Requestpoem.endpoint.endpoint.ToDynEndpoint→poem.request.Request
- Direction
- poem.endpoint.endpoint uses poem.request, so a change to poem.request can break poem.endpoint.endpoint, while a change to poem.endpoint.endpoint can't break poem.request.
- Position
- Below the diagonal: poem.endpoint.endpoint uses a module listed above it, which is the healthy direction.
17→1 poem.listener uses poem.listener.acme.auto_cert✕
- Connections
- 1 pair of types, where a type in poem.listener uses a type in poem.listener.acme.auto_cert.
- The types involved
poem.listener.Listener→poem.listener.acme.auto_cert.AutoCert
- Direction
- poem.listener uses poem.listener.acme.auto_cert, so a change to poem.listener.acme.auto_cert can break poem.listener, while a change to poem.listener can't break poem.listener.acme.auto_cert.
- Position
- Below the diagonal: poem.listener uses a module listed above it, which is the healthy direction.
17→10 poem.listener uses poem.web.addr✕
- Connections
- 3 pairs of types, where a type in poem.listener uses a type in poem.web.addr.
- The types involved
poem.listener.Acceptor→poem.web.addr.LocalAddrpoem.listener.DynAcceptor→poem.web.addr.LocalAddrpoem.listener.ToDynAcceptor→poem.web.addr.LocalAddr
- Direction
- poem.listener uses poem.web.addr, so a change to poem.web.addr can break poem.listener, while a change to poem.listener can't break poem.web.addr.
- Position
- Below the diagonal: poem.listener uses a module listed above it, which is the healthy direction.
17→11 poem.listener uses poem_lambda✕
- Connections
- 1 pair of types, where a type in poem.listener uses a type in poem_lambda.
- The types involved
poem.listener.BoxIo→poem_lambda.Context
- Direction
- poem.listener uses poem_lambda, so a change to poem_lambda can break poem.listener, while a change to poem.listener can't break poem_lambda.
- Position
- Below the diagonal: poem.listener uses a module listed above it, which is the healthy direction.
17→12 poem.listener uses poem.listener.acme.listener✕
- Connections
- 1 pair of types, where a type in poem.listener uses a type in poem.listener.acme.listener.
- The types involved
poem.listener.Listener→poem.listener.acme.listener.AutoCertListener
- Direction
- poem.listener uses poem.listener.acme.listener, so a change to poem.listener.acme.listener can break poem.listener, while a change to poem.listener can't break poem.listener.acme.listener.
- Position
- Below the diagonal: poem.listener uses a module listed above it, which is the healthy direction.
17→13 poem.listener uses poem.listener.openssl_tls✕
- Connections
- 2 pairs of types, where a type in poem.listener uses a type in poem.listener.openssl_tls.
- The types involved
poem.listener.AcceptorExt→poem.listener.openssl_tls.OpensslTlsAcceptorpoem.listener.Listener→poem.listener.openssl_tls.OpensslTlsListener
- Direction
- poem.listener uses poem.listener.openssl_tls, so a change to poem.listener.openssl_tls can break poem.listener, while a change to poem.listener can't break poem.listener.openssl_tls.
- Position
- Below the diagonal: poem.listener uses a module listed above it, which is the healthy direction.
18→7 poem.web.data uses poem.web✕
- Connections
- 2 pairs of types, where a type in poem.web.data uses a type in poem.web.
- The types involved
poem.web.data.Data→poem.web.FromRequestpoem.web.data.Data→poem.web.RequestBody
- Direction
- poem.web.data uses poem.web, so a change to poem.web can break poem.web.data, while a change to poem.web.data can't break poem.web.
- Position
- Below the diagonal: poem.web.data uses a module listed above it, which is the healthy direction.
18→14 poem.web.data uses poem.request✕
- Connections
- 1 pair of types, where a type in poem.web.data uses a type in poem.request.
- The types involved
poem.web.data.Data→poem.request.Request
- Direction
- poem.web.data uses poem.request, so a change to poem.request can break poem.web.data, while a change to poem.web.data can't break poem.request.
- Position
- Below the diagonal: poem.web.data uses a module listed above it, which is the healthy direction.
19→7 poem.web.path uses poem.web✕
- Connections
- 2 pairs of types, where a type in poem.web.path uses a type in poem.web.
- The types involved
poem.web.path.Path→poem.web.FromRequestpoem.web.path.Path→poem.web.RequestBody
- Direction
- poem.web.path uses poem.web, so a change to poem.web can break poem.web.path, while a change to poem.web.path can't break poem.web.
- Position
- Below the diagonal: poem.web.path uses a module listed above it, which is the healthy direction.
19→14 poem.web.path uses poem.request✕
- Connections
- 1 pair of types, where a type in poem.web.path uses a type in poem.request.
- The types involved
poem.web.path.Path→poem.request.Request
- Direction
- poem.web.path uses poem.request, so a change to poem.request can break poem.web.path, while a change to poem.web.path can't break poem.request.
- Position
- Below the diagonal: poem.web.path uses a module listed above it, which is the healthy direction.
20→14 poem_grpc.service uses poem.request✕
- Connections
- 4 pairs of types, where a type in poem_grpc.service uses a type in poem.request.
- The types involved
poem_grpc.service.BidirectionalStreamingService→poem.request.Requestpoem_grpc.service.ClientStreamingService→poem.request.Requestpoem_grpc.service.ServerStreamingService→poem.request.Requestpoem_grpc.service.UnaryService→poem.request.Request
- Direction
- poem_grpc.service uses poem.request, so a change to poem.request can break poem_grpc.service, while a change to poem_grpc.service can't break poem.request.
- Position
- Below the diagonal: poem_grpc.service uses a module listed above it, which is the healthy direction.
21→6 poem_openapi.base uses poem_openapi.registry✕
- Connections
- 14 pairs of types, where a type in poem_openapi.base uses a type in poem_openapi.registry.
- The types involved
poem_openapi.base.ApiExtractor→poem_openapi.registry.MetaParamInpoem_openapi.base.ApiExtractor→poem_openapi.registry.MetaRequestpoem_openapi.base.ApiExtractor→poem_openapi.registry.MetaSchemaRefpoem_openapi.base.ApiExtractor→poem_openapi.registry.Registrypoem_openapi.base.ApiResponse→poem_openapi.registry.MetaResponsespoem_openapi.base.ApiResponse→poem_openapi.registry.Registrypoem_openapi.base.OAuthScopes→poem_openapi.registry.MetaOAuthScopepoem_openapi.base.OpenApi→poem_openapi.registry.MetaApipoem_openapi.base.OpenApi→poem_openapi.registry.Registrypoem_openapi.base.ResponseContent→poem_openapi.registry.MetaMediaTypepoem_openapi.base.ResponseContent→poem_openapi.registry.Registrypoem_openapi.base.Tags→poem_openapi.registry.Registrypoem_openapi.base.Webhook→poem_openapi.registry.MetaWebhookpoem_openapi.base.Webhook→poem_openapi.registry.Registry
- Direction
- poem_openapi.base uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.base, while a change to poem_openapi.base can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.base uses a module listed above it, which is the healthy direction.
21→7 poem_openapi.base uses poem.web✕
- Connections
- 1 pair of types, where a type in poem_openapi.base uses a type in poem.web.
- The types involved
poem_openapi.base.ApiExtractor→poem.web.RequestBody
- Direction
- poem_openapi.base uses poem.web, so a change to poem.web can break poem_openapi.base, while a change to poem_openapi.base can't break poem.web.
- Position
- Below the diagonal: poem_openapi.base uses a module listed above it, which is the healthy direction.
21→14 poem_openapi.base uses poem.request✕
- Connections
- 1 pair of types, where a type in poem_openapi.base uses a type in poem.request.
- The types involved
poem_openapi.base.ApiExtractor→poem.request.Request
- Direction
- poem_openapi.base uses poem.request, so a change to poem.request can break poem_openapi.base, while a change to poem_openapi.base can't break poem.request.
- Position
- Below the diagonal: poem_openapi.base uses a module listed above it, which is the healthy direction.
21→23 poem_openapi.base uses poem.error part of a loop✕
- Connections
- 1 pair of types, where a type in poem_openapi.base uses a type in poem.error.
- The types involved
poem_openapi.base.ApiResponse→poem.error.Error
- Direction
- poem_openapi.base uses poem.error, so a change to poem.error can break poem_openapi.base, while a change to poem_openapi.base can't break poem.error.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→6 poem_openapi.payload uses poem_openapi.registry✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload uses a type in poem_openapi.registry.
- The types involved
poem_openapi.payload.Payload→poem_openapi.registry.MetaSchemaRefpoem_openapi.payload.Payload→poem_openapi.registry.Registrypoem_openapi.payload.payload$module→poem_openapi.registry.MetaResponses
- Direction
- poem_openapi.payload uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.payload, while a change to poem_openapi.payload can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.payload uses a module listed above it, which is the healthy direction.
22→7 poem_openapi.payload uses poem.web✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload uses a type in poem.web.
- The types involved
poem_openapi.payload.ParsePayload→poem.web.RequestBody
- Direction
- poem_openapi.payload uses poem.web, so a change to poem.web can break poem_openapi.payload, while a change to poem_openapi.payload can't break poem.web.
- Position
- Below the diagonal: poem_openapi.payload uses a module listed above it, which is the healthy direction.
22→14 poem_openapi.payload uses poem.request✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload uses a type in poem.request.
- The types involved
poem_openapi.payload.ParsePayload→poem.request.Request
- Direction
- poem_openapi.payload uses poem.request, so a change to poem.request can break poem_openapi.payload, while a change to poem_openapi.payload can't break poem.request.
- Position
- Below the diagonal: poem_openapi.payload uses a module listed above it, which is the healthy direction.
23→5 poem.error uses poem.response✕
- Connections
- 3 pairs of types, where a type in poem.error uses a type in poem.response.
- The types involved
poem.error.Error→poem.response.Responsepoem.error.ResponseError→poem.response.Responsepoem.error.StaticFileError→poem.response.Response
- Direction
- poem.error uses poem.response, so a change to poem.response can break poem.error, while a change to poem.error can't break poem.response.
- Position
- Below the diagonal: poem.error uses a module listed above it, which is the healthy direction.
23→6 poem.error uses poem_openapi.registry✕
- Connections
- 2 pairs of types, where a type in poem.error uses a type in poem_openapi.registry.
- The types involved
poem.error.Error→poem_openapi.registry.MetaResponsespoem.error.Error→poem_openapi.registry.Registry
- Direction
- poem.error uses poem_openapi.registry, so a change to poem_openapi.registry can break poem.error, while a change to poem.error can't break poem_openapi.registry.
- Position
- Below the diagonal: poem.error uses a module listed above it, which is the healthy direction.
23→21 poem.error uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem.error uses a type in poem_openapi.base.
- The types involved
poem.error.Error→poem_openapi.base.ApiResponse
- Direction
- poem.error uses poem_openapi.base, so a change to poem_openapi.base can break poem.error, while a change to poem.error can't break poem_openapi.base.
- Position
- Below the diagonal: poem.error uses a module listed above it, which is the healthy direction.
24→2 poem.middleware.requestid uses poem.middleware✕
- Connections
- 1 pair of types, where a type in poem.middleware.requestid uses a type in poem.middleware.
- The types involved
poem.middleware.requestid.RequestId→poem.middleware.Middleware
- Direction
- poem.middleware.requestid uses poem.middleware, so a change to poem.middleware can break poem.middleware.requestid, while a change to poem.middleware.requestid can't break poem.middleware.
- Position
- Below the diagonal: poem.middleware.requestid uses a module listed above it, which is the healthy direction.
24→5 poem.middleware.requestid uses poem.response✕
- Connections
- 1 pair of types, where a type in poem.middleware.requestid uses a type in poem.response.
- The types involved
poem.middleware.requestid.ReqId→poem.response.Response
- Direction
- poem.middleware.requestid uses poem.response, so a change to poem.response can break poem.middleware.requestid, while a change to poem.middleware.requestid can't break poem.response.
- Position
- Below the diagonal: poem.middleware.requestid uses a module listed above it, which is the healthy direction.
24→7 poem.middleware.requestid uses poem.web✕
- Connections
- 3 pairs of types, where a type in poem.middleware.requestid uses a type in poem.web.
- The types involved
poem.middleware.requestid.ReqId→poem.web.FromRequestpoem.middleware.requestid.ReqId→poem.web.IntoResponsepoem.middleware.requestid.ReqId→poem.web.RequestBody
- Direction
- poem.middleware.requestid uses poem.web, so a change to poem.web can break poem.middleware.requestid, while a change to poem.middleware.requestid can't break poem.web.
- Position
- Below the diagonal: poem.middleware.requestid uses a module listed above it, which is the healthy direction.
24→14 poem.middleware.requestid uses poem.request✕
- Connections
- 2 pairs of types, where a type in poem.middleware.requestid uses a type in poem.request.
- The types involved
poem.middleware.requestid.ReqId→poem.request.Requestpoem.middleware.requestid.RequestIdEndpoint→poem.request.Request
- Direction
- poem.middleware.requestid uses poem.request, so a change to poem.request can break poem.middleware.requestid, while a change to poem.middleware.requestid can't break poem.request.
- Position
- Below the diagonal: poem.middleware.requestid uses a module listed above it, which is the healthy direction.
24→16 poem.middleware.requestid uses poem.endpoint.endpoint✕
- Connections
- 1 pair of types, where a type in poem.middleware.requestid uses a type in poem.endpoint.endpoint.
- The types involved
poem.middleware.requestid.RequestIdEndpoint→poem.endpoint.endpoint.Endpoint
- Direction
- poem.middleware.requestid uses poem.endpoint.endpoint, so a change to poem.endpoint.endpoint can break poem.middleware.requestid, while a change to poem.middleware.requestid can't break poem.endpoint.endpoint.
- Position
- Below the diagonal: poem.middleware.requestid uses a module listed above it, which is the healthy direction.
25→3 poem.web.static_file uses poem_grpc.metadata✕
- Connections
- 1 pair of types, where a type in poem.web.static_file uses a type in poem_grpc.metadata.
- The types involved
poem.web.static_file.static_file$module→poem_grpc.metadata.Metadata
- Direction
- poem.web.static_file uses poem_grpc.metadata, so a change to poem_grpc.metadata can break poem.web.static_file, while a change to poem.web.static_file can't break poem_grpc.metadata.
- Position
- Below the diagonal: poem.web.static_file uses a module listed above it, which is the healthy direction.
25→5 poem.web.static_file uses poem.response✕
- Connections
- 1 pair of types, where a type in poem.web.static_file uses a type in poem.response.
- The types involved
poem.web.static_file.StaticFileResponse→poem.response.Response
- Direction
- poem.web.static_file uses poem.response, so a change to poem.response can break poem.web.static_file, while a change to poem.web.static_file can't break poem.response.
- Position
- Below the diagonal: poem.web.static_file uses a module listed above it, which is the healthy direction.
25→6 poem.web.static_file uses poem_openapi.registry✕
- Connections
- 2 pairs of types, where a type in poem.web.static_file uses a type in poem_openapi.registry.
- The types involved
poem.web.static_file.StaticFileResponse→poem_openapi.registry.MetaResponsespoem.web.static_file.StaticFileResponse→poem_openapi.registry.Registry
- Direction
- poem.web.static_file uses poem_openapi.registry, so a change to poem_openapi.registry can break poem.web.static_file, while a change to poem.web.static_file can't break poem_openapi.registry.
- Position
- Below the diagonal: poem.web.static_file uses a module listed above it, which is the healthy direction.
25→7 poem.web.static_file uses poem.web✕
- Connections
- 3 pairs of types, where a type in poem.web.static_file uses a type in poem.web.
- The types involved
poem.web.static_file.StaticFileRequest→poem.web.FromRequestpoem.web.static_file.StaticFileRequest→poem.web.RequestBodypoem.web.static_file.StaticFileResponse→poem.web.IntoResponse
- Direction
- poem.web.static_file uses poem.web, so a change to poem.web can break poem.web.static_file, while a change to poem.web.static_file can't break poem.web.
- Position
- Below the diagonal: poem.web.static_file uses a module listed above it, which is the healthy direction.
25→14 poem.web.static_file uses poem.request✕
- Connections
- 1 pair of types, where a type in poem.web.static_file uses a type in poem.request.
- The types involved
poem.web.static_file.StaticFileRequest→poem.request.Request
- Direction
- poem.web.static_file uses poem.request, so a change to poem.request can break poem.web.static_file, while a change to poem.web.static_file can't break poem.request.
- Position
- Below the diagonal: poem.web.static_file uses a module listed above it, which is the healthy direction.
25→21 poem.web.static_file uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem.web.static_file uses a type in poem_openapi.base.
- The types involved
poem.web.static_file.StaticFileResponse→poem_openapi.base.ApiResponse
- Direction
- poem.web.static_file uses poem_openapi.base, so a change to poem_openapi.base can break poem.web.static_file, while a change to poem.web.static_file can't break poem_openapi.base.
- Position
- Below the diagonal: poem.web.static_file uses a module listed above it, which is the healthy direction.
26→14 poem_grpc.reflection uses poem.request✕
- Connections
- 2 pairs of types, where a type in poem_grpc.reflection uses a type in poem.request.
- The types involved
poem_grpc.reflection.V1ReflectionService→poem.request.Requestpoem_grpc.reflection.V1alphaReflectionService→poem.request.Request
- Direction
- poem_grpc.reflection uses poem.request, so a change to poem.request can break poem_grpc.reflection, while a change to poem_grpc.reflection can't break poem.request.
- Position
- Below the diagonal: poem_grpc.reflection uses a module listed above it, which is the healthy direction.
26→16 poem_grpc.reflection uses poem.endpoint.endpoint✕
- Connections
- 2 pairs of types, where a type in poem_grpc.reflection uses a type in poem.endpoint.endpoint.
- The types involved
poem_grpc.reflection.ReflectionServices→poem.endpoint.endpoint.Endpointpoem_grpc.reflection.ReflectionServices→poem.endpoint.endpoint.IntoEndpoint
- Direction
- poem_grpc.reflection uses poem.endpoint.endpoint, so a change to poem.endpoint.endpoint can break poem_grpc.reflection, while a change to poem_grpc.reflection can't break poem.endpoint.endpoint.
- Position
- Below the diagonal: poem_grpc.reflection uses a module listed above it, which is the healthy direction.
26→20 poem_grpc.reflection uses poem_grpc.service✕
- Connections
- 1 pair of types, where a type in poem_grpc.reflection uses a type in poem_grpc.service.
- The types involved
poem_grpc.reflection.ReflectionServices→poem_grpc.service.Service
- Direction
- poem_grpc.reflection uses poem_grpc.service, so a change to poem_grpc.service can break poem_grpc.reflection, while a change to poem_grpc.reflection can't break poem_grpc.service.
- Position
- Below the diagonal: poem_grpc.reflection uses a module listed above it, which is the healthy direction.
27→3 poem_grpc.server uses poem_grpc.metadata✕
- Connections
- 1 pair of types, where a type in poem_grpc.server uses a type in poem_grpc.metadata.
- The types involved
poem_grpc.server.server$module→poem_grpc.metadata.Metadata
- Direction
- poem_grpc.server uses poem_grpc.metadata, so a change to poem_grpc.metadata can break poem_grpc.server, while a change to poem_grpc.server can't break poem_grpc.metadata.
- Position
- Below the diagonal: poem_grpc.server uses a module listed above it, which is the healthy direction.
27→5 poem_grpc.server uses poem.response✕
- Connections
- 2 pairs of types, where a type in poem_grpc.server uses a type in poem.response.
- The types involved
poem_grpc.server.GrpcServer→poem.response.Responsepoem_grpc.server.server$module→poem.response.Response
- Direction
- poem_grpc.server uses poem.response, so a change to poem.response can break poem_grpc.server, while a change to poem_grpc.server can't break poem.response.
- Position
- Below the diagonal: poem_grpc.server uses a module listed above it, which is the healthy direction.
27→14 poem_grpc.server uses poem.request✕
- Connections
- 2 pairs of types, where a type in poem_grpc.server uses a type in poem.request.
- The types involved
poem_grpc.server.GrpcServer→poem.request.Requestpoem_grpc.server.server$module→poem.request.Request
- Direction
- poem_grpc.server uses poem.request, so a change to poem.request can break poem_grpc.server, while a change to poem_grpc.server can't break poem.request.
- Position
- Below the diagonal: poem_grpc.server uses a module listed above it, which is the healthy direction.
27→15 poem_grpc.server uses poem.body✕
- Connections
- 1 pair of types, where a type in poem_grpc.server uses a type in poem.body.
- The types involved
poem_grpc.server.server$module→poem.body.Body
- Direction
- poem_grpc.server uses poem.body, so a change to poem.body can break poem_grpc.server, while a change to poem_grpc.server can't break poem.body.
- Position
- Below the diagonal: poem_grpc.server uses a module listed above it, which is the healthy direction.
28→5 poem_mcpserver.streamable_http uses poem.response✕
- Connections
- 1 pair of types, where a type in poem_mcpserver.streamable_http uses a type in poem.response.
- The types involved
poem_mcpserver.streamable_http.streamable_http$module→poem.response.Response
- Direction
- poem_mcpserver.streamable_http uses poem.response, so a change to poem.response can break poem_mcpserver.streamable_http, while a change to poem_mcpserver.streamable_http can't break poem.response.
- Position
- Below the diagonal: poem_mcpserver.streamable_http uses a module listed above it, which is the healthy direction.
28→14 poem_mcpserver.streamable_http uses poem.request✕
- Connections
- 2 pairs of types, where a type in poem_mcpserver.streamable_http uses a type in poem.request.
- The types involved
poem_mcpserver.streamable_http.State→poem.request.Requestpoem_mcpserver.streamable_http.streamable_http$module→poem.request.Request
- Direction
- poem_mcpserver.streamable_http uses poem.request, so a change to poem.request can break poem_mcpserver.streamable_http, while a change to poem_mcpserver.streamable_http can't break poem.request.
- Position
- Below the diagonal: poem_mcpserver.streamable_http uses a module listed above it, which is the healthy direction.
28→18 poem_mcpserver.streamable_http uses poem.web.data✕
- Connections
- 1 pair of types, where a type in poem_mcpserver.streamable_http uses a type in poem.web.data.
- The types involved
poem_mcpserver.streamable_http.streamable_http$module→poem.web.data.Data
- Direction
- poem_mcpserver.streamable_http uses poem.web.data, so a change to poem.web.data can break poem_mcpserver.streamable_http, while a change to poem_mcpserver.streamable_http can't break poem.web.data.
- Position
- Below the diagonal: poem_mcpserver.streamable_http uses a module listed above it, which is the healthy direction.
28→39 poem_mcpserver.streamable_http uses poem_mcpserver.server part of a loop✕
- Connections
- 2 pairs of types, where a type in poem_mcpserver.streamable_http uses a type in poem_mcpserver.server.
- The types involved
poem_mcpserver.streamable_http.Session→poem_mcpserver.server.McpServerpoem_mcpserver.streamable_http.streamable_http$module→poem_mcpserver.server.McpServer
- Direction
- poem_mcpserver.streamable_http uses poem_mcpserver.server, so a change to poem_mcpserver.server can break poem_mcpserver.streamable_http, while a change to poem_mcpserver.streamable_http can't break poem_mcpserver.server.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→6 poem_openapi.auth uses poem_openapi.registry✕
- Connections
- 1 pair of types, where a type in poem_openapi.auth uses a type in poem_openapi.registry.
- The types involved
poem_openapi.auth.ApiKeyAuthorization→poem_openapi.registry.MetaParamIn
- Direction
- poem_openapi.auth uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.auth, while a change to poem_openapi.auth can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.auth uses a module listed above it, which is the healthy direction.
29→14 poem_openapi.auth uses poem.request✕
- Connections
- 3 pairs of types, where a type in poem_openapi.auth uses a type in poem.request.
- The types involved
poem_openapi.auth.ApiKeyAuthorization→poem.request.Requestpoem_openapi.auth.BasicAuthorization→poem.request.Requestpoem_openapi.auth.BearerAuthorization→poem.request.Request
- Direction
- poem_openapi.auth uses poem.request, so a change to poem.request can break poem_openapi.auth, while a change to poem_openapi.auth can't break poem.request.
- Position
- Below the diagonal: poem_openapi.auth uses a module listed above it, which is the healthy direction.
29→21 poem_openapi.auth uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem_openapi.auth uses a type in poem_openapi.base.
- The types involved
poem_openapi.auth.ApiKeyAuthorization→poem_openapi.base.UrlQuery
- Direction
- poem_openapi.auth uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi.auth, while a change to poem_openapi.auth can't break poem_openapi.base.
- Position
- Below the diagonal: poem_openapi.auth uses a module listed above it, which is the healthy direction.
30→5 poem_openapi.payload.base64_payload uses poem.response✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.base64_payload uses a type in poem.response.
- The types involved
poem_openapi.payload.base64_payload.Base64→poem.response.Response
- Direction
- poem_openapi.payload.base64_payload uses poem.response, so a change to poem.response can break poem_openapi.payload.base64_payload, while a change to poem_openapi.payload.base64_payload can't break poem.response.
- Position
- Below the diagonal: poem_openapi.payload.base64_payload uses a module listed above it, which is the healthy direction.
30→6 poem_openapi.payload.base64_payload uses poem_openapi.registry✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload.base64_payload uses a type in poem_openapi.registry.
- The types involved
poem_openapi.payload.base64_payload.Base64→poem_openapi.registry.MetaResponsespoem_openapi.payload.base64_payload.Base64→poem_openapi.registry.MetaSchemaRefpoem_openapi.payload.base64_payload.Base64→poem_openapi.registry.Registry
- Direction
- poem_openapi.payload.base64_payload uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.payload.base64_payload, while a change to poem_openapi.payload.base64_payload can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.payload.base64_payload uses a module listed above it, which is the healthy direction.
30→7 poem_openapi.payload.base64_payload uses poem.web✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload.base64_payload uses a type in poem.web.
- The types involved
poem_openapi.payload.base64_payload.Base64→poem.web.IntoResponsepoem_openapi.payload.base64_payload.Base64→poem.web.RequestBodypoem_openapi.payload.base64_payload.base64_payload$module→poem.web.RequestBody
- Direction
- poem_openapi.payload.base64_payload uses poem.web, so a change to poem.web can break poem_openapi.payload.base64_payload, while a change to poem_openapi.payload.base64_payload can't break poem.web.
- Position
- Below the diagonal: poem_openapi.payload.base64_payload uses a module listed above it, which is the healthy direction.
30→14 poem_openapi.payload.base64_payload uses poem.request✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.base64_payload uses a type in poem.request.
- The types involved
poem_openapi.payload.base64_payload.Base64→poem.request.Request
- Direction
- poem_openapi.payload.base64_payload uses poem.request, so a change to poem.request can break poem_openapi.payload.base64_payload, while a change to poem_openapi.payload.base64_payload can't break poem.request.
- Position
- Below the diagonal: poem_openapi.payload.base64_payload uses a module listed above it, which is the healthy direction.
30→21 poem_openapi.payload.base64_payload uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.base64_payload uses a type in poem_openapi.base.
- The types involved
poem_openapi.payload.base64_payload.Base64→poem_openapi.base.ApiResponse
- Direction
- poem_openapi.payload.base64_payload uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi.payload.base64_payload, while a change to poem_openapi.payload.base64_payload can't break poem_openapi.base.
- Position
- Below the diagonal: poem_openapi.payload.base64_payload uses a module listed above it, which is the healthy direction.
30→22 poem_openapi.payload.base64_payload uses poem_openapi.payload✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.base64_payload uses a type in poem_openapi.payload.
- The types involved
poem_openapi.payload.base64_payload.Base64→poem_openapi.payload.ParsePayloadpoem_openapi.payload.base64_payload.Base64→poem_openapi.payload.Payload
- Direction
- poem_openapi.payload.base64_payload uses poem_openapi.payload, so a change to poem_openapi.payload can break poem_openapi.payload.base64_payload, while a change to poem_openapi.payload.base64_payload can't break poem_openapi.payload.
- Position
- Below the diagonal: poem_openapi.payload.base64_payload uses a module listed above it, which is the healthy direction.
31→5 poem_openapi.payload.binary uses poem.response✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.binary uses a type in poem.response.
- The types involved
poem_openapi.payload.binary.Binary→poem.response.Response
- Direction
- poem_openapi.payload.binary uses poem.response, so a change to poem.response can break poem_openapi.payload.binary, while a change to poem_openapi.payload.binary can't break poem.response.
- Position
- Below the diagonal: poem_openapi.payload.binary uses a module listed above it, which is the healthy direction.
31→6 poem_openapi.payload.binary uses poem_openapi.registry✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload.binary uses a type in poem_openapi.registry.
- The types involved
poem_openapi.payload.binary.Binary→poem_openapi.registry.MetaResponsespoem_openapi.payload.binary.Binary→poem_openapi.registry.MetaSchemaRefpoem_openapi.payload.binary.Binary→poem_openapi.registry.Registry
- Direction
- poem_openapi.payload.binary uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.payload.binary, while a change to poem_openapi.payload.binary can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.payload.binary uses a module listed above it, which is the healthy direction.
31→7 poem_openapi.payload.binary uses poem.web✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.binary uses a type in poem.web.
- The types involved
poem_openapi.payload.binary.Binary→poem.web.IntoResponsepoem_openapi.payload.binary.Binary→poem.web.RequestBody
- Direction
- poem_openapi.payload.binary uses poem.web, so a change to poem.web can break poem_openapi.payload.binary, while a change to poem_openapi.payload.binary can't break poem.web.
- Position
- Below the diagonal: poem_openapi.payload.binary uses a module listed above it, which is the healthy direction.
31→14 poem_openapi.payload.binary uses poem.request✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.binary uses a type in poem.request.
- The types involved
poem_openapi.payload.binary.Binary→poem.request.Request
- Direction
- poem_openapi.payload.binary uses poem.request, so a change to poem.request can break poem_openapi.payload.binary, while a change to poem_openapi.payload.binary can't break poem.request.
- Position
- Below the diagonal: poem_openapi.payload.binary uses a module listed above it, which is the healthy direction.
31→21 poem_openapi.payload.binary uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.binary uses a type in poem_openapi.base.
- The types involved
poem_openapi.payload.binary.Binary→poem_openapi.base.ApiResponse
- Direction
- poem_openapi.payload.binary uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi.payload.binary, while a change to poem_openapi.payload.binary can't break poem_openapi.base.
- Position
- Below the diagonal: poem_openapi.payload.binary uses a module listed above it, which is the healthy direction.
31→22 poem_openapi.payload.binary uses poem_openapi.payload✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.binary uses a type in poem_openapi.payload.
- The types involved
poem_openapi.payload.binary.Binary→poem_openapi.payload.ParsePayloadpoem_openapi.payload.binary.Binary→poem_openapi.payload.Payload
- Direction
- poem_openapi.payload.binary uses poem_openapi.payload, so a change to poem_openapi.payload can break poem_openapi.payload.binary, while a change to poem_openapi.payload.binary can't break poem_openapi.payload.
- Position
- Below the diagonal: poem_openapi.payload.binary uses a module listed above it, which is the healthy direction.
32→5 poem_openapi.payload.html uses poem.response✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.html uses a type in poem.response.
- The types involved
poem_openapi.payload.html.Html→poem.response.Response
- Direction
- poem_openapi.payload.html uses poem.response, so a change to poem.response can break poem_openapi.payload.html, while a change to poem_openapi.payload.html can't break poem.response.
- Position
- Below the diagonal: poem_openapi.payload.html uses a module listed above it, which is the healthy direction.
32→6 poem_openapi.payload.html uses poem_openapi.registry✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload.html uses a type in poem_openapi.registry.
- The types involved
poem_openapi.payload.html.Html→poem_openapi.registry.MetaResponsespoem_openapi.payload.html.Html→poem_openapi.registry.MetaSchemaRefpoem_openapi.payload.html.Html→poem_openapi.registry.Registry
- Direction
- poem_openapi.payload.html uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.payload.html, while a change to poem_openapi.payload.html can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.payload.html uses a module listed above it, which is the healthy direction.
32→7 poem_openapi.payload.html uses poem.web✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.html uses a type in poem.web.
- The types involved
poem_openapi.payload.html.Html→poem.web.IntoResponsepoem_openapi.payload.html.Html→poem.web.RequestBody
- Direction
- poem_openapi.payload.html uses poem.web, so a change to poem.web can break poem_openapi.payload.html, while a change to poem_openapi.payload.html can't break poem.web.
- Position
- Below the diagonal: poem_openapi.payload.html uses a module listed above it, which is the healthy direction.
32→14 poem_openapi.payload.html uses poem.request✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.html uses a type in poem.request.
- The types involved
poem_openapi.payload.html.Html→poem.request.Request
- Direction
- poem_openapi.payload.html uses poem.request, so a change to poem.request can break poem_openapi.payload.html, while a change to poem_openapi.payload.html can't break poem.request.
- Position
- Below the diagonal: poem_openapi.payload.html uses a module listed above it, which is the healthy direction.
32→21 poem_openapi.payload.html uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.html uses a type in poem_openapi.base.
- The types involved
poem_openapi.payload.html.Html→poem_openapi.base.ApiResponse
- Direction
- poem_openapi.payload.html uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi.payload.html, while a change to poem_openapi.payload.html can't break poem_openapi.base.
- Position
- Below the diagonal: poem_openapi.payload.html uses a module listed above it, which is the healthy direction.
32→22 poem_openapi.payload.html uses poem_openapi.payload✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.html uses a type in poem_openapi.payload.
- The types involved
poem_openapi.payload.html.Html→poem_openapi.payload.ParsePayloadpoem_openapi.payload.html.Html→poem_openapi.payload.Payload
- Direction
- poem_openapi.payload.html uses poem_openapi.payload, so a change to poem_openapi.payload can break poem_openapi.payload.html, while a change to poem_openapi.payload.html can't break poem_openapi.payload.
- Position
- Below the diagonal: poem_openapi.payload.html uses a module listed above it, which is the healthy direction.
33→5 poem_openapi.payload.json uses poem.response✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.json uses a type in poem.response.
- The types involved
poem_openapi.payload.json.Json→poem.response.Response
- Direction
- poem_openapi.payload.json uses poem.response, so a change to poem.response can break poem_openapi.payload.json, while a change to poem_openapi.payload.json can't break poem.response.
- Position
- Below the diagonal: poem_openapi.payload.json uses a module listed above it, which is the healthy direction.
33→6 poem_openapi.payload.json uses poem_openapi.registry✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload.json uses a type in poem_openapi.registry.
- The types involved
poem_openapi.payload.json.Json→poem_openapi.registry.MetaResponsespoem_openapi.payload.json.Json→poem_openapi.registry.MetaSchemaRefpoem_openapi.payload.json.Json→poem_openapi.registry.Registry
- Direction
- poem_openapi.payload.json uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.payload.json, while a change to poem_openapi.payload.json can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.payload.json uses a module listed above it, which is the healthy direction.
33→7 poem_openapi.payload.json uses poem.web✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.json uses a type in poem.web.
- The types involved
poem_openapi.payload.json.Json→poem.web.IntoResponsepoem_openapi.payload.json.Json→poem.web.RequestBody
- Direction
- poem_openapi.payload.json uses poem.web, so a change to poem.web can break poem_openapi.payload.json, while a change to poem_openapi.payload.json can't break poem.web.
- Position
- Below the diagonal: poem_openapi.payload.json uses a module listed above it, which is the healthy direction.
33→8 poem_openapi.payload.json uses poem_openapi.types✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload.json uses a type in poem_openapi.types.
- The types involved
poem_openapi.payload.json.Json→poem_openapi.types.ParseFromJSONpoem_openapi.payload.json.Json→poem_openapi.types.ToJSONpoem_openapi.payload.json.Json→poem_openapi.types.Type
- Direction
- poem_openapi.payload.json uses poem_openapi.types, so a change to poem_openapi.types can break poem_openapi.payload.json, while a change to poem_openapi.payload.json can't break poem_openapi.types.
- Position
- Below the diagonal: poem_openapi.payload.json uses a module listed above it, which is the healthy direction.
33→14 poem_openapi.payload.json uses poem.request✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.json uses a type in poem.request.
- The types involved
poem_openapi.payload.json.Json→poem.request.Request
- Direction
- poem_openapi.payload.json uses poem.request, so a change to poem.request can break poem_openapi.payload.json, while a change to poem_openapi.payload.json can't break poem.request.
- Position
- Below the diagonal: poem_openapi.payload.json uses a module listed above it, which is the healthy direction.
33→21 poem_openapi.payload.json uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.json uses a type in poem_openapi.base.
- The types involved
poem_openapi.payload.json.Json→poem_openapi.base.ApiResponse
- Direction
- poem_openapi.payload.json uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi.payload.json, while a change to poem_openapi.payload.json can't break poem_openapi.base.
- Position
- Below the diagonal: poem_openapi.payload.json uses a module listed above it, which is the healthy direction.
33→22 poem_openapi.payload.json uses poem_openapi.payload✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.json uses a type in poem_openapi.payload.
- The types involved
poem_openapi.payload.json.Json→poem_openapi.payload.ParsePayloadpoem_openapi.payload.json.Json→poem_openapi.payload.Payload
- Direction
- poem_openapi.payload.json uses poem_openapi.payload, so a change to poem_openapi.payload can break poem_openapi.payload.json, while a change to poem_openapi.payload.json can't break poem_openapi.payload.
- Position
- Below the diagonal: poem_openapi.payload.json uses a module listed above it, which is the healthy direction.
34→5 poem_openapi.payload.plain_text uses poem.response✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.plain_text uses a type in poem.response.
- The types involved
poem_openapi.payload.plain_text.PlainText→poem.response.Response
- Direction
- poem_openapi.payload.plain_text uses poem.response, so a change to poem.response can break poem_openapi.payload.plain_text, while a change to poem_openapi.payload.plain_text can't break poem.response.
- Position
- Below the diagonal: poem_openapi.payload.plain_text uses a module listed above it, which is the healthy direction.
34→6 poem_openapi.payload.plain_text uses poem_openapi.registry✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload.plain_text uses a type in poem_openapi.registry.
- The types involved
poem_openapi.payload.plain_text.PlainText→poem_openapi.registry.MetaResponsespoem_openapi.payload.plain_text.PlainText→poem_openapi.registry.MetaSchemaRefpoem_openapi.payload.plain_text.PlainText→poem_openapi.registry.Registry
- Direction
- poem_openapi.payload.plain_text uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.payload.plain_text, while a change to poem_openapi.payload.plain_text can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.payload.plain_text uses a module listed above it, which is the healthy direction.
34→7 poem_openapi.payload.plain_text uses poem.web✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.plain_text uses a type in poem.web.
- The types involved
poem_openapi.payload.plain_text.PlainText→poem.web.IntoResponsepoem_openapi.payload.plain_text.PlainText→poem.web.RequestBody
- Direction
- poem_openapi.payload.plain_text uses poem.web, so a change to poem.web can break poem_openapi.payload.plain_text, while a change to poem_openapi.payload.plain_text can't break poem.web.
- Position
- Below the diagonal: poem_openapi.payload.plain_text uses a module listed above it, which is the healthy direction.
34→14 poem_openapi.payload.plain_text uses poem.request✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.plain_text uses a type in poem.request.
- The types involved
poem_openapi.payload.plain_text.PlainText→poem.request.Request
- Direction
- poem_openapi.payload.plain_text uses poem.request, so a change to poem.request can break poem_openapi.payload.plain_text, while a change to poem_openapi.payload.plain_text can't break poem.request.
- Position
- Below the diagonal: poem_openapi.payload.plain_text uses a module listed above it, which is the healthy direction.
34→21 poem_openapi.payload.plain_text uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.plain_text uses a type in poem_openapi.base.
- The types involved
poem_openapi.payload.plain_text.PlainText→poem_openapi.base.ApiResponse
- Direction
- poem_openapi.payload.plain_text uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi.payload.plain_text, while a change to poem_openapi.payload.plain_text can't break poem_openapi.base.
- Position
- Below the diagonal: poem_openapi.payload.plain_text uses a module listed above it, which is the healthy direction.
34→22 poem_openapi.payload.plain_text uses poem_openapi.payload✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.plain_text uses a type in poem_openapi.payload.
- The types involved
poem_openapi.payload.plain_text.PlainText→poem_openapi.payload.ParsePayloadpoem_openapi.payload.plain_text.PlainText→poem_openapi.payload.Payload
- Direction
- poem_openapi.payload.plain_text uses poem_openapi.payload, so a change to poem_openapi.payload can break poem_openapi.payload.plain_text, while a change to poem_openapi.payload.plain_text can't break poem_openapi.payload.
- Position
- Below the diagonal: poem_openapi.payload.plain_text uses a module listed above it, which is the healthy direction.
35→5 poem_openapi.payload.xml uses poem.response✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.xml uses a type in poem.response.
- The types involved
poem_openapi.payload.xml.Xml→poem.response.Response
- Direction
- poem_openapi.payload.xml uses poem.response, so a change to poem.response can break poem_openapi.payload.xml, while a change to poem_openapi.payload.xml can't break poem.response.
- Position
- Below the diagonal: poem_openapi.payload.xml uses a module listed above it, which is the healthy direction.
35→6 poem_openapi.payload.xml uses poem_openapi.registry✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload.xml uses a type in poem_openapi.registry.
- The types involved
poem_openapi.payload.xml.Xml→poem_openapi.registry.MetaResponsespoem_openapi.payload.xml.Xml→poem_openapi.registry.MetaSchemaRefpoem_openapi.payload.xml.Xml→poem_openapi.registry.Registry
- Direction
- poem_openapi.payload.xml uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.payload.xml, while a change to poem_openapi.payload.xml can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.payload.xml uses a module listed above it, which is the healthy direction.
35→7 poem_openapi.payload.xml uses poem.web✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.xml uses a type in poem.web.
- The types involved
poem_openapi.payload.xml.Xml→poem.web.IntoResponsepoem_openapi.payload.xml.Xml→poem.web.RequestBody
- Direction
- poem_openapi.payload.xml uses poem.web, so a change to poem.web can break poem_openapi.payload.xml, while a change to poem_openapi.payload.xml can't break poem.web.
- Position
- Below the diagonal: poem_openapi.payload.xml uses a module listed above it, which is the healthy direction.
35→14 poem_openapi.payload.xml uses poem.request✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.xml uses a type in poem.request.
- The types involved
poem_openapi.payload.xml.Xml→poem.request.Request
- Direction
- poem_openapi.payload.xml uses poem.request, so a change to poem.request can break poem_openapi.payload.xml, while a change to poem_openapi.payload.xml can't break poem.request.
- Position
- Below the diagonal: poem_openapi.payload.xml uses a module listed above it, which is the healthy direction.
35→21 poem_openapi.payload.xml uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.xml uses a type in poem_openapi.base.
- The types involved
poem_openapi.payload.xml.Xml→poem_openapi.base.ApiResponse
- Direction
- poem_openapi.payload.xml uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi.payload.xml, while a change to poem_openapi.payload.xml can't break poem_openapi.base.
- Position
- Below the diagonal: poem_openapi.payload.xml uses a module listed above it, which is the healthy direction.
35→22 poem_openapi.payload.xml uses poem_openapi.payload✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.xml uses a type in poem_openapi.payload.
- The types involved
poem_openapi.payload.xml.Xml→poem_openapi.payload.ParsePayloadpoem_openapi.payload.xml.Xml→poem_openapi.payload.Payload
- Direction
- poem_openapi.payload.xml uses poem_openapi.payload, so a change to poem_openapi.payload can break poem_openapi.payload.xml, while a change to poem_openapi.payload.xml can't break poem_openapi.payload.
- Position
- Below the diagonal: poem_openapi.payload.xml uses a module listed above it, which is the healthy direction.
36→5 poem_openapi.payload.yaml uses poem.response✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.yaml uses a type in poem.response.
- The types involved
poem_openapi.payload.yaml.Yaml→poem.response.Response
- Direction
- poem_openapi.payload.yaml uses poem.response, so a change to poem.response can break poem_openapi.payload.yaml, while a change to poem_openapi.payload.yaml can't break poem.response.
- Position
- Below the diagonal: poem_openapi.payload.yaml uses a module listed above it, which is the healthy direction.
36→6 poem_openapi.payload.yaml uses poem_openapi.registry✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload.yaml uses a type in poem_openapi.registry.
- The types involved
poem_openapi.payload.yaml.Yaml→poem_openapi.registry.MetaResponsespoem_openapi.payload.yaml.Yaml→poem_openapi.registry.MetaSchemaRefpoem_openapi.payload.yaml.Yaml→poem_openapi.registry.Registry
- Direction
- poem_openapi.payload.yaml uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.payload.yaml, while a change to poem_openapi.payload.yaml can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.payload.yaml uses a module listed above it, which is the healthy direction.
36→7 poem_openapi.payload.yaml uses poem.web✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.yaml uses a type in poem.web.
- The types involved
poem_openapi.payload.yaml.Yaml→poem.web.IntoResponsepoem_openapi.payload.yaml.Yaml→poem.web.RequestBody
- Direction
- poem_openapi.payload.yaml uses poem.web, so a change to poem.web can break poem_openapi.payload.yaml, while a change to poem_openapi.payload.yaml can't break poem.web.
- Position
- Below the diagonal: poem_openapi.payload.yaml uses a module listed above it, which is the healthy direction.
36→14 poem_openapi.payload.yaml uses poem.request✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.yaml uses a type in poem.request.
- The types involved
poem_openapi.payload.yaml.Yaml→poem.request.Request
- Direction
- poem_openapi.payload.yaml uses poem.request, so a change to poem.request can break poem_openapi.payload.yaml, while a change to poem_openapi.payload.yaml can't break poem.request.
- Position
- Below the diagonal: poem_openapi.payload.yaml uses a module listed above it, which is the healthy direction.
36→21 poem_openapi.payload.yaml uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.yaml uses a type in poem_openapi.base.
- The types involved
poem_openapi.payload.yaml.Yaml→poem_openapi.base.ApiResponse
- Direction
- poem_openapi.payload.yaml uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi.payload.yaml, while a change to poem_openapi.payload.yaml can't break poem_openapi.base.
- Position
- Below the diagonal: poem_openapi.payload.yaml uses a module listed above it, which is the healthy direction.
36→22 poem_openapi.payload.yaml uses poem_openapi.payload✕
- Connections
- 2 pairs of types, where a type in poem_openapi.payload.yaml uses a type in poem_openapi.payload.
- The types involved
poem_openapi.payload.yaml.Yaml→poem_openapi.payload.ParsePayloadpoem_openapi.payload.yaml.Yaml→poem_openapi.payload.Payload
- Direction
- poem_openapi.payload.yaml uses poem_openapi.payload, so a change to poem_openapi.payload can break poem_openapi.payload.yaml, while a change to poem_openapi.payload.yaml can't break poem_openapi.payload.
- Position
- Below the diagonal: poem_openapi.payload.yaml uses a module listed above it, which is the healthy direction.
37→4 poem_openapi_derive.api uses poem_openapi_derive.common_args✕
- Connections
- 4 pairs of types, where a type in poem_openapi_derive.api uses a type in poem_openapi_derive.common_args.
- The types involved
poem_openapi_derive.api.APIOperation→poem_openapi_derive.common_args.CodeSamplepoem_openapi_derive.api.APIOperation→poem_openapi_derive.common_args.ExternalDocumentpoem_openapi_derive.api.APIOperationParam→poem_openapi_derive.common_args.DefaultValuepoem_openapi_derive.api.APIOperationParam→poem_openapi_derive.common_args.ExampleValue
- Direction
- poem_openapi_derive.api uses poem_openapi_derive.common_args, so a change to poem_openapi_derive.common_args can break poem_openapi_derive.api, while a change to poem_openapi_derive.api can't break poem_openapi_derive.common_args.
- Position
- Below the diagonal: poem_openapi_derive.api uses a module listed above it, which is the healthy direction.
37→8 poem_openapi_derive.api uses poem_openapi.types✕
- Connections
- 1 pair of types, where a type in poem_openapi_derive.api uses a type in poem_openapi.types.
- The types involved
poem_openapi_derive.api.APIOperation→poem_openapi.types.Type
- Direction
- poem_openapi_derive.api uses poem_openapi.types, so a change to poem_openapi.types can break poem_openapi_derive.api, while a change to poem_openapi_derive.api can't break poem_openapi.types.
- Position
- Below the diagonal: poem_openapi_derive.api uses a module listed above it, which is the healthy direction.
37→11 poem_openapi_derive.api uses poem_lambda✕
- Connections
- 1 pair of types, where a type in poem_openapi_derive.api uses a type in poem_lambda.
- The types involved
poem_openapi_derive.api.api$module→poem_lambda.Context
- Direction
- poem_openapi_derive.api uses poem_lambda, so a change to poem_lambda can break poem_openapi_derive.api, while a change to poem_openapi_derive.api can't break poem_lambda.
- Position
- Below the diagonal: poem_openapi_derive.api uses a module listed above it, which is the healthy direction.
37→19 poem_openapi_derive.api uses poem.web.path✕
- Connections
- 3 pairs of types, where a type in poem_openapi_derive.api uses a type in poem.web.path.
- The types involved
poem_openapi_derive.api.APIArgs→poem.web.path.Pathpoem_openapi_derive.api.APIOperation→poem.web.path.Pathpoem_openapi_derive.api.APIOperationParam→poem.web.path.Path
- Direction
- poem_openapi_derive.api uses poem.web.path, so a change to poem.web.path can break poem_openapi_derive.api, while a change to poem_openapi_derive.api can't break poem.web.path.
- Position
- Below the diagonal: poem_openapi_derive.api uses a module listed above it, which is the healthy direction.
37→21 poem_openapi_derive.api uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem_openapi_derive.api uses a type in poem_openapi.base.
- The types involved
poem_openapi_derive.api.APIOperationParam→poem_openapi.base.ParameterStyle
- Direction
- poem_openapi_derive.api uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi_derive.api, while a change to poem_openapi_derive.api can't break poem_openapi.base.
- Position
- Below the diagonal: poem_openapi_derive.api uses a module listed above it, which is the healthy direction.
38→2 poem.middleware.tower_compat uses poem.middleware✕
- Connections
- 1 pair of types, where a type in poem.middleware.tower_compat uses a type in poem.middleware.
- The types involved
poem.middleware.tower_compat.TowerCompatMiddleware→poem.middleware.Middleware
- Direction
- poem.middleware.tower_compat uses poem.middleware, so a change to poem.middleware can break poem.middleware.tower_compat, while a change to poem.middleware.tower_compat can't break poem.middleware.
- Position
- Below the diagonal: poem.middleware.tower_compat uses a module listed above it, which is the healthy direction.
38→11 poem.middleware.tower_compat uses poem_lambda✕
- Connections
- 1 pair of types, where a type in poem.middleware.tower_compat uses a type in poem_lambda.
- The types involved
poem.middleware.tower_compat.EndpointToTowerService→poem_lambda.Context
- Direction
- poem.middleware.tower_compat uses poem_lambda, so a change to poem_lambda can break poem.middleware.tower_compat, while a change to poem.middleware.tower_compat can't break poem_lambda.
- Position
- Below the diagonal: poem.middleware.tower_compat uses a module listed above it, which is the healthy direction.
38→14 poem.middleware.tower_compat uses poem.request✕
- Connections
- 2 pairs of types, where a type in poem.middleware.tower_compat uses a type in poem.request.
- The types involved
poem.middleware.tower_compat.EndpointToTowerService→poem.request.Requestpoem.middleware.tower_compat.TowerServiceToEndpoint→poem.request.Request
- Direction
- poem.middleware.tower_compat uses poem.request, so a change to poem.request can break poem.middleware.tower_compat, while a change to poem.middleware.tower_compat can't break poem.request.
- Position
- Below the diagonal: poem.middleware.tower_compat uses a module listed above it, which is the healthy direction.
38→16 poem.middleware.tower_compat uses poem.endpoint.endpoint✕
- Connections
- 1 pair of types, where a type in poem.middleware.tower_compat uses a type in poem.endpoint.endpoint.
- The types involved
poem.middleware.tower_compat.TowerServiceToEndpoint→poem.endpoint.endpoint.Endpoint
- Direction
- poem.middleware.tower_compat uses poem.endpoint.endpoint, so a change to poem.endpoint.endpoint can break poem.middleware.tower_compat, while a change to poem.middleware.tower_compat can't break poem.endpoint.endpoint.
- Position
- Below the diagonal: poem.middleware.tower_compat uses a module listed above it, which is the healthy direction.
38→20 poem.middleware.tower_compat uses poem_grpc.service✕
- Connections
- 1 pair of types, where a type in poem.middleware.tower_compat uses a type in poem_grpc.service.
- The types involved
poem.middleware.tower_compat.EndpointToTowerService→poem_grpc.service.Service
- Direction
- poem.middleware.tower_compat uses poem_grpc.service, so a change to poem_grpc.service can break poem.middleware.tower_compat, while a change to poem.middleware.tower_compat can't break poem_grpc.service.
- Position
- Below the diagonal: poem.middleware.tower_compat uses a module listed above it, which is the healthy direction.
38→23 poem.middleware.tower_compat uses poem.error✕
- Connections
- 2 pairs of types, where a type in poem.middleware.tower_compat uses a type in poem.error.
- The types involved
poem.middleware.tower_compat.WrappedError→poem.error.Errorpoem.middleware.tower_compat.tower_compat$module→poem.error.Error
- Direction
- poem.middleware.tower_compat uses poem.error, so a change to poem.error can break poem.middleware.tower_compat, while a change to poem.middleware.tower_compat can't break poem.error.
- Position
- Below the diagonal: poem.middleware.tower_compat uses a module listed above it, which is the healthy direction.
39→5 poem_mcpserver.server uses poem.response✕
- Connections
- 1 pair of types, where a type in poem_mcpserver.server uses a type in poem.response.
- The types involved
poem_mcpserver.server.McpServer→poem.response.Response
- Direction
- poem_mcpserver.server uses poem.response, so a change to poem.response can break poem_mcpserver.server, while a change to poem_mcpserver.server can't break poem.response.
- Position
- Below the diagonal: poem_mcpserver.server uses a module listed above it, which is the healthy direction.
39→14 poem_mcpserver.server uses poem.request✕
- Connections
- 1 pair of types, where a type in poem_mcpserver.server uses a type in poem.request.
- The types involved
poem_mcpserver.server.McpServer→poem.request.Request
- Direction
- poem_mcpserver.server uses poem.request, so a change to poem.request can break poem_mcpserver.server, while a change to poem_mcpserver.server can't break poem.request.
- Position
- Below the diagonal: poem_mcpserver.server uses a module listed above it, which is the healthy direction.
39→24 poem_mcpserver.server uses poem.middleware.requestid✕
- Connections
- 1 pair of types, where a type in poem_mcpserver.server uses a type in poem.middleware.requestid.
- The types involved
poem_mcpserver.server.McpServer→poem.middleware.requestid.RequestId
- Direction
- poem_mcpserver.server uses poem.middleware.requestid, so a change to poem.middleware.requestid can break poem_mcpserver.server, while a change to poem_mcpserver.server can't break poem.middleware.requestid.
- Position
- Below the diagonal: poem_mcpserver.server uses a module listed above it, which is the healthy direction.
39→28 poem_mcpserver.server uses poem_mcpserver.streamable_http✕
- Connections
- 1 pair of types, where a type in poem_mcpserver.server uses a type in poem_mcpserver.streamable_http.
- The types involved
poem_mcpserver.server.McpServer→poem_mcpserver.streamable_http.IntoMcpServer
- Direction
- poem_mcpserver.server uses poem_mcpserver.streamable_http, so a change to poem_mcpserver.streamable_http can break poem_mcpserver.server, while a change to poem_mcpserver.server can't break poem_mcpserver.streamable_http.
- Position
- Below the diagonal: poem_mcpserver.server uses a module listed above it, which is the healthy direction.
40→5 poem_openapi.payload.attachment uses poem.response✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.attachment uses a type in poem.response.
- The types involved
poem_openapi.payload.attachment.Attachment→poem.response.Response
- Direction
- poem_openapi.payload.attachment uses poem.response, so a change to poem.response can break poem_openapi.payload.attachment, while a change to poem_openapi.payload.attachment can't break poem.response.
- Position
- Below the diagonal: poem_openapi.payload.attachment uses a module listed above it, which is the healthy direction.
40→6 poem_openapi.payload.attachment uses poem_openapi.registry✕
- Connections
- 3 pairs of types, where a type in poem_openapi.payload.attachment uses a type in poem_openapi.registry.
- The types involved
poem_openapi.payload.attachment.Attachment→poem_openapi.registry.MetaResponsespoem_openapi.payload.attachment.Attachment→poem_openapi.registry.MetaSchemaRefpoem_openapi.payload.attachment.Attachment→poem_openapi.registry.Registry
- Direction
- poem_openapi.payload.attachment uses poem_openapi.registry, so a change to poem_openapi.registry can break poem_openapi.payload.attachment, while a change to poem_openapi.payload.attachment can't break poem_openapi.registry.
- Position
- Below the diagonal: poem_openapi.payload.attachment uses a module listed above it, which is the healthy direction.
40→7 poem_openapi.payload.attachment uses poem.web✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.attachment uses a type in poem.web.
- The types involved
poem_openapi.payload.attachment.Attachment→poem.web.IntoResponse
- Direction
- poem_openapi.payload.attachment uses poem.web, so a change to poem.web can break poem_openapi.payload.attachment, while a change to poem_openapi.payload.attachment can't break poem.web.
- Position
- Below the diagonal: poem_openapi.payload.attachment uses a module listed above it, which is the healthy direction.
40→21 poem_openapi.payload.attachment uses poem_openapi.base✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.attachment uses a type in poem_openapi.base.
- The types involved
poem_openapi.payload.attachment.Attachment→poem_openapi.base.ApiResponse
- Direction
- poem_openapi.payload.attachment uses poem_openapi.base, so a change to poem_openapi.base can break poem_openapi.payload.attachment, while a change to poem_openapi.payload.attachment can't break poem_openapi.base.
- Position
- Below the diagonal: poem_openapi.payload.attachment uses a module listed above it, which is the healthy direction.
40→22 poem_openapi.payload.attachment uses poem_openapi.payload✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.attachment uses a type in poem_openapi.payload.
- The types involved
poem_openapi.payload.attachment.Attachment→poem_openapi.payload.Payload
- Direction
- poem_openapi.payload.attachment uses poem_openapi.payload, so a change to poem_openapi.payload can break poem_openapi.payload.attachment, while a change to poem_openapi.payload.attachment can't break poem_openapi.payload.
- Position
- Below the diagonal: poem_openapi.payload.attachment uses a module listed above it, which is the healthy direction.
40→31 poem_openapi.payload.attachment uses poem_openapi.payload.binary✕
- Connections
- 1 pair of types, where a type in poem_openapi.payload.attachment uses a type in poem_openapi.payload.binary.
- The types involved
poem_openapi.payload.attachment.Attachment→poem_openapi.payload.binary.Binary
- Direction
- poem_openapi.payload.attachment uses poem_openapi.payload.binary, so a change to poem_openapi.payload.binary can break poem_openapi.payload.attachment, while a change to poem_openapi.payload.attachment can't break poem_openapi.payload.binary.
- Position
- Below the diagonal: poem_openapi.payload.attachment uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 20 | High / Critical |
| A07:2025 — Authentication Failures | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Begin by documenting significant design decisions in a dedicated ADR folder to establish architectural clarity, and immediately address the 112 orphaned files, prioritizing mod.rs, response.rs, and request.rs to restore code freshness. Next, enforce accessibility by integrating invariant checks into your existing test suite and gating them in CI, while simultaneously correcting page structure issues such as missing language attributes and landmark elements. Finally, enhance onboarding by adding a clear build and run quick-start section to the root README.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +5.3 pts | Medium | Architecture documentation |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +3.6 pts | Medium | A11y enforcement |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +3.4 pts | Medium | Page structure |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.6 pts | Medium | Documentation (README) |
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. | +1.3 pts | Low | REDACTED Scanning |
| Resolve the 112 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (5), response.rs (4), request.rs (3). | +5.0 pts | High | Knowledge Freshness |
| Resolve the 2 Off-boarding risk finding(s) in Bus Factor. | +0.8 pts | Low | Bus Factor |
| Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. | +0.7 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: 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.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| poem/src/listener/handshake_stream.rs | 6.3 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| poem/src/web/mod.rs | 6.9 | Mixed | Explicit Debt: FixmeComment |
| poem/src/lib.rs | 6.9 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| poem-openapi-derive/src/api.rs | 7.0 | Mixed | Cyclomatic Complexity: poem_openapi_derive::api::generate_operation (cyclomatic 40) |
| poem-openapi-derive/src/response.rs | 7.0 | Mixed | Cyclomatic Complexity: poem_openapi_derive::response::generate (cyclomatic 20) |
| poem-openapi-derive/src/object.rs | 7.0 | Mixed | Cyclomatic Complexity: poem_openapi_derive::object::generate (cyclomatic 34) |
| poem-openapi-derive/src/enum.rs | 7.0 | Mixed | God Classes: FunctionTooLong: poem_openapi_derive::enum::generate |
| poem-openapi-derive/src/multipart.rs | 7.1 | Mixed | God Classes: FunctionTooLong: poem_openapi_derive::multipart::generate |
| poem-grpc/src/client.rs | 7.1 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| poem-grpc/src/server.rs | 7.1 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| poem-openapi/src/registry/mod.rs | 7.1 | Mixed | Cyclomatic Complexity: MetaSchema::merge (cyclomatic 25) |
| poem-openapi-derive/src/security_scheme.rs | 7.1 | Mixed | Cognitive Complexity: poem_openapi_derive::security_scheme::generate (cognitive 24) |
| poem/src/route/internal/radix_tree.rs | 7.2 | Mixed | Cyclomatic Complexity: Node::matches (cyclomatic 16) |
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. 66 of 66 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 66 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, 308 of 330 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 llvm-cov`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), 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`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 131 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — measured, with a gap in what it reached — 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.
- 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. `REDACTED` 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.
- AC6 Visual & motion safety — 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. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
- 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 4 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'sqlx' is imported (poem-openapi/src/types/external/sqlx.rs:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'sqlx' is imported (poem-openapi/src/types/external/sqlx.rs:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'sqlx' is imported (poem-openapi/src/types/external/sqlx.rs:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'sqlx' is imported (poem-openapi/src/types/external/sqlx.rs:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
12 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was poem_openapi_derive::api::generate_operation at 40. A further 3 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 Code::from at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: poem-grpc/src/status.rs (Code::from at 18). 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 12 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with poem_openapi_derive::api::generate_operation (cyclomatic 40), poem_openapi_derive::object::generate (cyclomatic 34), poem_openapi_derive::union::generate (cyclomatic 26). — 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 12 together lifts Cyclomatic Complexity from 8.0 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
26 method(s) exceeded the cognitive complexity threshold of 15; the worst was poem_openapi_derive::object::generate at 75.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with poem_openapi_derive::object::generate (cognitive 75). — Refactoring it lifts Cognitive Complexity from 6.3 to about 6.5/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
15 god class(es) detected.
What to do
- Resolve the 10 FunctionTooLong finding(s) in God Classes — start with api.rs, object.rs, response.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with mod.rs, error.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with request.rs, openapi.rs. — One of this dimension's main actionable groups (2 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
72 duplicated block group(s) detected. A further 5 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 10 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with multipart.rs (2), api.rs, base64_payload.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with server.rs, prompts.rs, multipart.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with object.rs, oauth_scopes.rs, json.rs. — One of this dimension's main actionable groups (4 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
10 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 7 of the 10 (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)
2 of 105 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with handshake_stream.rs, mod.rs. — One of this dimension's main actionable groups (2 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
694 test methods: 394 unit, 300 integration, 0 BDD, 0 e2e. The Rust suite contributes 694 `#[test]` function(s) across 131 file(s) declaring at least one; its unit/integration split is Cargo's own — 29 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.
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. 107 of 124 direct crates were graded against crates.io (0 not published there, 17 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
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
3 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 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 531 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 6 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: poem-openapi-derive/src/api.rs (2×40=80); poem-mcpserver/src/streamable_http.rs (3×18=54); poem-openapi-derive/src/union.rs (2×26=52) Repeated repair below the complexity floor: poem/src/listener/rustls.rs (3 of 4 changes were fixes)
What to do
- Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with api.rs, streamable_http.rs, union.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with rustls.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
15 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is poem-grpc/src/encoding.rs. Counted over 176 of the 294 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
10 deducted task-comment markers across 49327 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 6 TodoComment finding(s) in Explicit Debt — start with lib.rs (3), REDACTED (2), server.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 FixmeComment finding(s) in Explicit Debt — start with mod.rs (3), base.rs. — One of this dimension's main actionable groups (4 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. 20 document(s) read across 1 unit(s).
D26 · Project Cohesion
2 of 11 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
8 finding(s): 0 critical, 8 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 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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)
20 finding(s): 0 critical, 17 high, 3 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `REDACTED` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 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 10 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 (10 issue-level, 0 of them charged here).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
115 of 176 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is poem/src/web/mod.rs. Counted over 176 of the 294 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 112 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (5), response.rs (4), request.rs (3). — One of this dimension's main actionable groups (112 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with endpoint.rs, cors.rs, object.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — poem-openapi/src/ui/stoplight_elements/stoplight-elements.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
C2 · Access Controls
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 69 of 83 project(s) that lack one — worth up to 1.7 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 409/503 types (81%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
- Only 2/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `poem-grpc`, `poem-openapi`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
What to do
- 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
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `https://unpkg.com/@stoplight/elements/web-components.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — poem-openapi/src/ui/stoplight_elements/stoplight-elements.html:8
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection_with_upgrades(` (poem/src/server.rs:499).
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `r` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:2
- `r.error_description||r.error_description||"Unable to get access token"` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1054
- `e.target.classList.contains("array-of-object")?"[{":e.target.classList.contains("array-of-array")?`[[ ${e.target.data…` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:1621
- `l.highlightedCode` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:3788
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — REDACTED:1054, REDACTED:2200
- `.then(…, pj)` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — REDACTED:1054
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn!` at line 120 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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`. — poem/src/listener/acme/listener.rs:120
- `warn!` at line 131 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`. — poem/src/listener/acme/listener.rs:131
What to do
- Interpolated log message defeats structured logging
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Strong | Solid. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 54% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 70% | Adequate — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 69% | Adequate — gated by D28, D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 57% | Adequate | Acceptable, with room to improve. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 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.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'sqlx' (poem-openapi/src/types/external/sqlx.rs:10) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'sqlx' (poem-openapi/src/types/external/sqlx.rs:10) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'sqlx' (poem-openapi/src/types/external/sqlx.rs:10) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 46 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: this repository stores data through 'sqlx' (poem-openapi/src/types/external/sqlx.rs:10) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- D10 Test Quality — ~16799 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- 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; Python, Rust, html 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 .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D32 Data Compliance (PII/GDPR) — 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not 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 (70 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: 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.
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — 28 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
Serious — 167 finding(s)
- FunctionTooLong: poem_openapi_derive::api::generate_operation poem-openapi-derive/src/api.rs:170
- FunctionTooLong: poem_openapi_derive::object::generate poem-openapi-derive/src/object.rs:93
- FunctionTooLong: poem_openapi_derive::response::generate poem-openapi-derive/src/response.rs:64
- FunctionTooLong: poem_openapi_derive::union::generate poem-openapi-derive/src/union.rs:50
- FunctionTooLong: poem_openapi_derive::multipart::generate poem-openapi-derive/src/multipart.rs:48
- FunctionTooLong: poem_openapi_derive::webhook::generate_operation poem-openapi-derive/src/webhook.rs:112
- FunctionTooLong: poem_grpc_build::server::generate poem-grpc-build/src/server.rs:18
- FunctionTooLong: poem_mcpserver::streamable_http::post_handler poem-mcpserver/src/streamable_http.rs:333
- FunctionTooLong: poem_openapi_derive::newtype::generate poem-openapi-derive/src/newtype.rs:50
- FunctionTooLong: poem_openapi_derive::enum::generate poem-openapi-derive/src/enum.rs:47
- Duplicated block (7 lines × 2) poem-openapi-derive/src/api.rs:547
- Duplicated block (7 lines × 2) poem-openapi-derive/src/multipart.rs:50
- Duplicated block (7 lines × 2) poem-openapi-derive/src/multipart.rs:261
- Duplicated block (7 lines × 2) poem-openapi/src/payload/base64_payload.rs:91
- Duplicated block (7 lines × 2) poem-openapi/src/payload/form.rs:35
- Duplicated block (7 lines × 2) poem-openapi/src/payload/json.rs:36
- Duplicated block (7 lines × 2) poem-openapi/src/payload/xml.rs:36
- Duplicated block (7 lines × 2) poem-openapi/src/payload/yaml.rs:36
- Duplicated block (7 lines × 2) poem-openapi-derive/src/security_scheme.rs:369
- Duplicated block (7 lines × 2) poem-openapi-derive/src/enum.rs:53
- poem_openapi_derive::object::generate (cognitive 75) poem-openapi-derive/src/object.rs:93
- poem_openapi_derive::api::generate_operation (cognitive 52) poem-openapi-derive/src/api.rs:170
- poem_openapi_derive::union::generate (cognitive 42) poem-openapi-derive/src/union.rs:50
- poem_openapi_derive::response::generate (cognitive 36) poem-openapi-derive/src/response.rs:64
- poem_openapi_derive::security_scheme::generate (cognitive 24) poem-openapi-derive/src/security_scheme.rs:429
- poem_openapi_derive::response_content::generate (cognitive 18) poem-openapi-derive/src/response_content.rs:35
- poem_openapi_derive::webhook::generate_operation (cognitive 18) poem-openapi-derive/src/webhook.rs:112
- poem_openapi_derive::newtype::generate (cognitive 17) poem-openapi-derive/src/newtype.rs:50
- Hotspot: poem-openapi-derive/src/api.rs poem-openapi-derive/src/api.rs:170
- Hotspot: poem-mcpserver/src/streamable_http.rs poem-mcpserver/src/streamable_http.rs:333
- Hotspot: poem-openapi-derive/src/union.rs poem-openapi-derive/src/union.rs:50
- Hotspot: poem/src/web/static_file.rs poem/src/web/static_file.rs:187
- Hotspot: poem/src/endpoint/static_files.rs poem/src/endpoint/static_files.rs:193
- Hotspot: poem/src/route/internal/radix_tree.rs poem/src/route/internal/radix_tree.rs:378
- TodoComment poem-worker/src/server.rs:22
- TodoComment poem/src/lib.rs:166
- TodoComment poem/src/lib.rs:171
- TodoComment poem/src/lib.rs:179
- TodoComment examples/openapi/todos/src/main.rs:14
- TodoComment examples/openapi/todos/src/main.rs:22
- Duplicated block (10 lines × 2) poem-grpc/src/server.rs:80
- Duplicated block (10 lines × 2) poem-mcpserver-macros/src/prompts.rs:58
- Duplicated block (10 lines × 2) poem-openapi-derive/src/multipart.rs:193
- Duplicated block (10 lines × 2) poem-openapi-derive/src/response.rs:115
- Duplicated block (10 lines × 2) poem/src/web/static_file.rs:137
- Duplicated block (10 lines × 2) poem-openapi/src/ui/openapi_explorer/mod.rs:35
- poem_openapi_derive::api::generate_operation (cyclomatic 40) poem-openapi-derive/src/api.rs:170
- poem_openapi_derive::object::generate (cyclomatic 34) poem-openapi-derive/src/object.rs:93
- poem_openapi_derive::union::generate (cyclomatic 26) poem-openapi-derive/src/union.rs:50
- poem_openapi_derive::response::generate (cyclomatic 20) poem-openapi-derive/src/response.rs:64
- FixmeComment poem-openapi/src/base.rs:265
- FixmeComment poem/src/web/mod.rs:328
- FixmeComment poem/src/web/mod.rs:808
- FixmeComment poem/src/web/mod.rs:816
- Duplicated block (11 lines × 2) poem-openapi-derive/src/object.rs:397
- Duplicated block (11 lines × 2) poem-openapi-derive/src/oauth_scopes.rs:42
- Duplicated block (11 lines × 2) poem/src/web/json.rs:150
- Duplicated block (11 lines × 2) poem/src/listener/acme/client.rs:186
- Duplicated block (6 lines × 2) poem-grpc/src/reflection.rs:210
- Duplicated block (6 lines × 2) poem-openapi-derive/src/response.rs:210
- Duplicated block (6 lines × 2) poem-openapi-derive/src/security_scheme.rs:340
- Duplicated block (6 lines × 2) poem/src/listener/acme/jose.rs:34
- Duplicated block (5 lines × 2) poem-openapi-derive/src/api.rs:425
- Duplicated block (5 lines × 2) poem-openapi-derive/src/enum.rs:145
- Duplicated block (5 lines × 2) poem/src/request.rs:384
- Duplicated block (5 lines × 2) poem-openapi-derive/src/object.rs:420
- Untrusted text written into markup unescaped REDACTED:2
- Untrusted text written into markup unescaped REDACTED:1054
- Untrusted text written into markup unescaped REDACTED:1621
- Untrusted text written into markup unescaped REDACTED:3788
- Members sharing a duplicated core (4 members, 50+ identical tokens) poem-grpc/src/client.rs:235
- Members sharing a duplicated core (4 members, 50+ identical tokens) poem-grpc/src/server.rs:52
- Members sharing a duplicated core (4 members, 50+ identical tokens) poem/src/listener/handshake_stream.rs:41
- Duplicated block (16 lines × 2) poem-grpc/src/client.rs:244
- Duplicated block (16 lines × 2) poem-grpc/src/client.rs:348
- Duplicated block (16 lines × 2) poem-mcpserver-macros/src/utils.rs:17
- Duplicated block (10–11 lines × 2) poem-openapi-derive/src/enum.rs:119
- Duplicated block (10–11 lines × 2) poem-openapi-derive/src/security_scheme.rs:455
- Duplicated block (10–11 lines × 2) poem/src/listener/native_tls.rs:165
- Duplicated block (9 lines × 2) poem-grpc-build/src/client.rs:10
- Duplicated block (9 lines × 2) poem/src/middleware/opentelemetry_metrics.rs:91
- Duplicated block (9 lines × 2) poem-openapi-derive/src/multipart.rs:58
- Duplicated block (5 lines × 3) poem-openapi-derive/src/object.rs:447
- Duplicated block (5 lines × 3) poem-grpc/src/metadata.rs:69
- Duplicated block (5 lines × 3) poem/src/listener/acme/jose.rs:35
- Swallowed exception (empty catch) REDACTED:1054
- Swallowed exception (empty catch) REDACTED:1054
- Swallowed exception (empty catch) REDACTED:2200
- poem_mcpserver_macros::tools::generate (cognitive 32) poem-mcpserver-macros/src/tools.rs:23
- poem_mcpserver_macros::prompts::generate (cognitive 30) poem-mcpserver-macros/src/prompts.rs:23
- poem::route::internal::radix_tree::parse_path_segments (cognitive 26) poem/src/route/internal/radix_tree.rs:39
- poem::listener::acme::listener::issue_cert (cognitive 24) poem/src/listener/acme/listener.rs:254
- REDACTED
- REDACTED
- FileTooLong: registry/mod.rs poem-openapi/src/registry/mod.rs
- FileTooLong: src/error.rs poem/src/error.rs
- TooManyMethods: Request poem/src/request.rs:128
- TooManyMethods: OpenApiService poem-openapi/src/openapi.rs:263
- Duplicated block (17 lines × 2) poem-grpc/src/client.rs:290
- Duplicated block (17 lines × 2) poem-grpc/src/server.rs:171
- Duplicated block (15 lines × 2) poem-grpc/src/server.rs:102
- Duplicated block (15 lines × 2) poem-openapi-derive/src/response.rs:278
- Duplicated block (13 lines × 2) poem-openapi-derive/src/api.rs:388
- Duplicated block (13 lines × 2) poem/src/request.rs:89
- Duplicated block (12 lines × 2) poem-openapi-derive/src/api.rs:237
- Duplicated block (12 lines × 2) poem-openapi-derive/src/oauth_scopes.rs:62
- Duplicated block (9 lines × 3) poem-openapi/src/param/cookie.rs:63
- Duplicated block (9 lines × 3) poem/src/listener/native_tls.rs:163
- Off the main sequence: poem-grpc-build
- Off the main sequence: poem
- Low cohesion: HandshakeStream (LCOM4 4) poem/src/listener/handshake_stream.rs:18
- Low cohesion: BoxIo (LCOM4 4) poem/src/listener/mod.rs:53
- Page without a main landmark poem-openapi/src/ui/stoplight_elements/stoplight-elements.html:2
- Accessibility enforcement below the top rung
- MetaSchema::merge (cyclomatic 25) poem-openapi/src/registry/mod.rs:191
- StaticFileRequest::create_response (cyclomatic 24) poem/src/web/static_file.rs:187
- StaticFilesEndpoint::serve (cyclomatic 19) poem/src/endpoint/static_files.rs:193
- poem_mcpserver::streamable_http::post_handler (cyclomatic 18) poem-mcpserver/src/streamable_http.rs:333
- Node::matches (cyclomatic 16) poem/src/route/internal/radix_tree.rs:378
- poem::route::internal::radix_tree::parse_path_segments (cyclomatic 16) poem/src/route/internal/radix_tree.rs:39
- poem_grpc::encoding::decode_single_response_message (cyclomatic 16) poem-grpc/src/encoding.rs:241
- check-licenses.check (cyclomatic 16) scripts/check-licenses.py:16
- Repeated repair: poem/src/listener/rustls.rs poem/src/listener/rustls.rs:407
- StaticFilesEndpoint::serve (cognitive 39) poem/src/endpoint/static_files.rs:193
- Server::run_with_graceful_shutdown (cognitive 36) poem/src/server.rs:166
- StaticFileRequest::create_response (cognitive 35) poem/src/web/static_file.rs:187
- poem_mcpserver::streamable_http::post_handler (cognitive 35) poem-mcpserver/src/streamable_http.rs:333
- check-licenses.check (cognitive 34) scripts/check-licenses.py:16
- MetaSchema::merge (cognitive 32) poem-openapi/src/registry/mod.rs:191
- poem_grpc::encoding::decode_single_response_message (cognitive 31) poem-grpc/src/encoding.rs:241
- AutoCertListener::into_acceptor (cognitive 29) poem/src/listener/acme/listener.rs:102
- Node::matches (cognitive 27) poem/src/route/internal/radix_tree.rs:378
- NativeTlsAcceptor::accept (cognitive 20) poem/src/listener/native_tls.rs:149
- OpensslTlsAcceptor::accept (cognitive 20) poem/src/listener/openssl_tls.rs:194
- RustlsAcceptor::accept (cognitive 20) poem/src/listener/rustls.rs:407
- CorsEndpoint::check_allow_headers (cognitive 17) poem/src/middleware/cors.rs:322
- Validators::create_validators (cognitive 16) poem-openapi-derive/src/validators.rs:52
- REDACTED
- TooManyFields: MetaSchema poem-openapi/src/registry/mod.rs:49
- REDACTED
- REDACTED
- Near-duplicate member family (4 members, 19 shared lines) poem-grpc-build/src/server.rs:244
- Members sharing a duplicated core (5 members, 50+ identical tokens) poem-openapi-derive/src/enum.rs:47
- Duplicated block (28 lines × 2) poem-grpc/src/server.rs:55
- Duplicated block (23 lines × 2) poem-mcpserver-macros/src/prompts.rs:32
- Duplicated block (22 lines × 2) poem-openapi-derive/src/response.rs:193
- Duplicated block (20 lines × 2) poem-grpc/src/client.rs:255
- Duplicated block (16 lines × 3) poem-mcpserver/src/server.rs:277
- Duplicated block (14 lines × 3) poem-openapi-derive/src/response.rs:216
- Duplicated block (14 lines × 2) poem-openapi/src/param/cookie.rs:65
- Duplicated block (13 lines × 4) poem-grpc-build/src/server.rs:274
- Duplicated block (12 lines × 4) poem/src/listener/handshake_stream.rs:42
- Duplicated block (11–12 lines × 2) poem-openapi/src/registry/mod.rs:265
- Duplicated block (8–11 lines × 4) poem-grpc/src/client.rs:251
- Duplicated block (11 lines × 3) poem-openapi-derive/src/object.rs:433
- Duplicated block (10 lines × 4) poem-grpc/src/server.rs:53
- Duplicated block (7–8 lines × 3) poem-openapi-derive/src/request.rs:41
- Duplicated block (6–8 lines × 4) poem-openapi-derive/src/security_scheme.rs:132
- Duplicated block (8 lines × 2) poem-openapi-derive/src/api.rs:553
- Duplicated block (7 lines × 5) poem-openapi-derive/src/enum.rs:121
- Duplicated block (6–7 lines × 2) poem-openapi-derive/src/multipart.rs:84
- Duplicated block (6 lines × 4) poem-grpc-build/src/server.rs:260
- Duplicated block (6 lines × 3) poem-openapi-derive/src/api.rs:568
- Duplicated block (8 lines × 3) poem-openapi/src/payload/response.rs:81
- Duplicated block (13 lines × 3) poem-openapi-derive/src/enum.rs:60
- Coverage collected but not gated
- Third-party script without Subresource Integrity poem-openapi/src/ui/stoplight_elements/stoplight-elements.html:8
Minor — 135 finding(s)
- Orphaned file poem/src/web/mod.rs:1
- Orphaned file poem/src/web/cookie.rs:1
- Orphaned file poem-openapi-derive/src/response.rs:1
- Orphaned file poem/src/web/path/de.rs:1
- Orphaned file poem-grpc/src/codec/json_codec/i64string_deserializer.rs:1
- Orphaned file poem/src/request.rs:1
- Orphaned file poem-grpc-build/src/config.rs:1
- Orphaned file poem-openapi-derive/src/validators.rs:1
- Orphaned file poem/src/middleware/mod.rs:1
- Orphaned file poem-openapi-derive/src/multipart.rs:1
- Orphaned file poem/src/listener/mod.rs:1
- Orphaned file poem/src/lib.rs:1
- Orphaned file poem/src/response.rs:1
- Orphaned file poem/src/middleware/csrf.rs:1
- Orphaned file poem-grpc/src/codec/json_codec/i64string_serializer.rs:1
- Orphaned file poem/src/listener/openssl_tls.rs:1
- Orphaned file poem/src/i18n/resources.rs:1
- Orphaned file poem/src/route/internal/trie.rs:1
- Orphaned file poem/src/route/router_method.rs:1
- Orphaned file poem/src/web/websocket/message.rs:1
- Orphaned file poem/src/listener/acme/client.rs:1
- Orphaned file poem-openapi-derive/src/newtype.rs:1
- Orphaned file poem-openapi-derive/src/enum.rs:1
- Orphaned file poem-grpc/src/health.rs:1
- Orphaned file poem/src/listener/native_tls.rs:1
- Most significant orphaned file poem/src/endpoint/endpoint.rs:1
- Most significant orphaned file poem/src/middleware/cors.rs:1
- Most significant orphaned file poem-openapi-derive/src/object.rs:1
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Interpolated log message defeats structured logging poem/src/listener/acme/listener.rs:120
- Interpolated log message defeats structured logging poem/src/listener/acme/listener.rs:131
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Large public API surface
- Logging is not universal
- No release approval gate
- No security response headers detected
- Duplicated predicate poem-grpc-build/src/client.rs:25
- Hand-rolled JSON/XML parsing via regex poem-openapi/src/ui/swagger_ui/swagger-ui-bundle.js:2
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-1f55eb7513f74f908dc2b9c032e2e963/history.json --exit-code 0 --source . | 7 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1f55eb7513f74f908dc2b9c032e2e963/tree.json --exit-code 0 --source . | 4 | 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 . | 20 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 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) — `REDACTED` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |