Public report of build-trust/ockam, published 28 October 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, 19:57 UTC · Survey ID cd_51099a7b6d194fb6a34054b4b8764d87
build-trust/ockam
Measured 28 October 2026, 08:53 UTC, at code version 0435d8d
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskNo 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: 156,143 lines of product code in 29 projects, tests not counted · Estimated rebuild effort: about 1.2 person-years · Weakest lens: Security and Compliance, 39
Findings by how serious they are
62 critical803 serious806 minor
30 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
28 October 2026, 08:53 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 Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸
55of 55 dimensions measured by tools.
1609of 1671 findings point to an exact file and line, so you can open each one in the code. The other 62 concern the repository as a whole, such as missing documentation.
55dimensions across 8 lenses, read from 156,143 lines of product code in 29 projects.
build-trust/ockam is rated At risk because critical security findings are open. Its score is held back in part because it has packages with a known security hole. It scores 55 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Security and Compliance, at 39, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Replacing the six passwords or keys found in the code's history comes next, worth about 3 points. Raising Security and Compliance to 68 would lift the score to about 65.
Fifteen known security holes in the packages the code depends on can be used by attackers. Twelve weaknesses in the code could be used by an attacker. Updating the vulnerable packages and fixing the weaknesses the scanner points to would close both risks. Passing outside input through environment variables would fix the 11 pipeline steps that put outside input straight into a shell command, and the eight passwords or keys in the code's history need replacing, with the old ones switched off. Moving the business rules into the object that owns the data would take care of the business object that only holds data.
The product code is 156,143 lines, about €170,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.
Watchdog compares 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: 2 findings
These 2 critical or serious findings were in the previous survey, on 14 October 2026, and are gone from this one.
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Rebuild cost: about €170,000 · Estimate
Cost to rebuild
€58,000 to €290,000, for 967 to 3,068 hours of work, about 1.2 person-years for 1 to 3 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.8 at a score of 55. 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: 156,143 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: Watchdog prices 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
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 8 points · Low effort · ADR Quality
2
Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED.
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 €170,000 to build again, about 1.2 person-years of work. Its weakest lens is Security and Compliance, at 39 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 1 ADR Quality findings. 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.
951 modules, with 3082 dependencies between them. 11 loops run through 98 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 911 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.
ockam_abac.policy_expr uses ockam_abac.expr, so a change to ockam_abac.expr can break ockam_abac.policy_expr, while a change to ockam_abac.policy_expr can't break ockam_abac.expr.
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.
ockam_api.orchestrator.email_address uses ockam_command.error, so a change to ockam_command.error can break ockam_api.orchestrator.email_address, while a change to ockam_api.orchestrator.email_address can't break ockam_command.error.
Position
Below the diagonal: ockam_api.orchestrator.email_address uses a module listed above it, which is the healthy direction.
ockam_api.ui.terminal uses ockam_api.ui.output, so a change to ockam_api.ui.output can break ockam_api.ui.terminal, while a change to ockam_api.ui.terminal can't break ockam_api.ui.output.
Position
Below the diagonal: ockam_api.ui.terminal uses a module listed above it, which is the healthy direction.
ockam_core.routing.route uses ockam_api.ui.output, so a change to ockam_api.ui.output can break ockam_core.routing.route, while a change to ockam_core.routing.route can't break ockam_api.ui.output.
Position
Below the diagonal: ockam_core.routing.route uses a module listed above it, which is the healthy direction.
13→20 ockam_core.routing.route uses ockam_core.messagepart of a loop✕
Connections
1 pair of types, where a type in ockam_core.routing.route uses a type in ockam_core.message.
ockam_core.routing.route uses ockam_core.message, so a change to ockam_core.message can break ockam_core.routing.route, while a change to ockam_core.routing.route can't break ockam_core.message.
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.
ockam_identity.models.timestamp uses ockam_api.ui.output, so a change to ockam_api.ui.output can break ockam_identity.models.timestamp, while a change to ockam_identity.models.timestamp can't break ockam_api.ui.output.
Position
Below the diagonal: ockam_identity.models.timestamp uses a module listed above it, which is the healthy direction.
ockam_macros.internals.ctx uses ockam_command.error, so a change to ockam_command.error can break ockam_macros.internals.ctx, while a change to ockam_macros.internals.ctx can't break ockam_command.error.
Position
Below the diagonal: ockam_macros.internals.ctx uses a module listed above it, which is the healthy direction.
ockam_node.storage.database.sqlx_database uses ockam_command.error, so a change to ockam_command.error can break ockam_node.storage.database.sqlx_database, while a change to ockam_node.storage.database.sqlx_database can't break ockam_command.error.
Position
Below the diagonal: ockam_node.storage.database.sqlx_database uses a module listed above it, which is the healthy direction.
ockam_abac.expr uses ockam_abac.policy_expr, so a change to ockam_abac.policy_expr can break ockam_abac.expr, while a change to ockam_abac.expr can't break ockam_abac.policy_expr.
Position
Below the diagonal: ockam_abac.expr uses a module listed above it, which is the healthy direction.
ockam_command.terminal.tui uses ockam_api.ui.terminal, so a change to ockam_api.ui.terminal can break ockam_command.terminal.tui, while a change to ockam_command.terminal.tui can't break ockam_api.ui.terminal.
Position
Below the diagonal: ockam_command.terminal.tui uses a module listed above it, which is the healthy direction.
ockam_core.routing.message.local_message uses ockam_core.routing.route, so a change to ockam_core.routing.route can break ockam_core.routing.message.local_message, while a change to ockam_core.routing.message.local_message can't break ockam_core.routing.route.
Position
Below the diagonal: ockam_core.routing.message.local_message uses a module listed above it, which is the healthy direction.
19→20 ockam_core.routing.message.local_message uses ockam_core.messagepart of a loop✕
Connections
2 pairs of types, where a type in ockam_core.routing.message.local_message uses a type in ockam_core.message.
ockam_core.routing.message.local_message uses ockam_core.message, so a change to ockam_core.message can break ockam_core.routing.message.local_message, while a change to ockam_core.routing.message.local_message can't break ockam_core.message.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→22 ockam_core.routing.message.local_message uses ockam_core.routing.addresspart of a loop✕
Connections
1 pair of types, where a type in ockam_core.routing.message.local_message uses a type in ockam_core.routing.address.
ockam_core.routing.message.local_message uses ockam_core.routing.address, so a change to ockam_core.routing.address can break ockam_core.routing.message.local_message, while a change to ockam_core.routing.message.local_message can't break ockam_core.routing.address.
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.
ockam_core.message uses ockam_core.routing.route, so a change to ockam_core.routing.route can break ockam_core.message, while a change to ockam_core.message can't break ockam_core.routing.route.
Position
Below the diagonal: ockam_core.message uses a module listed above it, which is the healthy direction.
ockam_core.message uses ockam_core.routing.message.local_message, so a change to ockam_core.routing.message.local_message can break ockam_core.message, while a change to ockam_core.message can't break ockam_core.routing.message.local_message.
Position
Below the diagonal: ockam_core.message uses a module listed above it, which is the healthy direction.
20→22 ockam_core.message uses ockam_core.routing.addresspart of a loop✕
Connections
1 pair of types, where a type in ockam_core.message uses a type in ockam_core.routing.address.
ockam_core.message uses ockam_core.routing.address, so a change to ockam_core.routing.address can break ockam_core.message, while a change to ockam_core.message can't break ockam_core.routing.address.
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.
1 pair of types, where a type in ockam_core.api uses a type in ockam_api.ui.output.
The types involved
ockam_core.api.Reply → ockam_api.ui.output.Output
Direction
ockam_core.api uses ockam_api.ui.output, so a change to ockam_api.ui.output can break ockam_core.api, while a change to ockam_core.api can't break ockam_api.ui.output.
Position
Below the diagonal: ockam_core.api uses a module listed above it, which is the healthy direction.
ockam_core.api uses ockam_command.error, so a change to ockam_command.error can break ockam_core.api, while a change to ockam_core.api can't break ockam_command.error.
Position
Below the diagonal: ockam_core.api uses a module listed above it, which is the healthy direction.
ockam_core.api uses ockam_core.message, so a change to ockam_core.message can break ockam_core.api, while a change to ockam_core.api can't break ockam_core.message.
Position
Below the diagonal: ockam_core.api uses a module listed above it, which is the healthy direction.
ockam_core.routing.address uses ockam_api.ui.output, so a change to ockam_api.ui.output can break ockam_core.routing.address, while a change to ockam_core.routing.address can't break ockam_api.ui.output.
Position
Below the diagonal: ockam_core.routing.address uses a module listed above it, which is the healthy direction.
ockam_core.routing.address uses ockam_core.routing.route, so a change to ockam_core.routing.route can break ockam_core.routing.address, while a change to ockam_core.routing.address can't break ockam_core.routing.route.
Position
Below the diagonal: ockam_core.routing.address uses a module listed above it, which is the healthy direction.
ockam_core.routing.address uses ockam_core.message, so a change to ockam_core.message can break ockam_core.routing.address, while a change to ockam_core.routing.address can't break ockam_core.message.
Position
Below the diagonal: ockam_core.routing.address uses a module listed above it, which is the healthy direction.
ockam_core.worker uses ockam_macros.internals.ctx, so a change to ockam_macros.internals.ctx can break ockam_core.worker, while a change to ockam_core.worker can't break ockam_macros.internals.ctx.
Position
Below the diagonal: ockam_core.worker uses a module listed above it, which is the healthy direction.
ockam_core.worker uses ockam_core.message, so a change to ockam_core.message can break ockam_core.worker, while a change to ockam_core.worker can't break ockam_core.message.
Position
Below the diagonal: ockam_core.worker uses a module listed above it, which is the healthy direction.
ockam_identity.models.credential_and_purpose_key uses ockam_core.message, so a change to ockam_core.message can break ockam_identity.models.credential_and_purpose_key, while a change to ockam_identity.models.credential_and_purpose_key can't break ockam_core.message.
Position
Below the diagonal: ockam_identity.models.credential_and_purpose_key uses a module listed above it, which is the healthy direction.
ockam_identity.models.identifiers uses ockam_core.message, so a change to ockam_core.message can break ockam_identity.models.identifiers, while a change to ockam_identity.models.identifiers can't break ockam_core.message.
Position
Below the diagonal: ockam_identity.models.identifiers uses a module listed above it, which is the healthy direction.
ockam.remote.addresses uses ockam_core.routing.address, so a change to ockam_core.routing.address can break ockam.remote.addresses, while a change to ockam.remote.addresses can't break ockam_core.routing.address.
Position
Below the diagonal: ockam.remote.addresses uses a module listed above it, which is the healthy direction.
ockam_api.orchestrator.secure_clients uses ockam_api.orchestrator.email_address, so a change to ockam_api.orchestrator.email_address can break ockam_api.orchestrator.secure_clients, while a change to ockam_api.orchestrator.secure_clients can't break ockam_api.orchestrator.email_address.
Position
Below the diagonal: ockam_api.orchestrator.secure_clients uses a module listed above it, which is the healthy direction.
ockam_api.orchestrator.secure_clients uses ockam_macros.internals.ctx, so a change to ockam_macros.internals.ctx can break ockam_api.orchestrator.secure_clients, while a change to ockam_api.orchestrator.secure_clients can't break ockam_macros.internals.ctx.
Position
Below the diagonal: ockam_api.orchestrator.secure_clients uses a module listed above it, which is the healthy direction.
ockam_api.orchestrator.secure_clients uses ockam_identity.models.identifiers, so a change to ockam_identity.models.identifiers can break ockam_api.orchestrator.secure_clients, while a change to ockam_api.orchestrator.secure_clients can't break ockam_identity.models.identifiers.
Position
Below the diagonal: ockam_api.orchestrator.secure_clients uses a module listed above it, which is the healthy direction.
ockam_core.flow_control.flow_controls.flow_controls uses ockam_core.flow_control.flow_control_id, so a change to ockam_core.flow_control.flow_control_id can break ockam_core.flow_control.flow_controls.flow_controls, while a change to ockam_core.flow_control.flow_controls.flow_controls can't break ockam_core.flow_control.flow_control_id.
Position
Below the diagonal: ockam_core.flow_control.flow_controls.flow_controls uses a module listed above it, which is the healthy direction.
ockam_core.flow_control.flow_controls.flow_controls uses ockam_core.routing.address, so a change to ockam_core.routing.address can break ockam_core.flow_control.flow_controls.flow_controls, while a change to ockam_core.flow_control.flow_controls.flow_controls can't break ockam_core.routing.address.
Position
Below the diagonal: ockam_core.flow_control.flow_controls.flow_controls uses a module listed above it, which is the healthy direction.
ockam_core.routing.message.relay_message uses ockam_core.routing.route, so a change to ockam_core.routing.route can break ockam_core.routing.message.relay_message, while a change to ockam_core.routing.message.relay_message can't break ockam_core.routing.route.
Position
Below the diagonal: ockam_core.routing.message.relay_message uses a module listed above it, which is the healthy direction.
ockam_core.routing.message.relay_message uses ockam_core.routing.message.local_message, so a change to ockam_core.routing.message.local_message can break ockam_core.routing.message.relay_message, while a change to ockam_core.routing.message.relay_message can't break ockam_core.routing.message.local_message.
Position
Below the diagonal: ockam_core.routing.message.relay_message uses a module listed above it, which is the healthy direction.
ockam_core.routing.message.relay_message uses ockam_core.routing.address, so a change to ockam_core.routing.address can break ockam_core.routing.message.relay_message, while a change to ockam_core.routing.message.relay_message can't break ockam_core.routing.address.
Position
Below the diagonal: ockam_core.routing.message.relay_message uses a module listed above it, which is the healthy direction.
ockam_identity.models.change_history uses ockam_identity.models.timestamp, so a change to ockam_identity.models.timestamp can break ockam_identity.models.change_history, while a change to ockam_identity.models.change_history can't break ockam_identity.models.timestamp.
Position
Below the diagonal: ockam_identity.models.change_history uses a module listed above it, which is the healthy direction.
ockam_identity.models.change_history uses ockam_identity.models.identifiers, so a change to ockam_identity.models.identifiers can break ockam_identity.models.change_history, while a change to ockam_identity.models.change_history can't break ockam_identity.models.identifiers.
Position
Below the diagonal: ockam_identity.models.change_history uses a module listed above it, which is the healthy direction.
ockam_api.cli_state.cli_state uses ockam_api.control_api.protocol.common, so a change to ockam_api.control_api.protocol.common can break ockam_api.cli_state.cli_state, while a change to ockam_api.cli_state.cli_state can't break ockam_api.control_api.protocol.common.
Position
Below the diagonal: ockam_api.cli_state.cli_state uses a module listed above it, which is the healthy direction.
ockam_api.cli_state.cli_state uses ockam_command.error, so a change to ockam_command.error can break ockam_api.cli_state.cli_state, while a change to ockam_api.cli_state.cli_state can't break ockam_command.error.
Position
Below the diagonal: ockam_api.cli_state.cli_state uses a module listed above it, which is the healthy direction.
ockam_api.cli_state.cli_state uses ockam_multiaddr, so a change to ockam_multiaddr can break ockam_api.cli_state.cli_state, while a change to ockam_api.cli_state.cli_state can't break ockam_multiaddr.
Position
Below the diagonal: ockam_api.cli_state.cli_state uses a module listed above it, which is the healthy direction.
ockam_api.cli_state.cli_state uses ockam_transport_core.hostname_port, so a change to ockam_transport_core.hostname_port can break ockam_api.cli_state.cli_state, while a change to ockam_api.cli_state.cli_state can't break ockam_transport_core.hostname_port.
Position
Below the diagonal: ockam_api.cli_state.cli_state uses a module listed above it, which is the healthy direction.
ockam_api.cli_state.cli_state uses ockam_api.orchestrator.email_address, so a change to ockam_api.orchestrator.email_address can break ockam_api.cli_state.cli_state, while a change to ockam_api.cli_state.cli_state can't break ockam_api.orchestrator.email_address.
Position
Below the diagonal: ockam_api.cli_state.cli_state uses a module listed above it, which is the healthy direction.
ockam_api.cli_state.cli_state uses ockam_node.storage.database.sqlx_database, so a change to ockam_node.storage.database.sqlx_database can break ockam_api.cli_state.cli_state, while a change to ockam_api.cli_state.cli_state can't break ockam_node.storage.database.sqlx_database.
Position
Below the diagonal: ockam_api.cli_state.cli_state uses a module listed above it, which is the healthy direction.
ockam_api.cli_state.cli_state uses ockam_core.routing.address, so a change to ockam_core.routing.address can break ockam_api.cli_state.cli_state, while a change to ockam_api.cli_state.cli_state can't break ockam_core.routing.address.
Position
Below the diagonal: ockam_api.cli_state.cli_state uses a module listed above it, which is the healthy direction.
ockam_api.cli_state.cli_state uses ockam_identity.models.identifiers, so a change to ockam_identity.models.identifiers can break ockam_api.cli_state.cli_state, while a change to ockam_api.cli_state.cli_state can't break ockam_identity.models.identifiers.
Position
Below the diagonal: ockam_api.cli_state.cli_state uses a module listed above it, which is the healthy direction.
ockam_api.cli_state.cli_state uses ockam_identity.models.change_history, so a change to ockam_identity.models.change_history can break ockam_api.cli_state.cli_state, while a change to ockam_api.cli_state.cli_state can't break ockam_identity.models.change_history.
Position
Below the diagonal: ockam_api.cli_state.cli_state uses a module listed above it, which is the healthy direction.
ockam_command.shared_args uses ockam_multiaddr, so a change to ockam_multiaddr can break ockam_command.shared_args, while a change to ockam_command.shared_args can't break ockam_multiaddr.
Position
Below the diagonal: ockam_command.shared_args uses a module listed above it, which is the healthy direction.
ockam_command.shared_args uses ockam_identity.models.change_history, so a change to ockam_identity.models.change_history can break ockam_command.shared_args, while a change to ockam_command.shared_args can't break ockam_identity.models.change_history.
Position
Below the diagonal: ockam_command.shared_args uses a module listed above it, which is the healthy direction.
ockam_node.storage.database.auto_retry uses ockam_abac.resource, so a change to ockam_abac.resource can break ockam_node.storage.database.auto_retry, while a change to ockam_node.storage.database.auto_retry can't break ockam_abac.resource.
Position
Below the diagonal: ockam_node.storage.database.auto_retry uses a module listed above it, which is the healthy direction.
ockam_node.storage.database.auto_retry uses ockam_api.orchestrator.email_address, so a change to ockam_api.orchestrator.email_address can break ockam_node.storage.database.auto_retry, while a change to ockam_node.storage.database.auto_retry can't break ockam_api.orchestrator.email_address.
Position
Below the diagonal: ockam_node.storage.database.auto_retry uses a module listed above it, which is the healthy direction.
ockam_node.storage.database.auto_retry uses ockam_identity.models.timestamp, so a change to ockam_identity.models.timestamp can break ockam_node.storage.database.auto_retry, while a change to ockam_node.storage.database.auto_retry can't break ockam_identity.models.timestamp.
Position
Below the diagonal: ockam_node.storage.database.auto_retry uses a module listed above it, which is the healthy direction.
ockam_node.storage.database.auto_retry uses ockam_abac.expr, so a change to ockam_abac.expr can break ockam_node.storage.database.auto_retry, while a change to ockam_node.storage.database.auto_retry can't break ockam_abac.expr.
Position
Below the diagonal: ockam_node.storage.database.auto_retry uses a module listed above it, which is the healthy direction.
ockam_node.storage.database.auto_retry uses ockam_core.routing.address, so a change to ockam_core.routing.address can break ockam_node.storage.database.auto_retry, while a change to ockam_node.storage.database.auto_retry can't break ockam_core.routing.address.
Position
Below the diagonal: ockam_node.storage.database.auto_retry uses a module listed above it, which is the healthy direction.
ockam_node.storage.database.auto_retry uses ockam_identity.models.credential_and_purpose_key, so a change to ockam_identity.models.credential_and_purpose_key can break ockam_node.storage.database.auto_retry, while a change to ockam_node.storage.database.auto_retry can't break ockam_identity.models.credential_and_purpose_key.
Position
Below the diagonal: ockam_node.storage.database.auto_retry uses a module listed above it, which is the healthy direction.
ockam_node.storage.database.auto_retry uses ockam_identity.models.identifiers, so a change to ockam_identity.models.identifiers can break ockam_node.storage.database.auto_retry, while a change to ockam_node.storage.database.auto_retry can't break ockam_identity.models.identifiers.
Position
Below the diagonal: ockam_node.storage.database.auto_retry uses a module listed above it, which is the healthy direction.
ockam_node.storage.database.auto_retry uses ockam_identity.models.change_history, so a change to ockam_identity.models.change_history can break ockam_node.storage.database.auto_retry, while a change to ockam_node.storage.database.auto_retry can't break ockam_identity.models.change_history.
Position
Below the diagonal: ockam_node.storage.database.auto_retry uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.background_node_client uses ockam_multiaddr, so a change to ockam_multiaddr can break ockam_api.nodes.service.background_node_client, while a change to ockam_api.nodes.service.background_node_client can't break ockam_multiaddr.
Position
Below the diagonal: ockam_api.nodes.service.background_node_client uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.background_node_client uses ockam_transport_core.hostname_port, so a change to ockam_transport_core.hostname_port can break ockam_api.nodes.service.background_node_client, while a change to ockam_api.nodes.service.background_node_client can't break ockam_transport_core.hostname_port.
Position
Below the diagonal: ockam_api.nodes.service.background_node_client uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.background_node_client uses ockam_abac.policy_expr, so a change to ockam_abac.policy_expr can break ockam_api.nodes.service.background_node_client, while a change to ockam_api.nodes.service.background_node_client can't break ockam_abac.policy_expr.
Position
Below the diagonal: ockam_api.nodes.service.background_node_client uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.background_node_client uses ockam_core.routing.route, so a change to ockam_core.routing.route can break ockam_api.nodes.service.background_node_client, while a change to ockam_api.nodes.service.background_node_client can't break ockam_core.routing.route.
Position
Below the diagonal: ockam_api.nodes.service.background_node_client uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.background_node_client uses ockam_macros.internals.ctx, so a change to ockam_macros.internals.ctx can break ockam_api.nodes.service.background_node_client, while a change to ockam_api.nodes.service.background_node_client can't break ockam_macros.internals.ctx.
Position
Below the diagonal: ockam_api.nodes.service.background_node_client uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.background_node_client uses ockam_core.api, so a change to ockam_core.api can break ockam_api.nodes.service.background_node_client, while a change to ockam_api.nodes.service.background_node_client can't break ockam_core.api.
Position
Below the diagonal: ockam_api.nodes.service.background_node_client uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.background_node_client uses ockam_core.routing.address, so a change to ockam_core.routing.address can break ockam_api.nodes.service.background_node_client, while a change to ockam_api.nodes.service.background_node_client can't break ockam_core.routing.address.
Position
Below the diagonal: ockam_api.nodes.service.background_node_client uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.background_node_client uses ockam_identity.models.credential_and_purpose_key, so a change to ockam_identity.models.credential_and_purpose_key can break ockam_api.nodes.service.background_node_client, while a change to ockam_api.nodes.service.background_node_client can't break ockam_identity.models.credential_and_purpose_key.
Position
Below the diagonal: ockam_api.nodes.service.background_node_client uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.background_node_client uses ockam_identity.models.identifiers, so a change to ockam_identity.models.identifiers can break ockam_api.nodes.service.background_node_client, while a change to ockam_api.nodes.service.background_node_client can't break ockam_identity.models.identifiers.
Position
Below the diagonal: ockam_api.nodes.service.background_node_client uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.background_node_client uses ockam_api.cli_state.cli_state, so a change to ockam_api.cli_state.cli_state can break ockam_api.nodes.service.background_node_client, while a change to ockam_api.nodes.service.background_node_client can't break ockam_api.cli_state.cli_state.
Position
Below the diagonal: ockam_api.nodes.service.background_node_client uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_abac.resource, so a change to ockam_abac.resource can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_abac.resource.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_api.control_api.protocol.common, so a change to ockam_api.control_api.protocol.common can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_api.control_api.protocol.common.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_core.flow_control.flow_control_id, so a change to ockam_core.flow_control.flow_control_id can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_core.flow_control.flow_control_id.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_multiaddr, so a change to ockam_multiaddr can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_multiaddr.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_transport_core.hostname_port, so a change to ockam_transport_core.hostname_port can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_transport_core.hostname_port.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_abac.policy_expr, so a change to ockam_abac.policy_expr can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_abac.policy_expr.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_core.routing.route, so a change to ockam_core.routing.route can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_core.routing.route.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_macros.internals.ctx, so a change to ockam_macros.internals.ctx can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_macros.internals.ctx.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_abac.expr, so a change to ockam_abac.expr can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_abac.expr.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_core.routing.address, so a change to ockam_core.routing.address can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_core.routing.address.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_identity.models.credential_and_purpose_key, so a change to ockam_identity.models.credential_and_purpose_key can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_identity.models.credential_and_purpose_key.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_identity.models.identifiers, so a change to ockam_identity.models.identifiers can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_identity.models.identifiers.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_api.orchestrator.secure_clients, so a change to ockam_api.orchestrator.secure_clients can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_api.orchestrator.secure_clients.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.manager uses ockam_api.cli_state.cli_state, so a change to ockam_api.cli_state.cli_state can break ockam_api.nodes.service.manager, while a change to ockam_api.nodes.service.manager can't break ockam_api.cli_state.cli_state.
Position
Below the diagonal: ockam_api.nodes.service.manager uses a module listed above it, which is the healthy direction.
ockam_command.command_global_opts uses ockam_api.ui.terminal, so a change to ockam_api.ui.terminal can break ockam_command.command_global_opts, while a change to ockam_command.command_global_opts can't break ockam_api.ui.terminal.
Position
Below the diagonal: ockam_command.command_global_opts uses a module listed above it, which is the healthy direction.
ockam_command.command_global_opts uses ockam_api.cli_state.cli_state, so a change to ockam_api.cli_state.cli_state can break ockam_command.command_global_opts, while a change to ockam_command.command_global_opts can't break ockam_api.cli_state.cli_state.
Position
Below the diagonal: ockam_command.command_global_opts uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_api.control_api.protocol.common, so a change to ockam_api.control_api.protocol.common can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_api.control_api.protocol.common.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_multiaddr, so a change to ockam_multiaddr can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_multiaddr.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_transport_core.hostname_port, so a change to ockam_transport_core.hostname_port can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_transport_core.hostname_port.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_abac.policy_expr, so a change to ockam_abac.policy_expr can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_abac.policy_expr.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_api.orchestrator.email_address, so a change to ockam_api.orchestrator.email_address can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_api.orchestrator.email_address.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_core.routing.route, so a change to ockam_core.routing.route can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_core.routing.route.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_macros.internals.ctx, so a change to ockam_macros.internals.ctx can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_macros.internals.ctx.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_core.routing.address, so a change to ockam_core.routing.address can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_core.routing.address.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_identity.models.credential_and_purpose_key, so a change to ockam_identity.models.credential_and_purpose_key can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_identity.models.credential_and_purpose_key.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_identity.models.identifiers, so a change to ockam_identity.models.identifiers can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_identity.models.identifiers.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_api.orchestrator.secure_clients, so a change to ockam_api.orchestrator.secure_clients can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_api.orchestrator.secure_clients.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_identity.models.change_history, so a change to ockam_identity.models.change_history can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_identity.models.change_history.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_api.cli_state.cli_state, so a change to ockam_api.cli_state.cli_state can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_api.cli_state.cli_state.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_api.nodes.service.in_memory_node uses ockam_api.nodes.service.manager, so a change to ockam_api.nodes.service.manager can break ockam_api.nodes.service.in_memory_node, while a change to ockam_api.nodes.service.in_memory_node can't break ockam_api.nodes.service.manager.
Position
Below the diagonal: ockam_api.nodes.service.in_memory_node uses a module listed above it, which is the healthy direction.
ockam_command.node uses ockam_macros.internals.ctx, so a change to ockam_macros.internals.ctx can break ockam_command.node, while a change to ockam_command.node can't break ockam_macros.internals.ctx.
Position
Below the diagonal: ockam_command.node uses a module listed above it, which is the healthy direction.
ockam_command.node uses ockam_command.command_global_opts, so a change to ockam_command.command_global_opts can break ockam_command.node, while a change to ockam_command.node can't break ockam_command.command_global_opts.
Position
Below the diagonal: ockam_command.node uses a module listed above it, which is the healthy direction.
ockam_command.node_command uses ockam_macros.internals.ctx, so a change to ockam_macros.internals.ctx can break ockam_command.node_command, while a change to ockam_command.node_command can't break ockam_macros.internals.ctx.
Position
Below the diagonal: ockam_command.node_command uses a module listed above it, which is the healthy direction.
ockam_command.node_command uses ockam_api.cli_state.cli_state, so a change to ockam_api.cli_state.cli_state can break ockam_command.node_command, while a change to ockam_command.node_command can't break ockam_api.cli_state.cli_state.
Position
Below the diagonal: ockam_command.node_command uses a module listed above it, which is the healthy direction.
ockam_command.node_command uses ockam_api.nodes.service.in_memory_node, so a change to ockam_api.nodes.service.in_memory_node can break ockam_command.node_command, while a change to ockam_command.node_command can't break ockam_api.nodes.service.in_memory_node.
Position
Below the diagonal: ockam_command.node_command uses a module listed above it, which is the healthy direction.
ockam_command.cluster.show uses ockam_api.ui.command, so a change to ockam_api.ui.command can break ockam_command.cluster.show, while a change to ockam_command.cluster.show can't break ockam_api.ui.command.
Position
Below the diagonal: ockam_command.cluster.show uses a module listed above it, which is the healthy direction.
ockam_command.cluster.show uses ockam_macros.internals.ctx, so a change to ockam_macros.internals.ctx can break ockam_command.cluster.show, while a change to ockam_command.cluster.show can't break ockam_macros.internals.ctx.
Position
Below the diagonal: ockam_command.cluster.show uses a module listed above it, which is the healthy direction.
ockam_command.cluster.show uses ockam_command.command_global_opts, so a change to ockam_command.command_global_opts can break ockam_command.cluster.show, while a change to ockam_command.cluster.show can't break ockam_command.command_global_opts.
Position
Below the diagonal: ockam_command.cluster.show uses a module listed above it, which is the healthy direction.
ockam_command.cluster.show uses ockam_api.nodes.service.in_memory_node, so a change to ockam_api.nodes.service.in_memory_node can break ockam_command.cluster.show, while a change to ockam_command.cluster.show can't break ockam_api.nodes.service.in_memory_node.
Position
Below the diagonal: ockam_command.cluster.show uses a module listed above it, which is the healthy direction.
ockam_command.cluster.show uses ockam_command.node_command, so a change to ockam_command.node_command can break ockam_command.cluster.show, while a change to ockam_command.cluster.show can't break ockam_command.node_command.
Position
Below the diagonal: ockam_command.cluster.show uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 72% · Adequate · gated by X4 ·
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
A03:2025 — Software Supply Chain Failures
78
High / Critical
A05:2025 — Injection
35
High / Critical
A02:2025 — Security Misconfiguration
24
High / Critical
A07:2025 — Authentication Failures
9
High / Critical
Roadmap
Begin by addressing critical security and stability risks, specifically removing six historical secrets from credential exchange files and updating the Rust toolchain to resolve the end-of-life runtime warning. Next, improve code maintainability by cleaning up 696 orphaned files, prioritizing mod.rs, create.rs, and delete.rs. Finally, establish a formal process for architectural decisions by documenting significant design choices in a dedicated ADR folder to ensure knowledge freshness and traceability.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.
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.
Resolve the 3 REDACTED finding(s) charged to Static Analysis (SAST) — the other 2 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
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 — 62
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 — 803
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 — 806
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 30
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 55 of 55 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 55 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, 1609 of 1671 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs, .exs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or lcov — `mix test --cover` with `excoveralls` (`mix coveralls.lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or lcov — `mix test --cover` with `excoveralls` (`mix coveralls.lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs, .exs) and this repository declares a Cargo test suite (repository root, 258 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D19 Documentation Quality — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D28 Secrets (history) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `implementations/rust/ockam/ockam_command/src/node/create/err_demo_config_files/1.missing-colon.json`, `implementations/rust/ockam/ockam_command/src/node/create/err_demo_config_files/2.missing-comma.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 10 | COPY --from=binary /work/target/x86_64-unknown-linux-musl/release/examples/rendezvous_server /opt/rendezvous_server 11 | -------------------- ERROR: failed to solve: cgr.dev/chainguard/wolfi-base: failed to resolve source metadata for cgr.dev/chainguard/wolfi-base:latest: failed to do request: Head "https://cgr.dev/v2/chainguard/wolfi-base/manifests/latest": Forbidden; runtime evidence skipped.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Elixir, Erlang, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Elixir, Erlang, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 554 further occurrence(s) are not listed individually; the score already reflects all 594.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. X7 measured the part of this repository it reads (C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart), and its Elixir, Erlang source is outside the check's reach, so the card covers only part of the product. That is a gap in this analyzer's language reach — not a finding that the unread source is free of silent defaults.
Repo exclusion declarations: 10 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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 REDACTED (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.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
14 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was ockam_abac::eval::eval at 58. A further 9 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being NodeManagerWorker::handle_request at 55 — they are counted neither in the figure above nor in this dimension's score. 5 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: implementations/rust/ockam/ockam_api/src/nodes/service/worker.rs (NodeManagerWorker::handle_request at 55), implementations/rust/ockam/ockam_command/src/subcommand.rs (OckamSubcommand::run at 44), implementations/rust/ockam/ockam_transport_core/src/error.rs (TransportError::fmt at 37), implementations/rust/ockam/ockam_abac/src/boolean_expr.rs (BooleanExpr::fmt at 21), implementations/rust/ockam/ockam_vault/src/error.rs (VaultError::fmt at 17). 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.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ockam_abac::eval::eval (cyclomatic 58), ockam_abac::parser::parse (cyclomatic 47). — 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 Cyclomatic Complexity from 7.5 to about 8.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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.
+ 38 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with ockam_abac::eval::eval (cognitive 129). — Refactoring it lifts Cognitive Complexity from 5.7 to about 6.5/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.2 / 10Stronggated by 32 serious findings✓ 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 MethodTooLong finding(s) in God Classes — start with dev.rs, worker.rs, node_manager.rs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 8 TooManyMethods finding(s) in God Classes — start with cli_state.rs, manager.rs, worker.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 4 FunctionTooLong finding(s) in God Classes — start with eval.rs, parser.rs, util.rs. — One of this dimension's main actionable groups (4 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
192 duplicated block group(s) detected. A further 13 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 5 of the 205 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 64 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 16 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with create.rs (2), expr.rs, state.rs. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 15 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with portal_worker.rs (2), show.rs (2), expr.rs. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 15 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with mutex.rs (2), lifecycle.rs, acceptor_worker.rs. — One of this dimension's main actionable groups (15 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.4 / 10Strong✓ 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.
28 production modules (Cargo+OTP), 0 dependency cycle(s), 2 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 26 of the 28 (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: ockam_rust_elixir_nifs (OTP) · ×3
Unstable project ockam (Cargo)
Unstable project ockam_api
What to do
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Unstable project ockam (Cargo) finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project ockam_api finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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 11 Low cohesion finding(s) in Cohesion (LCOM4) — start with options.rs (5), deploy.rs, handshake.rs. — One of this dimension's main actionable groups (11 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
699 test methods: 499 unit, 200 integration, 0 BDD, 0 e2e. The Rust suite contributes 699 `#[test]` function(s) across 258 file(s) declaring at least one; its unit/integration split is Cargo's own — 63 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
38 outdated, 0 retired direct Hex dependencies, 3 pinning defect(s). Whether any of these packages is UNMAINTAINED is not graded — hex.pm publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: a Hex app name does not determine the modules it provides (`ecto_sql` provides Ecto.Adapters.SQL), and a large idiomatic class of BEAM dependencies — runtime adapters, codec plugins, protocol implementations and OTP applications the release starts — is correctly declared and never referenced in source, so absence of a reference is not evidence of an unused dependency. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Floating source dependency: neotoma · ×3
Outdated: cbor · ×38
What to do
Resolve the 3 Floating source dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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 833 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository.
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.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
13 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is implementations/rust/ockam/ockam_command/src/zone/dev.rs. Counted over 699 of the 1281 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_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.
382 deducted task-comment markers across 156143 LoC (0.2/KLoC) → score 9.5. 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 332 TodoComment finding(s) in Explicit Debt — start with executor.rs (12), mod.rs (9), lib.rs (6). — One of this dimension's main actionable groups (332 warning-level).
Resolve the 48 FixmeComment finding(s) in Explicit Debt — start with sender.rs (12), mod.rs (9), listener.rs (5). — One of this dimension's main actionable groups (48 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with common.rs, secure_channel_test.exs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
6 of 29 build units (Cargo, Mix) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — 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).
35 finding(s): 0 critical, 32 high, 3 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `implementations/rust/ockam/ockam_abac/src/expr.rs`, `implementations/rust/ockam/ockam_command/src/node/create/err_demo_config_files/1.missing-colon.json`, `implementations/rust/ockam/ockam_command/src/node/create/err_demo_config_files/1.missing-colon.yaml`, `implementations/rust/ockam/ockam_command/src/node/create/err_demo_config_files/2.missing-comma.json` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 11 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
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10), REDACTED, REDACTED. — One of this dimension's main actionable groups (12 issue-level).
Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (11 issue-level).
Resolve the 3 REDACTED finding(s) charged to Static Analysis (SAST) — the other 2 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (5 issue-level, 3 of them charged here).
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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 17 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (17). — One of this dimension's main actionable groups (17 warning-level).
Resolve the 14 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (6). — One of this dimension's main actionable groups (14 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 6 High IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 11 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 7 Low IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
699 of 699 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is implementations/rust/ockam/ockam_command/src/zone/zone_config.rs. Counted over 699 of the 1281 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3implementations/rust/ockam/ockam_command/src/zone/zone_config.rs:1
Dormant codebase
What to do
Resolve the 696 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (31), create.rs (21), delete.rs (17). — One of this dimension's main actionable groups (696 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with zone_config.rs, mod.rs, REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
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 23 Change coupling finding(s) in Change Coupling — start with create.rs (5), delete.rs (3), list.rs (3). — One of this dimension's main actionable groups (23 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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. Scored 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. SCORED, not informational.
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.
1 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.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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?
DM4 · Rich vs anemic domain model7.9 / 10Strong✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`Vault` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside. — implementations/rust/ockam/ockam_identity/src/vault.rs:16
What to do
Move the domain logic onto the entity (invariant-enforcing `&mut self` commands) instead of a foreign service.
Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 35 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
What to do
Expand the README with getting-started, architecture overview and a project map.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 8 of 38 project(s) that lack one — worth up to 0.4 pts.
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.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
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 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.
Only 23/24 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `implementations/rust/ockam/ockam_macros`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route on your axum/actix router) 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.
What to do
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.
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 the language 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 · 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.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. 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.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a walk over an ETS table leaves the key it stands on alone — Erlang's own lists and maps are values no body can change, but an ETS key traversal asks the table for the key after the current one, so on a `set`, `bag` or `duplicate_bag` that is not fixed with `ets:safe_fixtable/2`, deleting the current key and then calling `ets:next/2` (or `ets:prev/2`) from it raises `badarg` and the rest of the table is never visited.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
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.
`error!` at line 47 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`. — implementations/rust/ockam/ockam_vault_aws/src/aws_signing_vault.rs:47
`debug!` at line 28 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`. — implementations/rust/ockam/ockam_transport_websocket/src/workers/listener.rs:28
`debug!` at line 57 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`. — implementations/rust/ockam/ockam_transport_websocket/src/workers/receiver.rs:57
`info!` at line 65 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`. — implementations/rust/ockam/ockam_transport_websocket/src/workers/receiver.rs:65
`trace!` at line 83 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — implementations/rust/ockam/ockam_transport_websocket/src/workers/receiver.rs:83, implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:83
`trace!` at line 91 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — implementations/rust/ockam/ockam_transport_websocket/src/workers/receiver.rs:91, implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:91
`trace!` at line 92 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — implementations/rust/ockam/ockam_transport_websocket/src/workers/receiver.rs:92, implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:92
`warn!` at line 201 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`. — implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:201
`debug!` at line 206 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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`. — implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:206
`warn!` at line 216 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`. — implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:216
`debug!` at line 220 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:220
`debug!` at line 81 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`. — implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:81
`trace!` at line 154 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:154
`trace!` at line 175 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:175
`trace!` at line 211 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:211
`error!` at line 45 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`. — implementations/rust/ockam/ockam_transport_uds/src/lib.rs:45
`error!` at line 36 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`. — implementations/rust/ockam/ockam_transport_uds/src/workers/listener.rs:36
`debug!` at line 40 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`. — implementations/rust/ockam/ockam_transport_uds/src/workers/listener.rs:40
`debug!` at line 47 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`. — implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:47
`trace!` at line 63 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:63
`error!` at line 72 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`. — implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:72
`error!` at line 228 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_uds/src/workers/sender.rs:228
`debug!` at line 43 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`. — implementations/rust/ockam/ockam_transport_uds/src/router/uds_router.rs:43
`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`. — implementations/rust/ockam/ockam_transport_uds/src/router/uds_router.rs:142
`error!` at line 173 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`. — implementations/rust/ockam/ockam_transport_uds/src/router/uds_router.rs:173
`trace!` at line 190 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_uds/src/router/uds_router.rs:190
`trace!` at line 200 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_uds/src/router/uds_router.rs:200
`error!` at line 241 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`. — implementations/rust/ockam/ockam_transport_uds/src/router/uds_router.rs:241
`error!` 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: `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`. — implementations/rust/ockam/ockam_transport_uds/src/router/uds_router.rs:260
`error!` at line 309 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`. — implementations/rust/ockam/ockam_transport_uds/src/router/uds_router.rs:309
`warn!` at line 70 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`. — implementations/rust/ockam/ockam_transport_udp/src/workers/receiver.rs:70
`trace!` at line 66 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_udp/src/workers/sender.rs:66
`trace!` at line 104 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_udp/src/workers/sender.rs:104
`error!` at line 107 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`. — implementations/rust/ockam/ockam_transport_udp/src/workers/sender.rs:107
`trace!` at line 43 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_udp/src/workers/pending_messages/peer_pending_routing_message_storage.rs:43
`trace!` at line 52 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_udp/src/workers/pending_messages/peer_pending_routing_message_storage.rs:52
`trace!` at line 78 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — implementations/rust/ockam/ockam_transport_udp/src/workers/pending_messages/peer_pending_routing_message_storage.rs:78
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 — 1 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.
X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
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.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 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 — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: the BEAM has no dependency-injection container — state lives in processes, and no process is handed an instance whose lifetime another one scopes; 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. Elixir processes share no mutable memory — state lives in a process's own mailbox — so there is no shared object to race on. Erlang processes share no mutable memory — state lives in a process's own mailbox — so there is no shared object to race on. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — 10 | COPY --from=binary /work/target/x86_64-unknown-linux-musl/release/examples/rendezvous_server /opt/rendezvous_server 11 | -------------------- ERROR: failed to solve: cgr.dev/chainguard/wolfi-base: failed to resolve source metadata for cgr.dev/chainguard/wolfi-base:latest: failed to do request: Head "https://cgr.dev/v2/chainguard/wolfi-base/manifests/latest": Forbidden; 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~19730 lines of test source are present (.rs, .exs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — D19 reads .NET projects as units only; 29 folder(s) declared by Cargo.toml, mix.exs were not judged for an overview, an example or the map.
D21 Naming Consistency — Naming consistency is measured on C# only; Elixir, Erlang, Python, Rust not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .erl, .ex, .exs, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Elixir, Erlang, Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — sqlx is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb. Elixir runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — 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
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
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. Elixir processes share no heap: a value sent to another process arrives as a copy, so no collection is reachable from two processes at once. Erlang processes share no heap: a value sent to another process arrives as a copy, so no collection is reachable from two processes at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
X31 Test-only surface in a production module — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
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.
DM4 · Rich vs anemic domain model· Anemic domain model · ×1
Anemic domain model: Vault implementations/rust/ockam/ockam_identity/src/vault.rs:16— `Vault` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside.
TodoComment implementations/rust/ockam/ockam_vault/src/software/vault_for_secure_channels/types.rs:71— // TODO — 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 implementations/rust/ockam/ockam_transport_ble/src/driver/bluetooth_hci/ble_uart.rs:247— // TODO — 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 implementations/rust/ockam/ockam_multiaddr/src/lib.rs:410— // TODO — 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 implementations/rust/ockam/ockam_multiaddr/src/lib.rs:420— // TODO — 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 implementations/rust/ockam/ockam_core/src/error/inner/formatting.rs:78— // TODO — 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 implementations/rust/ockam/ockam_core/src/error/inner/formatting.rs:85— // TODO — 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 implementations/rust/ockam/ockam_transport_websocket/src/router/handle.rs:58— // TODO: Remove in favor of `ockam_node::compat::asynchronous::resolve_peer` — 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 implementations/rust/ockam/ockam_transport_uds/src/router/handle.rs:136— // TODO: Remove in favor of `ockam_node::compat::asynchronous::resolve_peer` — 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 implementations/rust/ockam/ockam_transport_ble/src/router/handle.rs:61— // TODO: Remove in favor of `ockam_node::compat::asynchronous::resolve_peer` — 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 implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:192— // TODO: Check if this is the hostname and we have existing/pending connection to this IP — 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 implementations/rust/ockam/ockam_transport_uds/src/lib.rs:7— // TODO: Are there any known uses cases for no_std with UDS — 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 implementations/rust/ockam/ockam_transport_uds/src/lib.rs:23— // TODO: Should have documentation or enum for this — 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 implementations/rust/ockam/ockam_transport_udp/src/workers/pending_messages/peer_pending_routing_message_storage.rs:14— // TODO: Can we share them between other peers? — 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 implementations/rust/ockam/ockam_transport_udp/src/workers/pending_messages/pending_message.rs:15— // TODO: I think usually total number is low, so we can use bitmap or vec here — 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 implementations/rust/ockam/ockam_transport_udp/src/workers/pending_messages/pending_routing_message_storage.rs:8— /// TODO: Clearing everything for a socket after long inactivity would be nice — 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 implementations/rust/ockam/ockam_transport_udp/src/transport/bind.rs:91— // TODO: Would be better to tie this socket to a specific peer when — 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 implementations/rust/ockam/ockam_transport_udp/src/transport/mod.rs:15— // TODO: Add registry, — 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 implementations/rust/ockam/ockam_transport_udp/src/puncture/puncture/puncture.rs:24— // TODO: PUNCTURE make keepalives adjustable — 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 implementations/rust/ockam/ockam_transport_udp/src/puncture/puncture/puncture.rs:65— /// TODO: PUNCTURE optimize to return immediately if the puncture is open — 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 implementations/rust/ockam/ockam_transport_udp/src/puncture/puncture/receiver.rs:20— // TODO: PUNCTURE Possible future improvement, explicitly send list of possible — 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 implementations/rust/ockam/ockam_transport_udp/src/puncture/puncture/receiver.rs:185— // TODO: Add proper LocalInfo — 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 implementations/rust/ockam/ockam_transport_udp/src/puncture/puncture/sender.rs:44— // TODO: Add proper LocalInfo — 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 implementations/rust/ockam/ockam_transport_udp/src/messages/routing_message.rs:71— // TODO: Add proper LocalInfo — 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 implementations/rust/ockam/ockam_transport_udp/src/puncture/negotiation/listener.rs:59— // TODO: Consider limiting incoming access control for that bind — 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 implementations/rust/ockam/ockam_transport_udp/src/puncture/negotiation/negotiation.rs:42— // TODO: Consider limiting incoming access control for that bind — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/listener.rs:39— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/listener.rs:40— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:65— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:66— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:71— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:72— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:110— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:111— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:116— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:117— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:161— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:162— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:109— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:110— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:115— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:116— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_ble/src/workers/listener.rs:42— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_ble/src/workers/listener.rs:43— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_ble/src/workers/sender.rs:95— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_ble/src/workers/sender.rs:96— // FIXME: @ac — 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.
FixmeComment implementations/rust/ockam/ockam_transport_websocket/src/router/handle.rs:71— // FIXME: We only take ipv4 for now — 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.
FixmeComment implementations/rust/ockam/ockam_transport_tcp/src/privileged_portal/privileged_portals.rs:104— // FIXME — 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.
FixmeComment implementations/rust/ockam/ockam_transport_tcp/src/privileged_portal/privileged_portals.rs:137— // FIXME — 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.
FixmeComment implementations/rust/ockam/ockam_transport_tcp/src/privileged_portal/privileged_portals.rs:156— // FIXME — 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.
FixmeComment implementations/rust/ockam/ockam_transport_tcp/src/privileged_portal/privileged_portals.rs:192— // FIXME — 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.
Change coupling: inlet.rs ↔ outlet.rs implementations/rust/ockam/ockam_command/src/zone/inlet.rs:1— `implementations/rust/ockam/ockam_command/src/zone/inlet.rs` and `implementations/rust/ockam/ockam_command/src/zone/outlet.rs` change together 90% of the time (9 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 9 shared commits counted here, the most recent 3 are `7f4235bc` feat: add timeout to `zone inlet/outlet` creation when waiting for th…; `f820d1f8` feat(rust): improvements to cluster outlet command (at that commit the files were still `implementations/rust/ockam/ockam_command/src/cluster/inlet.rs` and `implementations/rust/ockam/ockam_command/src/cluster/outlet.rs`); `1271ff4f` feat: add `background` argument to `cluster inlet/outlet` (at that commit the files were still `implementations/rust/ockam/ockam_command/src/cluster/inlet.rs` and `implementations/rust/ockam/ockam_command/src/cluster/outlet.rs`) — run `git show` on any of them.
Change coupling: controller_client.rs ↔ node_service_client.rs implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/controller_client.rs:1— `implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/controller_client.rs` and `implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs` change together 82% of the time (9 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 9 shared commits counted here, the most recent 3 are `2cdd831d` Add dev enrollment ticket for gateway portal in dev mode; `d24499c9` Add user-level development token support for zone dev; `09a2fea6` Add create_gateway_token to AiPlatformApi trait — run `git show` on any of them.
Change coupling: delete.rs ↔ show.rs implementations/rust/ockam/ockam_command/src/space/delete.rs:1— `implementations/rust/ockam/ockam_command/src/space/delete.rs` and `implementations/rust/ockam/ockam_command/src/space/show.rs` change together 70% of the time (7 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 7 shared commits counted here, the most recent 3 are `d72f79e7` refactor(rust): add plural terms for `tui` traits; `fdb22e2e` refactor(rust): make it easier to write commands' api req/res handlers; `d7256de9` feat(rust): rename ockam command output format option — run `git show` on any of them.
Change coupling: create.rs ↔ delete.rs implementations/rust/ockam/ockam_command/src/tcp/connection/create.rs:1— `implementations/rust/ockam/ockam_command/src/tcp/connection/create.rs` and `implementations/rust/ockam/ockam_command/src/tcp/connection/delete.rs` change together 69% of the time (11 of the 16 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 11 shared commits counted here, the most recent 3 are `59583f09` feat(rust): unify output of crud tcp-connection commands; `d7b2fdd7` fix(rust): add worker address to the output of `tcp-connection create`; `437625c0` docs(rust): include documentation in tcp commands — run `git show` on any of them.
Change coupling: list.rs ↔ show.rs implementations/rust/ockam/ockam_command/src/node/list.rs:1— `implementations/rust/ockam/ockam_command/src/node/list.rs` and `implementations/rust/ockam/ockam_command/src/node/show.rs` change together 65% of the time (15 of the 23 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 15 shared commits counted here, the most recent 3 are `55bf8627` refactor(rust): add trait to tuify `show` commands; `692494fc` feat(rust): make `node show` interactive; `ed04005c` feat(rust): print default alongside node name — run `git show` on any of them.
Change coupling: registry.rs ↔ service.rs implementations/rust/ockam/ockam_api/src/nodes/registry.rs:1— `implementations/rust/ockam/ockam_api/src/nodes/registry.rs` and `implementations/rust/ockam/ockam_api/src/nodes/service.rs` change together 63% of the time (26 of the 41 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 26 shared commits counted here, the most recent 3 are `d32e00a3` feat(rust): added the possibility to overwrite http headers in inlets; `2373bff8` refactor(rust): adjust the node manager worker for deleting kafka ser…; `6d80e1bd` refactor(rust): adjust the code after rebase — run `git show` on any of them.
Change coupling: create.rs ↔ list.rs implementations/rust/ockam/ockam_command/src/tcp/connection/create.rs:1— `implementations/rust/ockam/ockam_command/src/tcp/connection/create.rs` and `implementations/rust/ockam/ockam_command/src/tcp/listener/list.rs` change together 62% of the time (8 of the 13 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 8 shared commits counted here, the most recent 3 are `437625c0` docs(rust): include documentation in tcp commands; `939eccb4` feat(rust): improve tcp command ux; `8518a608` feat(rust): get rid of `NodeManager` transport registry — run `git show` on any of them.
Change coupling: create.rs ↔ list.rs implementations/rust/ockam/ockam_command/src/tcp/listener/create.rs:1— `implementations/rust/ockam/ockam_command/src/tcp/listener/create.rs` and `implementations/rust/ockam/ockam_command/src/tcp/listener/list.rs` change together 62% of the time (8 of the 13 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 8 shared commits counted here, the most recent 3 are `437625c0` docs(rust): include documentation in tcp commands; `939eccb4` feat(rust): improve tcp command ux; `8ca9793f` feat(rust): `TCP` commands updates: — run `git show` on any of them.
Change coupling: base_command.rs ↔ repl.rs implementations/rust/ockam/ockam_command/src/base_command.rs:1— `implementations/rust/ockam/ockam_command/src/base_command.rs` and `implementations/rust/ockam/ockam_command/src/zone/repl.rs` change together 62% of the time (8 of the 13 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 8 shared commits counted here, the most recent 3 are `80728def` refactor: split repl into attach/repl subcommands; `8254dca6` feat: after deploying a zone, show public http server url; `ebff732b` chore: cluster/zone renames — run `git show` on any of them.
Change coupling: REDACTED ↔ space.rs implementations/rust/ockam/ockam_api/src/orchestrator/enroll.rs:1— `implementations/rust/ockam/ockam_api/src/orchestrator/enroll.rs` and `implementations/rust/ockam/ockam_api/src/orchestrator/space.rs` change together 57% of the time (20 of the 35 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 20 shared commits counted here, the most recent 3 are `20926bd4` feat(rust): propagating the errors from api clients to the command (at that commit the files were still `implementations/rust/ockam/ockam_api/src/cloud/enroll.rs` and `implementations/rust/ockam/ockam_api/src/cloud/space.rs`); `81f73eab` feat(rust): create a relay to the default project after enrolling and… (at that commit the files were still `implementations/rust/ockam/ockam_api/src/cloud/enroll.rs` and `implementations/rust/ockam/ockam_api/src/cloud/space.rs`); `808c3725` refactor(rust): remove the need for a model state (at that commit the files were still `implementations/rust/ockam/ockam_api/src/cloud/enroll.rs` and `implementations/rust/ockam/ockam_api/src/cloud/space.rs`) — run `git show` on any of them.
Change coupling: show.rs ↔ delete.rs implementations/rust/ockam/ockam_command/src/project/show.rs:1— `implementations/rust/ockam/ockam_command/src/project/show.rs` and `implementations/rust/ockam/ockam_command/src/space/delete.rs` change together 55% of the time (6 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 6 shared commits counted here, the most recent 3 are `d72f79e7` refactor(rust): add plural terms for `tui` traits; `d7256de9` feat(rust): rename ockam command output format option; `9eb80b76` refactor(rust): rename `NODEMAN_ADDR` to `NODEMANAGER_ADDR` — run `git show` on any of them.
Change coupling: node_service_client.rs ↔ create.rs implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:1— `implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs` and `implementations/rust/ockam/ockam_command/src/zone/create.rs` change together 54% of the time (7 of the 13 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 `d2b5156d` feat: in `cluster create`, parallelize `docker build` calls (at that commit the file was still `implementations/rust/ockam/ockam_command/src/cluster/create.rs`); `22e198ca` feat(rust): adjustments for public eks (at that commit the file was still `implementations/rust/ockam/ockam_command/src/cluster/create.rs`); `83390293` feat(rust): add cluster cbor struct (at that commit the file was still `implementations/rust/ockam/ockam_command/src/cluster/create.rs`) — run `git show` on any of them.
Change coupling: config.rs ↔ start.rs implementations/rust/ockam/ockam_command/src/service/config.rs:1— `implementations/rust/ockam/ockam_command/src/service/config.rs` and `implementations/rust/ockam/ockam_command/src/service/start.rs` change together 54% of the time (7 of the 13 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 `fcb95056` feat(rust): add flag to reload enrollers from a file; `7dbe8f3b` feat(rust): support json configuration for enrollers; `746ce0b1` feat(rust): make the okta tenant config more generic — run `git show` on any of them.
Change coupling: create.rs ↔ delete.rs implementations/rust/ockam/ockam_command/src/secure_channel/create.rs:1— `implementations/rust/ockam/ockam_command/src/secure_channel/create.rs` and `implementations/rust/ockam/ockam_command/src/secure_channel/delete.rs` change together 53% of the time (8 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 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 8 shared commits counted here, the most recent 3 are `97780be0` refactor(rust): improve error messages returned when parsing the node…; `d973283b` fix(rust): replace atty dependency with is-terminal; `1510927e` docs(rust): codespell implementations/rust/ — run `git show` on any of them.
Change coupling: list.rs ↔ delete.rs implementations/rust/ockam/ockam_command/src/tcp/connection/list.rs:1— `implementations/rust/ockam/ockam_command/src/tcp/connection/list.rs` and `implementations/rust/ockam/ockam_command/src/tcp/listener/delete.rs` change together 52% of the time (11 of the 21 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 11 shared commits counted here, the most recent 3 are `53745c66` docs(rust): update command docs; `437625c0` docs(rust): include documentation in tcp commands; `8518a608` feat(rust): get rid of `NodeManager` transport registry — run `git show` on any of them.
Change coupling: command.rs ↔ oidc_service.rs implementations/rust/ockam/ockam_command/src/enroll/command.rs:1— `implementations/rust/ockam/ockam_command/src/enroll/command.rs` and `implementations/rust/ockam/ockam_command/src/enroll/oidc_service.rs` change together 52% of the time (11 of the 21 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 11 shared commits counted here, the most recent 3 are `84a02edf` feat(rust): add ai subcommands for enroll and ticket; `d11b610e` feat: adjust `enroll` logic and output for the new subscription plans; `7fff1f6d` feat(rust): improve output for `enroll` command — run `git show` on any of them.
Change coupling: services.rs ↔ service.rs implementations/rust/ockam/ockam_api/src/nodes/models/services.rs:1— `implementations/rust/ockam/ockam_api/src/nodes/models/services.rs` and `implementations/rust/ockam/ockam_api/src/nodes/service.rs` change together 52% of the time (15 of the 29 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 15 shared commits counted here, the most recent 3 are `411fbad6` fix(rust): use the outlet socket address to search for the outlet status; `63f5bc2e` feat(rust): added a direct local kafka for simple deployments and fix…; `1f0b5670` feat(rust): add delete and list subcommands for kafka consumer/produc… — run `git show` on any of them.
Change coupling: addon.rs ↔ REDACTED implementations/rust/ockam/ockam_api/src/orchestrator/addon.rs:1— `implementations/rust/ockam/ockam_api/src/orchestrator/addon.rs` and `implementations/rust/ockam/ockam_api/src/orchestrator/enroll.rs` change together 50% of the time (7 of the 14 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 `20926bd4` feat(rust): propagating the errors from api clients to the command (at that commit the files were still `implementations/rust/ockam/ockam_api/src/cloud/addon.rs` and `implementations/rust/ockam/ockam_api/src/cloud/enroll.rs`); `a15b679a` refactor(rust): create tcp_connection along with secure channels in t… (at that commit the files were still `implementations/rust/ockam/ockam_api/src/cloud/addon.rs` and `implementations/rust/ockam/ockam_api/src/cloud/enroll.rs`); `0c34429b` feat(rust): parse `/node/n1` to `/worker/addr` after connecting to th… (at that commit the files were still `implementations/rust/ockam/ockam_api/src/cloud/addon.rs` and `implementations/rust/ockam/ockam_api/src/cloud/enroll.rs`) — run `git show` on any of them.
Change coupling: delete.rs ↔ inlet.rs implementations/rust/ockam/ockam_command/src/zone/delete.rs:1— `implementations/rust/ockam/ockam_command/src/zone/delete.rs` and `implementations/rust/ockam/ockam_command/src/zone/inlet.rs` change together 50% of the time (6 of the 12 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 `c871e4bb` refactor: cluster arguments (at that commit the files were still `implementations/rust/ockam/ockam_command/src/cluster/delete.rs` and `implementations/rust/ockam/ockam_command/src/cluster/inlet.rs`); `bf8b3582` fix: get cluster always from orchestrator (at that commit the files were still `implementations/rust/ockam/ockam_command/src/cluster/delete.rs` and `implementations/rust/ockam/ockam_command/src/cluster/inlet.rs`); `22e198ca` feat(rust): adjustments for public eks (at that commit the files were still `implementations/rust/ockam/ockam_command/src/cluster/delete.rs` and `implementations/rust/ockam/ockam_command/src/cluster/inlet.rs`) — run `git show` on any of them.
Change coupling: create.rs ↔ delete.rs implementations/rust/ockam/ockam_command/src/project/create.rs:1— `implementations/rust/ockam/ockam_command/src/project/create.rs` and `implementations/rust/ockam/ockam_command/src/project/delete.rs` change together 50% of the time (6 of the 12 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 `65ca55c0` fix(rust): when deleting the default vault/identity/project the data …; `d7256de9` feat(rust): rename ockam command output format option; `9eb80b76` refactor(rust): rename `NODEMAN_ADDR` to `NODEMANAGER_ADDR` — run `git show` on any of them.
Change coupling: list.rs ↔ create.rs implementations/rust/ockam/ockam_command/src/tcp/inlet/list.rs:1— `implementations/rust/ockam/ockam_command/src/tcp/inlet/list.rs` and `implementations/rust/ockam/ockam_command/src/tcp/outlet/create.rs` change together 50% of the time (5 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 — 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 5 shared commits counted here, the most recent 3 are `6523dfb2` feat(rust): unify output of show/list portals commands; `d11b610e` feat: adjust `enroll` logic and output for the new subscription plans; `a60c95ef` docs(rust): update docs for tcp-outlet commands — run `git show` on any of them.
Change coupling: delete.rs ↔ list.rs implementations/rust/ockam/ockam_command/src/tcp/outlet/delete.rs:1— `implementations/rust/ockam/ockam_command/src/tcp/outlet/delete.rs` and `implementations/rust/ockam/ockam_command/src/tcp/outlet/list.rs` change together 50% of the time (5 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 5 shared commits counted here, the most recent 3 are `6523dfb2` feat(rust): unify output of show/list portals commands; `dbd69980` feat(rust): improve ockam tcp-outlet commands ux output, help, logs, …; `437625c0` docs(rust): include documentation in tcp commands — run `git show` on any of them.
Change coupling: project.rs ↔ util.rs implementations/rust/ockam/ockam_api/src/nodes/connection/project.rs:1— `implementations/rust/ockam/ockam_api/src/nodes/connection/project.rs` and `implementations/rust/ockam/ockam_api/src/util.rs` change together 50% of the time (5 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 — 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 5 shared commits counted here, the most recent 3 are `cabbece9` refactor(rust): introduce a supervised node manager to support connec…; `f696a022` refactor(rust): simplify connections; `409685cf` chore(rust): add more context to `MultiAddr` errors caught at ockam_api — run `git show` on any of them.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×17
Duplicated block (7 lines × 2) implementations/rust/ockam/ockam_abac/src/expr.rs:95— implementations/rust/ockam/ockam_abac/src/expr.rs:95-101 | implementations/rust/ockam/ockam_abac/src/expr.rs:103-109 — 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 (7 lines × 2) implementations/rust/ockam/ockam_api/src/http/state.rs:39— implementations/rust/ockam/ockam_api/src/http/state.rs:39-45 | implementations/rust/ockam/ockam_api/src/http/state.rs:85-91 — 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 (7 lines × 2) implementations/rust/ockam/ockam_api/src/influxdb/portal.rs:229— implementations/rust/ockam/ockam_api/src/influxdb/portal.rs:229-235 | implementations/rust/ockam/ockam_api/src/nodes/service/kafka_services.rs:276-282 — 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 (7 lines × 2) implementations/rust/ockam/ockam_command/src/kafka/inlet/create.rs:143— implementations/rust/ockam/ockam_command/src/kafka/inlet/create.rs:143-149 | implementations/rust/ockam/ockam_command/src/kafka/outlet/create.rs:68-74 — 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 (7 lines × 2) implementations/rust/ockam/ockam_command/src/project/ticket.rs:283— implementations/rust/ockam/ockam_command/src/project/ticket.rs:283-289 | implementations/rust/ockam/ockam_command/src/zone/ticket.rs:99-105 — 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 (7 lines × 2) implementations/rust/ockam/ockam_core/src/routing/message/transport_message.rs:205— implementations/rust/ockam/ockam_core/src/routing/message/transport_message.rs:205-211 | implementations/rust/ockam/ockam_core/src/routing/message/transport_message.rs:304-310 — 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 (7 lines × 2) implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:333— implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:333-339 | implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:353-359 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs` and `implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (7 lines × 2) implementations/rust/ockam/ockam_command/src/relay/delete.rs:94— implementations/rust/ockam/ockam_command/src/relay/delete.rs:94-100 | implementations/rust/ockam/ockam_command/src/relay/show.rs:96-102 — 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) implementations/rust/ockam/ockam_identity/src/secure_channel/options.rs:282— implementations/rust/ockam/ockam_identity/src/secure_channel/options.rs:282-288 | implementations/rust/ockam/ockam_transport_udp/src/puncture/negotiation/options.rs:75-81 — 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 (7 lines × 2) implementations/rust/ockam/ockam_node/src/compat/mutex.rs:191— implementations/rust/ockam/ockam_node/src/compat/mutex.rs:191-197 | implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs:182-188 — before extracting anything, compare `implementations/rust/ockam/ockam_node/src/compat/mutex.rs` and `implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 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 (7 lines × 2) implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:306— implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:306-313 | implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs:139-145 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs` and `implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 69 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.
Duplicated block (7 lines × 2) implementations/rust/ockam/ockam/src/remote/lifecycle.rs:75— implementations/rust/ockam/ockam/src/remote/lifecycle.rs:75-81 | implementations/rust/ockam/ockam/src/remote/lifecycle.rs:117-123 — 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 (7 lines × 2) implementations/rust/ockam/ockam_transport_tcp/src/transport/common.rs:28— implementations/rust/ockam/ockam_transport_tcp/src/transport/common.rs:28-34 | implementations/rust/ockam/ockam_transport_tcp/src/transport/common.rs:43-49 — 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 (7 lines × 2) implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:55— implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:55-61 | implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:104-110 — 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 (7 lines × 2) implementations/elixir/ockam/ockam_services/lib/services/relay/static_forwarding_api.ex:33— implementations/elixir/ockam/ockam_services/lib/services/relay/static_forwarding_api.ex:33-39 | implementations/elixir/ockam/ockam_services/lib/services/token_lease_manager.ex:34-40 — 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 (7 lines × 2) implementations/elixir/ockam/ockam/lib/ockam/transport/tcp/address.ex:15— implementations/elixir/ockam/ockam/lib/ockam/transport/tcp/address.ex:15-21 | implementations/elixir/ockam/ockam/lib/ockam/transport/udp/address.ex:24-30 — 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 (9 lines × 2) implementations/rust/ockam/ockam_abac/src/expr.rs:134— implementations/rust/ockam/ockam_abac/src/expr.rs:134-142 | implementations/rust/ockam/ockam_abac/src/expr.rs:145-153 — 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) implementations/rust/ockam/ockam_api/src/logs/setup.rs:138— implementations/rust/ockam/ockam_api/src/logs/setup.rs:138-146 | implementations/rust/ockam/ockam_api/src/logs/setup.rs:162-170 — 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) implementations/rust/ockam/ockam_command/src/zone/dev.rs:623— implementations/rust/ockam/ockam_command/src/zone/dev.rs:623-631 | implementations/rust/ockam/ockam_command/src/zone/dev.rs:741-749 — 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) implementations/rust/ockam/ockam_executor/src/executor.rs:140— implementations/rust/ockam/ockam_executor/src/executor.rs:140-148 | implementations/rust/ockam/ockam_executor/src/executor.rs:153-161 — 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) implementations/rust/ockam/ockam_node/src/processor_builder.rs:244— implementations/rust/ockam/ockam_node/src/processor_builder.rs:244-252 | implementations/rust/ockam/ockam_node/src/worker_builder.rs:241-249 — 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 (9 lines × 2) implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.rs:567— implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.rs:567-575 | implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.rs:704-712 — 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) implementations/rust/ockam/ockam_api/src/logs/logging_options.rs:26— implementations/rust/ockam/ockam_api/src/logs/logging_options.rs:26-34 | implementations/rust/ockam/ockam_api/src/logs/tracing_options.rs:21-29 — 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 (9 lines × 2) implementations/rust/ockam/ockam_command/src/zone/inlet.rs:173— implementations/rust/ockam/ockam_command/src/zone/inlet.rs:173-181 | implementations/rust/ockam/ockam_command/src/zone/outlet.rs:181-189 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/zone/inlet.rs` and `implementations/rust/ockam/ockam_command/src/zone/outlet.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 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.
Duplicated block (9 lines × 2) implementations/rust/ockam/ockam_core/src/identity/local_info.rs:65— implementations/rust/ockam/ockam_core/src/identity/local_info.rs:65-73 | implementations/rust/ockam/ockam_core/src/transport/local_info.rs:65-73 — 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 (9 lines × 2) implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.rs:577— implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.rs:577-587 | implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.rs:714-722 — 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) implementations/rust/ockam/ockam_command/src/project/addon/configure_influxdb.rs:165— implementations/rust/ockam/ockam_command/src/project/addon/configure_influxdb.rs:165-173 | implementations/rust/ockam/ockam_command/src/project/addon/configure_okta.rs:140-149 — 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 (9 lines × 2) implementations/rust/ockam/ockam_command/src/policy/delete.rs:116— implementations/rust/ockam/ockam_command/src/policy/delete.rs:116-124 | implementations/rust/ockam/ockam_command/src/policy/show.rs:112-120 — 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 (9 lines × 2) implementations/rust/ockam/ockam_command/src/kafka/inlet/show.rs:97— implementations/rust/ockam/ockam_command/src/kafka/inlet/show.rs:97-105 | implementations/rust/ockam/ockam_command/src/kafka/outlet/show.rs:97-105 — 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 (9 lines × 2) implementations/rust/ockam/ockam_command/src/tcp/inlet/show.rs:110— implementations/rust/ockam/ockam_command/src/tcp/inlet/show.rs:110-118 | implementations/rust/ockam/ockam_command/src/tcp/outlet/show.rs:117-125 — 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 (9 lines × 2) implementations/elixir/ockam/ockam/lib/ockam/api/request.ex:71— implementations/elixir/ockam/ockam/lib/ockam/api/request.ex:71-79 | implementations/elixir/ockam/ockam/lib/ockam/api/response.ex:58-66 — 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) implementations/rust/ockam/ockam/src/remote/lifecycle.rs:83— implementations/rust/ockam/ockam/src/remote/lifecycle.rs:83-90 | implementations/rust/ockam/ockam/src/remote/lifecycle.rs:125-132 — 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 × 2) implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/acceptor_worker.rs:51— implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/acceptor_worker.rs:51-58 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs:63-70 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/acceptor_worker.rs` and `implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 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.
Duplicated block (8 lines × 2) implementations/rust/ockam/ockam_api/src/influxdb/influxdb_api_client.rs:223— implementations/rust/ockam/ockam_api/src/influxdb/influxdb_api_client.rs:223-230 | implementations/rust/ockam/ockam_api/src/influxdb/influxdb_api_client.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 (8 lines × 2) implementations/rust/ockam/ockam_command/src/kafka/consumer/list.rs:25— implementations/rust/ockam/ockam_command/src/kafka/consumer/list.rs:25-32 | implementations/rust/ockam/ockam_command/src/kafka/producer/list.rs:25-32 — 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 (8 lines × 2) implementations/rust/ockam/ockam_command/src/zone/dev.rs:513— implementations/rust/ockam/ockam_command/src/zone/dev.rs:513-520 | implementations/rust/ockam/ockam_command/src/zone/logs.rs:224-231 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/zone/dev.rs` and `implementations/rust/ockam/ockam_command/src/zone/logs.rs` as WHOLE FILES: this scan already matched 5 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. 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.
Duplicated block (8 lines × 2) implementations/rust/ockam/ockam_node/src/compat/mutex.rs:147— implementations/rust/ockam/ockam_node/src/compat/mutex.rs:147-154 | implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs:147-154 — before extracting anything, compare `implementations/rust/ockam/ockam_node/src/compat/mutex.rs` and `implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 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 (8 lines × 2) implementations/rust/ockam/ockam_node/src/compat/mutex.rs:247— implementations/rust/ockam/ockam_node/src/compat/mutex.rs:247-254 | implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs:238-245 — before extracting anything, compare `implementations/rust/ockam/ockam_node/src/compat/mutex.rs` and `implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 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 (8 lines × 2) implementations/rust/ockam/ockam_command/src/project/show.rs:65— implementations/rust/ockam/ockam_command/src/project/show.rs:65-72 | implementations/rust/ockam/ockam_command/src/space/show.rs:63-70 — 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 (8 lines × 2) implementations/rust/ockam/ockam_command/src/zone/deploy.rs:103— implementations/rust/ockam/ockam_command/src/zone/deploy.rs:103-110 | implementations/rust/ockam/ockam_command/src/zone/ticket.rs:85-92 — 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) implementations/rust/ockam/ockam_node/src/debugger.rs:221— implementations/rust/ockam/ockam_node/src/debugger.rs:221-229 | implementations/rust/ockam/ockam_node/src/debugger.rs:260-267 — 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 × 2) implementations/rust/ockam/ockam_command/src/arguments.rs:59— implementations/rust/ockam/ockam_command/src/arguments.rs:59-66 | implementations/rust/ockam/ockam_command/src/arguments.rs:71-79 — 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 × 2) implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:214— implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:214-221 | implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs:85-92 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs` and `implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 69 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.
Duplicated block (8 lines × 2) implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:169— implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:169-176 | implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:191-198 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs` and `implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (8 lines × 2) implementations/elixir/ockam/ockam_services/lib/services/relay/static_forwarding_api.ex:21— implementations/elixir/ockam/ockam_services/lib/services/relay/static_forwarding_api.ex:21-28 | implementations/elixir/ockam/ockam_services/lib/services/token_lease_manager.ex:22-29 — 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 (8 lines × 2) implementations/elixir/ockam/ockam/lib/ockam/session/pluggable/initiator.ex:160— implementations/elixir/ockam/ockam/lib/ockam/session/pluggable/initiator.ex:160-167 | implementations/elixir/ockam/ockam/lib/ockam/session/pluggable/responder.ex:83-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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×14
Duplicated block (5 lines × 2) implementations/rust/ockam/ockam_abac/src/parser.rs:113— implementations/rust/ockam/ockam_abac/src/parser.rs:113-117 | implementations/rust/ockam/ockam_abac/src/parser.rs:122-126 — 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) implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:99— implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:99-103 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:116-120 — 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) implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:97— implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:97-101 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs:101-105 — before extracting anything, compare `implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs` and `implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs` as WHOLE FILES: this scan already matched 5 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. 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.
Duplicated block (5 lines × 2) implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs:103— implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs:103-107 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs:119-123 — 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) implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:76— implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:76-81 | implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:120-124 — 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) implementations/rust/ockam/ockam_transport_ble/src/types.rs:35— implementations/rust/ockam/ockam_transport_ble/src/types.rs:35-39 | implementations/rust/ockam/ockam_transport_websocket/src/lib.rs:104-108 — 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) implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:412— implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:412-416 | implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs:244-248 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs` and `implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 69 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.
Duplicated block (5 lines × 2) implementations/rust/ockam/ockam_command/src/lease/list.rs:64— implementations/rust/ockam/ockam_command/src/lease/list.rs:64-68 | implementations/rust/ockam/ockam_command/src/lease/show.rs:76-80 — 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) implementations/rust/ockam/ockam_api/src/nodes/models/transport/json.rs:35— implementations/rust/ockam/ockam_api/src/nodes/models/transport/json.rs:35-39 | implementations/rust/ockam/ockam_command/src/util/mod.rs:50-54 — 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) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/formatter.ex:63— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/formatter.ex:63-67 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/formatter.ex:81-85 — 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) implementations/elixir/ockam/ockam/lib/ockam/mini_cbor.ex:57— implementations/elixir/ockam/ockam/lib/ockam/mini_cbor.ex:57-66 | implementations/elixir/ockam/ockam_typed_cbor/lib/typed_cbor.ex:462-466 — 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) implementations/elixir/ockam/ockam_kafka/lib/interceptor/kafka_interceptor.ex:250— implementations/elixir/ockam/ockam_kafka/lib/interceptor/kafka_interceptor.ex:250-254 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/kafka_interceptor.ex:262-266 — 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) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:91— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:91-95 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:113-117 — 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×12
Duplicated block (12 lines × 2) implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:307— implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:307-318 | implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:383-394 — 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) implementations/rust/ockam/ockam_api/src/nodes/connection/plain_tcp.rs:39— implementations/rust/ockam/ockam_api/src/nodes/connection/plain_tcp.rs:39-50 | implementations/rust/ockam/ockam_api/src/nodes/connection/plain_udp.rs:38-49 — 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 (12 lines × 2) implementations/rust/ockam/ockam_command/src/influxdb/outlet/create.rs:157— implementations/rust/ockam/ockam_command/src/influxdb/outlet/create.rs:157-168 | implementations/rust/ockam/ockam_command/src/tcp/outlet/create.rs:156-167 — 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 lines × 2) implementations/rust/ockam/ockam_command/src/tcp/inlet/show.rs:57— implementations/rust/ockam/ockam_command/src/tcp/inlet/show.rs:57-68 | implementations/rust/ockam/ockam_command/src/tcp/outlet/show.rs:64-75 — 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 lines × 2) implementations/rust/ockam/ockam_macros/src/node_attribute.rs:151— implementations/rust/ockam/ockam_macros/src/node_attribute.rs:151-162 | implementations/rust/ockam/ockam_macros/src/node_test_attribute.rs:231-242 — 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 (12 lines × 2) implementations/rust/ockam/ockam_transport_tcp/src/options.rs:81— implementations/rust/ockam/ockam_transport_tcp/src/options.rs:81-92 | implementations/rust/ockam/ockam_transport_udp/src/options.rs:46-57 — 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 lines × 2) implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:245— implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:245-256 | implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:309-322 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs` and `implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (12 lines × 2) implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:59— implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:59-70 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs:63-75 — before extracting anything, compare `implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs` and `implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs` as WHOLE FILES: this scan already matched 5 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. 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.
Duplicated block (12 lines × 2) implementations/rust/ockam/ockam_command/src/share/list.rs:65— implementations/rust/ockam/ockam_command/src/share/list.rs:65-76 | implementations/rust/ockam/ockam_command/src/share/list.rs:80-91 — 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) implementations/rust/ockam/ockam_command/src/zone/deploy.rs:498— implementations/rust/ockam/ockam_command/src/zone/deploy.rs:498-509 | implementations/rust/ockam/ockam_command/src/zone/deploy.rs:515-526 — 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) implementations/rust/ockam/ockam_command/src/lease/list.rs:71— implementations/rust/ockam/ockam_command/src/lease/list.rs:71-82 | implementations/rust/ockam/ockam_command/src/project/relays.rs:71-82 — 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 lines × 2) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:277— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:277-288 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:298-309 — 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) implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:81— implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:81-90 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs:86-95 — before extracting anything, compare `implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs` and `implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs` as WHOLE FILES: this scan already matched 5 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. 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.
Duplicated block (10 lines × 2) implementations/rust/ockam/ockam_api/src/logs/ockam_tonic_logs_client.rs:73— implementations/rust/ockam/ockam_api/src/logs/ockam_tonic_logs_client.rs:73-82 | implementations/rust/ockam/ockam_api/src/logs/ockam_tonic_traces_client.rs:73-82 — 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 (10 lines × 2) implementations/rust/ockam/ockam_command/src/kafka/consumer/delete.rs:24— implementations/rust/ockam/ockam_command/src/kafka/consumer/delete.rs:24-33 | implementations/rust/ockam/ockam_command/src/kafka/producer/delete.rs:24-33 — 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 (10 lines × 2) implementations/rust/ockam/ockam_command/src/project_admin/list.rs:46— implementations/rust/ockam/ockam_command/src/project_admin/list.rs:46-55 | implementations/rust/ockam/ockam_command/src/space_admin/list.rs:48-57 — 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 (10 lines × 2) implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:78— implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:78-87 | implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:140-149 — 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) implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_receiver.rs:159— implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_receiver.rs:159-168 | implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.rs:804-813 — 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 (10 lines × 2) implementations/rust/ockam/ockam_command/src/node/delete.rs:88— implementations/rust/ockam/ockam_command/src/node/delete.rs:88-97 | implementations/rust/ockam/ockam_command/src/node/show.rs:89-98 — 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 (10 lines × 2) implementations/rust/ockam/ockam_command/src/vault/delete.rs:75— implementations/rust/ockam/ockam_command/src/vault/delete.rs:75-84 | implementations/rust/ockam/ockam_command/src/vault/show.rs:78-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 (10 lines × 2) implementations/rust/ockam/ockam_command/src/relay/delete.rs:62— implementations/rust/ockam/ockam_command/src/relay/delete.rs:62-71 | implementations/rust/ockam/ockam_command/src/relay/show.rs:65-74 — 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 (10 lines × 2) implementations/rust/ockam/ockam_command/src/project/util.rs:192— implementations/rust/ockam/ockam_command/src/project/util.rs:192-202 | implementations/rust/ockam/ockam_command/src/project/util.rs:218-227 — 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) REDACTED:88— REDACTED:88-97 | REDACTED:179-188 — 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) implementations/rust/ockam/ockam_command/src/zone/dev.rs:448— implementations/rust/ockam/ockam_command/src/zone/dev.rs:448-457 | implementations/rust/ockam/ockam_command/src/zone/logs.rs:236-245 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/zone/dev.rs` and `implementations/rust/ockam/ockam_command/src/zone/logs.rs` as WHOLE FILES: this scan already matched 5 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. 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.
Duplicated block (14 lines × 2) implementations/rust/ockam/ockam_abac/src/expr.rs:261— implementations/rust/ockam/ockam_abac/src/expr.rs:261-274 | implementations/rust/ockam/ockam_node/src/storage/database/migrations/node_migrations/rust/sqlite/migration_20240111100002_delete_trust_context.rs:118-131 — 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 (14 lines × 2) implementations/rust/ockam/ockam_command/src/run/parser/resource/influxdb_inlets.rs:35— implementations/rust/ockam/ockam_command/src/run/parser/resource/influxdb_inlets.rs:35-48 | implementations/rust/ockam/ockam_command/src/run/parser/resource/tcp_inlets.rs:35-48 — 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 (14 lines × 2) implementations/rust/ockam/ockam_command/src/run/parser/resource/influxdb_outlets.rs:35— implementations/rust/ockam/ockam_command/src/run/parser/resource/influxdb_outlets.rs:35-48 | implementations/rust/ockam/ockam_command/src/run/parser/resource/tcp_outlets.rs:36-49 — 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 (14 lines × 2) implementations/rust/ockam/ockam_command/src/run/parser/resource/kafka_inlet.rs:35— implementations/rust/ockam/ockam_command/src/run/parser/resource/kafka_inlet.rs:35-48 | implementations/rust/ockam/ockam_command/src/run/parser/resource/kafka_outlet.rs:37-50 — 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 (14 lines × 2) implementations/rust/ockam/ockam_command/src/zone/inlet.rs:117— implementations/rust/ockam/ockam_command/src/zone/inlet.rs:117-130 | implementations/rust/ockam/ockam_command/src/zone/outlet.rs:126-139 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/zone/inlet.rs` and `implementations/rust/ockam/ockam_command/src/zone/outlet.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 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.
Duplicated block (14 lines × 2) implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:123— implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:123-136 | implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:193-206 — 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 (14 lines × 2) implementations/rust/ockam/ockam_command/src/bin/brand.rs:242— implementations/rust/ockam/ockam_command/src/bin/brand.rs:242-255 | implementations/rust/ockam/ockam_command/src/bin/brand.rs:258-275 — 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 (14 lines × 2) implementations/rust/ockam/ockam_node/src/relay/processor_relay.rs:111— implementations/rust/ockam/ockam_node/src/relay/processor_relay.rs:111-124 | implementations/rust/ockam/ockam_node/src/relay/worker_relay.rs:177-190 — 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 (14 lines × 2) implementations/rust/ockam/ockam_transport_tcp/src/privileged_portal/ebpf_support.rs:273— implementations/rust/ockam/ockam_transport_tcp/src/privileged_portal/ebpf_support.rs:273-286 | implementations/rust/ockam/ockam_transport_tcp/src/privileged_portal/ebpf_support.rs:308-321 — 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 (14 lines × 2) REDACTED:85— REDACTED:85-98 | implementations/rust/ockam/ockam_node/src/storage/database/migrations/node_migrations/rust/sqlite/migration_20240111100002_delete_trust_context.rs:74-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 (14 lines × 2) implementations/rust/ockam/ockam_api/src/test_utils/mod.rs:151— implementations/rust/ockam/ockam_api/src/test_utils/mod.rs:151-164 | implementations/rust/ockam/ockam_api/src/test_utils/mod.rs:301-314 — 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.
Low cohesion: RelayServiceOptions (LCOM4 7) implementations/rust/ockam/ockam/src/relay_service/options.rs:10— RelayServiceOptions'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: DeployCommand (LCOM4 7) implementations/rust/ockam/ockam_command/src/zone/deploy.rs:37— DeployCommand'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: HandshakeState (LCOM4 7) implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:502— HandshakeState'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: TcpOutletOptions (LCOM4 7) implementations/rust/ockam/ockam_transport_tcp/src/portal/options.rs:160— TcpOutletOptions'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: NodeInfo (LCOM4 6) implementations/rust/ockam/ockam_api/src/cli_state/nodes.rs:506— NodeInfo'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: SecureChannelOptions (LCOM4 6) implementations/rust/ockam/ockam_identity/src/secure_channel/options.rs:29— SecureChannelOptions'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: Context (LCOM4 6) implementations/rust/ockam/ockam_node/src/context/context.rs:26— Context'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: Terminal (LCOM4 5) implementations/rust/ockam/ockam_api/src/ui/terminal/mod.rs:47— Terminal's methods fall into 5 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 5 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: SecureChannelListenerOptions (LCOM4 5) implementations/rust/ockam/ockam_identity/src/secure_channel/options.rs:177— SecureChannelListenerOptions's methods fall into 5 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 5 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: ExportedIdentity (LCOM4 4) implementations/rust/ockam/ockam_command/src/identity/export.rs:78— ExportedIdentity'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: TcpConnectionOptions (LCOM4 4) implementations/rust/ockam/ockam_transport_tcp/src/options.rs:10— TcpConnectionOptions'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.
MethodTooLong: DevNodeCommand.run implementations/rust/ockam/ockam_command/src/zone/dev.rs:117— MethodTooLong — run runs 215 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 115 over it, 2.15× 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: NodeManagerWorker.handle_request implementations/rust/ockam/ockam_api/src/nodes/service/worker.rs:37— MethodTooLong — handle_request runs 171 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 71 over it, 1.71× 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: NodeManager.create_inlet implementations/rust/ockam/ockam_api/src/nodes/service/tcp_inlets/node_manager.rs:26— MethodTooLong — create_inlet runs 148 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 48 over it, 1.48× 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: InMemoryNode.start_kafka_inlet_service implementations/rust/ockam/ockam_api/src/nodes/service/kafka_services.rs:110— MethodTooLong — start_kafka_inlet_service runs 110 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 10 over it, 1.10× 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: TicketNodeCommand.run implementations/rust/ockam/ockam_command/src/project/ticket.rs:110— MethodTooLong — run runs 108 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 8 over it, 1.08× 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: CreateCommand.run implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:190— MethodTooLong — run 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.
MethodTooLong: NodeManager.create implementations/rust/ockam/ockam_api/src/nodes/service/manager.rs:73— MethodTooLong — create runs 103 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 3 over it, 1.03× 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: HttpControlNodeApiFrontend.route_request_impl implementations/rust/ockam/ockam_api/src/control_api/frontend.rs:172— MethodTooLong — route_request_impl runs 102 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 2 over it, 1.02× 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: ProjectsSqlxDatabase.store_project implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:167— MethodTooLong — store_project runs 101 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 1 over it, 1.01× 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: ReplCommand.open_repl implementations/rust/ockam/ockam_command/src/zone/repl.rs:59— MethodTooLong — open_repl runs 101 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 1 over it, 1.01× 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.
Duplicated block (6 lines × 2) implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:113— implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:113-118 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs:116-121 — before extracting anything, compare `implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs` and `implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs` as WHOLE FILES: this scan already matched 5 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. 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.
Duplicated block (6 lines × 2) implementations/rust/ockam/ockam_api/src/cli_state/storage/enrollments_repository_sql.rs:75— implementations/rust/ockam/ockam_api/src/cli_state/storage/enrollments_repository_sql.rs:75-80 | implementations/rust/ockam/ockam_api/src/cli_state/storage/enrollments_repository_sql.rs:95-100 — 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) REDACTED:522— REDACTED:522-527 | REDACTED:537-542 — 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) implementations/rust/ockam/ockam_transport_uds/src/router/uds_router.rs:275— implementations/rust/ockam/ockam_transport_uds/src/router/uds_router.rs:275-280 | implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:145-150 — 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) implementations/rust/ockam/ockam_identity/src/purpose_keys/purpose_key_creation.rs:46— implementations/rust/ockam/ockam_identity/src/purpose_keys/purpose_key_creation.rs:46-51 | implementations/rust/ockam/ockam_identity/src/purpose_keys/purpose_keys.rs:49-54 — 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) implementations/rust/ockam/ockam_vault/src/software/vault_for_signing/vault_for_signing.rs:159— implementations/rust/ockam/ockam_vault/src/software/vault_for_signing/vault_for_signing.rs:159-164 | implementations/rust/ockam/ockam_vault/src/software/vault_for_verifying_signatures.rs:45-50 — 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) implementations/rust/ockam/ockam_api/src/cli_state/identities.rs:159— implementations/rust/ockam/ockam_api/src/cli_state/identities.rs:159-166 | implementations/rust/ockam/ockam_api/src/cli_state/vaults.rs:256-261 — 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) implementations/rust/ockam/ockam_command/src/run/parser/resource/identities.rs:18— implementations/rust/ockam/ockam_command/src/run/parser/resource/identities.rs:18-23 | implementations/rust/ockam/ockam_command/src/run/parser/resource/policies.rs:30-35 — 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) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/formatter.ex:102— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/formatter.ex:102-107 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/formatter.ex:123-128 — 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) implementations/elixir/ockam/ockam/lib/ockam/protocol/stream.ex:7— implementations/elixir/ockam/ockam/lib/ockam/protocol/stream.ex:7-12 | implementations/elixir/ockam/ockam/lib/ockam/protocol/stream_partitioned.ex:7-12 — 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.
TooManyMethods: CliState implementations/rust/ockam/ockam_api/src/cli_state/cli_state.rs:43— TooManyMethods — 159 methods, declared across 17 files: cli_state/cli_state.rs (33), cli_state/nodes.rs (27), cli_state/identities.rs (21), cli_state/vaults.rs (16), +13 more file(s). The bar is 30 methods; this is 129 over it, 5.30× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: NodeManager implementations/rust/ockam/ockam_api/src/nodes/service/manager.rs:56— TooManyMethods — 85 methods, declared across 13 files: service/manager.rs (29), service/secure_channel.rs (11), orchestrator/secure_clients.rs (10), service/transport.rs (8), +9 more file(s). The bar is 30 methods; this is 55 over it, 2.83× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: NodeManagerWorker implementations/rust/ockam/ockam_api/src/nodes/service/worker.rs:15— TooManyMethods — 56 methods, declared across 15 files: service/secure_channel.rs (8), service/transport.rs (8), service/node_services.rs (7), influxdb/portal.rs (4), +11 more file(s). The bar is 30 methods; this is 26 over it, 1.87× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: Context implementations/rust/ockam/ockam_node/src/context/context.rs:26— TooManyMethods — 51 methods, declared across 10 files: context/context.rs (15), context/send_message.rs (9), context/context_lifecycle.rs (7), context/worker_lifecycle.rs (6), +6 more file(s). The bar is 30 methods; this is 21 over it, 1.70× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: Response implementations/rust/ockam/ockam_core/src/api.rs:656— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: Terminal implementations/rust/ockam/ockam_api/src/ui/terminal/mod.rs:47— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× 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: Node implementations/rust/ockam/ockam/src/node.rs:32— 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: SqlxDatabase REDACTED:42— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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.
Duplicated block (11 lines × 2) implementations/rust/ockam/ockam_core/src/access_control/cache.rs:119— implementations/rust/ockam/ockam_core/src/access_control/cache.rs:119-129 | implementations/rust/ockam/ockam_core/src/access_control/cache.rs:155-165 — 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 (11 lines × 2) implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:159— implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:159-169 | implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.rs:220-230 — 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 (11 lines × 2) implementations/rust/ockam/ockam_command/src/kafka/inlet/show.rs:48— implementations/rust/ockam/ockam_command/src/kafka/inlet/show.rs:48-58 | implementations/rust/ockam/ockam_command/src/kafka/outlet/show.rs:48-58 — 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 (11 lines × 2) implementations/rust/ockam/ockam_node/src/processor_builder.rs:150— implementations/rust/ockam/ockam_node/src/processor_builder.rs:150-160 | implementations/rust/ockam/ockam_node/src/worker_builder.rs:147-157 — 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) implementations/rust/ockam/ockam_command/src/kafka/inlet/delete.rs:111— implementations/rust/ockam/ockam_command/src/kafka/inlet/delete.rs:111-121 | implementations/rust/ockam/ockam_command/src/kafka/outlet/delete.rs:108-118 — 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 (11 lines × 2) implementations/rust/ockam/ockam_command/src/zone/dev.rs:458— implementations/rust/ockam/ockam_command/src/zone/dev.rs:458-468 | implementations/rust/ockam/ockam_command/src/zone/logs.rs:247-257 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/zone/dev.rs` and `implementations/rust/ockam/ockam_command/src/zone/logs.rs` as WHOLE FILES: this scan already matched 5 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. 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.
Duplicated block (11 lines × 2) implementations/rust/ockam/ockam_command/src/zone/inlet.rs:156— implementations/rust/ockam/ockam_command/src/zone/inlet.rs:156-166 | implementations/rust/ockam/ockam_command/src/zone/outlet.rs:164-174 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/zone/inlet.rs` and `implementations/rust/ockam/ockam_command/src/zone/outlet.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 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.
Duplicated block (15 lines × 2) implementations/rust/ockam/ockam_core/src/api.rs:628— implementations/rust/ockam/ockam_core/src/api.rs:628-642 | implementations/rust/ockam/ockam_core/src/api.rs:773-787 — 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 (15 lines × 2) implementations/rust/ockam/ockam_transport_tcp/src/transport_message.rs:83— implementations/rust/ockam/ockam_transport_tcp/src/transport_message.rs:83-97 | implementations/rust/ockam/ockam_transport_udp/src/messages/routing_message.rs:81-95 — 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) implementations/rust/ockam/ockam_command/src/sidecar/secure_relay_inlet.rs:71— implementations/rust/ockam/ockam_command/src/sidecar/secure_relay_inlet.rs:71-85 | implementations/rust/ockam/ockam_command/src/sidecar/secure_relay_outlet.rs:70-84 — 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 (15 lines × 2) implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:431— implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:431-445 | implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs:257-271 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs` and `implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 69 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.
Duplicated block (15 lines × 2) implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:148— implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:148-162 | implementations/rust/ockam/ockam_api/src/cli_state/storage/users_repository_sql.rs:48-62 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs` and `implementations/rust/ockam/ockam_api/src/cli_state/storage/users_repository_sql.rs` as WHOLE FILES: this scan already matched 4 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.
Duplicated block (15 lines × 2) implementations/elixir/ockam/ockam/lib/ockam/stream/client/consumer.ex:313— implementations/elixir/ockam/ockam/lib/ockam/stream/client/consumer.ex:313-327 | implementations/elixir/ockam/ockam/lib/ockam/stream/client/publisher.ex:245-259 — 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 (18 lines × 2) implementations/rust/ockam/ockam_api/src/control_api/backend/inlet.rs:228— implementations/rust/ockam/ockam_api/src/control_api/backend/inlet.rs:228-245 | implementations/rust/ockam/ockam_api/src/control_api/backend/outlet.rs:161-178 — 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 (18 lines × 2) implementations/rust/ockam/ockam_api/src/multiaddr_resolver/local_resolver.rs:16— implementations/rust/ockam/ockam_api/src/multiaddr_resolver/local_resolver.rs:16-33 | implementations/rust/ockam/ockam_api/src/multiaddr_resolver/transport_route_resolver.rs:88-105 — 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 (18 lines × 2) implementations/rust/ockam/ockam_command/src/share/create.rs:68— implementations/rust/ockam/ockam_command/src/share/create.rs:68-85 | implementations/rust/ockam/ockam_command/src/share/service.rs:79-96 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/share/create.rs` and `implementations/rust/ockam/ockam_command/src/share/service.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 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.
Duplicated block (18 lines × 2) implementations/rust/ockam/ockam_command/src/tcp/connection/delete.rs:95— implementations/rust/ockam/ockam_command/src/tcp/connection/delete.rs:95-112 | implementations/rust/ockam/ockam_command/src/tcp/connection/show.rs:95-112 — 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 (18 lines × 2) implementations/rust/ockam/ockam_node/src/relay/processor_relay.rs:126— implementations/rust/ockam/ockam_node/src/relay/processor_relay.rs:126-143 | implementations/rust/ockam/ockam_node/src/relay/worker_relay.rs:192-209 — 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 (16 lines × 2) implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:489— implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:489-504 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:528-543 — 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 (16 lines × 2) implementations/rust/ockam/ockam_api/src/session/session.rs:452— implementations/rust/ockam/ockam_api/src/session/session.rs:452-467 | implementations/rust/ockam/ockam_api/src/session/session.rs:558-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.
Duplicated block (16 lines × 2) implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:202— implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:202-217 | implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:263-278 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs` and `implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (16 lines × 2) implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:296— implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:296-311 | implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:404-419 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs` and `implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (16 lines × 2) implementations/rust/ockam/ockam_command/src/project_member/list.rs:72— implementations/rust/ockam/ockam_command/src/project_member/list.rs:72-87 | implementations/rust/ockam/ockam_command/src/project_member/list_ids.rs:61-76 — 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 (13 lines × 2) implementations/rust/ockam/ockam_api/src/ui/colors.rs:25— implementations/rust/ockam/ockam_api/src/ui/colors.rs:25-37 | implementations/rust/ockam/ockam_api/src/ui/mod.rs:26-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.
Duplicated block (13 lines × 2) implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:222— implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:222-234 | implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs:93-105 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs` and `implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 69 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.
Duplicated block (13 lines × 2) implementations/rust/ockam/ockam_api/src/influxdb/lease_issuer/worker.rs:125— implementations/rust/ockam/ockam_api/src/influxdb/lease_issuer/worker.rs:125-137 | implementations/rust/ockam/ockam_api/src/nodes/service/worker.rs:319-331 — 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 (13 lines × 2) implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:221— implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:221-233 | implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:282-294 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs` and `implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (13 lines × 2) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/parser.ex:71— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/parser.ex:71-83 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/parser.ex:87-99 — 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.
CreateCommand::start_services (cognitive 39) implementations/rust/ockam/ockam_command/src/node/create/foreground.rs:195— CreateCommand::start_services has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (29 pts), match/switch 2 (10 pts) (nesting depth added 27). 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.
CreateCommand::run (cognitive 31) implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:190— CreateCommand::run has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (25 pts), match/switch 2 (4 pts), boolean chains 1, 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.
CreateCommand::run (cognitive 21) implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:168— CreateCommand::run has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), match/switch 1 (2 pts), boolean chains 1, loops 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.
CreateCommand::parse_args (cognitive 21) implementations/rust/ockam/ockam_command/src/node/create.rs:274— CreateCommand::parse_args has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 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.
Expr::equals (cognitive 30) implementations/rust/ockam/ockam_abac/src/expr.rs:84— Expr::equals has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 3 (7 pts), match/switch 1 (2 pts) (nesting depth added 19). 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.
Expr::fmt (cognitive 27) implementations/rust/ockam/ockam_abac/src/expr.rs:260— Expr::fmt has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 3 (7 pts), match/switch 1 (2 pts) (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.
Expr::fmt (cognitive 27) implementations/rust/ockam/ockam_node/src/storage/database/migrations/node_migrations/rust/sqlite/migration_20240111100002_delete_trust_context.rs:117— Expr::fmt has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 3 (7 pts), match/switch 1 (2 pts) (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.
Expr::compare (cognitive 21) implementations/rust/ockam/ockam_abac/src/expr.rs:120— Expr::compare has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 3 (9 pts), match/switch 1 (2 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.
ockam_api::control_api::backend::ticket::create_encoded_ticket (cognitive 19) implementations/rust/ockam/ockam_api/src/control_api/backend/ticket.rs:128— ockam_api::control_api::backend::ticket::create_encoded_ticket has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (18 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.
ockam_api::common_api::tcp_inlet_create::parse_to_address (cognitive 18) implementations/rust/ockam/ockam_api/src/common_api/tcp_inlet_create.rs:11— ockam_api::common_api::tcp_inlet_create::parse_to_address has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 2, match/switch 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.
ockam_api::logs::exporting_configuration::opentelemetry_endpoint (cognitive 17) implementations/rust/ockam/ockam_api/src/logs/exporting_configuration.rs:443— ockam_api::logs::exporting_configuration::opentelemetry_endpoint has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1, match/switch 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.
ockam_api::control_api::backend::ticket::handle_ticket_enroll (cognitive 16) implementations/rust/ockam/ockam_api/src/control_api/backend/ticket.rs:281— ockam_api::control_api::backend::ticket::handle_ticket_enroll has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 3 (4 pts) (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.
FunctionTooLong: ockam_abac::eval::eval implementations/rust/ockam/ockam_abac/src/eval.rs:10— FunctionTooLong — ockam_abac::eval::eval 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: ockam_abac::parser::parse implementations/rust/ockam/ockam_abac/src/parser.rs:27— FunctionTooLong — ockam_abac::parser::parse runs 130 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 30 over it, 1.30× 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: ockam_command::node::util::spawn_node implementations/rust/ockam/ockam_command/src/node/util.rs:57— FunctionTooLong — ockam_command::node::util::spawn_node 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.
FunctionTooLong: ockam_api::control_api::backend::ticket::create_encoded_ticket implementations/rust/ockam/ockam_api/src/control_api/backend/ticket.rs:128— FunctionTooLong — ockam_api::control_api::backend::ticket::create_encoded_ticket runs 101 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 1 over it, 1.01× 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: src/api.rs implementations/rust/ockam/ockam_core/src/api.rs— FileTooLong — 653 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 153 over it, 1.31× 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: portal/portal_worker.rs implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.rs— FileTooLong — 582 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: TcpPortalWorker (5 blocks, 66-823). The bar is 500 significant lines; this is 82 over it, 1.16× 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: zone/dev.rs implementations/rust/ockam/ockam_command/src/zone/dev.rs— FileTooLong — 574 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 74 over it, 1.15× 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: service/manager.rs implementations/rust/ockam/ockam_api/src/nodes/service/manager.rs— FileTooLong — 547 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: NodeManager (2 blocks, 56-694). The bar is 500 significant lines; this is 47 over it, 1.09× 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:92— implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:92-103 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:108-120 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs:97-107 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs:112-123 — These 4 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 4 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 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) implementations/rust/ockam/ockam_api/src/authenticator/credential_issuer/credential_issuer_worker.rs:54— implementations/rust/ockam/ockam_api/src/authenticator/credential_issuer/credential_issuer_worker.rs:54-95 | implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:45-140 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/acceptor_worker.rs:34-70 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs:46-92 — These 4 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 4 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 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) implementations/rust/ockam/ockam_command/src/secure_channel/listener/list.rs:39— implementations/rust/ockam/ockam_command/src/secure_channel/listener/list.rs:39-70 | implementations/rust/ockam/ockam_command/src/service/list.rs:28-60 | implementations/rust/ockam/ockam_command/src/tcp/listener/list.rs:34-63 | implementations/rust/ockam/ockam_command/src/worker/list.rs:38-64 — These 4 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 4 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 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) implementations/rust/ockam/ockam_transport_ble/src/router/mod.rs:150— implementations/rust/ockam/ockam_transport_ble/src/router/mod.rs:150-194 | implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:78-126 | implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:49-85 | implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:94-130 — These 4 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 4 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 4 times.
Expr::fmt (cyclomatic 19) implementations/rust/ockam/ockam_abac/src/expr.rs:260— Expr::fmt 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.
Expr::equals (cyclomatic 18) implementations/rust/ockam/ockam_abac/src/expr.rs:84— Expr::equals 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.
Expr::fmt (cyclomatic 18) implementations/rust/ockam/ockam_node/src/storage/database/migrations/node_migrations/rust/sqlite/migration_20240111100002_delete_trust_context.rs:117— Expr::fmt 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.
Floating source dependency: neotoma — Runtime dependency `:neotoma` is fetched from source in implementations/elixir/ockam/ockam_abac/mix.exs and names no revision at all, so it tracks the default branch — the declaration pins no immutable revision, so `mix deps.update` moves this dependency to code nobody reviewed. Pin it with `ref:` (a full commit SHA) or `tag:`.
Floating source dependency: brod — Runtime dependency `:brod` is fetched from source in implementations/elixir/ockam/ockam_kafka/mix.exs and tracks a branch — the declaration pins no immutable revision, so `mix deps.update` moves this dependency to code nobody reviewed. Pin it with `ref:` (a full commit SHA) or `tag:`.
Floating source dependency: rustler — Runtime dependency `:rustler` is fetched from source in implementations/elixir/ockam/ockam_rust_elixir_nifs/mix.exs and tracks a branch — the declaration pins no immutable revision, so `mix deps.update` moves this dependency to code nobody reviewed. Pin it with `ref:` (a full commit SHA) or `tag:`.
ockam_abac::eval::eval (cognitive 129) implementations/rust/ockam/ockam_abac/src/eval.rs:10— ockam_abac::eval::eval has cognitive complexity 129 (threshold 15). Drivers by points: if/else 15 (61 pts), loops 9 (38 pts), match/switch 9 (30 pts) (nesting depth added 96). 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.
ockam_abac::parser::parse (cognitive 58) implementations/rust/ockam/ockam_abac/src/parser.rs:27— ockam_abac::parser::parse has cognitive complexity 58 (threshold 15). Drivers by points: if/else 9 (24 pts), match/switch 8 (24 pts), loops 4 (10 pts) (nesting depth added 37). 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.
ockam_abac::bin::repl::main (cognitive 16) implementations/rust/ockam/ockam_abac/src/bin/repl.rs:22— ockam_abac::bin::repl::main has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (11 pts), if/else 2 (4 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.
TooManyFunctions: attribute_rule_grammar implementations/elixir/ockam/ockam_abac/src/attribute_rule_grammar.erl:1— TooManyFunctions — 59 functions. The bar is 30 functions; this is 29 over it, 1.97× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Channel implementations/elixir/ockam/ockam/lib/ockam/secure_channel/channel.ex:1— TooManyFunctions — 36 functions. The bar is 30 functions; this is 6 over it, 1.20× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: ockam_api::logs::exporting_configuration implementations/rust/ockam/ockam_api/src/logs/exporting_configuration.rs:252— TooManyFunctions — 32 free functions. The bar is 30 free functions; 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.
ClassTooLong: TcpPortalWorker implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.rs:66— ClassTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 19 methods, 5 blocks, lines 66-823. The bar is 400 significant lines; this is 128 over it, 1.32× 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: NodeManager implementations/rust/ockam/ockam_api/src/nodes/service/manager.rs:56— ClassTooLong — 454 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 85 methods, 2 blocks, lines 56-694. The bar is 400 significant lines; this is 54 over it, 1.14× 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: EnrollHandler implementations/rust/ockam/ockam_command/src/enroll/handler.rs:41— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 3 blocks, lines 41-643. The bar is 400 significant lines; this is 30 over it, 1.08× 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.
Duplicated block (17 lines × 2) implementations/rust/ockam/ockam_command/src/share/create.rs:87— implementations/rust/ockam/ockam_command/src/share/create.rs:87-103 | implementations/rust/ockam/ockam_command/src/share/service.rs:98-114 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/share/create.rs` and `implementations/rust/ockam/ockam_command/src/share/service.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 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.
Duplicated block (17 lines × 2) implementations/rust/ockam/ockam_node/src/compat/mutex.rs:89— implementations/rust/ockam/ockam_node/src/compat/mutex.rs:89-105 | implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs:89-105 — before extracting anything, compare `implementations/rust/ockam/ockam_node/src/compat/mutex.rs` and `implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 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 (17 lines × 2) implementations/rust/ockam/ockam_abac/src/policy/incoming.rs:19— implementations/rust/ockam/ockam_abac/src/policy/incoming.rs:19-35 | implementations/rust/ockam/ockam_abac/src/policy/outgoing.rs:28-44 — 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 × 3) implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:120— implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:120-124 | implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:129-133 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/acceptor_worker.rs:62-66 — 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.
Duplicated block (5 lines × 3) implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:396— implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:396-400 | implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs:228-232 | implementations/rust/ockam/ockam_api/src/cli_state/storage/users_repository_sql.rs:121-125 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs` and `implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 69 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.
Duplicated block (5 lines × 3) implementations/rust/ockam/ockam_command/src/zone/create.rs:43— implementations/rust/ockam/ockam_command/src/zone/create.rs:43-47 | implementations/rust/ockam/ockam_command/src/zone/secret.rs:50-54 | implementations/rust/ockam/ockam_command/src/zone/ticket.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 all 3 call sites, so a change lands once.
Off the main sequence: ockam_rust_elixir_nifs (OTP) — ockam_rust_elixir_nifs (OTP): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: ockam_typed_cbor — ockam_typed_cbor: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: ockam_core — ockam_core: abstractness 0.13, instability 0.06, distance 0.81 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
ockam_abac::eval::eval (cyclomatic 58) implementations/rust/ockam/ockam_abac/src/eval.rs:10— ockam_abac::eval::eval has cyclomatic complexity 58 (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.
ockam_abac::parser::parse (cyclomatic 47) implementations/rust/ockam/ockam_abac/src/parser.rs:27— ockam_abac::parser::parse has cyclomatic complexity 47 (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.
ockam_command::node::util::spawn_node (cyclomatic 27) implementations/rust/ockam/ockam_command/src/node/util.rs:57— ockam_command::node::util::spawn_node 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.
ockam_command::markdown::generate_markdown_page (cyclomatic 19) implementations/rust/ockam/ockam_command/src/markdown/mod.rs:132— ockam_command::markdown::generate_markdown_page 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.
CreateCommand::spawn_background_node (cyclomatic 16) implementations/rust/ockam/ockam_command/src/authority/create.rs:134— CreateCommand::spawn_background_node has cyclomatic complexity 16 (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.
CreateCommand::run (cyclomatic 16) implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:190— CreateCommand::run 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.
HackComment implementations/rust/ockam/ockam_api/tests/common/common.rs:37— // Hack to create Authority Identity using the same vault and storage — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment implementations/elixir/ockam/ockam/test/ockam/secure_channel_test.exs:277— # Hacky way to get the receiver' pid, so we can monitor it and ensure it get terminated — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
ockam_command::markdown::generate_markdown_page (cognitive 35) implementations/rust/ockam/ockam_command/src/markdown/mod.rs:132— ockam_command::markdown::generate_markdown_page has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (27 pts), loops 3 (8 pts) (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.
ockam_command::node::util::spawn_node (cognitive 26) implementations/rust/ockam/ockam_command/src/node/util.rs:57— ockam_command::node::util::spawn_node has cognitive complexity 26 (threshold 15). Drivers by points: if/else 25, loops 1. 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.
ZoneConfig::transform_env_vars (cognitive 34) implementations/rust/ockam/ockam_command/src/zone/zone_config.rs:233— ZoneConfig::transform_env_vars has cognitive complexity 34 (threshold 15). Drivers by points: if/else 4 (17 pts), loops 4 (13 pts), match/switch 1 (4 pts) (nesting depth added 25). 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.
ZoneConfig::validate (cognitive 19) implementations/rust/ockam/ockam_command/src/zone/zone_config.rs:131— ZoneConfig::validate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 5 (7 pts) (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.
ockam_node::debugger::generate_graphs (cognitive 32) implementations/rust/ockam/ockam_node/src/debugger.rs:170— ockam_node::debugger::generate_graphs has cognitive complexity 32 (threshold 15). Drivers by points: loops 11 (29 pts), match/switch 2, if/else 1 (nesting depth added 18). 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.
ockam_node::storage::database::database_configuration::parse_connection_string (cognitive 17) implementations/rust/ockam/ockam_node/src/storage/database/database_configuration.rs:431— ockam_node::storage::database::database_configuration::parse_connection_string has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 4 (7 pts) (nesting depth added 9). 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.
ConnectionBuilder::instantiate (cognitive 28) implementations/rust/ockam/ockam_api/src/nodes/connection/mod.rs:250— ConnectionBuilder::instantiate has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (26 pts), loops 1 (2 pts) (nesting depth added 20). 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.
ConnectionBuilder::recalculate_transport_route (cognitive 16) implementations/rust/ockam/ockam_api/src/nodes/connection/mod.rs:323— ConnectionBuilder::recalculate_transport_route has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (14 pts), boolean chains 1, loops 1 (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.
DevCommand::run_containers (cognitive 25) implementations/rust/ockam/ockam_command/src/zone/dev.rs:647— DevCommand::run_containers has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 4 (9 pts), boolean chains 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.
DevCommand::add_container_env_vars (cognitive 19) implementations/rust/ockam/ockam_command/src/zone/dev.rs:850— DevCommand::add_container_env_vars has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (6 pts), match/switch 1 (2 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.
InletInterceptorImpl::handle_produce_request (cognitive 22) implementations/rust/ockam/ockam_api/src/kafka/protocol_aware/inlet/request.rs:193— InletInterceptorImpl::handle_produce_request has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 3 (7 pts) (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.
InletInterceptorImpl::handle_fetch_response (cognitive 22) implementations/rust/ockam/ockam_api/src/kafka/protocol_aware/inlet/response.rs:273— InletInterceptorImpl::handle_fetch_response has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 3 (7 pts) (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.
Duplicated block (23 lines × 2) implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:273— implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:273-295 | implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:381-403 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs` and `implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (23 lines × 2) implementations/rust/ockam/ockam_transport_udp/src/puncture/negotiation/message.rs:24— implementations/rust/ockam/ockam_transport_udp/src/puncture/negotiation/message.rs:24-46 | implementations/rust/ockam/ockam_transport_udp/src/puncture/rendezvous_service/messages.rs:15-45 — 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 (22 lines × 2) implementations/rust/ockam/ockam_api/src/control_api/backend/entrypoint.rs:188— implementations/rust/ockam/ockam_api/src/control_api/backend/entrypoint.rs:188-209 | implementations/rust/ockam/ockam_api/src/control_api/frontend.rs:393-414 — 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 (22 lines × 2) implementations/rust/ockam/ockam_api/src/nodes/service/manager.rs:98— implementations/rust/ockam/ockam_api/src/nodes/service/manager.rs:98-119 | implementations/rust/ockam/ockam_api/src/nodes/service/manager.rs:124-145 — 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 (21 lines × 2) implementations/rust/ockam/ockam_command/src/kafka/consumer/create.rs:44— implementations/rust/ockam/ockam_command/src/kafka/consumer/create.rs:44-64 | implementations/rust/ockam/ockam_command/src/kafka/producer/create.rs:44-64 — 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 (21 lines × 2) implementations/rust/ockam/ockam_node/src/compat/mutex.rs:125— implementations/rust/ockam/ockam_node/src/compat/mutex.rs:125-145 | implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs:125-145 — before extracting anything, compare `implementations/rust/ockam/ockam_node/src/compat/mutex.rs` and `implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 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 (20 lines × 2) implementations/rust/ockam/ockam_command/src/zone/inlet.rs:132— implementations/rust/ockam/ockam_command/src/zone/inlet.rs:132-151 | implementations/rust/ockam/ockam_command/src/zone/outlet.rs:140-159 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/zone/inlet.rs` and `implementations/rust/ockam/ockam_command/src/zone/outlet.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 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.
Duplicated block (20 lines × 2) implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:66— implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:66-85 | implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:111-130 — 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 (13–15 lines × 2) implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:83— implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:83-95 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:267-281 — 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 (13–15 lines × 2) implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:125— implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:125-137 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:322-336 — 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 × 4) implementations/rust/ockam/ockam_command/src/secure_channel/listener/list.rs:53— implementations/rust/ockam/ockam_command/src/secure_channel/listener/list.rs:53-60 | implementations/rust/ockam/ockam_command/src/service/list.rs:41-48 | implementations/rust/ockam/ockam_command/src/tcp/listener/list.rs:47-54 | implementations/rust/ockam/ockam_command/src/worker/list.rs:50-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (8 lines × 4) implementations/rust/ockam/ockam_api/src/cli_state/storage/identities_repository_sql.rs:217— implementations/rust/ockam/ockam_api/src/cli_state/storage/identities_repository_sql.rs:217-224 | implementations/rust/ockam/ockam_api/src/cli_state/storage/identities_repository_sql.rs:233-240 | implementations/rust/ockam/ockam_api/src/cli_state/storage/nodes_repository_sql.rs:123-130 | implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs:44-51 — there are 4 copies across 3 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.
Duplicated block (6 lines × 3) implementations/rust/ockam/ockam_command/src/zone/dev.rs:260— implementations/rust/ockam/ockam_command/src/zone/dev.rs:260-265 | implementations/rust/ockam/ockam_command/src/zone/dev.rs:356-361 | implementations/rust/ockam/ockam_command/src/zone/logs.rs:163-168 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/zone/dev.rs` and `implementations/rust/ockam/ockam_command/src/zone/logs.rs` as WHOLE FILES: this scan already matched 5 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. 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.
Duplicated block (6 lines × 3) implementations/rust/ockam/ockam_core/src/routing/message/transport_message.rs:145— implementations/rust/ockam/ockam_core/src/routing/message/transport_message.rs:145-150 | implementations/rust/ockam/ockam_transport_tcp/src/transport_message.rs:47-52 | implementations/rust/ockam/ockam_transport_udp/src/messages/routing_message.rs:56-61 — 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.
Duplicated block (24 lines × 2) implementations/rust/ockam/ockam_api/src/control_api/backend/inlet.rs:26— implementations/rust/ockam/ockam_api/src/control_api/backend/inlet.rs:26-49 | implementations/rust/ockam/ockam_api/src/control_api/backend/outlet.rs:25-48 — 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 (24 lines × 2) implementations/elixir/ockam/ockam/lib/ockam/examples/messaging/ordering.ex:12— implementations/elixir/ockam/ockam/lib/ockam/examples/messaging/ordering.ex:12-35 | implementations/elixir/ockam/ockam/lib/ockam/examples/messaging/ordering.ex:54-77 — 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 (11 lines × 5) implementations/rust/ockam/ockam_command/src/kafka/inlet/delete.rs:61— implementations/rust/ockam/ockam_command/src/kafka/inlet/delete.rs:61-71 | implementations/rust/ockam/ockam_command/src/kafka/outlet/delete.rs:58-68 | implementations/rust/ockam/ockam_command/src/tcp/connection/delete.rs:61-71 | implementations/rust/ockam/ockam_command/src/tcp/inlet/delete.rs:67-77 | implementations/rust/ockam/ockam_command/src/tcp/outlet/delete.rs:72-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (11 lines × 5) implementations/rust/ockam/ockam_command/src/share/accept.rs:49— implementations/rust/ockam/ockam_command/src/share/accept.rs:49-59 | implementations/rust/ockam/ockam_command/src/share/create.rs:68-79 | implementations/rust/ockam/ockam_command/src/share/list.rs:49-59 | implementations/rust/ockam/ockam_command/src/share/service.rs:79-90 | implementations/rust/ockam/ockam_command/src/share/show.rs:51-61 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/share/create.rs` and `implementations/rust/ockam/ockam_command/src/share/service.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 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.
Duplicated block (8 lines × 3) implementations/rust/ockam/ockam_api/src/cli_state/storage/identities_repository_sql.rs:217— implementations/rust/ockam/ockam_api/src/cli_state/storage/identities_repository_sql.rs:217-224 | implementations/rust/ockam/ockam_api/src/cli_state/storage/identities_repository_sql.rs:233-240 | implementations/rust/ockam/ockam_api/src/cli_state/storage/nodes_repository_sql.rs:123-130 — 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.
Duplicated block (8 lines × 3) implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:403— implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:403-410 | implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs:235-242 | implementations/rust/ockam/ockam_api/src/cli_state/storage/users_repository_sql.rs:151-158 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs` and `implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 69 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.
NodeConfig::merge (cyclomatic 26) implementations/rust/ockam/ockam_command/src/node/create/config.rs:161— NodeConfig::merge 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.
Node::args (cyclomatic 24) implementations/rust/ockam/ockam_command/src/run/parser/resource/node.rs:54— Node::args has cyclomatic complexity 24 (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.
ReplCommand::open_repl (cyclomatic 23) implementations/rust/ockam/ockam_command/src/zone/repl.rs:59— ReplCommand::open_repl has cyclomatic complexity 23 (threshold 15). Of this number, 21 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.
RequestState::process_http_buffer (cyclomatic 18) implementations/rust/ockam/ockam_api/src/http/state.rs:26— RequestState::process_http_buffer 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.
DeleteCommandTui::delete (cyclomatic 16) implementations/rust/ockam/ockam_command/src/terminal/tui.rs:177— DeleteCommandTui::delete 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.
DirectoryWatcher::_run (cognitive 47) implementations/rust/ockam/ockam_command/src/zone/watcher.rs:75— DirectoryWatcher::_run has cognitive complexity 47 (threshold 15). Drivers by points: if/else 9 (36 pts), loops 2 (5 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 33). 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.
ReplCommand::open_repl (cognitive 42) implementations/rust/ockam/ockam_command/src/zone/repl.rs:59— ReplCommand::open_repl has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (28 pts), match/switch 5 (10 pts), loops 3 (4 pts) (nesting depth added 22). Of this number, 39 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.
InletCommand::parse_args (cognitive 40) implementations/rust/ockam/ockam_command/src/zone/inlet.rs:197— InletCommand::parse_args has cognitive complexity 40 (threshold 15). Drivers by points: if/else 9 (31 pts), loops 2 (7 pts), boolean chains 2 (nesting depth added 27). 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.
Abac::is_authorized_static (cognitive 35) implementations/rust/ockam/ockam_abac/src/abac/abac.rs:143— Abac::is_authorized_static has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 4 (14 pts), loops 1 (4 pts) (nesting depth added 23). 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.
DeleteNodeCommand::run (cognitive 33) implementations/rust/ockam/ockam_command/src/project_member/delete.rs:71— DeleteNodeCommand::run has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 18). 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.
KafkaKeyExchangeControllerImpl::get_or_create_secure_channel (cognitive 30) implementations/rust/ockam/ockam_api/src/kafka/key_exchange/secure_channels.rs:58— KafkaKeyExchangeControllerImpl::get_or_create_secure_channel has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (27 pts), match/switch 2 (3 pts) (nesting depth added 18). 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.
StatusData::fmt (cognitive 30) implementations/rust/ockam/ockam_command/src/status/mod.rs:181— StatusData::fmt has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 4 (8 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.
Node::args (cognitive 29) implementations/rust/ockam/ockam_command/src/run/parser/resource/node.rs:54— Node::args has cognitive complexity 29 (threshold 15). Drivers by points: if/else 23 (29 pts) (nesting depth added 6). 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.
RelayService::handle_message (cognitive 27) implementations/rust/ockam/ockam/src/relay_service/relay_service.rs:67— RelayService::handle_message has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (22 pts), match/switch 1 (5 pts) (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.
RequestState::process_http_buffer (cognitive 27) implementations/rust/ockam/ockam_api/src/http/state.rs:26— RequestState::process_http_buffer has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 3 (8 pts), 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.
Migrator::run_migrations_impl (cognitive 27) implementations/rust/ockam/ockam_node/src/storage/database/migrations/migration_support/migrator.rs:121— Migrator::run_migrations_impl has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 6 (8 pts), loops 2 (4 pts) (nesting depth added 14). 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.
NodeConfig::merge (cognitive 26) implementations/rust/ockam/ockam_command/src/node/create/config.rs:161— NodeConfig::merge has cognitive complexity 26 (threshold 15). Drivers by points: if/else 22 (23 pts), boolean chains 2, loops 1 (nesting depth added 1). 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.
DeleteCommand::print_output (cognitive 25) implementations/rust/ockam/ockam_command/src/secure_channel/delete.rs:46— DeleteCommand::print_output has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (19 pts), boolean chains 3, match/switch 2 (3 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.
Command::run_with_retry (cognitive 24) implementations/rust/ockam/ockam_command/src/subcommand.rs:400— Command::run_with_retry has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 4 (14 pts), if/else 3 (8 pts), loops 1 (2 pts) (nesting depth added 16). 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.
DeleteCommandTui::delete (cognitive 24) implementations/rust/ockam/ockam_command/src/terminal/tui.rs:177— DeleteCommandTui::delete has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 2 (3 pts), boolean chains 2 (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.
OutletCommand::parse_args (cognitive 24) implementations/rust/ockam/ockam_command/src/zone/outlet.rs:205— OutletCommand::parse_args has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (3 pts), boolean chains 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.
SqlxDatabase::create_impl (cognitive 23) REDACTED:154— SqlxDatabase::create_impl has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 4 (9 pts), boolean chains 2 (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.
DevNodeCommand::run (cognitive 22) implementations/rust/ockam/ockam_command/src/zone/dev.rs:117— DevNodeCommand::run has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 5 (13 pts), if/else 8 (9 pts) (nesting depth added 9). 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.
HandshakeWorker::create (cognitive 22) implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake_worker.rs:136— HandshakeWorker::create has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (13 pts), match/switch 2 (9 pts) (nesting depth added 10). 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.
NodeResources::fmt (cognitive 21) implementations/rust/ockam/ockam_api/src/nodes/models/node.rs:146— NodeResources::fmt has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10, loops 5 (10 pts), boolean chains 1 (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.
EnrollHandler::get_user_space (cognitive 21) implementations/rust/ockam/ockam_command/src/enroll/handler.rs:397— EnrollHandler::get_user_space has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 2 (3 pts) (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.
TcpPortalWorker::handle_message (cognitive 21) implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.rs:613— TcpPortalWorker::handle_message has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 2 (4 pts), boolean chains 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.
TokioRuntimeWatchdog::watchdog_loop (cognitive 20) implementations/rust/ockam/ockam_node/src/watchdog.rs:33— TokioRuntimeWatchdog::watchdog_loop has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 4 (9 pts), boolean chains 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.
ShowCommandTui::show (cognitive 19) implementations/rust/ockam/ockam_command/src/terminal/tui.rs:26— ShowCommandTui::show has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 1 (3 pts), match/switch 2 (3 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.
OckamLogFormat::format_event (cognitive 18) implementations/rust/ockam/ockam_api/src/logs/logging_options.rs:102— OckamLogFormat::format_event has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 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.
Session::run_loop (cognitive 18) implementations/rust/ockam/ockam_api/src/session/session.rs:439— Session::run_loop has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 3 (7 pts), boolean chains 2, 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.
BleAdapter::connect (cognitive 17) implementations/rust/ockam/ockam_transport_ble/src/driver/btleplug/mod.rs:104— BleAdapter::connect has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 2 (3 pts) (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.
PeerPendingRoutingMessageStorage::add_transport_message_and_try_assemble (cognitive 17) implementations/rust/ockam/ockam_transport_udp/src/workers/pending_messages/peer_pending_routing_message_storage.rs:39— PeerPendingRoutingMessageStorage::add_transport_message_and_try_assemble has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (7 pts), if/else 4 (5 pts), loops 2 (5 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.
Brand::fmt (cognitive 16) implementations/rust/ockam/ockam_command/src/bin/brand.rs:228— Brand::fmt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7, loops 2 (6 pts), match/switch 1 (3 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.
DeployCommand::build_local_image (cognitive 16) implementations/rust/ockam/ockam_command/src/zone/deploy.rs:307— DeployCommand::build_local_image has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (5 pts), match/switch 1 (3 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.
InitCommand::create_target_path (cognitive 16) implementations/rust/ockam/ockam_command/src/zone/init.rs:97— InitCommand::create_target_path has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (15 pts), match/switch 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.
PendingMessage::add_transport_message (cognitive 16) implementations/rust/ockam/ockam_transport_udp/src/workers/pending_messages/pending_message.rs:78— PendingMessage::add_transport_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (16 pts) (nesting depth added 3). 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.
Channel.handle_inner_message_impl (cognitive 16) implementations/elixir/ockam/ockam/lib/ockam/secure_channel/channel.ex:539— Channel.handle_inner_message_impl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 3 (6 pts) (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.
D4 · Code Duplication· Near-duplicate member family (3 members, 8 shared lines) · ×1
Near-duplicate member family (3 members, 8 shared lines) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:313— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:313-326 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:330-345 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:349-366 — These 3 members are variants of one another: a block of 8 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
Near-duplicate member pair (49 shared lines) implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:168— implementations/rust/ockam/ockam_command/src/influxdb/inlet/create.rs:168-268 | implementations/rust/ockam/ockam_command/src/tcp/inlet/create.rs:190-342 — These two members are variants of one another: 49 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 (28 shared lines) implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:402— implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:402-449 | implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs:234-274 — These two members are variants of one another: 28 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· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:91— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:91-109 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:113-129 — 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 copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) implementations/rust/ockam/ockam_api/src/multiaddr_resolver/local_resolver.rs:11— implementations/rust/ockam/ockam_api/src/multiaddr_resolver/local_resolver.rs:11-60 | implementations/rust/ockam/ockam_api/src/multiaddr_resolver/transport_route_resolver.rs:41-117 — These two members are one piece of code written twice and then edited apart: 18 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 (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) implementations/rust/ockam/ockam_api/src/control_api/backend/entrypoint.rs:182— implementations/rust/ockam/ockam_api/src/control_api/backend/entrypoint.rs:182-222 | implementations/rust/ockam/ockam_api/src/control_api/frontend.rs:392-428 — These two members are one piece of code written twice and then edited apart: 22 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 (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:53— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:53-67 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:71-87 — These two members are one piece of code written twice and then edited apart: 15 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· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (12 members, 50+ identical tokens) implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:31— implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:31-69 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:75-110 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:117-160 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:168-200 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:209-250 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:257-301 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:309-344 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:353-405 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:417-460 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:467-504 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:510-543 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:549-589 — These 12 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 12 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 12 times.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) REDACTED:83— REDACTED:83-107 | REDACTED:113-138 | REDACTED:144-168 | REDACTED:174-197 | REDACTED:203-227 | REDACTED:233-256 | REDACTED:298-321 | REDACTED:327-350 | REDACTED:356-377 — These 9 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 9 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 9 times.
Duplicated block (42 lines × 2) implementations/rust/ockam/ockam_node/src/compat/mutex.rs:203— implementations/rust/ockam/ockam_node/src/compat/mutex.rs:203-244 | implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs:194-235 — before extracting anything, compare `implementations/rust/ockam/ockam_node/src/compat/mutex.rs` and `implementations/rust/ockam/ockam_transport_ble/src/driver/mutex.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 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 (40 lines × 2) implementations/rust/ockam/ockam_abac/src/expr.rs:275— implementations/rust/ockam/ockam_abac/src/expr.rs:275-314 | implementations/rust/ockam/ockam_node/src/storage/database/migrations/node_migrations/rust/sqlite/migration_20240111100002_delete_trust_context.rs:132-171 — 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 (32 lines × 2) implementations/rust/ockam/ockam_command/src/zone/dev.rs:243— implementations/rust/ockam/ockam_command/src/zone/dev.rs:243-274 | implementations/rust/ockam/ockam_command/src/zone/dev.rs:339-370 — 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 (26–27 lines × 2) implementations/rust/ockam/ockam_command/src/zone/dev.rs:215— implementations/rust/ockam/ockam_command/src/zone/dev.rs:215-241 | implementations/rust/ockam/ockam_command/src/zone/dev.rs:312-337 — 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 (24–25 lines × 2) implementations/rust/ockam/ockam_command/src/zone/dev.rs:328— implementations/rust/ockam/ockam_command/src/zone/dev.rs:328-351 | implementations/rust/ockam/ockam_command/src/zone/logs.rs:133-157 — before extracting anything, compare `implementations/rust/ockam/ockam_command/src/zone/dev.rs` and `implementations/rust/ockam/ockam_command/src/zone/logs.rs` as WHOLE FILES: this scan already matched 5 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. 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.
Duplicated block (22–24 lines × 2) implementations/rust/ockam/ockam_transport_ble/src/router/mod.rs:69— implementations/rust/ockam/ockam_transport_ble/src/router/mod.rs:69-90 | implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:216-239 — 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–18 lines × 2) implementations/rust/ockam/ockam_api/src/influxdb/portal.rs:245— implementations/rust/ockam/ockam_api/src/influxdb/portal.rs:245-259 | implementations/rust/ockam/ockam_api/src/nodes/service/kafka_services.rs:298-315 — 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 (17 lines × 4) implementations/rust/ockam/ockam_transport_ble/src/router/mod.rs:172— implementations/rust/ockam/ockam_transport_ble/src/router/mod.rs:172-188 | implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:105-121 | implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:61-77 | implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:106-122 — there are 4 copies across 3 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.
Duplicated block (15 lines × 4) implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:43— implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:43-57 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:229-243 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:377-391 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:434-448 — 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.
Duplicated block (13–15 lines × 3) implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:477— implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:477-491 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:518-530 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:557-569 — 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 (14 lines × 12) implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:48— implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:48-61 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:87-100 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:129-142 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:184-197 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:234-247 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:273-286 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:328-341 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:382-395 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:439-452 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:483-496 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:522-535 | implementations/rust/ockam/ockam_api/src/orchestrator/ai_platform/node_service_client.rs:561-574 — all 12 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 (13 lines × 4) implementations/rust/ockam/ockam_api/src/authenticator/credential_issuer/credential_issuer_worker.rs:55— implementations/rust/ockam/ockam_api/src/authenticator/credential_issuer/credential_issuer_worker.rs:55-67 | implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:46-58 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/acceptor_worker.rs:35-47 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs:47-59 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs` and `implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 (11–12 lines × 2) REDACTED:96— REDACTED:96-107 | REDACTED:340-350 — 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 (7–11 lines × 2) implementations/rust/ockam/ockam_api/src/orchestrator/project/project.rs:62— implementations/rust/ockam/ockam_api/src/orchestrator/project/project.rs:62-72 | implementations/rust/ockam/ockam_api/src/orchestrator/project/project.rs:93-99 — 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–11 lines × 2) implementations/rust/ockam/ockam_command/src/output/mod.rs:80— implementations/rust/ockam/ockam_command/src/output/mod.rs:80-88 | implementations/rust/ockam/ockam_command/src/output/mod.rs:146-156 — 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–10 lines × 2) implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:110— implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:110-117 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs:79-88 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs` and `implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 (8–9 lines × 2) implementations/rust/ockam/ockam_command/src/secure_channel/listener/list.rs:54— implementations/rust/ockam/ockam_command/src/secure_channel/listener/list.rs:54-62 | implementations/rust/ockam/ockam_command/src/service/list.rs:42-49 — 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–7 lines × 3) implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:131— implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs:131-135 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/acceptor_worker.rs:64-69 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs:85-91 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator_worker.rs` and `implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 (30 lines × 3) implementations/rust/ockam/ockam_api/src/nodes/models/transport/request.rs:15— implementations/rust/ockam/ockam_api/src/nodes/models/transport/request.rs:15-83 | implementations/rust/ockam/ockam_api/src/orchestrator/share/accept.rs:15-44 | implementations/rust/ockam/ockam_api/src/orchestrator/share/list.rs:15-54 — 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.
Duplicated block (29 lines × 2) implementations/rust/ockam/ockam_identity/src/purpose_key/credential/purpose_key.rs:22— implementations/rust/ockam/ockam_identity/src/purpose_key/credential/purpose_key.rs:22-50 | implementations/rust/ockam/ockam_identity/src/purpose_key/secure_channel/purpose_key.rs:22-50 — 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 (7 lines × 5) implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:33— implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs:33-39 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_repository_sql.rs:35-41 | implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs:37-43 | implementations/rust/ockam/ockam_identity/src/identities/storage/credential_repository_sql.rs:37-43 | implementations/rust/ockam/ockam_identity/src/identities/storage/identity_attributes_repository_sql.rs:38-44 — before extracting anything, compare `implementations/rust/ockam/ockam_abac/src/policy/storage/resource_policy_repository_sql.rs` and `implementations/rust/ockam/ockam_abac/src/policy/storage/resource_type_policy_repository_sql.rs` as WHOLE FILES: this scan already matched 5 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. 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.
Duplicated block (7 lines × 15) implementations/rust/ockam/ockam_api/src/authenticator/storage/authority_enrollment_token_repository_sql.rs:33— implementations/rust/ockam/ockam_api/src/authenticator/storage/authority_enrollment_token_repository_sql.rs:33-39 | implementations/rust/ockam/ockam_api/src/authenticator/storage/authority_members_repository_sql.rs:28-34 | implementations/rust/ockam/ockam_api/src/cli_state/storage/enrollments_repository_sql.rs:29-35 | implementations/rust/ockam/ockam_api/src/cli_state/storage/identities_repository_sql.rs:27-33 | implementations/rust/ockam/ockam_api/src/cli_state/storage/journeys_repository_sql.rs:26-32 | implementations/rust/ockam/ockam_api/src/cli_state/storage/nodes_repository_sql.rs:30-36 | implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs:45-51 | implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs:27-33 | implementations/rust/ockam/ockam_api/src/cli_state/storage/tcp_portals_repository_sql.rs:34-40 | implementations/rust/ockam/ockam_api/src/cli_state/storage/users_repository_sql.rs:27-33 | implementations/rust/ockam/ockam_api/src/cli_state/storage/vaults_repository_sql.rs:24-30 | implementations/rust/ockam/ockam_identity/src/identities/storage/change_history_repository_sql.rs:33-39 | implementations/rust/ockam/ockam_identity/src/purpose_keys/storage/purpose_keys_repository_sql.rs:35-41 | implementations/rust/ockam/ockam_identity/src/secure_channels/storage/secure_channel_repository_sql.rs:32-38 | implementations/rust/ockam/ockam_vault/src/storage/secrets_repository_sql.rs:37-43 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.rs` and `implementations/rust/ockam/ockam_api/src/cli_state/storage/spaces_repository_sql.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 69 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.
Duplicated block (8 lines × 5) implementations/rust/ockam/ockam_command/src/cluster/show.rs:74— implementations/rust/ockam/ockam_command/src/cluster/show.rs:74-81 | implementations/rust/ockam/ockam_command/src/zone/create.rs:70-77 | implementations/rust/ockam/ockam_command/src/zone/delete.rs:76-83 | implementations/rust/ockam/ockam_command/src/zone/list.rs:89-96 | implementations/rust/ockam/ockam_command/src/zone/secret.rs:99-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (11 lines × 3) implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator.rs:151— implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator.rs:151-161 | implementations/rust/ockam/ockam_api/src/authenticator/direct/direct_authenticator.rs:192-202 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer.rs:62-75 — 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.
Duplicated block (12 lines × 3) implementations/rust/ockam/ockam_command/src/kafka/inlet/list.rs:38— implementations/rust/ockam/ockam_command/src/kafka/inlet/list.rs:38-49 | implementations/rust/ockam/ockam_command/src/kafka/outlet/list.rs:36-47 | implementations/rust/ockam/ockam_command/src/tcp/inlet/list.rs:41-52 — 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.
Duplicated block (8 lines × 7) REDACTED:117— REDACTED:117-124 | REDACTED:148-155 | REDACTED:207-214 | REDACTED:237-246 | REDACTED:304-311 | REDACTED:333-340 | REDACTED:361-368 — all 7 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 (9 lines × 3) implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/acceptor_worker.rs:49— implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/acceptor_worker.rs:49-57 | implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs:61-69 | implementations/rust/ockam/ockam_api/src/okta/mod.rs:72-80 — before extracting anything, compare `implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/acceptor_worker.rs` and `implementations/rust/ockam/ockam_api/src/authenticator/enrollment_tokens/issuer_worker.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 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.
Duplicated block (16–17 lines × 2) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/request/parser.ex:59— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/request/parser.ex:59-75 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/request/parser.ex:83-98 — 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 × 3) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:254— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:254-264 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:275-284 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:296-305 — 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 (3–10 lines × 3) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:38— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:38-47 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:55-63 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:72-74 — 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–9 lines × 3) implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:316— implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:316-324 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:334-341 | implementations/elixir/ockam/ockam_kafka/lib/interceptor/protocol/metadata/response/parser.ex:354-361 — 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 (33–34 lines × 2) implementations/rust/ockam/ockam_api/src/test_utils/mod.rs:407— implementations/rust/ockam/ockam_api/src/test_utils/mod.rs:407-440 | implementations/rust/ockam/ockam_api/src/test_utils/mod.rs:462-494 — 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 (25 lines × 2) implementations/elixir/ockam/ockam/lib/ockam/examples/messaging/reliable_deduplication.ex:74— implementations/elixir/ockam/ockam/lib/ockam/examples/messaging/reliable_deduplication.ex:74-98 | implementations/elixir/ockam/ockam/lib/ockam/examples/messaging/reliable_deduplication.ex:110-134 — 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 (13 lines × 3) implementations/elixir/ockam/ockam/lib/ockam/examples/session/count_to.ex:35— implementations/elixir/ockam/ockam/lib/ockam/examples/session/count_to.ex:35-47 | implementations/elixir/ockam/ockam/lib/ockam/examples/session/routing.ex:59-71 | implementations/elixir/ockam/ockam/lib/ockam/examples/session/routing.ex:76-88 — 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.
End-of-life runtime: Rust 1.86 rust-toolchain.toml:1— rust-toolchain.toml declares Rust 1.86 as this project's toolchain file, and Rust 1.86, superseded by 1.87 on 2025-05-15 (the Rust project patches only the current stable). An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2025-05-15 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Orphaned file implementations/rust/ockam/ockam_core/src/api.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.
Orphaned file implementations/rust/ockam/ockam_command/src/zone/dev.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.
Orphaned file REDACTED: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.
Orphaned file implementations/rust/ockam/ockam_api/src/cli_state/storage/projects_repository_sql.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.
Orphaned file implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_worker.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.
Orphaned file implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake.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.
Orphaned file implementations/rust/ockam/ockam_abac/src/boolean_expr.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.
Orphaned file implementations/rust/ockam/ockam_api/src/cli_state/vaults.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.
Orphaned file implementations/rust/ockam/ockam_api/src/cli_state/nodes.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.
Orphaned file implementations/rust/ockam/ockam_api/src/cli_state/enrollments.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.
Orphaned file implementations/rust/ockam/ockam_api/src/authority_node/authority.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.
Orphaned file implementations/rust/ockam/ockam_api/src/nodes/service/manager.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.
Orphaned file implementations/rust/ockam/ockam_command/src/node/create/config.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.
Orphaned file implementations/rust/ockam/ockam_api/src/logs/exporting_configuration.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.
Orphaned file implementations/rust/ockam/ockam_command/src/enroll/handler.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.
Orphaned file implementations/rust/ockam/ockam_transport_tcp/src/portal/interceptor.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.
Orphaned file implementations/rust/ockam/ockam_api/src/control_api/frontend.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.
Orphaned file implementations/rust/ockam/ockam_command/src/node/create.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.
Orphaned file implementations/rust/ockam/ockam_multiaddr/src/lib.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.
Orphaned file implementations/rust/ockam/ockam_api/src/session/session.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.
Orphaned file implementations/rust/ockam/ockam_identity/src/secure_channel/handshake/handshake_worker.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.
Orphaned file implementations/rust/ockam/ockam_command/src/zone/repl.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.
Orphaned file implementations/rust/ockam/ockam_abac/src/expr.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.
Orphaned file implementations/elixir/ockam/ockam/lib/ockam/secure_channel/channel.ex: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.
Orphaned file implementations/rust/ockam/ockam_command/src/zone/deploy.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.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_vault_aws/src/aws_signing_vault.rs:47— `error!` at line 47 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 implementations/rust/ockam/ockam_transport_websocket/src/workers/listener.rs:28— `debug!` at line 28 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 implementations/rust/ockam/ockam_transport_websocket/src/workers/receiver.rs:57— `debug!` at line 57 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 implementations/rust/ockam/ockam_transport_websocket/src/workers/receiver.rs:65— `info!` at line 65 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 implementations/rust/ockam/ockam_transport_websocket/src/workers/receiver.rs:83— `trace!` at line 83 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_websocket/src/workers/receiver.rs:91— `trace!` at line 91 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_websocket/src/workers/receiver.rs:92— `trace!` at line 92 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:201— `warn!` at line 201 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 implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:206— `debug!` at line 206 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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 implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:216— `warn!` at line 216 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 implementations/rust/ockam/ockam_transport_websocket/src/workers/sender.rs:220— `debug!` at line 220 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:81— `debug!` at line 81 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 implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:154— `trace!` at line 154 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:175— `trace!` at line 175 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_websocket/src/router/mod.rs:211— `trace!` at line 211 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_uds/src/lib.rs:45— `error!` at line 45 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 implementations/rust/ockam/ockam_transport_uds/src/workers/listener.rs:36— `error!` at line 36 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 implementations/rust/ockam/ockam_transport_uds/src/workers/listener.rs:40— `debug!` at line 40 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 implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:47— `debug!` at line 47 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 implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:63— `trace!` at line 63 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:72— `error!` at line 72 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 implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:83— `trace!` at line 83 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:91— `trace!` at line 91 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_uds/src/workers/receiver.rs:92— `trace!` at line 92 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging implementations/rust/ockam/ockam_transport_uds/src/workers/sender.rs:228— `error!` at line 228 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file implementations/rust/ockam/ockam_command/src/zone/zone_config.rs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file implementations/rust/ockam/ockam_api/src/ui/terminal/mod.rs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file REDACTED:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D30 · Dependency Vulnerabilities· Stale vulnerability suppression · ×2
Duplicated predicate implementations/elixir/ockam/ockam/lib/ockam/identity/trust_policy.ex:159— `is_atom(module) and is_atom(function) and is_list(args)` appears character-identically in 2 files — implementations/elixir/ockam/ockam/lib/ockam/identity/trust_policy.ex, implementations/elixir/ockam/ockam/lib/ockam/worker/authorization.ex. 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 implementations/rust/ockam/ockam_command/src/node/start.rs:39— `self.node_name.is_some() || !opts.terminal.can_ask_for_user_input()` appears character-identically in 2 files — implementations/rust/ockam/ockam_command/src/node/start.rs, implementations/rust/ockam/ockam_command/src/node/stop.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 11 significant file(s) lose their only recent owner: implementations/rust/ockam/ockam_command/src/zone/init.rs, implementations/rust/ockam/ockam_command/src/zone/outlet.rs, implementations/rust/ockam/ockam_command/src/zone/common_args.rs, implementations/rust/ockam/ockam_command/src/zone/secret.rs, implementations/rust/ockam/ockam_command/src/zone/inlet.rs, implementations/rust/ockam/ockam_command/src/zone/attach.rs, implementations/rust/ockam/ockam_command/src/base_command.rs, implementations/rust/ockam/ockam_command/src/zone/delete.rs (+3 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (13 single-owned of 699 analysed files in total, 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; 699 of the 1281 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: implementations/rust/ockam/ockam_command/src/zone/dev.rs, implementations/rust/ockam/ockam_api/src/logs/span_exporters.rs.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 6 of 29 project(s) overshoot their size bounds, lowering Project Cohesion to 6.2/10. The most over is `implementations/rust/ockam/ockam_api` (43336 LoC, 438 module-visible types across 41 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
Dormant codebase — 699 of 699 significant files have no living knowledge — the codebase as a whole is dormant, not 699 separate risks. Counted over 699 of the 1281 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
Thin README — The root README is 35 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
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.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
Logging is not universal — Only 23/24 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `implementations/rust/ockam/ockam_macros`.
Outdated: cbor — `:cbor` is locked at 1.0.1 but 1.0.2 is the current stable release on hex.pm, and it already satisfies the `"~> 1.0.0"` requirement declared in implementations/elixir/ockam/ockam/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update cbor` and commit the updated REDACTED.
Outdated: cbor — `:cbor` is locked at 1.0.1 but 1.0.2 is the current stable release on hex.pm, and it already satisfies the `"~> 1.0.0"` requirement declared in implementations/elixir/ockam/ockam_typed_cbor/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update cbor` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.12 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in implementations/elixir/ockam/ockam_healthcheck/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.12 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in implementations/elixir/ockam/ockam_metrics/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.12 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in implementations/elixir/ockam/ockam_kafka/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.12 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in implementations/elixir/ockam/ockam_services/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.12 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in implementations/elixir/ockam/ockam_typed_cbor/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.12 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in implementations/elixir/ockam/ockam_cloud_node/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.12 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in implementations/elixir/ockam/ockam_rust_elixir_nifs/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.12 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in implementations/elixir/ockam/ockam_abac/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: credo — `:credo` is locked at 1.7.12 but 1.7.19 is the current stable release on hex.pm, and it already satisfies the `"~> 1.6"` requirement declared in implementations/elixir/ockam/ockam/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update credo` and commit the updated REDACTED.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.5 but 1.4.8 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in implementations/elixir/ockam/ockam_abac/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated REDACTED.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.5 but 1.4.8 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in implementations/elixir/ockam/ockam_cloud_node/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated REDACTED.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.5 but 1.4.8 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in implementations/elixir/ockam/ockam_services/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated REDACTED.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.5 but 1.4.8 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in implementations/elixir/ockam/ockam_typed_cbor/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated REDACTED.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.5 but 1.4.8 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in implementations/elixir/ockam/ockam/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated REDACTED.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.5 but 1.4.8 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in implementations/elixir/ockam/ockam_healthcheck/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated REDACTED.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.5 but 1.4.8 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in implementations/elixir/ockam/ockam_metrics/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated REDACTED.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.5 but 1.4.8 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in implementations/elixir/ockam/ockam_kafka/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated REDACTED.
Outdated: ex_doc — `:ex_doc` is locked at 0.38.2 but 0.40.4 is the current stable release on hex.pm, and it already satisfies the `"~> 0.25"` requirement declared in implementations/elixir/ockam/ockam_metrics/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ex_doc` and commit the updated REDACTED.
Outdated: ex_doc — `:ex_doc` is locked at 0.38.2 but 0.40.4 is the current stable release on hex.pm, and it already satisfies the `"~> 0.25"` requirement declared in implementations/elixir/ockam/ockam/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ex_doc` and commit the updated REDACTED.
Outdated: ex_doc — `:ex_doc` is locked at 0.38.2 but 0.40.4 is the current stable release on hex.pm, and it already satisfies the `"~> 0.25"` requirement declared in implementations/elixir/ockam/ockam_kafka/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ex_doc` and commit the updated REDACTED.
Outdated: ex_doc — `:ex_doc` is locked at 0.38.2 but 0.40.4 is the current stable release on hex.pm, and it already satisfies the `"~> 0.25"` requirement declared in implementations/elixir/ockam/ockam_typed_cbor/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ex_doc` and commit the updated REDACTED.
Outdated: ex_doc — `:ex_doc` is locked at 0.38.2 but 0.40.4 is the current stable release on hex.pm, and it already satisfies the `"~> 0.25"` requirement declared in implementations/elixir/ockam/ockam_abac/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ex_doc` and commit the updated REDACTED.
Outdated: ex_doc — `:ex_doc` is locked at 0.38.2 but 0.40.4 is the current stable release on hex.pm, and it already satisfies the `"~> 0.25"` requirement declared in implementations/elixir/ockam/ockam_healthcheck/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ex_doc` and commit the updated REDACTED.
+ 13 more in this group — see findings.md.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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 01a181b7-5479-718d-9198-c9c1b03afb30 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 62 · Warnings: 803 · Recommendations: 768 · Info: 38 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 28-10-2026 @ 08:53 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.