Executive summary
seanmonstar/warp falls short of our standard for a preview release because we found no recorded design decisions and no architecture document or diagram. It scores 59 out of 100 and is rated Adequate, and all six of its critical findings are security problems in the build pipeline.
Maturity, at 51, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Naming the access rules comes next, worth about 4 points. Raising Maturity to 62 would lift the score to about 63.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 9,907 lines, about €14,000 to rebuild.
If Maturity rose from 51 to 62, the lowest score rated Strong, the score would rise from 59 to about 63.
New since the last survey: 40 findings
- Cognitive Complexity · Event::fmt (cognitive 16) src/filters/sse.rs
- Code Duplication · Edited copy of a member (30 corresponding lines) src/filter/or.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/tls.rs
- Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) src/filter/and.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/filters/multipart.rs
- Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) src/filters/compression.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) src/filters/header.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/filter/map.rs
- Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) src/filters/ws.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/filters/body.rs
- Code Coverage · Low coverage: src/bodyt.rs src/bodyt.rs
- Code Coverage · Low coverage: src/error.rs src/error.rs
- Code Coverage · Low coverage: src/filter/and.rs src/filter/and.rs
- Code Coverage · Low coverage: src/filter/and_then.rs src/filter/and_then.rs
- Code Coverage · Low coverage: src/filter/boxed.rs src/filter/boxed.rs
- Code Coverage · Low coverage: src/filter/map.rs src/filter/map.rs
- Code Coverage · Low coverage: src/filter/map_err.rs src/filter/map_err.rs
- Code Coverage · Low coverage: src/filter/or.rs src/filter/or.rs
- Code Coverage · Low coverage: src/filter/or_else.rs src/filter/or_else.rs
- Code Coverage · Low coverage: src/filter/recover.rs src/filter/recover.rs
- Code Coverage · Low coverage: src/filter/service.rs src/filter/service.rs
- Code Coverage · Low coverage: src/filter/then.rs src/filter/then.rs
- Code Coverage · Low coverage: src/filter/unify.rs src/filter/unify.rs
- Code Coverage · Low coverage: src/filter/untuple_one.rs src/filter/untuple_one.rs
- Code Coverage · Low coverage: src/filters/addr.rs src/filters/addr.rs
- Code Coverage · Low coverage: src/filters/body.rs src/filters/body.rs
- Code Coverage · Low coverage: src/filters/cookie.rs src/filters/cookie.rs
- Code Coverage · Low coverage: src/filters/cors.rs src/filters/cors.rs
- Code Coverage · Low coverage: src/filters/ext.rs src/filters/ext.rs
- Code Coverage · Low coverage: src/filters/fs.rs src/filters/fs.rs
- Code Coverage · Low coverage: src/filters/header.rs src/filters/header.rs
- Code Coverage · Low coverage: src/filters/host.rs src/filters/host.rs
- Code Coverage · Low coverage: src/filters/log.rs src/filters/log.rs
- Code Coverage · Low coverage: src/filters/query.rs src/filters/query.rs
- Code Coverage · Low coverage: src/filters/sse.rs src/filters/sse.rs
- Code Coverage · Low coverage: src/filters/trace.rs src/filters/trace.rs
- Code Coverage · Low coverage: src/generic.rs src/generic.rs
- Code Coverage · Low coverage: src/redirect.rs src/redirect.rs
- Code Coverage · Low coverage: src/reply.rs src/reply.rs
- Code Coverage · Low coverage: src/route.rs src/route.rs
Fixed since the last survey: 2 findings
- Secrets (history) · Secret: private-key examples/tls/key.ecc
- Secrets (history) · Secret: private-key examples/tls/key.rsa
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,500 to €23,000, for 76 to 241 hours of work, under 0.1 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 59. 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 | Small: 9,907 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 bodyt | 2 filter.and | 3 filter.boxed | 4 filter.map | 5 filter.map_err | 6 filter.unify | 7 filter.untuple_one | 8 filters.body | 9 filters.cors | 10 route | 11 filter.and_then | 12 filter.or | 13 filter.service | 14 filter.then | 15 filter.or_else | 16 filter.recover | 17 filter | 18 filters.any | 19 filters.cors.internal | 20 filters.multipart | 21 filters.path | 22 reply.sealed | 23 filter.wrap | 24 filters.compression | 25 filters.log | 26 filters.reply | 27 filters.trace | 28 reply | 29 error | 30 filters.compression.internal | 31 filters.fs | 32 filters.log.internal | 33 filters.trace.internal | 34 generic | 35 filters.reply.sealed | 36 filters.ws | 37 server | 38 tls | 39 reject | 40 server.run |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 bodyt | ||||||||||||||||||||||||||||||||||||||||
| 2 filter.and | 2 | |||||||||||||||||||||||||||||||||||||||
| 3 filter.boxed | 4 | |||||||||||||||||||||||||||||||||||||||
| 4 filter.map | 2 | |||||||||||||||||||||||||||||||||||||||
| 5 filter.map_err | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 filter.unify | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 filter.untuple_one | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 filters.body | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 filters.cors | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 route | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 filter.and_then | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 filter.or | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 filter.service | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 filter.then | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 filter.or_else | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 16 filter.recover | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 filter | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 18 filters.any | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 filters.cors.internal | 3 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 filters.multipart | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 filters.path | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 reply.sealed | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 filter.wrap | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 filters.compression | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 filters.log | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 filters.reply | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 27 filters.trace | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 reply | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 error | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 filters.compression.internal | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 filters.fs | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 filters.log.internal | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 filters.trace.internal | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 generic | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 filters.reply.sealed | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 36 filters.ws | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 server | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 tls | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 reject | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 server.run | 1 | 3 |
2→17 filter.and uses filter part of a loop✕
- Connections
- 2 pairs of types, where a type in filter.and uses a type in filter.
- The types involved
warp.filter.and.And→warp.filter.FilterBasewarp.filter.and.And→warp.filter.Internal
- Direction
- filter.and uses filter, so a change to filter can break filter.and, while a change to filter.and can't break filter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→17 filter.boxed uses filter part of a loop✕
- Connections
- 4 pairs of types, where a type in filter.boxed uses a type in filter.
- The types involved
warp.filter.boxed.BoxedFilter→warp.filter.FilterBasewarp.filter.boxed.BoxedFilter→warp.filter.Internalwarp.filter.boxed.BoxingFilter→warp.filter.FilterBasewarp.filter.boxed.BoxingFilter→warp.filter.Internal
- Direction
- filter.boxed uses filter, so a change to filter can break filter.boxed, while a change to filter.boxed can't break filter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→17 filter.map uses filter part of a loop✕
- Connections
- 2 pairs of types, where a type in filter.map uses a type in filter.
- The types involved
warp.filter.map.Map→warp.filter.FilterBasewarp.filter.map.Map→warp.filter.Internal
- Direction
- filter.map uses filter, so a change to filter can break filter.map, while a change to filter.map can't break filter.
- 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→17 filter.map_err uses filter part of a loop✕
- Connections
- 2 pairs of types, where a type in filter.map_err uses a type in filter.
- The types involved
warp.filter.map_err.MapErr→warp.filter.FilterBasewarp.filter.map_err.MapErr→warp.filter.Internal
- Direction
- filter.map_err uses filter, so a change to filter can break filter.map_err, while a change to filter.map_err can't break filter.
- 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→17 filter.unify uses filter part of a loop✕
- Connections
- 2 pairs of types, where a type in filter.unify uses a type in filter.
- The types involved
warp.filter.unify.Unify→warp.filter.FilterBasewarp.filter.unify.Unify→warp.filter.Internal
- Direction
- filter.unify uses filter, so a change to filter can break filter.unify, while a change to filter.unify can't break filter.
- 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→17 filter.untuple_one uses filter part of a loop✕
- Connections
- 2 pairs of types, where a type in filter.untuple_one uses a type in filter.
- The types involved
warp.filter.untuple_one.UntupleOne→warp.filter.FilterBasewarp.filter.untuple_one.UntupleOne→warp.filter.Internal
- Direction
- filter.untuple_one uses filter, so a change to filter can break filter.untuple_one, while a change to filter.untuple_one can't break filter.
- 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→29 filters.body uses error part of a loop✕
- Connections
- 1 pair of types, where a type in filters.body uses a type in error.
- The types involved
warp.filters.body.BodyReadError→warp.error.Error
- Direction
- filters.body uses error, so a change to error can break filters.body, while a change to filters.body can't break error.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→19 filters.cors uses filters.cors.internal part of a loop✕
- Connections
- 2 pairs of types, where a type in filters.cors uses a type in filters.cors.internal.
- The types involved
warp.filters.cors.Builder→warp.filters.cors.internal.Wrappedwarp.filters.cors.Cors→warp.filters.cors.internal.Wrapped
- Direction
- filters.cors uses filters.cors.internal, so a change to filters.cors.internal can break filters.cors, while a change to filters.cors can't break filters.cors.internal.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→23 filters.cors uses filter.wrap part of a loop✕
- Connections
- 2 pairs of types, where a type in filters.cors uses a type in filter.wrap.
- The types involved
warp.filters.cors.Builder→warp.filter.wrap.WrapSealedwarp.filters.cors.Cors→warp.filter.wrap.WrapSealed
- Direction
- filters.cors uses filter.wrap, so a change to filter.wrap can break filters.cors, while a change to filters.cors can't break filter.wrap.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 route uses bodyt✕
- Connections
- 1 pair of types, where a type in route uses a type in bodyt.
- The types involved
warp.route.Route→warp.bodyt.Body
- Direction
- route uses bodyt, so a change to bodyt can break route, while a change to route can't break bodyt.
- Position
- Below the diagonal: route uses a module listed above it, which is the healthy direction.
11→2 filter.and_then uses filter.and✕
- Connections
- 1 pair of types, where a type in filter.and_then uses a type in filter.and.
- The types involved
warp.filter.and_then.AndThenFuture→warp.filter.and.State
- Direction
- filter.and_then uses filter.and, so a change to filter.and can break filter.and_then, while a change to filter.and_then can't break filter.and.
- Position
- Below the diagonal: filter.and_then uses a module listed above it, which is the healthy direction.
11→17 filter.and_then uses filter part of a loop✕
- Connections
- 2 pairs of types, where a type in filter.and_then uses a type in filter.
- The types involved
warp.filter.and_then.AndThen→warp.filter.FilterBasewarp.filter.and_then.AndThen→warp.filter.Internal
- Direction
- filter.and_then uses filter, so a change to filter can break filter.and_then, while a change to filter.and_then can't break filter.
- 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→2 filter.or uses filter.and✕
- Connections
- 1 pair of types, where a type in filter.or uses a type in filter.and.
- The types involved
warp.filter.or.EitherFuture→warp.filter.and.State
- Direction
- filter.or uses filter.and, so a change to filter.and can break filter.or, while a change to filter.or can't break filter.and.
- Position
- Below the diagonal: filter.or uses a module listed above it, which is the healthy direction.
12→17 filter.or uses filter part of a loop✕
- Connections
- 2 pairs of types, where a type in filter.or uses a type in filter.
- The types involved
warp.filter.or.Or→warp.filter.FilterBasewarp.filter.or.Or→warp.filter.Internal
- Direction
- filter.or uses filter, so a change to filter can break filter.or, while a change to filter.or can't break filter.
- 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 filter.service uses route✕
- Connections
- 1 pair of types, where a type in filter.service uses a type in route.
- The types involved
warp.filter.service.FilteredFuture→warp.route.Route
- Direction
- filter.service uses route, so a change to route can break filter.service, while a change to filter.service can't break route.
- Position
- Below the diagonal: filter.service uses a module listed above it, which is the healthy direction.
14→2 filter.then uses filter.and✕
- Connections
- 1 pair of types, where a type in filter.then uses a type in filter.and.
- The types involved
warp.filter.then.ThenFuture→warp.filter.and.State
- Direction
- filter.then uses filter.and, so a change to filter.and can break filter.then, while a change to filter.then can't break filter.and.
- Position
- Below the diagonal: filter.then uses a module listed above it, which is the healthy direction.
14→17 filter.then uses filter part of a loop✕
- Connections
- 2 pairs of types, where a type in filter.then uses a type in filter.
- The types involved
warp.filter.then.Then→warp.filter.FilterBasewarp.filter.then.Then→warp.filter.Internal
- Direction
- filter.then uses filter, so a change to filter can break filter.then, while a change to filter.then can't break filter.
- 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→2 filter.or_else uses filter.and✕
- Connections
- 1 pair of types, where a type in filter.or_else uses a type in filter.and.
- The types involved
warp.filter.or_else.OrElseFuture→warp.filter.and.State
- Direction
- filter.or_else uses filter.and, so a change to filter.and can break filter.or_else, while a change to filter.or_else can't break filter.and.
- Position
- Below the diagonal: filter.or_else uses a module listed above it, which is the healthy direction.
15→12 filter.or_else uses filter.or✕
- Connections
- 1 pair of types, where a type in filter.or_else uses a type in filter.or.
- The types involved
warp.filter.or_else.OrElseFuture→warp.filter.or.PathIndex
- Direction
- filter.or_else uses filter.or, so a change to filter.or can break filter.or_else, while a change to filter.or_else can't break filter.or.
- Position
- Below the diagonal: filter.or_else uses a module listed above it, which is the healthy direction.
15→17 filter.or_else uses filter part of a loop✕
- Connections
- 2 pairs of types, where a type in filter.or_else uses a type in filter.
- The types involved
warp.filter.or_else.OrElse→warp.filter.FilterBasewarp.filter.or_else.OrElse→warp.filter.Internal
- Direction
- filter.or_else uses filter, so a change to filter can break filter.or_else, while a change to filter.or_else can't break filter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→2 filter.recover uses filter.and✕
- Connections
- 1 pair of types, where a type in filter.recover uses a type in filter.and.
- The types involved
warp.filter.recover.RecoverFuture→warp.filter.and.State
- Direction
- filter.recover uses filter.and, so a change to filter.and can break filter.recover, while a change to filter.recover can't break filter.and.
- Position
- Below the diagonal: filter.recover uses a module listed above it, which is the healthy direction.
16→12 filter.recover uses filter.or✕
- Connections
- 1 pair of types, where a type in filter.recover uses a type in filter.or.
- The types involved
warp.filter.recover.RecoverFuture→warp.filter.or.PathIndex
- Direction
- filter.recover uses filter.or, so a change to filter.or can break filter.recover, while a change to filter.recover can't break filter.or.
- Position
- Below the diagonal: filter.recover uses a module listed above it, which is the healthy direction.
16→17 filter.recover uses filter part of a loop✕
- Connections
- 2 pairs of types, where a type in filter.recover uses a type in filter.
- The types involved
warp.filter.recover.Recover→warp.filter.FilterBasewarp.filter.recover.Recover→warp.filter.Internal
- Direction
- filter.recover uses filter, so a change to filter can break filter.recover, while a change to filter.recover can't break filter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 filter uses filter.and✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.and.
- The types involved
warp.filter.Filter→warp.filter.and.And
- Direction
- filter uses filter.and, so a change to filter.and can break filter, while a change to filter can't break filter.and.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→3 filter uses filter.boxed✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.boxed.
- The types involved
warp.filter.Filter→warp.filter.boxed.BoxedFilter
- Direction
- filter uses filter.boxed, so a change to filter.boxed can break filter, while a change to filter can't break filter.boxed.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→4 filter uses filter.map✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.map.
- The types involved
warp.filter.Filter→warp.filter.map.Map
- Direction
- filter uses filter.map, so a change to filter.map can break filter, while a change to filter can't break filter.map.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→5 filter uses filter.map_err✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.map_err.
- The types involved
warp.filter.FilterBase→warp.filter.map_err.MapErr
- Direction
- filter uses filter.map_err, so a change to filter.map_err can break filter, while a change to filter can't break filter.map_err.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→6 filter uses filter.unify✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.unify.
- The types involved
warp.filter.Filter→warp.filter.unify.Unify
- Direction
- filter uses filter.unify, so a change to filter.unify can break filter, while a change to filter can't break filter.unify.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→7 filter uses filter.untuple_one✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.untuple_one.
- The types involved
warp.filter.Filter→warp.filter.untuple_one.UntupleOne
- Direction
- filter uses filter.untuple_one, so a change to filter.untuple_one can break filter, while a change to filter can't break filter.untuple_one.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→11 filter uses filter.and_then✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.and_then.
- The types involved
warp.filter.Filter→warp.filter.and_then.AndThen
- Direction
- filter uses filter.and_then, so a change to filter.and_then can break filter, while a change to filter can't break filter.and_then.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→12 filter uses filter.or✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.or.
- The types involved
warp.filter.Filter→warp.filter.or.Or
- Direction
- filter uses filter.or, so a change to filter.or can break filter, while a change to filter can't break filter.or.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→14 filter uses filter.then✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.then.
- The types involved
warp.filter.Filter→warp.filter.then.Then
- Direction
- filter uses filter.then, so a change to filter.then can break filter, while a change to filter can't break filter.then.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→15 filter uses filter.or_else✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.or_else.
- The types involved
warp.filter.Filter→warp.filter.or_else.OrElse
- Direction
- filter uses filter.or_else, so a change to filter.or_else can break filter, while a change to filter can't break filter.or_else.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→16 filter uses filter.recover✕
- Connections
- 1 pair of types, where a type in filter uses a type in filter.recover.
- The types involved
warp.filter.Filter→warp.filter.recover.Recover
- Direction
- filter uses filter.recover, so a change to filter.recover can break filter, while a change to filter can't break filter.recover.
- Position
- Below the diagonal: filter uses a module listed above it, which is the healthy direction.
17→19 filter uses filters.cors.internal part of a loop✕
- Connections
- 1 pair of types, where a type in filter uses a type in filters.cors.internal.
- The types involved
warp.filter.Filter→warp.filters.cors.internal.Wrapped
- Direction
- filter uses filters.cors.internal, so a change to filters.cors.internal can break filter, while a change to filter can't break filters.cors.internal.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→17 filters.any uses filter✕
- Connections
- 2 pairs of types, where a type in filters.any uses a type in filter.
- The types involved
warp.filters.any.Any→warp.filter.FilterBasewarp.filters.any.Any→warp.filter.Internal
- Direction
- filters.any uses filter, so a change to filter can break filters.any, while a change to filters.any can't break filter.
- Position
- Below the diagonal: filters.any uses a module listed above it, which is the healthy direction.
19→9 filters.cors.internal uses filters.cors✕
- Connections
- 3 pairs of types, where a type in filters.cors.internal uses a type in filters.cors.
- The types involved
warp.filters.cors.internal.CorsFilter→warp.filters.cors.Configuredwarp.filters.cors.internal.Preflight→warp.filters.cors.Configuredwarp.filters.cors.internal.Wrapped→warp.filters.cors.Configured
- Direction
- filters.cors.internal uses filters.cors, so a change to filters.cors can break filters.cors.internal, while a change to filters.cors.internal can't break filters.cors.
- Position
- Below the diagonal: filters.cors.internal uses a module listed above it, which is the healthy direction.
19→17 filters.cors.internal uses filter✕
- Connections
- 2 pairs of types, where a type in filters.cors.internal uses a type in filter.
- The types involved
warp.filters.cors.internal.CorsFilter→warp.filter.FilterBasewarp.filters.cors.internal.CorsFilter→warp.filter.Internal
- Direction
- filters.cors.internal uses filter, so a change to filter can break filters.cors.internal, while a change to filters.cors.internal can't break filter.
- Position
- Below the diagonal: filters.cors.internal uses a module listed above it, which is the healthy direction.
19→28 filters.cors.internal uses reply part of a loop✕
- Connections
- 2 pairs of types, where a type in filters.cors.internal uses a type in reply.
- The types involved
warp.filters.cors.internal.Preflight→warp.reply.Replywarp.filters.cors.internal.Wrapped→warp.reply.Reply
- Direction
- filters.cors.internal uses reply, so a change to reply can break filters.cors.internal, while a change to filters.cors.internal can't break reply.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→17 filters.multipart uses filter✕
- Connections
- 2 pairs of types, where a type in filters.multipart uses a type in filter.
- The types involved
warp.filters.multipart.FormOptions→warp.filter.FilterBasewarp.filters.multipart.FormOptions→warp.filter.Internal
- Direction
- filters.multipart uses filter, so a change to filter can break filters.multipart, while a change to filters.multipart can't break filter.
- Position
- Below the diagonal: filters.multipart uses a module listed above it, which is the healthy direction.
21→10 filters.path uses route✕
- Connections
- 1 pair of types, where a type in filters.path uses a type in route.
- The types involved
warp.filters.path.path$module→warp.route.Route
- Direction
- filters.path uses route, so a change to route can break filters.path, while a change to filters.path can't break route.
- Position
- Below the diagonal: filters.path uses a module listed above it, which is the healthy direction.
21→17 filters.path uses filter✕
- Connections
- 2 pairs of types, where a type in filters.path uses a type in filter.
- The types involved
warp.filters.path.Exact→warp.filter.FilterBasewarp.filters.path.Exact→warp.filter.Internal
- Direction
- filters.path uses filter, so a change to filter can break filters.path, while a change to filters.path can't break filter.
- Position
- Below the diagonal: filters.path uses a module listed above it, which is the healthy direction.
22→17 reply.sealed uses filter✕
- Connections
- 1 pair of types, where a type in reply.sealed uses a type in filter.
- The types involved
warp.reply.sealed.BoxedReply→warp.filter.Internal
- Direction
- reply.sealed uses filter, so a change to filter can break reply.sealed, while a change to reply.sealed can't break filter.
- Position
- Below the diagonal: reply.sealed uses a module listed above it, which is the healthy direction.
22→28 reply.sealed uses reply part of a loop✕
- Connections
- 1 pair of types, where a type in reply.sealed uses a type in reply.
- The types involved
warp.reply.sealed.Reply_→warp.reply.Reply
- Direction
- reply.sealed uses reply, so a change to reply can break reply.sealed, while a change to reply.sealed can't break reply.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→19 filter.wrap uses filters.cors.internal✕
- Connections
- 2 pairs of types, where a type in filter.wrap uses a type in filters.cors.internal.
- The types involved
warp.filter.wrap.WrapFn→warp.filters.cors.internal.Wrappedwarp.filter.wrap.WrapSealed→warp.filters.cors.internal.Wrapped
- Direction
- filter.wrap uses filters.cors.internal, so a change to filters.cors.internal can break filter.wrap, while a change to filter.wrap can't break filters.cors.internal.
- Position
- Below the diagonal: filter.wrap uses a module listed above it, which is the healthy direction.
24→19 filters.compression uses filters.cors.internal✕
- Connections
- 1 pair of types, where a type in filters.compression uses a type in filters.cors.internal.
- The types involved
warp.filters.compression.Compression→warp.filters.cors.internal.Wrapped
- Direction
- filters.compression uses filters.cors.internal, so a change to filters.cors.internal can break filters.compression, while a change to filters.compression can't break filters.cors.internal.
- Position
- Below the diagonal: filters.compression uses a module listed above it, which is the healthy direction.
24→23 filters.compression uses filter.wrap✕
- Connections
- 1 pair of types, where a type in filters.compression uses a type in filter.wrap.
- The types involved
warp.filters.compression.Compression→warp.filter.wrap.WrapSealed
- Direction
- filters.compression uses filter.wrap, so a change to filter.wrap can break filters.compression, while a change to filters.compression can't break filter.wrap.
- Position
- Below the diagonal: filters.compression uses a module listed above it, which is the healthy direction.
25→10 filters.log uses route✕
- Connections
- 1 pair of types, where a type in filters.log uses a type in route.
- The types involved
warp.filters.log.Info→warp.route.Route
- Direction
- filters.log uses route, so a change to route can break filters.log, while a change to filters.log can't break route.
- Position
- Below the diagonal: filters.log uses a module listed above it, which is the healthy direction.
25→19 filters.log uses filters.cors.internal✕
- Connections
- 1 pair of types, where a type in filters.log uses a type in filters.cors.internal.
- The types involved
warp.filters.log.Log→warp.filters.cors.internal.Wrapped
- Direction
- filters.log uses filters.cors.internal, so a change to filters.cors.internal can break filters.log, while a change to filters.log can't break filters.cors.internal.
- Position
- Below the diagonal: filters.log uses a module listed above it, which is the healthy direction.
25→23 filters.log uses filter.wrap✕
- Connections
- 1 pair of types, where a type in filters.log uses a type in filter.wrap.
- The types involved
warp.filters.log.Log→warp.filter.wrap.WrapSealed
- Direction
- filters.log uses filter.wrap, so a change to filter.wrap can break filters.log, while a change to filters.log can't break filter.wrap.
- Position
- Below the diagonal: filters.log uses a module listed above it, which is the healthy direction.
26→19 filters.reply uses filters.cors.internal✕
- Connections
- 3 pairs of types, where a type in filters.reply uses a type in filters.cors.internal.
- The types involved
warp.filters.reply.WithDefaultHeader→warp.filters.cors.internal.Wrappedwarp.filters.reply.WithHeader→warp.filters.cors.internal.Wrappedwarp.filters.reply.WithHeaders→warp.filters.cors.internal.Wrapped
- Direction
- filters.reply uses filters.cors.internal, so a change to filters.cors.internal can break filters.reply, while a change to filters.reply can't break filters.cors.internal.
- Position
- Below the diagonal: filters.reply uses a module listed above it, which is the healthy direction.
26→23 filters.reply uses filter.wrap✕
- Connections
- 3 pairs of types, where a type in filters.reply uses a type in filter.wrap.
- The types involved
warp.filters.reply.WithDefaultHeader→warp.filter.wrap.WrapSealedwarp.filters.reply.WithHeader→warp.filter.wrap.WrapSealedwarp.filters.reply.WithHeaders→warp.filter.wrap.WrapSealed
- Direction
- filters.reply uses filter.wrap, so a change to filter.wrap can break filters.reply, while a change to filters.reply can't break filter.wrap.
- Position
- Below the diagonal: filters.reply uses a module listed above it, which is the healthy direction.
27→10 filters.trace uses route✕
- Connections
- 1 pair of types, where a type in filters.trace uses a type in route.
- The types involved
warp.filters.trace.Info→warp.route.Route
- Direction
- filters.trace uses route, so a change to route can break filters.trace, while a change to filters.trace can't break route.
- Position
- Below the diagonal: filters.trace uses a module listed above it, which is the healthy direction.
27→19 filters.trace uses filters.cors.internal✕
- Connections
- 1 pair of types, where a type in filters.trace uses a type in filters.cors.internal.
- The types involved
warp.filters.trace.Trace→warp.filters.cors.internal.Wrapped
- Direction
- filters.trace uses filters.cors.internal, so a change to filters.cors.internal can break filters.trace, while a change to filters.trace can't break filters.cors.internal.
- Position
- Below the diagonal: filters.trace uses a module listed above it, which is the healthy direction.
27→23 filters.trace uses filter.wrap✕
- Connections
- 1 pair of types, where a type in filters.trace uses a type in filter.wrap.
- The types involved
warp.filters.trace.Trace→warp.filter.wrap.WrapSealed
- Direction
- filters.trace uses filter.wrap, so a change to filter.wrap can break filters.trace, while a change to filters.trace can't break filter.wrap.
- Position
- Below the diagonal: filters.trace uses a module listed above it, which is the healthy direction.
28→8 reply uses filters.body✕
- Connections
- 1 pair of types, where a type in reply uses a type in filters.body.
- The types involved
warp.reply.reply$module→warp.filters.body.Json
- Direction
- reply uses filters.body, so a change to filters.body can break reply, while a change to reply can't break filters.body.
- Position
- Below the diagonal: reply uses a module listed above it, which is the healthy direction.
28→22 reply uses reply.sealed✕
- Connections
- 1 pair of types, where a type in reply uses a type in reply.sealed.
- The types involved
warp.reply.Reply→warp.reply.sealed.BoxedReply
- Direction
- reply uses reply.sealed, so a change to reply.sealed can break reply, while a change to reply can't break reply.sealed.
- Position
- Below the diagonal: reply uses a module listed above it, which is the healthy direction.
28→26 reply uses filters.reply✕
- Connections
- 1 pair of types, where a type in reply uses a type in filters.reply.
- The types involved
warp.reply.reply$module→warp.filters.reply.WithHeader
- Direction
- reply uses filters.reply, so a change to filters.reply can break reply, while a change to reply can't break filters.reply.
- Position
- Below the diagonal: reply uses a module listed above it, which is the healthy direction.
29→28 error uses reply✕
- Connections
- 1 pair of types, where a type in error uses a type in reply.
- The types involved
warp.error.Error→warp.reply.Reply
- Direction
- error uses reply, so a change to reply can break error, while a change to error can't break reply.
- Position
- Below the diagonal: error uses a module listed above it, which is the healthy direction.
30→1 filters.compression.internal uses bodyt✕
- Connections
- 1 pair of types, where a type in filters.compression.internal uses a type in bodyt.
- The types involved
warp.filters.compression.internal.CompressableBody→warp.bodyt.Body
- Direction
- filters.compression.internal uses bodyt, so a change to bodyt can break filters.compression.internal, while a change to filters.compression.internal can't break bodyt.
- Position
- Below the diagonal: filters.compression.internal uses a module listed above it, which is the healthy direction.
30→17 filters.compression.internal uses filter✕
- Connections
- 2 pairs of types, where a type in filters.compression.internal uses a type in filter.
- The types involved
warp.filters.compression.internal.WithCompression→warp.filter.FilterBasewarp.filters.compression.internal.WithCompression→warp.filter.Internal
- Direction
- filters.compression.internal uses filter, so a change to filter can break filters.compression.internal, while a change to filters.compression.internal can't break filter.
- Position
- Below the diagonal: filters.compression.internal uses a module listed above it, which is the healthy direction.
30→24 filters.compression.internal uses filters.compression✕
- Connections
- 2 pairs of types, where a type in filters.compression.internal uses a type in filters.compression.
- The types involved
warp.filters.compression.internal.WithCompression→warp.filters.compression.Compressionwarp.filters.compression.internal.WithCompressionFuture→warp.filters.compression.Compression
- Direction
- filters.compression.internal uses filters.compression, so a change to filters.compression can break filters.compression.internal, while a change to filters.compression.internal can't break filters.compression.
- Position
- Below the diagonal: filters.compression.internal uses a module listed above it, which is the healthy direction.
30→28 filters.compression.internal uses reply✕
- Connections
- 1 pair of types, where a type in filters.compression.internal uses a type in reply.
- The types involved
warp.filters.compression.internal.Compressed→warp.reply.Reply
- Direction
- filters.compression.internal uses reply, so a change to reply can break filters.compression.internal, while a change to filters.compression.internal can't break reply.
- Position
- Below the diagonal: filters.compression.internal uses a module listed above it, which is the healthy direction.
31→28 filters.fs uses reply✕
- Connections
- 1 pair of types, where a type in filters.fs uses a type in reply.
- The types involved
warp.filters.fs.File→warp.reply.Reply
- Direction
- filters.fs uses reply, so a change to reply can break filters.fs, while a change to filters.fs can't break reply.
- Position
- Below the diagonal: filters.fs uses a module listed above it, which is the healthy direction.
32→17 filters.log.internal uses filter✕
- Connections
- 2 pairs of types, where a type in filters.log.internal uses a type in filter.
- The types involved
warp.filters.log.internal.WithLog→warp.filter.FilterBasewarp.filters.log.internal.WithLog→warp.filter.Internal
- Direction
- filters.log.internal uses filter, so a change to filter can break filters.log.internal, while a change to filters.log.internal can't break filter.
- Position
- Below the diagonal: filters.log.internal uses a module listed above it, which is the healthy direction.
32→25 filters.log.internal uses filters.log✕
- Connections
- 2 pairs of types, where a type in filters.log.internal uses a type in filters.log.
- The types involved
warp.filters.log.internal.WithLog→warp.filters.log.Logwarp.filters.log.internal.WithLogFuture→warp.filters.log.Log
- Direction
- filters.log.internal uses filters.log, so a change to filters.log can break filters.log.internal, while a change to filters.log.internal can't break filters.log.
- Position
- Below the diagonal: filters.log.internal uses a module listed above it, which is the healthy direction.
32→28 filters.log.internal uses reply✕
- Connections
- 1 pair of types, where a type in filters.log.internal uses a type in reply.
- The types involved
warp.filters.log.internal.Logged→warp.reply.Reply
- Direction
- filters.log.internal uses reply, so a change to reply can break filters.log.internal, while a change to filters.log.internal can't break reply.
- Position
- Below the diagonal: filters.log.internal uses a module listed above it, which is the healthy direction.
33→17 filters.trace.internal uses filter✕
- Connections
- 2 pairs of types, where a type in filters.trace.internal uses a type in filter.
- The types involved
warp.filters.trace.internal.WithTrace→warp.filter.FilterBasewarp.filters.trace.internal.WithTrace→warp.filter.Internal
- Direction
- filters.trace.internal uses filter, so a change to filter can break filters.trace.internal, while a change to filters.trace.internal can't break filter.
- Position
- Below the diagonal: filters.trace.internal uses a module listed above it, which is the healthy direction.
33→27 filters.trace.internal uses filters.trace✕
- Connections
- 1 pair of types, where a type in filters.trace.internal uses a type in filters.trace.
- The types involved
warp.filters.trace.internal.WithTrace→warp.filters.trace.Trace
- Direction
- filters.trace.internal uses filters.trace, so a change to filters.trace can break filters.trace.internal, while a change to filters.trace.internal can't break filters.trace.
- Position
- Below the diagonal: filters.trace.internal uses a module listed above it, which is the healthy direction.
33→28 filters.trace.internal uses reply✕
- Connections
- 1 pair of types, where a type in filters.trace.internal uses a type in reply.
- The types involved
warp.filters.trace.internal.Traced→warp.reply.Reply
- Direction
- filters.trace.internal uses reply, so a change to reply can break filters.trace.internal, while a change to filters.trace.internal can't break reply.
- Position
- Below the diagonal: filters.trace.internal uses a module listed above it, which is the healthy direction.
34→28 generic uses reply✕
- Connections
- 1 pair of types, where a type in generic uses a type in reply.
- The types involved
warp.generic.Either→warp.reply.Reply
- Direction
- generic uses reply, so a change to reply can break generic, while a change to generic can't break reply.
- Position
- Below the diagonal: generic uses a module listed above it, which is the healthy direction.
35→26 filters.reply.sealed uses filters.reply✕
- Connections
- 3 pairs of types, where a type in filters.reply.sealed uses a type in filters.reply.
- The types involved
warp.filters.reply.sealed.WithDefaultHeader_→warp.filters.reply.WithDefaultHeaderwarp.filters.reply.sealed.WithHeader_→warp.filters.reply.WithHeaderwarp.filters.reply.sealed.WithHeaders_→warp.filters.reply.WithHeaders
- Direction
- filters.reply.sealed uses filters.reply, so a change to filters.reply can break filters.reply.sealed, while a change to filters.reply.sealed can't break filters.reply.
- Position
- Below the diagonal: filters.reply.sealed uses a module listed above it, which is the healthy direction.
35→34 filters.reply.sealed uses generic✕
- Connections
- 3 pairs of types, where a type in filters.reply.sealed uses a type in generic.
- The types involved
warp.filters.reply.sealed.WithDefaultHeader_→warp.generic.Funcwarp.filters.reply.sealed.WithHeader_→warp.generic.Funcwarp.filters.reply.sealed.WithHeaders_→warp.generic.Func
- Direction
- filters.reply.sealed uses generic, so a change to generic can break filters.reply.sealed, while a change to filters.reply.sealed can't break generic.
- Position
- Below the diagonal: filters.reply.sealed uses a module listed above it, which is the healthy direction.
36→28 filters.ws uses reply✕
- Connections
- 1 pair of types, where a type in filters.ws uses a type in reply.
- The types involved
warp.filters.ws.WsReply→warp.reply.Reply
- Direction
- filters.ws uses reply, so a change to reply can break filters.ws, while a change to filters.ws can't break reply.
- Position
- Below the diagonal: filters.ws uses a module listed above it, which is the healthy direction.
36→29 filters.ws uses error✕
- Connections
- 1 pair of types, where a type in filters.ws uses a type in error.
- The types involved
warp.filters.ws.MissingConnectionUpgrade→warp.error.Error
- Direction
- filters.ws uses error, so a change to error can break filters.ws, while a change to filters.ws can't break error.
- Position
- Below the diagonal: filters.ws uses a module listed above it, which is the healthy direction.
37→34 server uses generic✕
- Connections
- 1 pair of types, where a type in server uses a type in generic.
- The types involved
warp.server.Server→warp.generic.Func
- Direction
- server uses generic, so a change to generic can break server, while a change to server can't break generic.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
38→2 tls uses filter.and✕
- Connections
- 1 pair of types, where a type in tls uses a type in filter.and.
- The types involved
warp.tls.TlsStream→warp.filter.and.State
- Direction
- tls uses filter.and, so a change to filter.and can break tls, while a change to tls can't break filter.and.
- Position
- Below the diagonal: tls uses a module listed above it, which is the healthy direction.
38→29 tls uses error✕
- Connections
- 1 pair of types, where a type in tls uses a type in error.
- The types involved
warp.tls.TlsConfigError→warp.error.Error
- Direction
- tls uses error, so a change to error can break tls, while a change to tls can't break error.
- Position
- Below the diagonal: tls uses a module listed above it, which is the healthy direction.
38→31 tls uses filters.fs✕
- Connections
- 1 pair of types, where a type in tls uses a type in filters.fs.
- The types involved
warp.tls.LazyFile→warp.filters.fs.File
- Direction
- tls uses filters.fs, so a change to filters.fs can break tls, while a change to tls can't break filters.fs.
- Position
- Below the diagonal: tls uses a module listed above it, which is the healthy direction.
39→8 reject uses filters.body✕
- Connections
- 2 pairs of types, where a type in reject uses a type in filters.body.
- The types involved
warp.reject.Known→warp.filters.body.BodyDeserializeErrorwarp.reject.Known→warp.filters.body.BodyReadError
- Direction
- reject uses filters.body, so a change to filters.body can break reject, while a change to reject can't break filters.body.
- Position
- Below the diagonal: reject uses a module listed above it, which is the healthy direction.
39→9 reject uses filters.cors✕
- Connections
- 1 pair of types, where a type in reject uses a type in filters.cors.
- The types involved
warp.reject.Known→warp.filters.cors.CorsForbidden
- Direction
- reject uses filters.cors, so a change to filters.cors can break reject, while a change to reject can't break filters.cors.
- Position
- Below the diagonal: reject uses a module listed above it, which is the healthy direction.
39→36 reject uses filters.ws✕
- Connections
- 1 pair of types, where a type in reject uses a type in filters.ws.
- The types involved
warp.reject.Known→warp.filters.ws.MissingConnectionUpgrade
- Direction
- reject uses filters.ws, so a change to filters.ws can break reject, while a change to reject can't break filters.ws.
- Position
- Below the diagonal: reject uses a module listed above it, which is the healthy direction.
40→29 server.run uses error✕
- Connections
- 1 pair of types, where a type in server.run uses a type in error.
- The types involved
warp.server.run.run$module→warp.error.Error
- Direction
- server.run uses error, so a change to error can break server.run, while a change to server.run can't break error.
- Position
- Below the diagonal: server.run uses a module listed above it, which is the healthy direction.
40→37 server.run uses server✕
- Connections
- 3 pairs of types, where a type in server.run uses a type in server.
- The types involved
warp.server.run.Graceful→warp.server.Serverwarp.server.run.Run→warp.server.Serverwarp.server.run.Standard→warp.server.Server
- Direction
- server.run uses server, so a change to server can break server.run, while a change to server.run can't break server.
- Position
- Below the diagonal: server.run uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 6 | High / Critical |
Roadmap
Top priorities: 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; Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own; Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
| 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. | +6.5 pts | Medium | Architecture documentation |
| Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own. | +4.2 pts | Medium | Access Controls |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +4.0 pts | Medium | Documentation (README) |
| Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with trace.rs, compression.rs, host.rs. | +1.1 pts | Low | Knowledge Freshness |
| Interpolated log message defeats structured logging | +2.1 pts | Medium | Structured logging |
| 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. | +1.6 pts | Medium | Web-Security Posture |
| Resolve the 30 Low coverage finding(s) in Code Coverage — start with bodyt.rs, error.rs, and.rs. | +1.5 pts | Medium | Code Coverage |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.5 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| src/filters/cors.rs | 5.5 | Mixed | Cognitive Complexity: Configured::check_request (cognitive 21) |
| src/filters/sse.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/filters/log.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/filters/compression.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/server.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/filters/fs.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/filter/or.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (30 corresponding lines) |
| src/filter/and.rs | 7.0 | Near-clean | Code Duplication: Edited copies of one member (3 members, 17+ corresponding lines) |
| src/filters/header.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (17 corresponding lines) |
| src/filter/map.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (10 corresponding lines) |
| src/filters/body.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (10 corresponding lines) |
| src/filter/and_then.rs | 7.0 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| src/filter/or_else.rs | 7.0 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| src/test.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/filter/mod.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| examples/todos.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/tls.rs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (14 corresponding lines) |
| src/filters/multipart.rs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (8 corresponding lines) |
| src/filters/ws.rs | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 6+ corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 36 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, 107 of 116 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (9907 LoC, 147 module-visible types across 3 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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.
- 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
0 function(s) exceeded the cyclomatic complexity threshold of 15. A further 3 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Known::inner_as_any at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/reject.rs (Known::inner_as_any at 16). 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.
D2 · Cognitive Complexity
2 function(s) exceeded the cognitive complexity threshold of 15; the worst was Configured::check_request at 21.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with Configured::check_request (cognitive 21), Event::fmt (cognitive 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 over-large unit(s) detected — types, modules or files that carry too much.
D4 · Code Duplication
6 duplicated block group(s) detected. 3.6 % of the production lines (354 of 9,907) are in a reported copy. A further 9 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with log.rs (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with map.rs, body.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with and_then.rs, server.rs. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
1 of 20 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with cors.rs. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 37.2% — 30 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 38 production file(s), 1 test binaries and 93 doc-test binaries).
What to do
- Resolve the 30 Low coverage finding(s) in Code Coverage — start with bodyt.rs, error.rs, and.rs. — One of this dimension's main actionable groups (30 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 45 test files): measured (0 flaky).
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 91 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/filters/sse.rs. Counted over 33 of the 46 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
8 deducted task-comment markers across 9907 LoC (0.1/KLoC) → score 9.9. 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 7 TodoComment finding(s) in Explicit Debt — start with server.rs, test.rs, compression.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with sse.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
3 of 33 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/filters/trace.rs. Counted over 33 of the 46 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
- Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
What to do
- Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
- Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- 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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- 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(` (src/server.rs:391).
What to do
- 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
X21 · Side-effecting pattern guard
X4 · Structured logging
- `error!` at line 454 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/reject.rs:454
- `error!` at line 104 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/reply.rs:104
- `error!` at line 370 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/reply.rs:370
- `error!` at line 376 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/reply.rs:376
- `error!` at line 425 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/reply.rs:425
- `debug!` at line 380 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/server.rs:380
- `error!` at line 394 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/server.rs:394
- `debug!` at line 440 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/server.rs:440
- `error!` at line 453 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/server.rs:453
- `error!` at line 477 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/server.rs:477
- `debug!` at line 60 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/body.rs:60
- `debug!` at line 113 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/body.rs:113
- `debug!` at line 154 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/body.rs:154
- `debug!` at line 185 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/body.rs:185
- `debug!` at line 220 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/body.rs:220
- `trace!` at line 264 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/body.rs:264
- `debug!` at line 273 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/filters/body.rs:273, src/filters/fs.rs:273
- `debug!` at line 282 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/body.rs:282
- `trace!` at line 287 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/body.rs:287
- `trace!` at line 395 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/cors.rs:395
- `trace!` at line 52 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:52
- `trace!` at line 105 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:105
- `debug!` at line 116 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:116
- `trace!` 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: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:120
- `trace!` at line 158 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:158
- `trace!` at line 172 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:172
- `trace!` at line 189 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:189
- `warn!` at line 277 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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`. — src/filters/fs.rs:277
- `error!` at line 281 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:281
- `debug!` at line 298 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:298
- `trace!` at line 397 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:397
- `debug!` at line 438 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/fs.rs:438
- `trace!` at line 41 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/header.rs:41
- `trace!` at line 55 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/header.rs:55
- `trace!` at line 83 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/header.rs:83
- `trace!` at line 142 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/header.rs:142
- `trace!` at line 174 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/header.rs:174
- `trace!` at line 206 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/header.rs:206
- `trace!` at line 134 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/filters/method.rs:134
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 51% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 64% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58% | Adequate — gated by C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2952 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.
- 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 — N/A — too few peers to establish a naming convention (1153 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (37 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 38 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 6 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 57 finding(s)
- Low coverage: src/bodyt.rs src/bodyt.rs:1
- Low coverage: src/error.rs src/error.rs:1
- Low coverage: src/filter/and.rs src/filter/and.rs:1
- Low coverage: src/filter/and_then.rs src/filter/and_then.rs:1
- Low coverage: src/filter/boxed.rs src/filter/boxed.rs:1
- Low coverage: src/filter/map.rs src/filter/map.rs:1
- Low coverage: src/filter/map_err.rs src/filter/map_err.rs:1
- Low coverage: src/filter/or.rs src/filter/or.rs:1
- Low coverage: src/filter/or_else.rs src/filter/or_else.rs:1
- Low coverage: src/filter/recover.rs src/filter/recover.rs:1
- Low coverage: src/filter/service.rs src/filter/service.rs:1
- Low coverage: src/filter/then.rs src/filter/then.rs:1
- Low coverage: src/filter/unify.rs src/filter/unify.rs:1
- Low coverage: src/filter/untuple_one.rs src/filter/untuple_one.rs:1
- Low coverage: src/filters/addr.rs src/filters/addr.rs:1
- Low coverage: src/filters/body.rs src/filters/body.rs:1
- Low coverage: src/filters/cookie.rs src/filters/cookie.rs:1
- Low coverage: src/filters/cors.rs src/filters/cors.rs:1
- Low coverage: src/filters/ext.rs src/filters/ext.rs:1
- Low coverage: src/filters/fs.rs src/filters/fs.rs:1
- Low coverage: src/filters/header.rs src/filters/header.rs:1
- Low coverage: src/filters/host.rs src/filters/host.rs:1
- Low coverage: src/filters/log.rs src/filters/log.rs:1
- Low coverage: src/filters/query.rs src/filters/query.rs:1
- Low coverage: src/filters/sse.rs src/filters/sse.rs:1
- TodoComment src/server.rs:463
- TodoComment src/test.rs:375
- TodoComment src/filters/compression.rs:50
- TodoComment src/filters/fs.rs:481
- TodoComment src/filters/log.rs:35
- TodoComment src/filter/mod.rs:473
- TodoComment examples/todos.rs:139
- Duplicated block (6 lines × 2) src/filters/log.rs:138
- Duplicated block (6 lines × 2) src/filters/log.rs:146
- Duplicated block (6 lines × 2) src/filters/log.rs:159
- Edited copy of a member (10 corresponding lines) src/filter/map.rs:49
- Edited copy of a member (10 corresponding lines) src/filters/body.rs:180
- Duplicated block (8 lines × 2) src/filter/and_then.rs:91
- Duplicated block (8 lines × 2) src/server.rs:376
- FixmeComment src/filters/sse.rs:357
- Configured::check_request (cognitive 21) src/filters/cors.rs:355
- Event::fmt (cognitive 16) src/filters/sse.rs:140
- REDACTED
- Edited copy of a member (30 corresponding lines) src/filter/or.rs:73
- Edited copy of a member (14 corresponding lines) src/tls.rs:318
- Edited copies of one member (3 members, 17+ corresponding lines) src/filter/and.rs:79
- Edited copy of a member (8 corresponding lines) src/filters/multipart.rs:167
- Edited copies of one member (3 members, 14+ corresponding lines) src/filters/compression.rs:67
- Edited copy of a member (17 corresponding lines) src/filters/header.rs:140
- Edited copies of one member (3 members, 6+ corresponding lines) src/filters/ws.rs:237
- Duplicated block (7 lines × 2) src/filter/or_else.rs:29
- Low cohesion: Builder (LCOM4 5) src/filters/cors.rs:64
Minor — 53 finding(s)
- Interpolated log message defeats structured logging src/reject.rs:454
- Interpolated log message defeats structured logging src/reply.rs:104
- Interpolated log message defeats structured logging src/reply.rs:370
- Interpolated log message defeats structured logging src/reply.rs:376
- Interpolated log message defeats structured logging src/reply.rs:425
- Interpolated log message defeats structured logging src/server.rs:380
- Interpolated log message defeats structured logging src/server.rs:394
- Interpolated log message defeats structured logging src/server.rs:440
- Interpolated log message defeats structured logging src/server.rs:453
- Interpolated log message defeats structured logging src/server.rs:477
- Interpolated log message defeats structured logging src/filters/body.rs:60
- Interpolated log message defeats structured logging src/filters/body.rs:113
- Interpolated log message defeats structured logging src/filters/body.rs:154
- Interpolated log message defeats structured logging src/filters/body.rs:185
- Interpolated log message defeats structured logging src/filters/body.rs:220
- Interpolated log message defeats structured logging src/filters/body.rs:264
- Interpolated log message defeats structured logging src/filters/body.rs:273
- Interpolated log message defeats structured logging src/filters/body.rs:282
- Interpolated log message defeats structured logging src/filters/body.rs:287
- Interpolated log message defeats structured logging src/filters/cors.rs:395
- Interpolated log message defeats structured logging src/filters/fs.rs:52
- Interpolated log message defeats structured logging src/filters/fs.rs:105
- Interpolated log message defeats structured logging src/filters/fs.rs:116
- Interpolated log message defeats structured logging src/filters/fs.rs:120
- Interpolated log message defeats structured logging src/filters/fs.rs:158
- Orphaned file src/filters/trace.rs:1
- Orphaned file src/filters/compression.rs:1
- Orphaned file src/filters/host.rs:1
- No named authorization policies
- Thin authorization enforcement
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- No security response headers detected
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a49b0809accc4cf89d7d14bdb7328a81/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a49b0809accc4cf89d7d14bdb7328a81/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 6 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |