Public report of salvo-rs/salvo, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 20:35 UTC · Survey ID cd_23e7b8325a7b4b58bc16455bcfeb9423
salvo-rs/salvo
Measured 14 November 2026, 20:30 UTC, at code version 75d0473
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 103,724 lines of product code in 23 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Event-Driven, 10
Findings by how serious they are
16 critical376 serious48 minor
23 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 20:30 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
49of 49 dimensions measured by tools.
425of 440 findings point to an exact file and line, so you can open each one in the code. The other 15 concern the repository as a whole, such as missing documentation.
49dimensions across 7 lenses, read from 103,724 lines of product code in 23 projects.
salvo-rs/salvo falls short of our standard for production, held back most by its Event-Driven lens, the way the code's parts exchange events. It scores 43 out of 100 and is rated Weak, and 15 of its 16 critical findings are security problems.
Event-Driven, at 10, is the weakest lens and counts most in the score. The best first step is stopping the event handlers from waiting on other services, worth about 28 points. Raising Event-Driven to 70 would lift the score to about 70.
Nine passwords or keys in the code's history and three in the code are open to anyone who can read the repository. Two pipeline steps install packages that can change without warning, and one automatic update takes new releases before a bad one can be spotted. Replacing each exposed password or key, pinning what the pipeline installs and setting a waiting period for automatic updates would close these risks. Letting the handler publish a message instead of waiting for the reply would take care of the message handler that waits for another service.
The product code is 103,724 lines, about €110,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Event-Driven rose from 10 to 70, the lowest score rated Strong, the score would rise from 43 to about 70.
Code composition: what the lines of code are
Product code 80%Tests 20%
New since the last survey: 132 findings
These 132 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 122 findings
These 122 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one. The first 100 are listed here.
€37,000 to €190,000, for 623 to 1,977 hours of work, about 0.8 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 43. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 103,724 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.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place.
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.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.8 person-years of work. Its weakest lens is Event-Driven, at 10 (Critical). Event-Driven is about whether the parts of the system can rely on the messages they send each other. Because the weakest lens counts most in the score, work on Event-Driven also moves the score most.
Based on: the rebuild estimate · the Event-Driven grade · how much each lens counts
What to do: Start with the Event-Driven actions in Top priorities.
If you do one thing first · First action
Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place. Of all the actions in this report, it raises the score most for the work it takes: about 28 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
248 modules, with 697 dependencies between them. 12 loops run through 80 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 208 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
salvo_core.fuse uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.fuse, while a change to salvo_core.fuse can't break salvo_core.conn.ctrl.
Position
Below the diagonal: salvo_core.fuse uses a module listed above it, which is the healthy direction.
6→23 salvo_oapi.openapi.schema.object uses salvo_oapi.openapi.schema.arraypart of a loop✕
Connections
1 pair of types, where a type in salvo_oapi.openapi.schema.object uses a type in salvo_oapi.openapi.schema.array.
salvo_oapi.openapi.schema.object uses salvo_oapi.openapi.schema.array, so a change to salvo_oapi.openapi.schema.array can break salvo_oapi.openapi.schema.object, while a change to salvo_oapi.openapi.schema.object can't break salvo_oapi.openapi.schema.array.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→31 salvo_oapi.openapi.schema.object uses salvo_oapi.openapi.schemapart of a loop✕
Connections
3 pairs of types, where a type in salvo_oapi.openapi.schema.object uses a type in salvo_oapi.openapi.schema.
salvo_oapi.openapi.schema.object uses salvo_oapi.openapi.schema, so a change to salvo_oapi.openapi.schema can break salvo_oapi.openapi.schema.object, while a change to salvo_oapi.openapi.schema.object can't break salvo_oapi.openapi.schema.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→37 salvo_oapi.openapi.schema.object uses salvo_oapi.openapipart of a loop✕
Connections
2 pairs of types, where a type in salvo_oapi.openapi.schema.object uses a type in salvo_oapi.openapi.
salvo_oapi.openapi.schema.object uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi.openapi.schema.object, while a change to salvo_oapi.openapi.schema.object can't break salvo_oapi.openapi.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→12 salvo_oapi_macros.shared uses salvo_oapi_macros.featurepart of a loop✕
Connections
1 pair of types, where a type in salvo_oapi_macros.shared uses a type in salvo_oapi_macros.feature.
salvo_oapi_macros.shared uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.shared, while a change to salvo_oapi_macros.shared can't break salvo_oapi_macros.feature.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→16 salvo_oapi_macros.shared uses salvo_oapi_macros.feature.attributespart of a loop✕
Connections
4 pairs of types, where a type in salvo_oapi_macros.shared uses a type in salvo_oapi_macros.feature.attributes.
salvo_oapi_macros.shared uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi_macros.shared, while a change to salvo_oapi_macros.shared can't break salvo_oapi_macros.feature.attributes.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
salvo_core.conn.proto uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.conn.proto, while a change to salvo_core.conn.proto can't break salvo_core.conn.ctrl.
Position
Below the diagonal: salvo_core.conn.proto uses a module listed above it, which is the healthy direction.
salvo_core.conn.proto uses salvo_core.fuse, so a change to salvo_core.fuse can break salvo_core.conn.proto, while a change to salvo_core.conn.proto can't break salvo_core.fuse.
Position
Below the diagonal: salvo_core.conn.proto uses a module listed above it, which is the healthy direction.
salvo_core.http.response uses salvo_core.fuse, so a change to salvo_core.fuse can break salvo_core.http.response, while a change to salvo_core.http.response can't break salvo_core.fuse.
Position
Below the diagonal: salvo_core.http.response uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.schema_type uses salvo_oapi_macros.shared, so a change to salvo_oapi_macros.shared can break salvo_oapi_macros.schema_type, while a change to salvo_oapi_macros.schema_type can't break salvo_oapi_macros.shared.
Position
Below the diagonal: salvo_oapi_macros.schema_type uses a module listed above it, which is the healthy direction.
10→12 salvo_oapi_macros.schema_type uses salvo_oapi_macros.featurepart of a loop✕
Connections
2 pairs of types, where a type in salvo_oapi_macros.schema_type uses a type in salvo_oapi_macros.feature.
salvo_oapi_macros.schema_type uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.schema_type, while a change to salvo_oapi_macros.schema_type can't break salvo_oapi_macros.feature.
Position
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.
salvo_core.routing.flow_ctrl uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.routing.flow_ctrl, while a change to salvo_core.routing.flow_ctrl can't break salvo_core.conn.ctrl.
Position
Below the diagonal: salvo_core.routing.flow_ctrl uses a module listed above it, which is the healthy direction.
salvo_core.routing.flow_ctrl uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.routing.flow_ctrl, while a change to salvo_core.routing.flow_ctrl can't break salvo_core.depot.
Position
Below the diagonal: salvo_core.routing.flow_ctrl uses a module listed above it, which is the healthy direction.
salvo_core.routing.flow_ctrl uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.routing.flow_ctrl, while a change to salvo_core.routing.flow_ctrl can't break salvo_core.http.response.
Position
Below the diagonal: salvo_core.routing.flow_ctrl uses a module listed above it, which is the healthy direction.
11→15 salvo_core.routing.flow_ctrl uses salvo_core.http.requestpart of a loop✕
Connections
1 pair of types, where a type in salvo_core.routing.flow_ctrl uses a type in salvo_core.http.request.
salvo_core.routing.flow_ctrl uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.routing.flow_ctrl, while a change to salvo_core.routing.flow_ctrl can't break salvo_core.http.request.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
salvo_oapi_macros.feature uses salvo_oapi_macros.shared, so a change to salvo_oapi_macros.shared can break salvo_oapi_macros.feature, while a change to salvo_oapi_macros.feature can't break salvo_oapi_macros.shared.
Position
Below the diagonal: salvo_oapi_macros.feature uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.feature uses salvo_oapi_macros.schema_type, so a change to salvo_oapi_macros.schema_type can break salvo_oapi_macros.feature, while a change to salvo_oapi_macros.feature can't break salvo_oapi_macros.schema_type.
Position
Below the diagonal: salvo_oapi_macros.feature uses a module listed above it, which is the healthy direction.
12→16 salvo_oapi_macros.feature uses salvo_oapi_macros.feature.attributespart of a loop✕
Connections
35 pairs of types, where a type in salvo_oapi_macros.feature uses a type in salvo_oapi_macros.feature.attributes. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
salvo_oapi_macros.feature uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi_macros.feature, while a change to salvo_oapi_macros.feature can't break salvo_oapi_macros.feature.attributes.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
salvo_core.http.form uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.depot.
Position
Below the diagonal: salvo_core.http.form uses a module listed above it, which is the healthy direction.
salvo_core.http.form uses salvo_core.extract.metadata, so a change to salvo_core.extract.metadata can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.extract.metadata.
Position
Below the diagonal: salvo_core.http.form uses a module listed above it, which is the healthy direction.
salvo_core.http.form uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.http.response.
Position
Below the diagonal: salvo_core.http.form uses a module listed above it, which is the healthy direction.
salvo_core.http.form uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_core.http.form uses a module listed above it, which is the healthy direction.
13→15 salvo_core.http.form uses salvo_core.http.requestpart of a loop✕
Connections
1 pair of types, where a type in salvo_core.http.form uses a type in salvo_core.http.request.
salvo_core.http.form uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.http.request.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→18 salvo_core.http.form uses salvo_core.handlerpart of a loop✕
Connections
1 pair of types, where a type in salvo_core.http.form uses a type in salvo_core.handler.
salvo_core.http.form uses salvo_core.handler, so a change to salvo_core.handler can break salvo_core.http.form, while a change to salvo_core.http.form can't break salvo_core.handler.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
salvo_oapi_macros.parse_utils uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.parse_utils, while a change to salvo_oapi_macros.parse_utils can't break salvo_oapi_macros.feature.
Position
Below the diagonal: salvo_oapi_macros.parse_utils uses a module listed above it, which is the healthy direction.
14→16 salvo_oapi_macros.parse_utils uses salvo_oapi_macros.feature.attributespart of a loop✕
Connections
2 pairs of types, where a type in salvo_oapi_macros.parse_utils uses a type in salvo_oapi_macros.feature.attributes.
salvo_oapi_macros.parse_utils uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi_macros.parse_utils, while a change to salvo_oapi_macros.parse_utils can't break salvo_oapi_macros.feature.attributes.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
salvo_core.http.request uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.depot.
Position
Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
salvo_core.http.request uses salvo_core.extract.metadata, so a change to salvo_core.extract.metadata can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.extract.metadata.
Position
Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
salvo_core.http.request uses salvo_core.fuse, so a change to salvo_core.fuse can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.fuse.
Position
Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
salvo_core.http.request uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.http.response.
Position
Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
salvo_core.http.request uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
salvo_core.http.request uses salvo_core.http.form, so a change to salvo_core.http.form can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.http.form.
Position
Below the diagonal: salvo_core.http.request uses a module listed above it, which is the healthy direction.
15→18 salvo_core.http.request uses salvo_core.handlerpart of a loop✕
Connections
1 pair of types, where a type in salvo_core.http.request uses a type in salvo_core.handler.
salvo_core.http.request uses salvo_core.handler, so a change to salvo_core.handler can break salvo_core.http.request, while a change to salvo_core.http.request can't break salvo_core.handler.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
salvo_oapi_macros.feature.attributes uses salvo_oapi_macros.shared, so a change to salvo_oapi_macros.shared can break salvo_oapi_macros.feature.attributes, while a change to salvo_oapi_macros.feature.attributes can't break salvo_oapi_macros.shared.
Position
Below the diagonal: salvo_oapi_macros.feature.attributes uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.feature.attributes uses salvo_oapi_macros.schema_type, so a change to salvo_oapi_macros.schema_type can break salvo_oapi_macros.feature.attributes, while a change to salvo_oapi_macros.feature.attributes can't break salvo_oapi_macros.schema_type.
Position
Below the diagonal: salvo_oapi_macros.feature.attributes uses a module listed above it, which is the healthy direction.
71 pairs of types, where a type in salvo_oapi_macros.feature.attributes uses a type in salvo_oapi_macros.feature. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
salvo_oapi_macros.feature.attributes uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.feature.attributes, while a change to salvo_oapi_macros.feature.attributes can't break salvo_oapi_macros.feature.
Position
Below the diagonal: salvo_oapi_macros.feature.attributes uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.feature.attributes uses salvo_oapi_macros.parse_utils, so a change to salvo_oapi_macros.parse_utils can break salvo_oapi_macros.feature.attributes, while a change to salvo_oapi_macros.feature.attributes can't break salvo_oapi_macros.parse_utils.
Position
Below the diagonal: salvo_oapi_macros.feature.attributes uses a module listed above it, which is the healthy direction.
salvo_core.extract uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.extract, while a change to salvo_core.extract can't break salvo_core.depot.
Position
Below the diagonal: salvo_core.extract uses a module listed above it, which is the healthy direction.
salvo_core.extract uses salvo_core.extract.metadata, so a change to salvo_core.extract.metadata can break salvo_core.extract, while a change to salvo_core.extract can't break salvo_core.extract.metadata.
Position
Below the diagonal: salvo_core.extract uses a module listed above it, which is the healthy direction.
salvo_core.extract uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.extract, while a change to salvo_core.extract can't break salvo_core.http.request.
Position
Below the diagonal: salvo_core.extract uses a module listed above it, which is the healthy direction.
salvo_core.handler uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.handler, while a change to salvo_core.handler can't break salvo_core.depot.
Position
Below the diagonal: salvo_core.handler uses a module listed above it, which is the healthy direction.
salvo_core.handler uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.handler, while a change to salvo_core.handler can't break salvo_core.http.response.
Position
Below the diagonal: salvo_core.handler uses a module listed above it, which is the healthy direction.
salvo_core.handler uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_core.handler, while a change to salvo_core.handler can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_core.handler uses a module listed above it, which is the healthy direction.
salvo_core.handler uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.handler, while a change to salvo_core.handler can't break salvo_core.http.request.
Position
Below the diagonal: salvo_core.handler uses a module listed above it, which is the healthy direction.
salvo_core.routing.filters uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.routing.filters, while a change to salvo_core.routing.filters can't break salvo_core.http.request.
Position
Below the diagonal: salvo_core.routing.filters uses a module listed above it, which is the healthy direction.
salvo_core.routing.router uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.routing.router, while a change to salvo_core.routing.router can't break salvo_core.http.response.
Position
Below the diagonal: salvo_core.routing.router uses a module listed above it, which is the healthy direction.
salvo_core.routing.router uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.routing.router, while a change to salvo_core.routing.router can't break salvo_core.http.request.
Position
Below the diagonal: salvo_core.routing.router uses a module listed above it, which is the healthy direction.
salvo_core.writing uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.writing, while a change to salvo_core.writing can't break salvo_core.depot.
Position
Below the diagonal: salvo_core.writing uses a module listed above it, which is the healthy direction.
salvo_core.writing uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.writing, while a change to salvo_core.writing can't break salvo_core.http.response.
Position
Below the diagonal: salvo_core.writing uses a module listed above it, which is the healthy direction.
salvo_core.writing uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.writing, while a change to salvo_core.writing can't break salvo_core.http.request.
Position
Below the diagonal: salvo_core.writing uses a module listed above it, which is the healthy direction.
salvo_cors.inner uses salvo_core.depot, so a change to salvo_core.depot can break salvo_cors.inner, while a change to salvo_cors.inner can't break salvo_core.depot.
Position
Below the diagonal: salvo_cors.inner uses a module listed above it, which is the healthy direction.
salvo_cors.inner uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_cors.inner, while a change to salvo_cors.inner can't break salvo_core.http.request.
Position
Below the diagonal: salvo_cors.inner uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi.schema.array uses salvo_oapi.openapi.schema.object, so a change to salvo_oapi.openapi.schema.object can break salvo_oapi.openapi.schema.array, while a change to salvo_oapi.openapi.schema.array can't break salvo_oapi.openapi.schema.object.
Position
Below the diagonal: salvo_oapi.openapi.schema.array uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi.schema.array uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi.openapi.schema.array, while a change to salvo_oapi.openapi.schema.array can't break salvo_oapi_macros.feature.attributes.
Position
Below the diagonal: salvo_oapi.openapi.schema.array uses a module listed above it, which is the healthy direction.
23→31 salvo_oapi.openapi.schema.array uses salvo_oapi.openapi.schemapart of a loop✕
Connections
3 pairs of types, where a type in salvo_oapi.openapi.schema.array uses a type in salvo_oapi.openapi.schema.
salvo_oapi.openapi.schema.array uses salvo_oapi.openapi.schema, so a change to salvo_oapi.openapi.schema can break salvo_oapi.openapi.schema.array, while a change to salvo_oapi.openapi.schema.array can't break salvo_oapi.openapi.schema.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→37 salvo_oapi.openapi.schema.array uses salvo_oapi.openapipart of a loop✕
Connections
3 pairs of types, where a type in salvo_oapi.openapi.schema.array uses a type in salvo_oapi.openapi.
salvo_oapi.openapi.schema.array uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi.openapi.schema.array, while a change to salvo_oapi.openapi.schema.array can't break salvo_oapi.openapi.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
salvo_oapi_macros.component uses salvo_oapi_macros.schema_type, so a change to salvo_oapi_macros.schema_type can break salvo_oapi_macros.component, while a change to salvo_oapi_macros.component can't break salvo_oapi_macros.schema_type.
Position
Below the diagonal: salvo_oapi_macros.component uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.component uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.component, while a change to salvo_oapi_macros.component can't break salvo_oapi_macros.feature.
Position
Below the diagonal: salvo_oapi_macros.component uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.component uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi_macros.component, while a change to salvo_oapi_macros.component can't break salvo_oapi_macros.feature.attributes.
Position
Below the diagonal: salvo_oapi_macros.component uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.parameter.derive uses salvo_core.extract.metadata, so a change to salvo_core.extract.metadata can break salvo_oapi_macros.parameter.derive, while a change to salvo_oapi_macros.parameter.derive can't break salvo_core.extract.metadata.
Position
Below the diagonal: salvo_oapi_macros.parameter.derive uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.parameter.derive uses salvo_oapi_macros.shared, so a change to salvo_oapi_macros.shared can break salvo_oapi_macros.parameter.derive, while a change to salvo_oapi_macros.parameter.derive can't break salvo_oapi_macros.shared.
Position
Below the diagonal: salvo_oapi_macros.parameter.derive uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.parameter.derive uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.parameter.derive, while a change to salvo_oapi_macros.parameter.derive can't break salvo_oapi_macros.feature.
Position
Below the diagonal: salvo_oapi_macros.parameter.derive uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.parameter.derive uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi_macros.parameter.derive, while a change to salvo_oapi_macros.parameter.derive can't break salvo_oapi_macros.feature.attributes.
Position
Below the diagonal: salvo_oapi_macros.parameter.derive uses a module listed above it, which is the healthy direction.
salvo_core.catcher uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.conn.ctrl.
Position
Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
salvo_core.catcher uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.depot.
Position
Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
salvo_core.catcher uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.http.response.
Position
Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
salvo_core.catcher uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
salvo_core.catcher uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.http.request.
Position
Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
salvo_core.catcher uses salvo_core.handler, so a change to salvo_core.handler can break salvo_core.catcher, while a change to salvo_core.catcher can't break salvo_core.handler.
Position
Below the diagonal: salvo_core.catcher uses a module listed above it, which is the healthy direction.
salvo_core.error uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.error, while a change to salvo_core.error can't break salvo_core.http.response.
Position
Below the diagonal: salvo_core.error uses a module listed above it, which is the healthy direction.
salvo_core.error uses salvo_core.writing, so a change to salvo_core.writing can break salvo_core.error, while a change to salvo_core.error can't break salvo_core.writing.
Position
Below the diagonal: salvo_core.error uses a module listed above it, which is the healthy direction.
salvo_cors uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_cors, while a change to salvo_cors can't break salvo_core.http.response.
Position
Below the diagonal: salvo_cors uses a module listed above it, which is the healthy direction.
salvo_cors uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_cors, while a change to salvo_cors can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_cors uses a module listed above it, which is the healthy direction.
salvo_cors uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_cors, while a change to salvo_cors can't break salvo_core.http.request.
Position
Below the diagonal: salvo_cors uses a module listed above it, which is the healthy direction.
salvo_cors uses salvo_core.handler, so a change to salvo_core.handler can break salvo_cors, while a change to salvo_cors can't break salvo_core.handler.
Position
Below the diagonal: salvo_cors uses a module listed above it, which is the healthy direction.
salvo_csrf uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_csrf, while a change to salvo_csrf can't break salvo_core.http.response.
Position
Below the diagonal: salvo_csrf uses a module listed above it, which is the healthy direction.
salvo_csrf uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_csrf, while a change to salvo_csrf can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_csrf uses a module listed above it, which is the healthy direction.
salvo_csrf uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_csrf, while a change to salvo_csrf can't break salvo_core.http.request.
Position
Below the diagonal: salvo_csrf uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in salvo_csrf uses a type in salvo_core.handler.
The types involved
salvo_csrf.Csrf → salvo_core.handler.Handler
Direction
salvo_csrf uses salvo_core.handler, so a change to salvo_core.handler can break salvo_csrf, while a change to salvo_csrf can't break salvo_core.handler.
Position
Below the diagonal: salvo_csrf uses a module listed above it, which is the healthy direction.
salvo_flash uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_flash, while a change to salvo_flash can't break salvo_core.http.response.
Position
Below the diagonal: salvo_flash uses a module listed above it, which is the healthy direction.
salvo_flash uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_flash, while a change to salvo_flash can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_flash uses a module listed above it, which is the healthy direction.
salvo_flash uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_flash, while a change to salvo_flash can't break salvo_core.http.request.
Position
Below the diagonal: salvo_flash uses a module listed above it, which is the healthy direction.
salvo_flash uses salvo_core.handler, so a change to salvo_core.handler can break salvo_flash, while a change to salvo_flash can't break salvo_core.handler.
Position
Below the diagonal: salvo_flash uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi.schema uses salvo_oapi.openapi.schema.object, so a change to salvo_oapi.openapi.schema.object can break salvo_oapi.openapi.schema, while a change to salvo_oapi.openapi.schema can't break salvo_oapi.openapi.schema.object.
Position
Below the diagonal: salvo_oapi.openapi.schema uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi.schema uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi.openapi.schema, while a change to salvo_oapi.openapi.schema can't break salvo_oapi_macros.feature.attributes.
Position
Below the diagonal: salvo_oapi.openapi.schema uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi.schema uses salvo_oapi.openapi.schema.array, so a change to salvo_oapi.openapi.schema.array can break salvo_oapi.openapi.schema, while a change to salvo_oapi.openapi.schema can't break salvo_oapi.openapi.schema.array.
Position
Below the diagonal: salvo_oapi.openapi.schema uses a module listed above it, which is the healthy direction.
31→37 salvo_oapi.openapi.schema uses salvo_oapi.openapipart of a loop✕
Connections
1 pair of types, where a type in salvo_oapi.openapi.schema uses a type in salvo_oapi.openapi.
salvo_oapi.openapi.schema uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi.openapi.schema, while a change to salvo_oapi.openapi.schema can't break salvo_oapi.openapi.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
salvo_oapi.swagger_ui uses salvo_core.depot, so a change to salvo_core.depot can break salvo_oapi.swagger_ui, while a change to salvo_oapi.swagger_ui can't break salvo_core.depot.
Position
Below the diagonal: salvo_oapi.swagger_ui uses a module listed above it, which is the healthy direction.
salvo_oapi.swagger_ui uses salvo_oapi.openapi.response, so a change to salvo_oapi.openapi.response can break salvo_oapi.swagger_ui, while a change to salvo_oapi.swagger_ui can't break salvo_oapi.openapi.response.
Position
Below the diagonal: salvo_oapi.swagger_ui uses a module listed above it, which is the healthy direction.
salvo_oapi.swagger_ui uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_oapi.swagger_ui, while a change to salvo_oapi.swagger_ui can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_oapi.swagger_ui uses a module listed above it, which is the healthy direction.
salvo_oapi.swagger_ui uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_oapi.swagger_ui, while a change to salvo_oapi.swagger_ui can't break salvo_core.http.request.
Position
Below the diagonal: salvo_oapi.swagger_ui uses a module listed above it, which is the healthy direction.
salvo_oapi.swagger_ui uses salvo_core.handler, so a change to salvo_core.handler can break salvo_oapi.swagger_ui, while a change to salvo_oapi.swagger_ui can't break salvo_core.handler.
Position
Below the diagonal: salvo_oapi.swagger_ui uses a module listed above it, which is the healthy direction.
salvo_oapi.swagger_ui uses salvo_core.routing.router, so a change to salvo_core.routing.router can break salvo_oapi.swagger_ui, while a change to salvo_oapi.swagger_ui can't break salvo_core.routing.router.
Position
Below the diagonal: salvo_oapi.swagger_ui uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.endpoint.attr uses salvo_oapi_macros.shared, so a change to salvo_oapi_macros.shared can break salvo_oapi_macros.endpoint.attr, while a change to salvo_oapi_macros.endpoint.attr can't break salvo_oapi_macros.shared.
Position
Below the diagonal: salvo_oapi_macros.endpoint.attr uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.endpoint.attr uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.endpoint.attr, while a change to salvo_oapi_macros.endpoint.attr can't break salvo_oapi_macros.feature.
Position
Below the diagonal: salvo_oapi_macros.endpoint.attr uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.endpoint.attr uses salvo_oapi_macros.parse_utils, so a change to salvo_oapi_macros.parse_utils can break salvo_oapi_macros.endpoint.attr, while a change to salvo_oapi_macros.endpoint.attr can't break salvo_oapi_macros.parse_utils.
Position
Below the diagonal: salvo_oapi_macros.endpoint.attr uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.endpoint.attr uses salvo_oapi_macros.parameter.derive, so a change to salvo_oapi_macros.parameter.derive can break salvo_oapi_macros.endpoint.attr, while a change to salvo_oapi_macros.endpoint.attr can't break salvo_oapi_macros.parameter.derive.
Position
Below the diagonal: salvo_oapi_macros.endpoint.attr uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.schema.struct_schemas uses salvo_core.extract.metadata, so a change to salvo_core.extract.metadata can break salvo_oapi_macros.schema.struct_schemas, while a change to salvo_oapi_macros.schema.struct_schemas can't break salvo_core.extract.metadata.
Position
Below the diagonal: salvo_oapi_macros.schema.struct_schemas uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.schema.struct_schemas uses salvo_oapi_macros.shared, so a change to salvo_oapi_macros.shared can break salvo_oapi_macros.schema.struct_schemas, while a change to salvo_oapi_macros.schema.struct_schemas can't break salvo_oapi_macros.shared.
Position
Below the diagonal: salvo_oapi_macros.schema.struct_schemas uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.schema.struct_schemas uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.schema.struct_schemas, while a change to salvo_oapi_macros.schema.struct_schemas can't break salvo_oapi_macros.feature.
Position
Below the diagonal: salvo_oapi_macros.schema.struct_schemas uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.schema.struct_schemas uses salvo_oapi_macros.parse_utils, so a change to salvo_oapi_macros.parse_utils can break salvo_oapi_macros.schema.struct_schemas, while a change to salvo_oapi_macros.schema.struct_schemas can't break salvo_oapi_macros.parse_utils.
Position
Below the diagonal: salvo_oapi_macros.schema.struct_schemas uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.schema.struct_schemas uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi_macros.schema.struct_schemas, while a change to salvo_oapi_macros.schema.struct_schemas can't break salvo_oapi_macros.feature.attributes.
Position
Below the diagonal: salvo_oapi_macros.schema.struct_schemas uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.schema.struct_schemas uses salvo_oapi_macros.component, so a change to salvo_oapi_macros.component can break salvo_oapi_macros.schema.struct_schemas, while a change to salvo_oapi_macros.schema.struct_schemas can't break salvo_oapi_macros.component.
Position
Below the diagonal: salvo_oapi_macros.schema.struct_schemas uses a module listed above it, which is the healthy direction.
salvo_proxy uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_proxy, while a change to salvo_proxy can't break salvo_core.conn.ctrl.
Position
Below the diagonal: salvo_proxy uses a module listed above it, which is the healthy direction.
salvo_proxy uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_proxy, while a change to salvo_proxy can't break salvo_core.http.response.
Position
Below the diagonal: salvo_proxy uses a module listed above it, which is the healthy direction.
salvo_proxy uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_proxy, while a change to salvo_proxy can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_proxy uses a module listed above it, which is the healthy direction.
salvo_proxy uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_proxy, while a change to salvo_proxy can't break salvo_core.http.request.
Position
Below the diagonal: salvo_proxy uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in salvo_proxy uses a type in salvo_core.handler.
The types involved
salvo_proxy.Proxy → salvo_core.handler.Handler
Direction
salvo_proxy uses salvo_core.handler, so a change to salvo_core.handler can break salvo_proxy, while a change to salvo_proxy can't break salvo_core.handler.
Position
Below the diagonal: salvo_proxy uses a module listed above it, which is the healthy direction.
salvo_core.service uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.conn.ctrl.
Position
Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
salvo_core.service uses salvo_core.depot, so a change to salvo_core.depot can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.depot.
Position
Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
salvo_core.service uses salvo_core.fuse, so a change to salvo_core.fuse can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.fuse.
Position
Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
salvo_core.service uses salvo_core.http.response, so a change to salvo_core.http.response can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.http.response.
Position
Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
salvo_core.service uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
salvo_core.service uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.http.request.
Position
Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
salvo_core.service uses salvo_core.handler, so a change to salvo_core.handler can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.handler.
Position
Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
salvo_core.service uses salvo_core.routing.router, so a change to salvo_core.routing.router can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.routing.router.
Position
Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
salvo_core.service uses salvo_core.catcher, so a change to salvo_core.catcher can break salvo_core.service, while a change to salvo_core.service can't break salvo_core.catcher.
Position
Below the diagonal: salvo_core.service uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi uses salvo_core.depot, so a change to salvo_core.depot can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.depot.
Position
Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi uses salvo_oapi.openapi.response, so a change to salvo_oapi.openapi.response can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_oapi.openapi.response.
Position
Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi uses salvo_oapi.openapi.schema.object, so a change to salvo_oapi.openapi.schema.object can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_oapi.openapi.schema.object.
Position
Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi uses salvo_core.routing.flow_ctrl, so a change to salvo_core.routing.flow_ctrl can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.routing.flow_ctrl.
Position
Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi uses salvo_core.http.request, so a change to salvo_core.http.request can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.http.request.
Position
Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_oapi_macros.feature.attributes.
Position
Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi uses salvo_core.handler, so a change to salvo_core.handler can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.handler.
Position
Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi uses salvo_core.routing.router, so a change to salvo_core.routing.router can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_core.routing.router.
Position
Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi uses salvo_oapi.openapi.schema.array, so a change to salvo_oapi.openapi.schema.array can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_oapi.openapi.schema.array.
Position
Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi uses salvo_oapi.openapi.schema, so a change to salvo_oapi.openapi.schema can break salvo_oapi.openapi, while a change to salvo_oapi.openapi can't break salvo_oapi.openapi.schema.
Position
Below the diagonal: salvo_oapi.openapi uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.operation uses salvo_oapi_macros.shared, so a change to salvo_oapi_macros.shared can break salvo_oapi_macros.operation, while a change to salvo_oapi_macros.operation can't break salvo_oapi_macros.shared.
Position
Below the diagonal: salvo_oapi_macros.operation uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.operation uses salvo_oapi_macros.feature, so a change to salvo_oapi_macros.feature can break salvo_oapi_macros.operation, while a change to salvo_oapi_macros.operation can't break salvo_oapi_macros.feature.
Position
Below the diagonal: salvo_oapi_macros.operation uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.operation uses salvo_oapi_macros.feature.attributes, so a change to salvo_oapi_macros.feature.attributes can break salvo_oapi_macros.operation, while a change to salvo_oapi_macros.operation can't break salvo_oapi_macros.feature.attributes.
Position
Below the diagonal: salvo_oapi_macros.operation uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.operation uses salvo_oapi_macros.parameter.derive, so a change to salvo_oapi_macros.parameter.derive can break salvo_oapi_macros.operation, while a change to salvo_oapi_macros.operation can't break salvo_oapi_macros.parameter.derive.
Position
Below the diagonal: salvo_oapi_macros.operation uses a module listed above it, which is the healthy direction.
salvo_oapi_macros.operation uses salvo_oapi_macros.endpoint.attr, so a change to salvo_oapi_macros.endpoint.attr can break salvo_oapi_macros.operation, while a change to salvo_oapi_macros.operation can't break salvo_oapi_macros.endpoint.attr.
Position
Below the diagonal: salvo_oapi_macros.operation uses a module listed above it, which is the healthy direction.
salvo_core.conn uses salvo_core.conn.ctrl, so a change to salvo_core.conn.ctrl can break salvo_core.conn, while a change to salvo_core.conn can't break salvo_core.conn.ctrl.
Position
Below the diagonal: salvo_core.conn uses a module listed above it, which is the healthy direction.
salvo_core.conn uses salvo_core.fuse, so a change to salvo_core.fuse can break salvo_core.conn, while a change to salvo_core.conn can't break salvo_core.fuse.
Position
Below the diagonal: salvo_core.conn uses a module listed above it, which is the healthy direction.
salvo_core.conn uses salvo_core.conn.proto, so a change to salvo_core.conn.proto can break salvo_core.conn, while a change to salvo_core.conn can't break salvo_core.conn.proto.
Position
Below the diagonal: salvo_core.conn uses a module listed above it, which is the healthy direction.
salvo_core.conn uses salvo_core.service, so a change to salvo_core.service can break salvo_core.conn, while a change to salvo_core.conn can't break salvo_core.service.
Position
Below the diagonal: salvo_core.conn uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi.operation uses salvo_oapi.openapi.response, so a change to salvo_oapi.openapi.response can break salvo_oapi.openapi.operation, while a change to salvo_oapi.openapi.operation can't break salvo_oapi.openapi.response.
Position
Below the diagonal: salvo_oapi.openapi.operation uses a module listed above it, which is the healthy direction.
salvo_oapi.openapi.operation uses salvo_oapi.openapi, so a change to salvo_oapi.openapi can break salvo_oapi.openapi.operation, while a change to salvo_oapi.openapi.operation can't break salvo_oapi.openapi.
Position
Below the diagonal: salvo_oapi.openapi.operation uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A07:2025 — Authentication Failures
13
High / Critical
A05:2025 — Injection
4
High / Critical
A03:2025 — Software Supply Chain Failures
4
Medium
Roadmap
Top priorities: Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place; 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; 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place.
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.
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.
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.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 16
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.
Serious — 376
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.
Minor — 48
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 23
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 49 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.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 49 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
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, 425 of 440 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
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.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`codecov/codecov-action`) shows coverage is measured in your own CI.
D10 Test 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. The 1 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 283 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs, .js) and this repository declares a Cargo test suite (repository root, 331 test files), but it was not re-run: its build outgrew the 12 GB scratch ceiling (12.488 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (98 contributor(s) across 4055 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 97 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — 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.
D21 Naming 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
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.
D32 Data Compliance (PII/GDPR) — 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. `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-standalone-preset.js`, `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui.js` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
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.
AXR1 Runtime accessibility — 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. Render strategy: boot via DockerCompose (examples/db-postgres-sea-orm/docker-compose.yml). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c cargo build --release --target-dir target" did not complete successfully: exit code: 101; runtime evidence skipped.
ED5 Idempotency — not measured this run — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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 the 5 JavaScript/TypeScript file(s) found looked minified or bundled, which this check does not read, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
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
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
36 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was StaticDir::handle at 59. A further 9 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Feature::fmt at 47 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/oapi-macros/src/feature.rs (Feature::fmt at 47), crates/core/src/http/errors/status_error.rs (StatusError::from_code at 40), crates/oapi-macros/src/schema_type.rs (Variant::parse at 30), crates/tus/src/error.rs (TusError::status at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 28 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 36 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with StaticDir::handle (cyclomatic 59), salvo_tus::handlers::post::create (cyclomatic 53), RequestDeserializer::fill_value (cyclomatic 52). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 36 together lifts Cyclomatic Complexity from 6.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 50 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with RequestDeserializer::fill_value (cognitive 183), StaticDir::handle (cognitive 177). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.4 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 12 MethodTooLong finding(s) in God Classes — start with enum_schemas.rs (4), struct_schemas.rs, component.rs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 12 FileTooLong finding(s) in God Classes — start with enum_schemas.rs, path.rs, request.rs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 7 FunctionTooLong finding(s) in God Classes — start with post.rs, patch.rs, extract.rs. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
122 duplicated block group(s) detected. 4.2 % of the production lines (4,405 of 103,724) are in a reported copy. A further 56 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 87 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with craft.rs (2), handshake.rs, enum_variant.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with path.rs, patch.rs, disk.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with openapi.rs (2), req.rs, encoder.rs. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.3 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
22 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 17 of the 22 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: salvo-serde-util · ×2
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with stream.rs, openapi.rs, router.rs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests. Measured on the JavaScript/TypeScript suite only — at least 283 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
0 outdated, 0 yanked direct Cargo dependencies. 100 of 131 direct crates were graded against crates.io (0 not published there, 31 not resolved by a committed Cargo.lock). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 718 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 20 Hotspot finding(s) in Churn × Complexity Hotspots — start with lib.rs (2), dir.rs, named_file.rs. — One of this dimension's main actionable groups (20 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
14 deducted task-comment markers across 103724 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 13 TodoComment finding(s) in Explicit Debt — start with client.rs (4), main.rs, head.rs. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with enum_schemas.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
9 finding(s): 0 critical, 9 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
4 finding(s): 0 critical, 3 high, 0 medium, 1 low. semgrep hit a parse error in 4 file(s) — `crates/core/src/extract/parameter/cookie.rs` (line 15), `crates/core/src/http/response.rs` (line 278, lines 278–280, lines 281–282, …), `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-standalone-preset.js`, `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui.js` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
1 of 245 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/cors/src/inner.rs. Counted over 245 of the 280 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned files with no living knowledge
Orphaned filecrates/cors/src/inner.rs:1
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 6 Change coupling finding(s) in Change Coupling — start with listener.rs (2), config.rs, named_file.rs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with cookie.rs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with listener.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Other · Event-Driven — Whether event/message handlers avoid synchronous blocking waits — a blocking wait inside a handler stalls throughput and risks deadlock.
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
`Timeout.handle` is an event/message handler that blocks the executor on a synchronous wait (`block_on`/`blocking_recv`/`thread::sleep`/a blocking `recv()`) — it stalls the handler and serialises throughput, and on an async runtime can starve the reactor. Either move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`, if the result isn't needed inline) or make the handler itself `async` so it can `.await`. — crates/extra/src/timeout.rs:124
What to do
Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability8.8 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 17/18 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:7
What to do
Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Read from this repository's Rust source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (`.serve_connection(` (crates/core/src/conn/proto.rs:161)), so its Rust source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Rust spelling appears in production source, not proven on every route. A Rocket 0.5 application is credited the headers Rocket's default `Shield` sends unless it attaches its own, and its cookie jar's SameSite=Strict default; a session middleware its default cookie flags.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
Set: X-Content-Type-Options. Missing: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.5 on this card.) The server: `.serve_connection(` (crates/core/src/conn/proto.rs:161).
What to do
Add Content-Security-Policy, Strict-Transport-Security, X-Frame-Options beside the headers the Rust server already sets.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`warn!` at line 266 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:266
`warn!` at line 307 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:307
`warn!` at line 442 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:442
`warn!` 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: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:477
`warn!` at line 493 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:493
`warn!` at line 504 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/stores/disk.rs:504
`info!` at line 111 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/handlers/patch.rs:111
`info!` at line 266 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tus/src/handlers/post.rs:266
`error!` at line 171 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/serve-static/src/embed.rs:171
`error!` at line 379 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/oapi/src/naming.rs:379
`warn!` at line 733 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/oapi/src/openapi.rs:733
`debug!` at line 330 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/jwt-auth/src/oidc.rs:330
`debug!` at line 420 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/jwt-auth/src/oidc/cache.rs:420
`error!` 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: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/extra/src/concurrency_limiter.rs:142
`error!` at line 308 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/extra/src/sse.rs:308
`debug!` at line 553 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/extra/src/websocket.rs:553
`error!` at line 608 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/cors/src/lib.rs:608
`warn!` at line 149 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/catcher.rs:149
`info!` at line 391 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/server.rs:391
`info!` at line 516 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/server.rs:516
`info!` at line 568 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/server.rs:568
`error!` at line 290 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/serde/request.rs:290
`info!` at line 278 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/conn/proto.rs:278
`error!` at line 188 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/conn/quinn/builder.rs:188
`debug!` at line 260 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/conn/quinn/builder.rs:260
`error!` at line 305 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/conn/quinn/builder.rs:305
`info!` at line 393 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/core/src/conn/quinn/client.rs:393
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 65 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c cargo build --release --target-dir target" did not complete successfully: exit code: 101; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — D21 withholds its sibling role token rows: 2 candidate(s) found and not reported.
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; comments in this repository's .py, .rs source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Rust suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (112 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — Not assessed, and this one is on us: 44 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
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
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. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Blocking wait inside a handler: Timeout.handle crates/extra/src/timeout.rs:124— `Timeout.handle` is an event/message handler that blocks the executor on a synchronous wait (`block_on`/`blocking_recv`/`thread::sleep`/a blocking `recv()`) — it stalls the handler and serialises throughput, and on an async runtime can starve the reactor. Either move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`, if the result isn't needed inline) or make the handler itself `async` so it can `.await`.
Hotspot: crates/serve-static/src/dir.rs crates/serve-static/src/dir.rs:526— crates/serve-static/src/dir.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 59 in StaticDir::handle at line 526. 2 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/serve-static/src/dir.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core/src/fs/named_file.rs crates/core/src/fs/named_file.rs:817— crates/core/src/fs/named_file.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in NamedFile::send_with_method at line 817. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/core/src/fs/named_file.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/compression/src/lib.rs crates/compression/src/lib.rs:504— crates/compression/src/lib.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in Compression::handle at line 504. 2 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/compression/src/lib.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tus/src/handlers/post.rs crates/tus/src/handlers/post.rs:22— crates/tus/src/handlers/post.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in salvo_tus::handlers::post::create at line 22. 2 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/tus/src/handlers/post.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/serve-static/src/embed.rs crates/serve-static/src/embed.rs:106— crates/serve-static/src/embed.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in salvo_serve_static::embed::render_embedded_data at line 106. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/serve-static/src/embed.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core/src/service.rs crates/core/src/service.rs:268— crates/core/src/service.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in HyperHandler::handle at line 268. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/core/src/service.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tus/src/handlers/patch.rs crates/tus/src/handlers/patch.rs:18— crates/tus/src/handlers/patch.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in salvo_tus::handlers::patch::patch at line 18. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/tus/src/handlers/patch.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/oapi-macros/src/schema/struct_schemas.rs crates/oapi-macros/src/schema/struct_schemas.rs:179— crates/oapi-macros/src/schema/struct_schemas.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in NamedStructSchema::try_to_tokens at line 179. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/oapi-macros/src/schema/struct_schemas.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/oapi/src/openapi.rs crates/oapi/src/openapi.rs:628— crates/oapi/src/openapi.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in OpenApi::merge_norm_node at line 628. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/oapi/src/openapi.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/oapi-macros/src/parameter/derive.rs crates/oapi-macros/src/parameter/derive.rs:67— crates/oapi-macros/src/parameter/derive.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in ToParameters::try_to_tokens at line 67. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/oapi-macros/src/parameter/derive.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core/src/conn/quinn/builder.rs crates/core/src/conn/quinn/builder.rs:105— crates/core/src/conn/quinn/builder.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in Builder::serve_connection at line 105. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/core/src/conn/quinn/builder.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core/src/writing/seek.rs crates/core/src/writing/seek.rs:77— crates/core/src/writing/seek.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in ReadSeeker::send_inner at line 77. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/core/src/writing/seek.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/macros/src/extract.rs crates/macros/src/extract.rs:274— crates/macros/src/extract.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in salvo_macros::extract::generate at line 274. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/macros/src/extract.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/craft-macros/src/craft.rs crates/craft-macros/src/craft.rs:141— crates/craft-macros/src/craft.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in salvo_craft_macros::craft::rewrite_method at line 141. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/craft-macros/src/craft.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/oapi-macros/src/operation.rs crates/oapi-macros/src/operation.rs:115— crates/oapi-macros/src/operation.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Operation::modifiers at line 115. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/oapi-macros/src/operation.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/jwt-auth/src/oidc/cache.rs crates/jwt-auth/src/oidc/cache.rs:65— crates/jwt-auth/src/oidc/cache.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in CachePolicy::parse_bytes at line 65. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/jwt-auth/src/oidc/cache.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/oapi/src/routing.rs crates/oapi/src/routing.rs:105— crates/oapi/src/routing.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in NormNode::with_method at line 105. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/oapi/src/routing.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/core/src/server.rs crates/core/src/server.rs:366— crates/core/src/server.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in Server::try_serve at line 366. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/core/src/server.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/otel/src/tracing.rs crates/otel/src/tracing.rs:119— crates/otel/src/tracing.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Tracing::handle at line 119. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/otel/src/tracing.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/serde-util/src/lib.rs crates/serde-util/src/lib.rs:90— crates/serde-util/src/lib.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SerdeValue::parse at line 90. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 04:10:41 +08:00' --until='2026-11-15 04:10:41 +08:00' --full-history --no-merges -- crates/serde-util/src/lib.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
TodoComment examples/todos-utoipa/src/main.rs:241— /// Todo not found from storage — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tus/src/handlers/head.rs:73— // TODO: Time handle — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tus/src/handlers/patch.rs:103— // TODO: Time handle — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/otel/src/tracing.rs:126— // TODO: Will remove after opentelemetry_http updated — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/oapi-macros/src/component.rs:635— // TODO: refs support `summary` field but currently there is no such — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/oapi-macros/src/type_tree.rs:261— // TODO should we recognize unknown generic types with `GenericType::Unknown` instead of `None`? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/oapi-macros/src/schema/enum_schemas.rs:539— // TODO need to be able to split variant.attrs for variant and the struct representation! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/oapi/src/openapi/schema.rs:394— // TODO: REMOVE THE unnecessary description Option wrapping. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/core/src/conn/proto.rs:372— // TODO: There should be a way to do following two lines cleaner... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/core/src/conn/quinn/client.rs:523— /// TODO: If data is polled before the response has been received, an error will be thrown. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/core/src/conn/quinn/client.rs:525— /// TODO: If trailers are polled but the body hasn't been fully received, an UNEXPECTED_FRAME error will be — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/core/src/conn/quinn/client.rs:637— // TODO what if called before recv_response ? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/core/src/conn/quinn/client.rs:655— // TODO take by value to prevent any further call as this request is cancelled — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
MethodTooLong: NamedStructSchema.try_to_tokens crates/oapi-macros/src/schema/struct_schemas.rs:179— MethodTooLong — try_to_tokens runs 260 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 160 over it, 2.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ComponentSchema.non_generic_to_tokens crates/oapi-macros/src/component.rs:397— MethodTooLong — non_generic_to_tokens runs 225 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StaticDir.handle crates/serve-static/src/dir.rs:526— MethodTooLong — handle runs 190 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NamedFile.send_with_method crates/core/src/fs/named_file.rs:817— MethodTooLong — send_with_method runs 167 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ComplexEnum.tagged_variant_tokens crates/oapi-macros/src/schema/enum_schemas.rs:759— MethodTooLong — tagged_variant_tokens runs 152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ToParameters.try_to_tokens crates/oapi-macros/src/parameter/derive.rs:67— MethodTooLong — try_to_tokens runs 147 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RequestDeserializer.fill_value crates/core/src/serde/request.rs:280— MethodTooLong — fill_value runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EnumSchema.new crates/oapi-macros/src/schema/enum_schemas.rs:63— MethodTooLong — new runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Builder.serve_connection crates/core/src/conn/quinn/builder.rs:105— MethodTooLong — serve_connection runs 137 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ComplexEnum.adjacently_tagged_variant_tokens crates/oapi-macros/src/schema/enum_schemas.rs:964— MethodTooLong — adjacently_tagged_variant_tokens runs 132 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ToSchema.try_to_tokens crates/oapi-macros/src/schema.rs:75— MethodTooLong — try_to_tokens runs 119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ComplexEnum.variant_tokens crates/oapi-macros/src/schema/enum_schemas.rs:531— MethodTooLong — variant_tokens runs 116 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: schema/enum_schemas.rs crates/oapi-macros/src/schema/enum_schemas.rs— FileTooLong — 935 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 435 over it, 1.87× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: filters/path.rs crates/core/src/routing/filters/path.rs— FileTooLong — 825 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 325 over it, 1.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: http/request.rs crates/core/src/http/request.rs— FileTooLong — 756 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 86% of them inside a single declaration: Request (4 blocks, 203-1716). The bar is 500 significant lines; this is 256 over it, 1.51× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs crates/oapi/src/lib.rs— FileTooLong — 718 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 218 over it, 1.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/dir.rs crates/serve-static/src/dir.rs— FileTooLong — 697 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 197 over it, 1.39× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: fs/named_file.rs crates/core/src/fs/named_file.rs— FileTooLong — 641 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 141 over it, 1.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: feature/attributes.rs crates/oapi-macros/src/feature/attributes.rs— FileTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 107 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/schema_type.rs crates/oapi-macros/src/schema_type.rs— FileTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 70 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/response.rs crates/oapi-macros/src/response.rs— FileTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 69 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/component.rs crates/oapi-macros/src/component.rs— FileTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: ComponentSchema (3 blocks, 63-732). The bar is 500 significant lines; this is 55 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: schema/struct_schemas.rs crates/oapi-macros/src/schema/struct_schemas.rs— FileTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: NamedStructSchema (3 blocks, 30-551). The bar is 500 significant lines; this is 11 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/openapi.rs crates/oapi/src/openapi.rs— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 67% of them inside a single declaration: OpenApi (3 blocks, 87-790). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Duplicated block (9 lines × 2) crates/core/src/conn/stream/handshake.rs:55— crates/core/src/conn/stream/handshake.rs:55-63 | crates/core/src/conn/stream/handshake.rs:73-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) crates/craft-macros/src/craft.rs:194— crates/craft-macros/src/craft.rs:194-202 | crates/oapi-macros/src/endpoint.rs:43-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/craft-macros/src/craft.rs:194` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/oapi-macros/src/schema/enum_variant.rs:210— crates/oapi-macros/src/schema/enum_variant.rs:210-218 | crates/oapi-macros/src/schema/enum_variant.rs:309-317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) crates/oapi-macros/src/schema/struct_schemas.rs:93— crates/oapi-macros/src/schema/struct_schemas.rs:93-101 | crates/oapi-macros/src/schema/struct_schemas.rs:183-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/oapi/src/openapi.rs:894— crates/oapi/src/openapi.rs:894-902 | crates/oapi/src/openapi.rs:950-958 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi/src/openapi.rs:894` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/rate-limiter/src/lib.rs:350— crates/rate-limiter/src/lib.rs:350-358 | crates/rate-limiter/src/lib.rs:378-386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/rate-limiter/src/lib.rs:350` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/craft-macros/src/craft.rs:196— crates/craft-macros/src/craft.rs:196-204 | crates/craft-macros/src/craft.rs:217-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/craft-macros/src/craft.rs:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/oapi-macros/src/operation/encoding.rs:23— crates/oapi-macros/src/operation/encoding.rs:23-32 | crates/oapi-macros/src/server.rs:20-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/operation/encoding.rs:23` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/oapi/src/openapi/path.rs:147— crates/oapi/src/openapi/path.rs:147-151 | crates/oapi/src/openapi/security.rs:637-641 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi/src/openapi/path.rs:147` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/tus/src/handlers/patch.rs:184— crates/tus/src/handlers/patch.rs:184-188 | crates/tus/src/handlers/post.rs:147-151 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) crates/tus/src/stores/disk.rs:623— crates/tus/src/stores/disk.rs:623-627 | crates/tus/src/stores/disk.rs:629-633 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/core/src/conn/openssl/config.rs:42— crates/core/src/conn/openssl/config.rs:42-46 | crates/core/src/conn/rustls/config.rs:57-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/cors/src/allow_credentials.rs:50— crates/cors/src/allow_credentials.rs:50-54 | crates/cors/src/allow_private_network.rs:49-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/cors/src/allow_credentials.rs:56` calls `pub`, `is_true` and `crates/cors/src/allow_private_network.rs:55` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) crates/cors/src/allow_headers.rs:71— crates/cors/src/allow_headers.rs:71-75 | crates/cors/src/allow_methods.rs:83-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) crates/cors/src/expose_headers.rs:70— crates/cors/src/expose_headers.rs:70-74 | crates/cors/src/max_age.rs:54-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/cors/src/expose_headers.rs:76` calls `pub`, `is_wildcard`, `Exact` and `crates/cors/src/max_age.rs:60` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) crates/macros/src/handler.rs:168— crates/macros/src/handler.rs:168-172 | crates/macros/src/handler.rs:187-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/macros/src/handler.rs:168` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
FunctionTooLong: salvo_tus::handlers::post::create crates/tus/src/handlers/post.rs:22— FunctionTooLong — salvo_tus::handlers::post::create runs 178 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: salvo_tus::handlers::patch::patch crates/tus/src/handlers/patch.rs:18— FunctionTooLong — salvo_tus::handlers::patch::patch runs 169 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: salvo_macros::extract::generate crates/macros/src/extract.rs:274— FunctionTooLong — salvo_macros::extract::generate runs 153 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: salvo_serve_static::embed::render_embedded_data crates/serve-static/src/embed.rs:106— FunctionTooLong — salvo_serve_static::embed::render_embedded_data runs 137 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: salvo_craft_macros::craft::rewrite_method crates/craft-macros/src/craft.rs:141— FunctionTooLong — salvo_craft_macros::craft::rewrite_method runs 121 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: salvo_oapi_macros::endpoint::generate crates/oapi-macros/src/endpoint.rs:173— FunctionTooLong — salvo_oapi_macros::endpoint::generate runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: salvo_oapi_macros::bound::relevant_types crates/oapi-macros/src/bound.rs:57— FunctionTooLong — salvo_oapi_macros::bound::relevant_types runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×7
Edited copy of a member (8 corresponding lines) crates/core/src/http/body/req.rs:205— crates/core/src/http/body/req.rs:205-212 | crates/core/src/http/body/res.rs:231-238 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/compression/src/encoder.rs:62— crates/compression/src/encoder.rs:62-69 | crates/compression/src/encoder.rs:72-79 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/cors/src/inner.rs:77— crates/cors/src/inner.rs:77-85 | crates/cors/src/inner.rs:115-122 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/core/src/extract/parameter/header.rs:113— crates/core/src/extract/parameter/header.rs:113-120 | crates/core/src/extract/parameter/query.rs:99-106 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/oapi/src/openapi.rs:523— crates/oapi/src/openapi.rs:523-530 | crates/oapi/src/openapi/components.rs:185-192 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/oapi/src/openapi.rs:554— crates/oapi/src/openapi.rs:554-561 | crates/oapi/src/openapi/components.rs:214-221 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/csrf/src/lib.rs:328— crates/csrf/src/lib.rs:328-335 | crates/jwt-auth/src/lib.rs:466-473 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) crates/core/src/conn/tcp.rs:198— crates/core/src/conn/tcp.rs:198-205 | crates/core/src/conn/unix.rs:127-134 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) crates/core/src/http/body/req.rs:165— crates/core/src/http/body/req.rs:165-172 | crates/core/src/http/body/res.rs:156-163 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) crates/macros/src/handler.rs:143— crates/macros/src/handler.rs:143-150 | crates/oapi-macros/src/endpoint.rs:360-367 — before extracting anything, compare `crates/macros/src/handler.rs` and `crates/oapi-macros/src/endpoint.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/macros/src/handler.rs:143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/oapi-macros/src/endpoint.rs:368` calls `push` and `crates/macros/src/handler.rs:151` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) crates/oapi/src/openapi/response.rs:42— crates/oapi/src/openapi/response.rs:42-49 | crates/oapi/src/openapi/schema.rs:48-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) crates/cors/src/allow_headers.rs:98— crates/cors/src/allow_headers.rs:98-105 | crates/cors/src/allow_methods.rs:110-117 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cors/src/allow_headers.rs:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/tus/src/handlers/post.rs:232— crates/tus/src/handlers/post.rs:232-241 | crates/tus/src/handlers/post.rs:254-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/tus/src/handlers/post.rs:232` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/core/src/routing/filters/others.rs:180— crates/core/src/routing/filters/others.rs:180-187 | crates/core/src/routing/filters/others.rs:252-259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/macros/src/handler.rs:175— crates/macros/src/handler.rs:175-180 | crates/macros/src/handler.rs:194-199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/macros/src/handler.rs:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/oapi/src/naming.rs:229— crates/oapi/src/naming.rs:229-235 | crates/oapi/src/naming.rs:319-324 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi/src/naming.rs:229` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/oapi/src/naming.rs:325` calls `is_empty`, `push` and `crates/oapi/src/naming.rs:236` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) crates/cache/src/lib.rs:828— crates/cache/src/lib.rs:828-833 | crates/compression/src/lib.rs:668-673 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/oapi/src/rapidoc.rs:117— crates/oapi/src/rapidoc.rs:117-122 | crates/oapi/src/redoc.rs:132-137 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi/src/rapidoc.rs:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/core/src/http/form.rs:267— crates/core/src/http/form.rs:267-272 | crates/core/src/http/request.rs:1003-1008 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) crates/oapi/src/openapi/path.rs:59— crates/oapi/src/openapi/path.rs:59-64 | crates/oapi/src/openapi/schema.rs:101-106 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) crates/core/src/conn/native_tls/listener.rs:64— crates/core/src/conn/native_tls/listener.rs:64-69 | crates/core/src/conn/quinn/listener.rs:74-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Change coupling: listener.rs ↔ listener.rs crates/core/src/conn/native_tls/listener.rs:1— `crates/core/src/conn/native_tls/listener.rs` and `crates/core/src/conn/openssl/listener.rs` change together 91% of the time (31 of the 34 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 31 shared commits counted here, the most recent 3 are `43e9abed` Reload TLS configs in background (#1404); `04d61078` Remove AsyncRead and AsyncWrite constraint from Acceptor (#1181); `bdf8bd3f` Allow TLS without HTTP2 and fallback to HTTP 1.1 (#858) — run `git show` on any of them.
Change coupling: listener.rs ↔ config.rs crates/core/src/conn/native_tls/listener.rs:1— `crates/core/src/conn/native_tls/listener.rs` and `crates/core/src/conn/openssl/config.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `bdf8bd3f` Allow TLS without HTTP2 and fallback to HTTP 1.1 (#858); `7ae657ba` feat!: Acme and Http3 work together! (#384); `617954f1` feat!: Make tls more generic (#380) — run `git show` on any of them.
Change coupling: config.rs ↔ listener.rs crates/core/src/conn/openssl/config.rs:1— `crates/core/src/conn/openssl/config.rs` and `crates/core/src/conn/openssl/listener.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `bdf8bd3f` Allow TLS without HTTP2 and fallback to HTTP 1.1 (#858); `7ae657ba` feat!: Acme and Http3 work together! (#384); `617954f1` feat!: Make tls more generic (#380) — run `git show` on any of them.
Change coupling: named_file.rs ↔ seek.rs crates/core/src/fs/named_file.rs:1— `crates/core/src/fs/named_file.rs` and `crates/core/src/writing/seek.rs` change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `9d9b1c34` Respect HTTP range unit semantics in static responses (#1801); `c24faa81` Ignore Range when serving HEAD representations (#1745); `50a835bf` fix(core): correct conditional-request ordering, multi-range and IPv6… — run `git show` on any of them.
Change coupling: metrics.rs ↔ tracing.rs crates/otel/src/metrics.rs:1— `crates/otel/src/metrics.rs` and `crates/otel/src/tracing.rs` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `e8da0e24` Record OpenTelemetry metrics and spans after response finalization (#…; `ca0748ab` feat(otel)!: follow the OpenTelemetry HTTP semantic conventions (#1700); `ec25bc28` chore(otel): Treat status_code=none as 200(OK) (#927) — run `git show` on any of them.
Change coupling: req.rs ↔ res.rs crates/core/src/http/body/req.rs:1— `crates/core/src/http/body/req.rs` and `crates/core/src/http/body/res.rs` change together 59% of the time (10 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `dc4ea7ca` Document core HTTP types and validate ranges (#1682); `3cca8f64` Improve debug info for `ReqBody` and `ResBody` (#578); `5a954829` Add `BytesFrame` type to wrap `Frame<Bytes>` (#447) — run `git show` on any of them.
Duplicated block (7 lines × 2) crates/oapi-macros/src/operation/request_body.rs:76— crates/oapi-macros/src/operation/request_body.rs:76-82 | crates/oapi-macros/src/schema/xml.rs:35-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/operation/request_body.rs:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/oapi/src/naming.rs:343— crates/oapi/src/naming.rs:343-349 | crates/oapi/src/naming.rs:369-375 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi/src/naming.rs:343` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/core/src/serde/flat_value.rs:126— crates/core/src/serde/flat_value.rs:126-132 | crates/core/src/serde/vec_value.rs:112-118 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/cors/src/allow_headers.rs:139— crates/cors/src/allow_headers.rs:139-145 | crates/cors/src/expose_headers.rs:122-128 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/cors/src/allow_headers.rs:148— crates/cors/src/allow_headers.rs:148-154 | crates/cors/src/expose_headers.rs:131-137 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/macros/src/handler.rs:120— crates/macros/src/handler.rs:120-126 | crates/oapi-macros/src/endpoint.rs:340-346 — before extracting anything, compare `crates/macros/src/handler.rs` and `crates/oapi-macros/src/endpoint.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/macros/src/handler.rs:120` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/macros/src/handler.rs:101— crates/macros/src/handler.rs:101-114 | crates/oapi-macros/src/endpoint.rs:325-338 — before extracting anything, compare `crates/macros/src/handler.rs` and `crates/oapi-macros/src/endpoint.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/macros/src/handler.rs:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:334— crates/oapi-macros/src/schema/enum_schemas.rs:334-347 | crates/oapi-macros/src/schema/enum_schemas.rs:412-425 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:334` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/session/src/lib.rs:155— crates/session/src/lib.rs:155-168 | crates/session/src/lib.rs:398-411 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) crates/core/src/fs/named_file.rs:1109— crates/core/src/fs/named_file.rs:1109-1122 | crates/core/src/writing/seek.rs:232-245 — before extracting anything, compare `crates/core/src/fs/named_file.rs` and `crates/core/src/writing/seek.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) crates/core/src/fs/named_file.rs:1125— crates/core/src/fs/named_file.rs:1125-1138 | crates/core/src/writing/seek.rs:248-261 — before extracting anything, compare `crates/core/src/fs/named_file.rs` and `crates/core/src/writing/seek.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) crates/core/src/conn/quinn/builder.rs:217— crates/core/src/conn/quinn/builder.rs:217-226 | crates/core/src/conn/quinn/builder.rs:241-250 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/core/src/extract/case.rs:115— crates/core/src/extract/case.rs:115-124 | crates/serde-util/src/case.rs:150-159 — before extracting anything, compare `crates/core/src/extract/case.rs` and `crates/serde-util/src/case.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) crates/core/src/http/request.rs:677— crates/core/src/http/request.rs:677-686 | crates/core/src/http/response.rs:183-192 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) crates/oapi-macros/src/schema/enum_variant.rs:230— crates/oapi-macros/src/schema/enum_variant.rs:230-239 | crates/oapi-macros/src/schema/enum_variant.rs:329-338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_variant.rs:230` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/tus/src/handlers/patch.rs:35— crates/tus/src/handlers/patch.rs:35-44 | crates/tus/src/handlers/post.rs:29-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/tus/src/handlers/patch.rs:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Low cohesion: EncodeStream (LCOM4 7) crates/compression/src/stream.rs:21— EncodeStream's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: OpenApi (LCOM4 7) crates/oapi/src/openapi.rs:87— OpenApi's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Router (LCOM4 6) crates/core/src/routing/router.rs:16— Router's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DynStream (LCOM4 4) crates/core/src/conn.rs:518— DynStream's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Cors (LCOM4 4) crates/cors/src/lib.rs:107— Cors's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
TooManyMethods: Request crates/core/src/http/request.rs:203— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Router crates/core/src/routing/router.rs:16— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OpenApi crates/oapi/src/openapi.rs:87— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Object crates/oapi/src/openapi/schema/object.rs:19— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×4
Edited copy of a member (10 corresponding lines) crates/oapi-macros/src/response.rs:449— crates/oapi-macros/src/response.rs:449-465 | crates/oapi-macros/src/schema/feature.rs:259-268 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/core/src/conn/stream/handshake.rs:115— crates/core/src/conn/stream/handshake.rs:115-124 | crates/core/src/conn/stream/handshake.rs:150-159 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/oapi-macros/src/response/link.rs:15— crates/oapi-macros/src/response/link.rs:15-24 | crates/oapi-macros/src/response/link.rs:153-163 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/oapi-macros/src/response.rs:25— crates/oapi-macros/src/response.rs:25-34 | crates/oapi-macros/src/schema.rs:35-44 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) crates/jwt-auth/src/oidc/cache.rs:239— crates/jwt-auth/src/oidc/cache.rs:239-245 | crates/jwt-auth/src/oidc/cache.rs:247-256 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/cors/src/allow_methods.rs:49— crates/cors/src/allow_methods.rs:49-57 | crates/cors/src/allow_headers.rs:39-45 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/core/src/serde/flat_value.rs:97— crates/core/src/serde/flat_value.rs:97-103 | crates/core/src/serde/vec_value.rs:83-89 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/core/src/serde/flat_value.rs:109— crates/core/src/serde/flat_value.rs:109-115 | crates/core/src/serde/vec_value.rs:95-101 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (18 lines × 2) crates/core/src/extract/case.rs:62— crates/core/src/extract/case.rs:62-79 | crates/serde-util/src/case.rs:99-116 — before extracting anything, compare `crates/core/src/extract/case.rs` and `crates/serde-util/src/case.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/extract/case.rs:62` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `variant` to `impl AsRef<str>` in one and `&str` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/serde-util/src/case.rs:98` calls `to_owned` and `crates/core/src/extract/case.rs:61` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) crates/oapi-macros/src/component.rs:139— crates/oapi-macros/src/component.rs:139-156 | crates/oapi-macros/src/component.rs:165-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/component.rs:139` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) crates/oapi-macros/src/response.rs:479— crates/oapi-macros/src/response.rs:479-496 | crates/oapi-macros/src/response.rs:556-573 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/response.rs:556` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) crates/oapi-macros/src/schema/enum_variant.rs:237— crates/oapi-macros/src/schema/enum_variant.rs:237-254 | crates/oapi-macros/src/schema/enum_variant.rs:343-360 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_variant.rs:237` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/oapi/src/openapi/schema/all_of.rs:58— crates/oapi/src/openapi/schema/all_of.rs:58-68 | crates/oapi/src/openapi/schema/one_of.rs:58-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) crates/oapi/src/rapidoc.rs:105— crates/oapi/src/rapidoc.rs:105-115 | crates/oapi/src/redoc.rs:120-130 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) crates/csrf/src/aes_gcm_cipher.rs:81— crates/csrf/src/aes_gcm_cipher.rs:81-91 | crates/csrf/src/ccp_cipher.rs:81-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) crates/core/src/conn/proto.rs:170— crates/core/src/conn/proto.rs:170-182 | crates/core/src/conn/proto.rs:232-242 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/conn/proto.rs:170` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
salvo_tus::handlers::post::create (cyclomatic 53) crates/tus/src/handlers/post.rs:22— salvo_tus::handlers::post::create has cyclomatic complexity 53 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
salvo_tus::handlers::patch::patch (cyclomatic 47) crates/tus/src/handlers/patch.rs:18— salvo_tus::handlers::patch::patch has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
salvo_tus::handlers::head::head (cyclomatic 17) crates/tus/src/handlers/head.rs:15— salvo_tus::handlers::head::head has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RequestDeserializer::fill_value (cognitive 183) crates/core/src/serde/request.rs:280— RequestDeserializer::fill_value has cognitive complexity 183 (threshold 15). Drivers by points: if/else 38 (132 pts), loops 9 (41 pts), match/switch 3 (10 pts) (nesting depth added 133). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestDeserializer::deserialize_value (cognitive 20) crates/core/src/serde/request.rs:202— RequestDeserializer::deserialize_value has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestDeserializer::real_parser (cognitive 16) crates/core/src/serde/request.rs:180— RequestDeserializer::real_parser has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PathParser::scan_wisps (cognitive 73) crates/core/src/routing/filters/path.rs:844— PathParser::scan_wisps has cognitive complexity 73 (threshold 15). Drivers by points: if/else 26 (66 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 44). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PathParser::scan_regex (cognitive 17) crates/core/src/routing/filters/path.rs:761— PathParser::scan_regex has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PathParser::validate (cognitive 16) crates/core/src/routing/filters/path.rs:992— PathParser::validate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
salvo_tus::handlers::patch::patch (cognitive 66) crates/tus/src/handlers/patch.rs:18— salvo_tus::handlers::patch::patch has cognitive complexity 66 (threshold 15). Drivers by points: if/else 27 (40 pts), match/switch 13 (21 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
salvo_tus::handlers::post::create (cognitive 66) crates/tus/src/handlers/post.rs:22— salvo_tus::handlers::post::create has cognitive complexity 66 (threshold 15). Drivers by points: if/else 29 (40 pts), match/switch 11 (17 pts), boolean chains 9 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
salvo_tus::handlers::head::head (cognitive 23) crates/tus/src/handlers/head.rs:15— salvo_tus::handlers::head::head has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (18 pts), match/switch 4 (5 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
salvo_oapi_macros::bound::relevant_types (cognitive 38) crates/oapi-macros/src/bound.rs:57— salvo_oapi_macros::bound::relevant_types has cognitive complexity 38 (threshold 15). Drivers by points: loops 10 (20 pts), match/switch 6 (8 pts), if/else 5 (7 pts), boolean chains 3 (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
salvo_oapi_macros::endpoint::generate (cognitive 18) crates/oapi-macros/src/endpoint.rs:173— salvo_oapi_macros::endpoint::generate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (6 pts), loops 1 (2 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
salvo_oapi_macros::shared::parse_input_type (cognitive 18) crates/oapi-macros/src/shared.rs:55— salvo_oapi_macros::shared::parse_input_type has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (18 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StraightStream::poll_write (cognitive 33) crates/core/src/conn/stream/straight.rs:116— StraightStream::poll_write has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (24 pts), match/switch 2 (5 pts), boolean chains 4 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (StraightStream::poll_write_vectored) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
StraightStream::poll_write_vectored (cognitive 33) crates/core/src/conn/stream/straight.rs:190— StraightStream::poll_write_vectored has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (24 pts), match/switch 2 (5 pts), boolean chains 4 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (StraightStream::poll_write) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
StraightStream::poll_read (cognitive 17) crates/core/src/conn/stream/straight.rs:73— StraightStream::poll_read has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ClassTooLong: Request crates/core/src/http/request.rs:203— ClassTooLong — 647 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 76 methods, 4 blocks, lines 203-1716. The bar is 400 significant lines; this is 247 over it, 1.62× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ComplexEnum crates/oapi-macros/src/schema/enum_schemas.rs:511— ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 3 blocks, lines 511-1234. The bar is 400 significant lines; this is 152 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ComponentSchema crates/oapi-macros/src/component.rs:63— ClassTooLong — 489 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 3 blocks, lines 63-732. The bar is 400 significant lines; this is 89 over it, 1.22× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) crates/core/src/routing/filters/others.rs:177— crates/core/src/routing/filters/others.rs:177-190 | crates/core/src/routing/filters/others.rs:249-264 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/oapi-macros/src/response.rs:257— crates/oapi-macros/src/response.rs:257-270 | crates/oapi-macros/src/response.rs:275-288 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/core/src/routing/filters/opts.rs:45— crates/core/src/routing/filters/opts.rs:45-58 | crates/core/src/routing/filters/opts.rs:73-86 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (26 lines × 2) crates/macros/src/shared.rs:80— crates/macros/src/shared.rs:80-105 | crates/oapi-macros/src/shared.rs:100-125 — before extracting anything, compare `crates/macros/src/shared.rs` and `crates/oapi-macros/src/shared.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 135 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (26 lines × 2) crates/macros/src/shared.rs:117— crates/macros/src/shared.rs:117-142 | crates/oapi-macros/src/shared.rs:133-158 — before extracting anything, compare `crates/macros/src/shared.rs` and `crates/oapi-macros/src/shared.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 135 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/macros/src/shared.rs:117` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `tokens` to `proc_macro2::TokenStream` in one and `TokenStream` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (26 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:545— crates/oapi-macros/src/schema/enum_schemas.rs:545-570 | crates/oapi-macros/src/schema/enum_schemas.rs:593-618 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:545` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) crates/extra/src/tower_compat.rs:122— crates/extra/src/tower_compat.rs:122-137 | crates/extra/src/tower_compat.rs:354-369 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/extra/src/tower_compat.rs:122` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 2) crates/macros/src/extract.rs:312— crates/macros/src/extract.rs:312-327 | crates/oapi-macros/src/parameter/derive.rs:183-198 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:798— crates/oapi-macros/src/schema/enum_schemas.rs:798-813 | crates/oapi-macros/src/schema/enum_schemas.rs:871-886 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:798` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) crates/compression/src/lib.rs:416— crates/compression/src/lib.rs:416-430 | crates/serve-static/src/dir.rs:642-656 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:1015— crates/oapi-macros/src/schema/enum_schemas.rs:1015-1029 | crates/oapi-macros/src/schema/enum_schemas.rs:1069-1083 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:1015` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) crates/oapi-macros/src/schema_type.rs:69— crates/oapi-macros/src/schema_type.rs:69-83 | crates/oapi-macros/src/schema_type.rs:358-372 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema_type.rs:69` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) crates/oapi-macros/src/response.rs:259— crates/oapi-macros/src/response.rs:259-270 | crates/oapi-macros/src/response.rs:277-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/response.rs:259` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/oapi-macros/src/schema.rs:293— crates/oapi-macros/src/schema.rs:293-304 | crates/oapi-macros/src/schema.rs:327-338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) crates/oapi-macros/src/schema/struct_schemas.rs:262— crates/oapi-macros/src/schema/struct_schemas.rs:262-273 | crates/oapi-macros/src/schema/struct_schemas.rs:479-490 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 3) crates/core/src/conn/stream/straight.rs:104— crates/core/src/conn/stream/straight.rs:104-112 | crates/core/src/conn/stream/straight.rs:172-180 | crates/core/src/conn/stream/straight.rs:248-256 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/conn/stream/straight.rs:104` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) crates/oapi-macros/src/response/derive.rs:308— crates/oapi-macros/src/response/derive.rs:308-316 | crates/oapi-macros/src/response/derive.rs:408-416 | crates/oapi-macros/src/response/derive.rs:519-527 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) crates/tus/src/handlers/patch.rs:33— crates/tus/src/handlers/patch.rs:33-41 | crates/tus/src/handlers/post.rs:27-35 | crates/tus/src/method_override.rs:78-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/tus/src/handlers/patch.rs:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×3
JavaScript dependencies are not locked examples/jwt-clerk/package.json:12— examples/jwt-clerk/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked examples/jwt-oidc-clerk/package.json:12— examples/jwt-oidc-clerk/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked examples/proxy-react-app/react-app/package.json:5— examples/proxy-react-app/react-app/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
StraightStream::poll_write (cyclomatic 18) crates/core/src/conn/stream/straight.rs:116— StraightStream::poll_write has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (StraightStream::poll_write_vectored) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
StraightStream::poll_write_vectored (cyclomatic 18) crates/core/src/conn/stream/straight.rs:190— StraightStream::poll_write_vectored has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (StraightStream::poll_write) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
NamedStructSchema::try_to_tokens (cognitive 80) crates/oapi-macros/src/schema/struct_schemas.rs:179— NamedStructSchema::try_to_tokens has cognitive complexity 80 (threshold 15). Drivers by points: if/else 25 (49 pts), match/switch 7 (19 pts), boolean chains 6, loops 4 (6 pts) (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NamedStructSchema::field_as_schema_property (cognitive 17) crates/oapi-macros/src/schema/struct_schemas.rs:60— NamedStructSchema::field_as_schema_property has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, match/switch 3 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CombWisp::detect (cognitive 44) crates/core/src/routing/filters/path.rs:448— CombWisp::detect has cognitive complexity 44 (threshold 15). Drivers by points: if/else 21 (40 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CombWisp::new (cognitive 24) crates/core/src/routing/filters/path.rs:353— CombWisp::new has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (21 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
salvo_serve_static::embed::render_embedded_data (cognitive 43) crates/serve-static/src/embed.rs:106— salvo_serve_static::embed::render_embedded_data has cognitive complexity 43 (threshold 15). Drivers by points: if/else 22 (29 pts), match/switch 3 (9 pts), boolean chains 5 (nesting depth added 13). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
salvo_serve_static::dir::list_html (cognitive 17) crates/serve-static/src/dir.rs:939— salvo_serve_static::dir::list_html has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 7). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
salvo_macros::extract::generate (cognitive 31) crates/macros/src/extract.rs:274— salvo_macros::extract::generate has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (21 pts), loops 4 (7 pts), boolean chains 2, match/switch 1 (nesting depth added 10). Of this number, 30 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
salvo_macros::shared::parse_input_type (cognitive 19) crates/macros/src/shared.rs:33— salvo_macros::shared::parse_input_type has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (19 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestBodyAttr::try_to_tokens (cognitive 21) crates/oapi-macros/src/operation/request_body.rs:158— RequestBodyAttr::try_to_tokens has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestBodyAttr::parse (cognitive 20) crates/oapi-macros/src/operation/request_body.rs:67— RequestBodyAttr::parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (6 pts), match/switch 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Router::detect_with_method (cognitive 19) crates/core/src/routing/router.rs:256— Router::detect_with_method has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Router::fmt::print (cognitive 17) crates/core/src/routing/router.rs:670— Router::fmt::print has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), loops 2 (4 pts), match/switch 1 (3 pts) (nesting depth added 5). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) crates/macros/src/shared.rs:113— crates/macros/src/shared.rs:113-142 | crates/oapi-macros/src/shared.rs:130-158 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) crates/core/src/conn/openssl/listener.rs:203— crates/core/src/conn/openssl/listener.rs:203-235 | crates/core/src/conn/rustls/listener.rs:204-232 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×2
Edited copies of one member (3 members, 21+ corresponding lines) crates/core/src/conn/native_tls/listener.rs:62— crates/core/src/conn/native_tls/listener.rs:62-90 | crates/core/src/conn/openssl/listener.rs:64-84 | crates/core/src/conn/rustls/listener.rs:62-84 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 21+ corresponding lines) crates/core/src/conn/openssl/listener.rs:94— crates/core/src/conn/openssl/listener.rs:94-114 | crates/core/src/conn/quinn/listener.rs:101-121 | crates/core/src/conn/rustls/listener.rs:94-116 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) crates/oapi/src/rapidoc.rs:104— crates/oapi/src/rapidoc.rs:104-122 | crates/oapi/src/redoc.rs:119-137 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) crates/oapi-macros/src/response.rs:478— crates/oapi-macros/src/response.rs:478-496 | crates/oapi-macros/src/response.rs:553-573 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) crates/core/src/catcher.rs:426— crates/core/src/catcher.rs:426-451 | crates/core/src/catcher.rs:480-500 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/oapi/src/openapi.rs:889— crates/oapi/src/openapi.rs:889-909 | crates/oapi/src/openapi.rs:945-965 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×2
Edited copies of one member (3 members, 14+ corresponding lines) crates/core/src/catcher.rs:344— crates/core/src/catcher.rs:344-357 | crates/oapi/src/html.rs:1-14 | crates/serve-static/src/dir.rs:907-920 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) crates/acme/src/listener.rs:43— crates/acme/src/listener.rs:43-56 | crates/core/src/conn/rustls.rs:38-51 | crates/proxy/src/hyper_client.rs:39-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) crates/core/src/conn/openssl/config.rs:94— crates/core/src/conn/openssl/config.rs:94-104 | crates/core/src/conn/rustls/config.rs:132-142 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/macros/src/attribute.rs:5— crates/macros/src/attribute.rs:5-15 | crates/oapi-macros/src/attribute.rs:16-26 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) crates/core/src/conn/stream/handshake.rs:126— crates/core/src/conn/stream/handshake.rs:126-134 | crates/core/src/conn/stream/handshake.rs:136-144 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/oapi/src/openapi/schema/object.rs:279— crates/oapi/src/openapi/schema/object.rs:279-287 | crates/oapi/src/swagger_ui/config.rs:635-644 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×2
Edited copies of one member (3 members, 7+ corresponding lines) crates/craft-macros/src/lib.rs:83— crates/craft-macros/src/lib.rs:83-89 | crates/macros/src/lib.rs:70-76 | crates/oapi-macros/src/lib.rs:91-98 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) crates/oapi/src/openapi.rs:411— crates/oapi/src/openapi.rs:411-417 | crates/oapi/src/openapi/operation.rs:317-323 | crates/oapi/src/openapi/parameter.rs:433-439 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (24 lines × 2) crates/macros/src/handler.rs:16— crates/macros/src/handler.rs:16-39 | crates/oapi-macros/src/endpoint.rs:182-205 — before extracting anything, compare `crates/macros/src/handler.rs` and `crates/oapi-macros/src/endpoint.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/macros/src/handler.rs:16` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) crates/oapi-macros/src/response.rs:503— crates/oapi-macros/src/response.rs:503-526 | crates/oapi-macros/src/response.rs:601-624 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/response.rs:503` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) crates/csrf/src/aes_gcm_cipher.rs:57— crates/csrf/src/aes_gcm_cipher.rs:57-79 | crates/csrf/src/ccp_cipher.rs:57-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:844— crates/oapi-macros/src/schema/enum_schemas.rs:844-866 | crates/oapi-macros/src/schema/enum_schemas.rs:1030-1052 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:844` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/oapi-macros/src/schema/enum_schemas.rs:1055` calls `Some` and `crates/oapi-macros/src/schema/enum_schemas.rs:867` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 2) crates/proxy/src/hyper_client.rs:149— crates/proxy/src/hyper_client.rs:149-169 | crates/proxy/src/reqwest_client.rs:105-125 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/proxy/src/hyper_client.rs:149` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (21 lines × 2) crates/macros/src/shared.rs:34— crates/macros/src/shared.rs:34-54 | crates/oapi-macros/src/shared.rs:56-76 — before extracting anything, compare `crates/macros/src/shared.rs` and `crates/oapi-macros/src/shared.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 135 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/macros/src/shared.rs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/macros/src/shared.rs:56` calls `ConnCtrl` and `crates/oapi-macros/src/shared.rs:77` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 3) crates/craft-macros/src/utils.rs:14— crates/craft-macros/src/utils.rs:14-27 | crates/macros/src/shared.rs:18-31 | crates/oapi-macros/src/shared.rs:40-53 — before extracting anything, compare `crates/craft-macros/src/utils.rs` and `crates/macros/src/shared.rs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 3) crates/tus/src/handlers/delete.rs:35— crates/tus/src/handlers/delete.rs:35-48 | crates/tus/src/handlers/get.rs:31-44 | crates/tus/src/handlers/head.rs:30-43 — before extracting anything, compare `crates/tus/src/handlers/delete.rs` and `crates/tus/src/handlers/get.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/tus/src/handlers/delete.rs:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/core/src/extract/case.rs:90— crates/core/src/extract/case.rs:90-102 | crates/serde-util/src/case.rs:124-136 — before extracting anything, compare `crates/core/src/extract/case.rs` and `crates/serde-util/src/case.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/extract/case.rs:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/oapi-macros/src/response/derive.rs:271— crates/oapi-macros/src/response/derive.rs:271-283 | crates/oapi-macros/src/response/derive.rs:318-330 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–11 lines × 2) crates/core/src/routing/filters/path.rs:636— crates/core/src/routing/filters/path.rs:636-645 | crates/core/src/routing/filters/path.rs:654-664 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/routing/filters/path.rs:654` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 2) crates/oapi-macros/src/operation/example.rs:25— crates/oapi-macros/src/operation/example.rs:25-34 | crates/oapi-macros/src/server.rs:124-134 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/operation/example.rs:25` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 2) crates/core/src/catcher.rs:433— crates/core/src/catcher.rs:433-441 | crates/core/src/catcher.rs:483-492 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/catcher.rs:433` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9–10 lines × 2) crates/oapi-macros/src/component.rs:232— crates/oapi-macros/src/component.rs:232-241 | crates/oapi-macros/src/component.rs:317-325 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 3) crates/oapi-macros/src/component.rs:436— crates/oapi-macros/src/component.rs:436-443 | crates/oapi-macros/src/component.rs:586-593 | crates/oapi-macros/src/component.rs:622-629 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) crates/oapi-macros/src/feature.rs:33— crates/oapi-macros/src/feature.rs:33-40 | crates/oapi-macros/src/feature.rs:56-63 | crates/oapi-macros/src/feature.rs:66-73 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/oapi-macros/src/feature.rs:53` calls `lookahead1`, `peek` and `crates/oapi-macros/src/feature.rs:31` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) crates/core/src/catcher.rs:345— crates/core/src/catcher.rs:345-351 | crates/oapi/src/html.rs:2-8 | crates/serve-static/src/dir.rs:908-914 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/catcher.rs:345` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) crates/oapi/src/openapi/callback.rs:80— crates/oapi/src/openapi/callback.rs:80-86 | crates/oapi/src/openapi/response.rs:28-35 | crates/oapi/src/openapi/schema.rs:34-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Off the main sequence: salvo-serde-util — salvo-serde-util: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: salvo_core — salvo_core: abstractness 0.11, instability 0.06, distance 0.83 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
StaticDir::handle (cyclomatic 59) crates/serve-static/src/dir.rs:526— StaticDir::handle has cyclomatic complexity 59 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RequestDeserializer::fill_value (cyclomatic 52) crates/core/src/serde/request.rs:280— RequestDeserializer::fill_value has cyclomatic complexity 52 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NamedFile::send_with_method (cyclomatic 42) crates/core/src/fs/named_file.rs:817— NamedFile::send_with_method has cyclomatic complexity 42 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
salvo_oapi_macros::bound::relevant_types (cyclomatic 40) crates/oapi-macros/src/bound.rs:57— salvo_oapi_macros::bound::relevant_types has cyclomatic complexity 40 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
NamedStructSchema::try_to_tokens (cyclomatic 37) crates/oapi-macros/src/schema/struct_schemas.rs:179— NamedStructSchema::try_to_tokens has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ComponentSchema::non_generic_to_tokens (cyclomatic 35) crates/oapi-macros/src/component.rs:397— ComponentSchema::non_generic_to_tokens has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HyperHandler::handle (cyclomatic 33) crates/core/src/service.rs:268— HyperHandler::handle has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Builder::serve_connection (cyclomatic 32) crates/core/src/conn/quinn/builder.rs:105— Builder::serve_connection has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Compression::handle (cyclomatic 30) crates/compression/src/lib.rs:504— Compression::handle has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ReadSeeker::send_inner (cyclomatic 27) crates/core/src/writing/seek.rs:77— ReadSeeker::send_inner has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Proxy::build_proxied_request (cyclomatic 26) crates/proxy/src/lib.rs:506— Proxy::build_proxied_request has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
salvo_serve_static::embed::render_embedded_data (cyclomatic 26) crates/serve-static/src/embed.rs:106— salvo_serve_static::embed::render_embedded_data has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HttpBuilder::serve_connection (cyclomatic 25) crates/core/src/conn/proto.rs:82— HttpBuilder::serve_connection has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PathParser::scan_wisps (cyclomatic 22) crates/core/src/routing/filters/path.rs:844— PathParser::scan_wisps has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
salvo_macros::extract::generate (cyclomatic 22) crates/macros/src/extract.rs:274— salvo_macros::extract::generate has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UnnamedStructSchema::try_to_tokens (cyclomatic 21) crates/oapi-macros/src/schema/struct_schemas.rs:575— UnnamedStructSchema::try_to_tokens has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OpenApi::merge_norm_node (cyclomatic 20) crates/oapi/src/openapi.rs:628— OpenApi::merge_norm_node has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NormNode::with_method (cyclomatic 20) crates/oapi/src/routing.rs:105— NormNode::with_method has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Server::try_serve (cyclomatic 19) crates/core/src/server.rs:366— Server::try_serve has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
salvo_craft_macros::craft::rewrite_method (cyclomatic 19) crates/craft-macros/src/craft.rs:141— salvo_craft_macros::craft::rewrite_method has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CachePolicy::parse_bytes (cyclomatic 19) crates/jwt-auth/src/oidc/cache.rs:65— CachePolicy::parse_bytes has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EndpointAttr::parse (cyclomatic 19) crates/oapi-macros/src/endpoint/attr.rs:29— EndpointAttr::parse has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
check_macro_paths.main (cyclomatic 19) .github/scripts/check_macro_paths.py:8— check_macro_paths.main has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CombWisp::detect (cyclomatic 18) crates/core/src/routing/filters/path.rs:448— CombWisp::detect has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToParameters::try_to_tokens (cyclomatic 18) crates/oapi-macros/src/parameter/derive.rs:67— ToParameters::try_to_tokens has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ResBody::poll_frame (cyclomatic 17) crates/core/src/http/body/res.rs:150— ResBody::poll_frame has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Tracing::handle (cyclomatic 17) crates/otel/src/tracing.rs:119— Tracing::handle has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HttpRange::parse (cyclomatic 16) crates/core/src/http/range.rs:44— HttpRange::parse has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Operation::modifiers (cyclomatic 16) crates/oapi-macros/src/operation.rs:115— Operation::modifiers has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SerdeValue::parse (cyclomatic 16) crates/serde-util/src/lib.rs:90— SerdeValue::parse has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
SerdeContainer::parse_attribute (cyclomatic 16) crates/serde-util/src/lib.rs:190— SerdeContainer::parse_attribute has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
FixmeComment crates/oapi-macros/src/schema/enum_schemas.rs:962— // FIXME perhaps design this better to lessen the amount of args. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
StaticDir::handle (cognitive 177) crates/serve-static/src/dir.rs:526— StaticDir::handle has cognitive complexity 177 (threshold 15). Drivers by points: if/else 48 (141 pts), loops 7 (27 pts), boolean chains 7, match/switch 1 (2 pts) (nesting depth added 114). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ComponentSchema::non_generic_to_tokens (cognitive 84) crates/oapi-macros/src/component.rs:397— ComponentSchema::non_generic_to_tokens has cognitive complexity 84 (threshold 15). Drivers by points: if/else 34 (71 pts), boolean chains 10, loops 1 (2 pts), match/switch 1 (nesting depth added 38). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Builder::serve_connection (cognitive 71) crates/core/src/conn/quinn/builder.rs:105— Builder::serve_connection has cognitive complexity 71 (threshold 15). Drivers by points: match/switch 12 (36 pts), if/else 16 (34 pts), loops 1 (nesting depth added 42). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
HttpBuilder::serve_connection (cognitive 61) crates/core/src/conn/proto.rs:82— HttpBuilder::serve_connection has cognitive complexity 61 (threshold 15). Drivers by points: if/else 15 (40 pts), match/switch 9 (21 pts) (nesting depth added 37). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
NamedFile::send_with_method (cognitive 59) crates/core/src/fs/named_file.rs:817— NamedFile::send_with_method has cognitive complexity 59 (threshold 15). Drivers by points: if/else 36 (42 pts), match/switch 4 (10 pts), boolean chains 7 (nesting depth added 12). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
HyperHandler::handle (cognitive 50) crates/core/src/service.rs:268— HyperHandler::handle has cognitive complexity 50 (threshold 15). Drivers by points: if/else 25 (38 pts), boolean chains 10, loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Compression::handle (cognitive 47) crates/compression/src/lib.rs:504— Compression::handle has cognitive complexity 47 (threshold 15). Drivers by points: if/else 27 (43 pts), boolean chains 3, match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Proxy::build_proxied_request (cognitive 42) crates/proxy/src/lib.rs:506— Proxy::build_proxied_request has cognitive complexity 42 (threshold 15). Drivers by points: if/else 20 (30 pts), match/switch 3 (7 pts), boolean chains 4, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenApi::merge_norm_node (cognitive 36) crates/oapi/src/openapi.rs:628— OpenApi::merge_norm_node has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (20 pts), match/switch 4 (11 pts), boolean chains 4, loops 1 (nesting depth added 16). Of this number, 33 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
salvo_oapi::routing::normalize_oapi_path (cognitive 34) crates/oapi/src/routing.rs:12— salvo_oapi::routing::normalize_oapi_path has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReadSeeker::send_inner (cognitive 33) crates/core/src/writing/seek.rs:77— ReadSeeker::send_inner has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (24 pts), boolean chains 5, match/switch 2 (4 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
check_macro_paths.main (cognitive 33) .github/scripts/check_macro_paths.py:8— check_macro_paths.main has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 10 (20 pts), if/else 6 (11 pts), boolean chains 1, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CharsWispBuilder::build (cognitive 31) crates/core/src/routing/filters/path.rs:217— CharsWispBuilder::build has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (31 pts) (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Server::try_serve (cognitive 31) crates/core/src/server.rs:366— Server::try_serve has cognitive complexity 31 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 7 (11 pts), loops 4 (5 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormData::read_with_directory (cognitive 29) crates/core/src/http/form.rs:131— FormData::read_with_directory has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
HttpRange::parse (cognitive 27) crates/core/src/http/range.rs:44— HttpRange::parse has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (26 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Operation::modifiers (cognitive 26) crates/oapi-macros/src/operation.rs:115— Operation::modifiers has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (17 pts), match/switch 2 (6 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NormNode::with_method (cognitive 25) crates/oapi/src/routing.rs:105— NormNode::with_method has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 2 (3 pts), match/switch 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResponseTuple::try_to_tokens (cognitive 25) crates/oapi-macros/src/response.rs:297— ResponseTuple::try_to_tokens has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 5 (11 pts) (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
salvo_craft_macros::craft::rewrite_method (cognitive 24) crates/craft-macros/src/craft.rs:141— salvo_craft_macros::craft::rewrite_method has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 4 (7 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Csrf::handle (cognitive 24) crates/csrf/src/lib.rs:357— Csrf::handle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (23 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CachePolicy::parse_bytes (cognitive 24) crates/jwt-auth/src/oidc/cache.rs:65— CachePolicy::parse_bytes has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 4, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlatParser::next (cognitive 23) crates/core/src/serde/flat_value.rs:233— FlatParser::next has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlexNamer::assign_name (cognitive 23) crates/oapi/src/naming.rs:332— FlexNamer::assign_name has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SessionHandler::handle (cognitive 23) crates/session/src/lib.rs:418— SessionHandler::handle has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebSocketUpgrade::upgrade (cognitive 22) crates/extra/src/websocket.rs:377— WebSocketUpgrade::upgrade has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (18 pts), match/switch 2 (4 pts) (nesting depth added 5). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
Tracing::handle (cognitive 20) crates/otel/src/tracing.rs:119— Tracing::handle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 2, loops 1, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ReqwestClient::execute (cognitive 20) crates/proxy/src/reqwest_client.rs:58— ReqwestClient::execute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 1 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UnnamedStructSchema::try_to_tokens (cognitive 19) crates/oapi-macros/src/schema/struct_schemas.rs:575— UnnamedStructSchema::try_to_tokens has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToSchema::try_to_tokens (cognitive 19) crates/oapi-macros/src/schema.rs:75— ToSchema::try_to_tokens has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (13 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TusOptions::extract_host_and_proto (cognitive 19) crates/tus/src/options.rs:355— TusOptions::extract_host_and_proto has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EncodeStream::poll_next (cognitive 18) crates/compression/src/stream.rs:144— EncodeStream::poll_next has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 3 (7 pts), loops 1 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RegexWisp::detect (cognitive 18) crates/core/src/routing/filters/path.rs:622— RegexWisp::detect has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FieldInfo::try_from (cognitive 18) crates/macros/src/extract.rs:27— FieldInfo::try_from has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComplexEnum::tagged_variant_tokens (cognitive 18) crates/oapi-macros/src/schema/enum_schemas.rs:759— ComplexEnum::tagged_variant_tokens has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
salvo_core::routing::path_state::parse_path_parts (cognitive 17) crates/core/src/routing/path_state.rs:251— salvo_core::routing::path_state::parse_path_parts has cognitive complexity 17 (threshold 15). Drivers by points: loops 3 (5 pts), match/switch 2 (5 pts), if/else 2 (4 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HyperClient::execute (cognitive 17) crates/proxy/src/hyper_client.rs:123— HyperClient::execute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 1 (4 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AcmeListenerBuilder::try_bind (cognitive 16) crates/acme/src/listener.rs:436— AcmeListenerBuilder::try_bind has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), match/switch 2 (5 pts), loops 3, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EndpointAttr::parse (cognitive 16) crates/oapi-macros/src/endpoint/attr.rs:29— EndpointAttr::parse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EnumResponse::parse_variant_attributes (cognitive 16) crates/oapi-macros/src/response/derive.rs:586— EnumResponse::parse_variant_attributes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SerdeValue::parse (cognitive 16) crates/serde-util/src/lib.rs:90— SerdeValue::parse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), boolean chains 4, match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StaticEmbed::handle (cognitive 16) crates/serve-static/src/embed.rs:356— StaticEmbed::handle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiskStore::try_finalize_if_complete (cognitive 16) crates/tus/src/stores/disk.rs:428— DiskStore::try_finalize_if_complete has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 2 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check_macro_contracts.main (cognitive 16) .github/scripts/check_macro_contracts.py:29— check_macro_contracts.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3, error handling 1 (2 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change coupling clique: cookie.rs, header.rs, path.rs, query.rs, json.rs crates/core/src/extract/parameter/cookie.rs— 5 files — `crates/core/src/extract/parameter/cookie.rs`, `crates/core/src/extract/parameter/header.rs`, `crates/core/src/extract/parameter/path.rs`, `crates/core/src/extract/parameter/query.rs`, `crates/core/src/extract/payload/json.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 10 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Change-coupling hub: listener.rs → listener.rs, config.rs, listener.rs, listener.rs crates/core/src/conn/rustls/listener.rs— `crates/core/src/conn/rustls/listener.rs` changes together with 4 other files — `crates/core/src/conn/native_tls/listener.rs`, `crates/core/src/conn/openssl/config.rs`, `crates/core/src/conn/openssl/listener.rs`, `crates/core/src/conn/quinn/listener.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Near-duplicate member pair (112 shared lines) crates/oapi-macros/src/schema/enum_schemas.rs:767— crates/oapi-macros/src/schema/enum_schemas.rs:767-960 | crates/oapi-macros/src/schema/enum_schemas.rs:973-1131 — These two members are variants of one another: 112 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (29 shared lines) crates/macros/src/handler.rs:96— crates/macros/src/handler.rs:96-206 | crates/oapi-macros/src/endpoint.rs:320-421 — These two members are variants of one another: 29 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) crates/tus/src/handlers/delete.rs:14— crates/tus/src/handlers/delete.rs:14-74 | crates/tus/src/handlers/get.rs:16-115 | crates/tus/src/handlers/head.rs:15-118 | crates/tus/src/handlers/patch.rs:18-300 | crates/tus/src/handlers/post.rs:22-300 | crates/tus/src/method_override.rs:75-91 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Edited copy of a member (63 corresponding lines) · ×1
Edited copy of a member (63 corresponding lines) crates/core/src/conn/stream/straight.rs:116— crates/core/src/conn/stream/straight.rs:116-180 | crates/core/src/conn/stream/straight.rs:194-256 — These two members are one piece of code written twice and then edited apart: 63 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (71 corresponding lines) · ×1
Edited copy of a member (71 corresponding lines) crates/oapi-macros/src/schema_type.rs:66— crates/oapi-macros/src/schema_type.rs:66-137 | crates/oapi-macros/src/schema_type.rs:356-426 — These two members are one piece of code written twice and then edited apart: 71 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) crates/oapi-macros/src/operation/example.rs:19— crates/oapi-macros/src/operation/example.rs:19-71 | crates/oapi-macros/src/server.rs:118-164 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) crates/core/src/conn/tcp.rs:228— crates/core/src/conn/tcp.rs:228-267 | crates/core/src/conn/unix.rs:172-211 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) crates/oapi-macros/src/response/derive.rs:307— crates/oapi-macros/src/response/derive.rs:307-359 | crates/oapi-macros/src/response/derive.rs:407-447 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) crates/cache/src/lib.rs:803— crates/cache/src/lib.rs:803-837 | crates/compression/src/lib.rs:644-677 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) crates/macros/src/shared.rs:33— crates/macros/src/shared.rs:33-72 | crates/oapi-macros/src/shared.rs:55-92 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) crates/oapi-macros/src/operation/encoding.rs:22— crates/oapi-macros/src/operation/encoding.rs:22-58 | crates/oapi-macros/src/server.rs:19-61 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) crates/core/src/extract/case.rs:56— crates/core/src/extract/case.rs:56-79 | crates/serde-util/src/case.rs:94-116 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) crates/core/src/extract/case.rs:86— crates/core/src/extract/case.rs:86-111 | crates/serde-util/src/case.rs:120-146 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) crates/oapi/src/naming.rs:222— crates/oapi/src/naming.rs:222-237 | crates/oapi/src/naming.rs:313-329 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) crates/rate-limiter/src/lib.rs:333— crates/rate-limiter/src/lib.rs:333-358 | crates/rate-limiter/src/lib.rs:363-386 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) crates/oapi/src/extract/payload.rs:101— crates/oapi/src/extract/payload.rs:101-117 | crates/oapi/src/extract/payload.rs:121-139 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) crates/cors/src/inner.rs:50— crates/cors/src/inner.rs:50-57 | crates/cors/src/inner.rs:89-97 | crates/cors/src/inner.rs:126-133 | crates/cors/src/inner.rs:151-158 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) crates/oapi/src/openapi/security.rs:550— crates/oapi/src/openapi/security.rs:550-562 | crates/oapi/src/openapi/security.rs:596-608 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) crates/oapi-macros/src/parameter/derive.rs:355— crates/oapi-macros/src/parameter/derive.rs:355-387 | crates/oapi-macros/src/parameter.rs:215-241 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 6+ corresponding lines) · ×1
Edited copies of one member (4 members, 6+ corresponding lines) crates/oapi/src/openapi.rs:481— crates/oapi/src/openapi.rs:481-488 | crates/oapi/src/openapi/components.rs:143-150 | crates/oapi/src/openapi/content.rs:152-160 | crates/oapi/src/openapi/response.rs:112-117 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) crates/core/src/conn/openssl/config.rs:58— crates/core/src/conn/openssl/config.rs:58-62 | crates/core/src/conn/rustls/config.rs:73-77 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) crates/cors/src/expose_headers.rs:85— crates/cors/src/expose_headers.rs:85-88 | crates/cors/src/max_age.rs:65-68 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (41 lines × 2) crates/core/src/conn/stream/straight.rs:137— crates/core/src/conn/stream/straight.rs:137-177 | crates/core/src/conn/stream/straight.rs:213-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/conn/stream/straight.rs:137` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (39–40 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:922— crates/oapi-macros/src/schema/enum_schemas.rs:922-960 | crates/oapi-macros/src/schema/enum_schemas.rs:1092-1131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (38 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:768— crates/oapi-macros/src/schema/enum_schemas.rs:768-805 | crates/oapi-macros/src/schema/enum_schemas.rs:974-1011 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:768` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (48 lines × 3) crates/craft-macros/src/utils.rs:32— crates/craft-macros/src/utils.rs:32-79 | crates/macros/src/shared.rs:180-227 | crates/oapi-macros/src/shared.rs:546-593 — before extracting anything, compare `crates/craft-macros/src/utils.rs` and `crates/macros/src/shared.rs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/craft-macros/src/utils.rs:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (35–36 lines × 2) crates/core/src/fs/named_file.rs:965— crates/core/src/fs/named_file.rs:965-1000 | crates/core/src/writing/seek.rs:154-188 — before extracting anything, compare `crates/core/src/fs/named_file.rs` and `crates/core/src/writing/seek.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (24–30 lines × 2) crates/oapi-macros/src/operation/request_body.rs:165— crates/oapi-macros/src/operation/request_body.rs:165-188 | crates/oapi-macros/src/response.rs:325-354 — before extracting anything, compare `crates/oapi-macros/src/operation/request_body.rs` and `crates/oapi-macros/src/response.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/operation/request_body.rs:165` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (28 lines × 3) crates/core/src/conn/native_tls/listener.rs:154— crates/core/src/conn/native_tls/listener.rs:154-181 | crates/core/src/conn/openssl/listener.rs:141-168 | crates/core/src/conn/rustls/listener.rs:143-170 — `crates/core/src/conn/native_tls/listener.rs` and `crates/core/src/conn/openssl/listener.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `current_acceptor` to `Arc<ArcSwapOption<tokio_native_tls::TlsAcceptor>>` in one and `Arc<ArcSwapOption<SslAcceptor>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (24–26 lines × 2) crates/core/src/server.rs:390— crates/core/src/server.rs:390-415 | crates/core/src/server.rs:567-590 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/server.rs:390` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) crates/core/src/conn/tcp.rs:237— crates/core/src/conn/tcp.rs:237-261 | crates/core/src/conn/unix.rs:181-205 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/conn/tcp.rs:237` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 3) crates/oapi-macros/src/schema/enum_schemas.rs:540— crates/oapi-macros/src/schema/enum_schemas.rs:540-559 | crates/oapi-macros/src/schema/enum_schemas.rs:769-788 | crates/oapi-macros/src/schema/enum_schemas.rs:975-994 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:540` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/oapi-macros/src/schema/enum_schemas.rs:768` calls `oapi_crate` and `crates/oapi-macros/src/schema/enum_schemas.rs:538` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19–20 lines × 2) crates/cache/src/lib.rs:804— crates/cache/src/lib.rs:804-822 | crates/compression/src/lib.rs:645-664 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cache/src/lib.rs:804` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `headers` to `&HeaderMap` in one and `&http::HeaderMap` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (20 lines × 2) crates/macros/src/handler.rs:51— crates/macros/src/handler.rs:51-70 | crates/oapi-macros/src/endpoint.rs:258-277 — before extracting anything, compare `crates/macros/src/handler.rs` and `crates/oapi-macros/src/endpoint.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/oapi-macros/src/endpoint.rs:278` calls `type_name_suffix` and `crates/macros/src/handler.rs:71` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11–19 lines × 3) crates/oapi-macros/src/operation/request_body.rs:170— crates/oapi-macros/src/operation/request_body.rs:170-182 | crates/oapi-macros/src/response.rs:331-349 | crates/oapi-macros/src/response.rs:921-931 — before extracting anything, compare `crates/oapi-macros/src/operation/request_body.rs` and `crates/oapi-macros/src/response.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/response.rs:921` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:139— crates/oapi-macros/src/schema/enum_schemas.rs:139-157 | crates/oapi-macros/src/schema/enum_schemas.rs:179-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:179` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18–19 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:165— crates/oapi-macros/src/schema/enum_schemas.rs:165-183 | crates/oapi-macros/src/schema/enum_schemas.rs:201-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 3) crates/oapi-macros/src/schema/enum_schemas.rs:590— crates/oapi-macros/src/schema/enum_schemas.rs:590-607 | crates/oapi-macros/src/schema/enum_schemas.rs:846-863 | crates/oapi-macros/src/schema/enum_schemas.rs:1032-1049 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17 lines × 2) crates/core/src/http/body/channel.rs:103— crates/core/src/http/body/channel.rs:103-119 | crates/core/src/http/body/channel.rs:138-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 6) crates/oapi-macros/src/schema/enum_schemas.rs:545— crates/oapi-macros/src/schema/enum_schemas.rs:545-559 | crates/oapi-macros/src/schema/enum_schemas.rs:593-607 | crates/oapi-macros/src/schema/enum_schemas.rs:774-788 | crates/oapi-macros/src/schema/enum_schemas.rs:849-863 | crates/oapi-macros/src/schema/enum_schemas.rs:980-994 | crates/oapi-macros/src/schema/enum_schemas.rs:1035-1049 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:545` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) crates/tus/src/handlers/delete.rs:16— crates/tus/src/handlers/delete.rs:16-30 | crates/tus/src/handlers/get.rs:18-32 | crates/tus/src/handlers/head.rs:17-31 — before extracting anything, compare `crates/tus/src/handlers/delete.rs` and `crates/tus/src/handlers/get.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13–15 lines × 2) crates/oapi-macros/src/component.rs:456— crates/oapi-macros/src/component.rs:456-468 | crates/oapi-macros/src/component.rs:606-620 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/component.rs:456` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) crates/oapi-macros/src/parameter.rs:255— crates/oapi-macros/src/parameter.rs:255-267 | crates/oapi-macros/src/parameter/derive.rs:455-468 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12–13 lines × 3) crates/core/src/conn/stream/straight.rs:83— crates/core/src/conn/stream/straight.rs:83-95 | crates/core/src/conn/stream/straight.rs:130-141 | crates/core/src/conn/stream/straight.rs:206-217 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/conn/stream/straight.rs:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) crates/oapi-macros/src/schema/enum_schemas.rs:869— crates/oapi-macros/src/schema/enum_schemas.rs:869-880 | crates/oapi-macros/src/schema/enum_schemas.rs:1055-1067 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/schema/enum_schemas.rs:869` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–11 lines × 2) crates/oapi-macros/src/operation/request_body.rs:196— crates/oapi-macros/src/operation/request_body.rs:196-206 | crates/oapi-macros/src/response.rs:362-370 — before extracting anything, compare `crates/oapi-macros/src/operation/request_body.rs` and `crates/oapi-macros/src/response.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/operation/request_body.rs:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 3) crates/core/src/conn/native_tls/listener.rs:74— crates/core/src/conn/native_tls/listener.rs:74-83 | crates/core/src/conn/openssl/listener.rs:73-81 | crates/core/src/conn/rustls/listener.rs:72-81 — `crates/core/src/conn/native_tls/listener.rs` and `crates/core/src/conn/openssl/listener.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/conn/native_tls/listener.rs:74` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–10 lines × 3) crates/oapi-macros/src/response/derive.rs:413— crates/oapi-macros/src/response/derive.rs:413-422 | crates/oapi-macros/src/response/derive.rs:469-478 | crates/oapi-macros/src/response/derive.rs:677-684 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/response/derive.rs:413` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–10 lines × 2) crates/core/src/conn/stream/straight.rs:117— crates/core/src/conn/stream/straight.rs:117-126 | crates/core/src/conn/stream/straight.rs:195-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7–8 lines × 3) crates/oapi-macros/src/component.rs:459— crates/oapi-macros/src/component.rs:459-465 | crates/oapi-macros/src/component.rs:611-617 | crates/oapi-macros/src/component.rs:648-655 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/component.rs:459` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 5) crates/tus/src/handlers/delete.rs:20— crates/tus/src/handlers/delete.rs:20-25 | crates/tus/src/handlers/get.rs:22-27 | crates/tus/src/handlers/head.rs:21-26 | crates/tus/src/handlers/post.rs:27-32 | crates/tus/src/method_override.rs:78-83 — before extracting anything, compare `crates/tus/src/handlers/delete.rs` and `crates/tus/src/handlers/get.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/tus/src/handlers/delete.rs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) crates/oapi-macros/src/component.rs:459— crates/oapi-macros/src/component.rs:459-464 | crates/oapi-macros/src/component.rs:611-616 | crates/oapi-macros/src/component.rs:648-653 | crates/oapi-macros/src/component.rs:659-664 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/component.rs:459` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (4–6 lines × 4) crates/compression/src/lib.rs:586— crates/compression/src/lib.rs:586-589 | crates/compression/src/lib.rs:597-602 | crates/compression/src/lib.rs:611-616 | crates/compression/src/lib.rs:624-629 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/compression/src/lib.rs:586` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (2–5 lines × 4) crates/core/src/http/body/req.rs:208— crates/core/src/http/body/req.rs:208-212 | crates/core/src/http/body/res.rs:168-169 | crates/core/src/http/body/res.rs:174-175 | crates/core/src/http/body/res.rs:234-238 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/http/body/req.rs:208` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 3) crates/oapi-macros/src/operation/encoding.rs:42— crates/oapi-macros/src/operation/encoding.rs:42-58 | crates/oapi-macros/src/response.rs:523-539 | crates/oapi-macros/src/response.rs:621-637 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `crates/oapi-macros/src/operation/encoding.rs:42` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) crates/core/src/conn/native_tls/listener.rs:218— crates/core/src/conn/native_tls/listener.rs:218-229 | crates/core/src/conn/openssl/listener.rs:204-215 | crates/core/src/conn/rustls/listener.rs:205-216 — `crates/core/src/conn/native_tls/listener.rs` and `crates/core/src/conn/openssl/listener.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 4) crates/core/src/conn/proto.rs:184— crates/core/src/conn/proto.rs:184-191 | crates/core/src/conn/proto.rs:202-209 | crates/core/src/conn/proto.rs:244-251 | crates/core/src/conn/proto.rs:259-266 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/core/src/conn/proto.rs:184` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:266— `warn!` at line 266 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`.
Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:307— `warn!` at line 307 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`.
Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:442— `warn!` at line 442 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`.
Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:477— `warn!` 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: `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`.
Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:493— `warn!` at line 493 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`.
Interpolated log message defeats structured logging crates/tus/src/stores/disk.rs:504— `warn!` at line 504 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`.
Interpolated log message defeats structured logging crates/tus/src/handlers/patch.rs:111— `info!` at line 111 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/tus/src/handlers/post.rs:266— `info!` at line 266 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/serve-static/src/embed.rs:171— `error!` at line 171 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`.
Interpolated log message defeats structured logging crates/oapi/src/naming.rs:379— `error!` at line 379 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`.
Interpolated log message defeats structured logging crates/oapi/src/openapi.rs:733— `warn!` at line 733 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`.
Interpolated log message defeats structured logging crates/jwt-auth/src/oidc.rs:330— `debug!` at line 330 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`.
Interpolated log message defeats structured logging crates/jwt-auth/src/oidc/cache.rs:420— `debug!` at line 420 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`.
Interpolated log message defeats structured logging crates/extra/src/concurrency_limiter.rs:142— `error!` 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: `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`.
Interpolated log message defeats structured logging crates/extra/src/sse.rs:308— `error!` at line 308 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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`.
Interpolated log message defeats structured logging crates/extra/src/websocket.rs:553— `debug!` at line 553 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`.
Interpolated log message defeats structured logging crates/cors/src/lib.rs:608— `error!` at line 608 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`.
Interpolated log message defeats structured logging crates/core/src/catcher.rs:149— `warn!` at line 149 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core/src/server.rs:391— `info!` at line 391 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core/src/server.rs:516— `info!` at line 516 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core/src/server.rs:568— `info!` at line 568 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core/src/serde/request.rs:290— `error!` at line 290 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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`.
Interpolated log message defeats structured logging crates/core/src/conn/proto.rs:278— `info!` at line 278 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/core/src/conn/quinn/builder.rs:188— `error!` at line 188 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`.
Interpolated log message defeats structured logging crates/core/src/conn/quinn/builder.rs:260— `debug!` at line 260 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`.
Duplicated predicate crates/craft-macros/src/utils.rs:42— `!input.is_empty() && !input.peek(syn::Token![,])` appears character-identically in 3 files — crates/craft-macros/src/utils.rs, crates/macros/src/shared.rs, crates/oapi-macros/src/shared.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/macros/src/handler.rs:144— `!status_code.is_client_error() && !status_code.is_server_error()` appears character-identically in 2 files — crates/macros/src/handler.rs, crates/oapi-macros/src/endpoint.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/core/src/fs/named_file.rs:824— `method == Method::GET || method == Method::HEAD` appears character-identically in 2 files — crates/core/src/fs/named_file.rs, crates/core/src/writing/seek.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/core/src/fs/named_file.rs:858— `req_headers.contains_key(IF_NONE_MATCH) || !retrieval` appears character-identically in 2 files — crates/core/src/fs/named_file.rs, crates/core/src/writing/seek.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Hand-rolled JSON/XML parsing via regex crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-bundle.js:2— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-es-bundle.js:2— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — 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.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 23 project(s) overshoot their size bounds, lowering Project Cohesion to 9.1/10. The most over is `crates/core` (30750 LoC, 173 module-visible types across 18 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 1 of 245 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 245 of the 280 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: crates/cors/src/inner.rs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Orphaned file crates/cors/src/inner.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
No ADRs — 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.
Logging is not universal — Only 17/18 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
P3 · Security & performance tooling· Dependabot does not watch npm · ×1
Dependabot does not watch npm REDACTED:7— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
Security headers incomplete — Set: X-Content-Type-Options. Missing: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.5 on this card.) The server: `.serve_connection(` (crates/core/src/conn/proto.rs:161).
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui-standalone-preset.js`, `crates/oapi/src/swagger_ui/v5.34.0/swagger-ui.js` — so the PII/GDPR sweep did not cover them at all.
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.
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.
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.
Run 01a1dbc1-4e34-77be-8ea1-eb00e22cc4b5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 16 · Warnings: 376 · Recommendations: 48 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 20:30 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.