Public report of bondy-io/bondy, published 15 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 15 November 2026, 06:26 UTC · Survey ID cd_6021cd2f7ec34d109b5be6e170e5a315
bondy-io/bondy
Measured 15 November 2026, 06:25 UTC, at code version d5df200
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 7 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: 195,410 lines of product code in 22 projects, tests not counted · Estimated rebuild effort: about 2.2 person-years · Weakest lens: Code Health, 21
Findings by how serious they are
41 critical727 serious36 minor
16 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 06:25 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
60of 60 dimensions measured by tools.
784of 804 findings point to an exact file and line, so you can open each one in the code. The other 20 concern the repository as a whole, such as missing documentation.
60dimensions across 8 lenses, read from 195,410 lines of product code in 22 projects.
bondy-io/bondy falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 42 out of 100 and is rated Weak, and 37 of its 41 critical findings are security problems.
Code Health, at 21, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 5 points. Adding type checking would lift Code Health itself, worth about 4 points. Raising Code Health to 70 would lift the score to about 58.
Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven secrets can leak from the build pipeline, and three passwords or keys in the code and two in the code's history are open to anyone who can read the repository. Pinning each tool to an exact version, limiting each secret to its own step and replacing each exposed password or key would close these risks. Updating the vulnerable packages would fix the two packages with a known security hole, and the two pipeline steps that run downloads without checking them need each download checked against a known checksum first. Moving the write out of the read operation would take care of the three read operations that also write data.
The product code is 195,410 lines, about €320,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Code Health rose from 21 to 70, the lowest score rated Strong, the score would rise from 42 to about 58.
Code composition: what the lines of code are
Product code 53%Tests 47%
New since the last survey: 579 findings
These 579 critical or serious findings weren't in the previous survey, on 30 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · FileTooLong: src/bondy_oplog_instance.erl apps/bondy_oplog/src/bondy_oplog_instance.erl
God Classes · FileTooLong: src/bondy_db.erl apps/bondy_db/src/bondy_db.erl
God Classes · FileTooLong: src/bondy_dealer.erl apps/bondy_router/src/bondy_dealer.erl
God Classes · FileTooLong: src/bondy_realm.erl apps/bondy_router/src/bondy_realm.erl
God Classes · FileTooLong: src/bondy_oplog_applier.erl apps/bondy_oplog/src/bondy_oplog_applier.erl
God Classes · FileTooLong: src/bondy_log_wal.erl apps/bondy_log/src/bondy_log_wal.erl
God Classes · FileTooLong: src/bondy_connect_error.erl apps/bondy_connect_lib/src/bondy_connect_error.erl
God Classes · FileTooLong: src/bondy_mst.erl apps/bondy_mst/src/bondy_mst.erl
God Classes · FileTooLong: src/bondy_registry_store.erl apps/bondy_router/src/bondy_registry_store.erl
God Classes · FileTooLong: src/bondy_connect_connection.erl apps/bondy_connect_sdk/src/bondy_connect_connection.erl
God Classes · FileTooLong: src/bondy_prometheus_db.erl apps/bondy_telemetry_exporter/src/bondy_prometheus_db.erl
God Classes · FileTooLong: src/bondy_rbac_user.erl apps/bondy_router/src/bondy_rbac_user.erl
God Classes · FileTooLong: include/bondy_wamp.hrl apps/bondy_wamp/include/bondy_wamp.hrl
God Classes · FileTooLong: src/bondy_mcp_http_handler.erl apps/bondy_mcp/src/bondy_mcp_http_handler.erl
God Classes · FileTooLong: src/bondy_http_gateway_rest_handler.erl apps/bondy_router/src/bondy_http_gateway_rest_handler.erl
God Classes · FileTooLong: src/bondy_mst_pack_store.erl apps/bondy_mst/src/bondy_mst_pack_store.erl
God Classes · FileTooLong: src/bondy_wamp_protocol.erl apps/bondy_router/src/bondy_wamp_protocol.erl
God Classes · FileTooLong: src/bondy_rbac.erl apps/bondy_router/src/bondy_rbac.erl
God Classes · FileTooLong: src/bondy_mst_pack_writer.erl apps/bondy_mst/src/bondy_mst_pack_writer.erl
God Classes · FileTooLong: src/bondy_oplog_cell_apply.erl apps/bondy_oplog/src/bondy_oplog_cell_apply.erl
God Classes · FileTooLong: src/bondy_bridge_relay_client.erl apps/bondy_router/src/bondy_bridge_relay_client.erl
God Classes · FileTooLong: src/bondy_oplog_core.erl apps/bondy_oplog/src/bondy_oplog_core.erl
God Classes · FileTooLong: src/bondy_registry_ptrie.erl apps/bondy_router/src/bondy_registry_ptrie.erl
God Classes · FileTooLong: src/bondy_prometheus.erl apps/bondy_telemetry_exporter/src/bondy_prometheus.erl
God Classes · FileTooLong: src/bondy_log_recovery.erl apps/bondy_log/src/bondy_log_recovery.erl
God Classes · TooManyFunctions: bondy_oplog_config apps/bondy_oplog/src/bondy_oplog_config.erl
God Classes · FileTooLong: src/bondy_oplog_sync_session.erl apps/bondy_oplog/src/bondy_oplog_sync_session.erl
God Classes · FileTooLong: src/bondy_export.erl apps/bondy_router/src/bondy_export.erl
God Classes · FileTooLong: src/bondy_oidc_handler.erl apps/bondy_router/src/bondy_oidc_handler.erl
God Classes · FileTooLong: src/bondy_oplog_sync_scheduler.erl apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl
God Classes · FileTooLong: src/bondy_oauth_token.erl apps/bondy_router/src/bondy_oauth_token.erl
God Classes · FileTooLong: src/bondy_bridge_relay_server.erl apps/bondy_router/src/bondy_bridge_relay_server.erl
God Classes · FileTooLong: src/bondy_oplog_core_registry.erl apps/bondy_oplog/src/bondy_oplog_core_registry.erl
God Classes · TooManyFunctions: bondy_oplog apps/bondy_oplog/src/bondy_oplog.erl
God Classes · TooManyFunctions: bondy_http_gateway apps/bondy_router/src/bondy_http_gateway.erl
God Classes · FileTooLong: src/bondy_session.erl apps/bondy_router/src/bondy_session.erl
God Classes · TooManyFunctions: bondy_connect_interval_set apps/bondy_connect_lib/src/bondy_connect_interval_set.erl
God Classes · TooManyFunctions: bondy_context apps/bondy_router/src/bondy_context.erl
God Classes · FileTooLong: src/bondy_registry_rib.erl apps/bondy_router/src/bondy_registry_rib.erl
God Classes · FileTooLong: src/bondy_ticket.erl apps/bondy_router/src/bondy_ticket.erl
God Classes · FileTooLong: src/bondy_registry.erl apps/bondy_router/src/bondy_registry.erl
God Classes · FileTooLong: src/bondy_wamp_encoding.erl apps/bondy_wamp/src/bondy_wamp_encoding.erl
God Classes · FileTooLong: src/bondy_mcp_handshake.erl apps/bondy_mcp/src/bondy_mcp_handshake.erl
God Classes · FileTooLong: src/bondy_wamp_message.erl apps/bondy_wamp/src/bondy_wamp_message.erl
God Classes · TooManyFunctions: bondy_mail_worker apps/bondy_mail/src/bondy_mail_worker.erl
God Classes · FileTooLong: src/bondy_auth.erl apps/bondy_router/src/bondy_auth.erl
God Classes · FileTooLong: src/mops.erl apps/mops/src/mops.erl
God Classes · TooManyFunctions: bondy_aae_reactor apps/bondy_router/src/bondy_aae_reactor.erl
God Classes · TooManyFunctions: bondy_wamp_api_utils apps/bondy_router/src/bondy_wamp_api_utils.erl
God Classes · FileTooLong: src/bondy_oplog_registry.erl apps/bondy_oplog/src/bondy_oplog_registry.erl
God Classes · TooManyFunctions: bondy_metrics apps/bondy_metrics/src/bondy_metrics.erl
God Classes · TooManyFunctions: bondy_registry_partition apps/bondy_router/src/bondy_registry_partition.erl
God Classes · FileTooLong: src/bondy_broker.erl apps/bondy_router/src/bondy_broker.erl
God Classes · FileTooLong: src/bondy_mcp_upstream.erl apps/bondy_mcp/src/bondy_mcp_upstream.erl
God Classes · TooManyFunctions: bondy_mst_pack_index apps/bondy_mst/src/bondy_mst_pack_index.erl
God Classes · TooManyFunctions: bondy_oplog_origin_bans apps/bondy_oplog/src/bondy_oplog_origin_bans.erl
God Classes · TooManyFunctions: bondy_alarm_api apps/bondy_router/src/bondy_alarm_api.erl
God Classes · TooManyFunctions: bondy_cert_manager apps/bondy_router/src/bondy_cert_manager.erl
God Classes · FileTooLong: src/bondy_wamp_tcp_connection_handler.erl apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl
God Classes · FileTooLong: src/bondy_namespace_catalog.erl apps/bondy_router/src/bondy_namespace_catalog.erl
God Classes · TooManyFunctions: bondy_router_utils apps/bondy_router/src/bondy_router_utils.erl
God Classes · TooManyFunctions: bondy_telemetry apps/bondy_router/src/bondy_telemetry.erl
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 8 findings
These 8 critical or serious findings were in the previous survey, on 30 October 2026, and are gone from this one.
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java
€110,000 to €530,000, for 1,754 to 5,564 hours of work, about 2.2 person-years for 1 to 5 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 42. 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: 195,410 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 4 points · Medium effort · Type Safety
3
Act on each finding's own remediation rather than one rule: the move depends on what recurs.
Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
Raises the score by about 4 points · Medium effort · Code Duplication
Diagnosis: what the measurements show together
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 €320,000 to build again, about 2.2 person-years of work. Its weakest lens is Code Health, at 21 (Critical). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 3 REDACTED Scanning 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.
At a glance — Code Health · 21% · Critical · gated by R1, R10, R7, X5 ·
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
A05:2025 — Injection
28
High / Critical
A02:2025 — Security Misconfiguration
23
High / Critical
A03:2025 — Software Supply Chain Failures
12
High / Critical
A01:2025 — Broken Access Control
9
Medium
A07:2025 — Authentication Failures
6
High / Critical
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED; Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Bring the 14 bodies over 15 down to 15 or less in Cognitive Complexity — start with bondy_oplog_instance.do_handle_call (cognitive 47), bondy_prometheus_db.collect_leveled (cognitive 41), bondy_rbac_api.handle_call (cognitive 35).
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 — 41
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 — 727
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 — 36
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 16
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 60 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 60 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, 784 of 804 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.erl) 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.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.erl) and this repository declares a rebar3 project (repository root, 340 test files, 169 Common Test suites), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a rebar.config / erlang.mk DEPS (Hex), but the licence verdict published here was taken over its Hex package dependencies. Nothing was read about its Rebar dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (9 contributor(s) across 3830 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 8 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen.app.src), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container bondy-grafana exited (1); runtime evidence skipped.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Erlang, Java, Python, clojure is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Erlang, Python, clojure is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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, got, undici, node:http; 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.
X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
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.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
25 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was bondy_oplog_instance.do_handle_call at 118. A further 32 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being bondy_connect_error.entry at 109 — they are counted neither in the figure above nor in this dimension's score. 19 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: apps/bondy_router/src/bondy_wamp_api.erl (bondy_wamp_api.resolve at 47), apps/bondy_mail/src/bondy_mail.erl (bondy_mail.to_error at 32), apps/bondy_oplog/src/bondy_oplog_applier.erl (bondy_oplog_applier.handle_call at 28), apps/bondy_router/src/bondy_oauth2_api.erl (bondy_oauth2_api.handle_call at 27), apps/bondy_broker_bridge/src/bondy_kafka_bridge.erl (bondy_kafka_bridge.validate_action at 26), and 14 more not listed here. 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.
+ 19 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with bondy_oplog_instance.do_handle_call (cyclomatic 118), bondy_rbac_api.handle_call (cyclomatic 95), bondy_prometheus_db.do_handle_event (cyclomatic 74). — 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 4 together lifts Cyclomatic Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 14 bodies over 15 down to 15 or less in Cognitive Complexity — start with bondy_oplog_instance.do_handle_call (cognitive 47), bondy_prometheus_db.collect_leveled (cognitive 41), bondy_rbac_api.handle_call (cognitive 35). — 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 14 together lifts Cognitive Complexity from 7.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 56 FileTooLong finding(s) in God Classes — start with bondy_oplog_instance.erl, bondy_db.erl, bondy_dealer.erl. — One of this dimension's main actionable groups (56 warning-level).
Resolve the 30 TooManyFunctions finding(s) in God Classes — start with bondy_oplog_config.erl, bondy_oplog.erl, bondy_http_gateway.erl. — One of this dimension's main actionable groups (30 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
175 duplicated block group(s) detected. 5.5 % of the production lines (10,746 of 195,410) are in a reported copy. A further 277 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 10 of the 452 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.
Edited copy of a member (10 corresponding lines) · ×18apps/bondy_oplog/src/bondy_oplog_applier.erl:2855
Edited copy of a member (11 corresponding lines) · ×17apps/bondy_router/src/bondy_registry_ptrie.erl:988
Edited copy of a member (4 corresponding lines) · ×17apps/bondy_oplog/src/bondy_oplog_crdt_max_register.erl:94
+ 137 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 18 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with bondy_connect_connection.erl (2), bondy_oplog_instance.erl (2), bondy_oplog_applier.erl. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 17 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with bondy_relation.erl (2), bondy_oplog_origin.erl (2), bondy_registry_ptrie.erl. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 17 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with bondy_oplog_crdt_max_register.erl (3), bondy_aae_reactor.erl (2), bondy_oplog_core_dispatcher.erl. — One of this dimension's main actionable groups (17 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.6 / 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.
21 production modules (OTP), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 5 module(s) off the main sequence, with abstractness counted on 17 of the 21 (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: bondy_cluster · ×5
Unstable project bondy_oplog
What to do
Resolve the 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Unstable project bondy_oplog finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
3 outdated, 0 retired direct Hex dependencies, 0 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 mix.lock there.
Outdated: benchee · ×3
✓ On the Gold path — maintain.
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.
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 8 shipped Hex package(s) use a banned license. Licences were resolved from hex.pm over the packages a consumer installs — this repository's mix.lock closed over the declarations its mix.exs files do not gate behind `only:`. Packages it asks for ONLY under `only: [:dev, :test]` (or any other non-prod environment, such as `:docs`) are excluded: they are not installed by anything that depends on this repository. Each licence is the one hex.pm publishes for the package's current release. ★ COVERAGE OF THIS VERDICT: it grades this repository's Hex package dependencies and nothing else. The repository also declares a rebar.config / erlang.mk DEPS (Hex), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with bondy_rbac_api.erl. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
86 deducted task-comment markers across 195410 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 85 TodoComment finding(s) in Explicit Debt — start with bondy_http_gateway_rest_handler.erl (14), bondy_realm.erl (10), REDACTED (3). — One of this dimension's main actionable groups (85 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with bondy_router_peer.erl. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 71 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.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: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with fly.toml. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
0 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
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.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
28 finding(s): 0 critical, 28 high, 0 medium, 0 low. 19 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 3 file(s) — `harness/fleet-scale/run-fleet-lg.sh` (line 137), `harness/m0-fly-spike/probe.sh` (line 51), `harness/m0-fly-spike/run-spike.sh` (line 86) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 19 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (19 issue-level, 0 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 `REDACTED` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 17 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (10), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (17 warning-level).
Resolve the 4 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)3.9 / 10Weak✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
Resolve the 9 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (3), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d32_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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 454 of the 546 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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 2 Change coupling finding(s) in Change Coupling — start with bondy_auth_password.erl, bondy_oauth2_client.erl. — One of this dimension's main actionable groups (2 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.
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — 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 recommendation-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. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. 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.
`bondy_connect_table_manager` has a `handle_call` query clause that reads a store and, on the not-found (cache-miss) branch, WRITES it — a get-or-create that mutates as a side effect of a read. A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the lazy-init write into a command. (×3) — apps/bondy_connect_lib/src/bondy_connect_table_manager.erl:268, apps/bondy_connect_lib/src/bondy_connect_table_manager.erl:280, apps/bondy_connect_lib/src/bondy_connect_table_manager.erl:291
What to do
Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
Other · Event Sourcing — Whether the event-sourcing replay fold reconstructs state purely from the event (no wall clock, UUID or randomness) so replay is reproducible.
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.
`bondy_oplog_instance`'s event-replay reducer reads a wall clock / randomness / a peer process / persistence while reconstructing aggregate state — replaying the same events would rebuild DIFFERENT state each run. A fold must be a pure function of (state, event); stamp the timestamp/id into the event at raise-time and read it back in the fold. — apps/bondy_oplog/src/bondy_oplog_instance.erl:3313
What to do
Keep the event-replay reducer pure — move every clock/UUID/random into the event at raise-time and read it back in the fold.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
apps/bondy_mst/README.md links to `reference/`, but `apps/bondy_mst/reference` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — apps/bondy_mst/README.md:372
What to do
Reconcile the README with reality: apps/bondy_mst/README.md links to `reference/`, but `apps/bondy_mst/reference` does not exist.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
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.
What to do
Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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.
`apps/bondy_mcp/test/bondy_mcp_e2e_SUITE_data/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — apps/bondy_mcp/test/bondy_mcp_e2e_SUITE_data/package.json:6
What to do
Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
Enable Dependabot/Renovate or a dependency-review gate.
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.
Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — apps/bondy_broker_bridge/src/channel_handler/email_adapter_mailgun2.erl:124, apps/bondy_broker_bridge/src/channel_handler/email_adapter_sendgrid.erl:144
`hackney:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — apps/bondy_http_connector/src/bondy_http_connector_auth_generic.erl:177, apps/bondy_http_connector/src/bondy_http_connector_http_pool.erl:188, apps/bondy_http_connector/src/bondy_http_connector_http_pool.erl:420
What to do
Pass an explicit bound on every request — `{timeout, Ms}` in `httpc:request/4`'s HTTP options (its default is `infinity`), `{recv_timeout, Ms}` for hackney, a timeout on `gun:await/3` — and wrap dependencies that fail in a breaker (`fuse`) with back-off (`backoff`).
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 6 plain JS — the untyped files are apps/bondy_mcp/test/bondy_mcp_e2e_SUITE_data/handshake_client.mjs, apps/bondy_mcp/test/bondy_mcp_e2e_SUITE_data/modern_client.mjs, harness/k6/fleet_smoke.js, harness/k6/lib/wamp.js, harness/k6/pubsub_smoke.js, harness/k6/rpc_smoke.js.
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
harness/k6/pubsub_smoke.js:33 · harness/k6/rpc_smoke.js:20 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — harness/k6/pubsub_smoke.js:33
harness/k6/fleet_smoke.js:191 · harness/k6/fleet_smoke.js:267 — the two spans are one implementation copied and then locally edited — 458 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — harness/k6/fleet_smoke.js:191
harness/k6/pubsub_smoke.js:101 · harness/k6/rpc_smoke.js:95 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — harness/k6/pubsub_smoke.js:101
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 18 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — harness/k6/fleet_smoke.js:273
(anonymous) has cyclomatic complexity 12 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — harness/k6/rpc_smoke.js:70
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling3.3 / 10Weak✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✗ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add a test runner (vitest / jest / playwright) and eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
2 file(s) (~137 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — apps/bondy_mcp/test/bondy_mcp_e2e_SUITE_data
Unreachable from the 1 application, 0 tooling and 2 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
no import path from any entry point (1 application, 0 tooling, 2 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — harness/k6/fleet_smoke.js, harness/k6/rpc_smoke.js
Nothing imports this binding — it is safe to review for removal. — harness/k6/lib/wamp.js:21
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in apps/bondy_mcp/test/bondy_mcp_e2e_SUITE_data/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
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 an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` 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. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.
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.
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.
`catch error:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×7) — apps/bondy_router/src/bondy_data_validators.erl:315, apps/bondy_router/src/bondy_data_validators.erl:344, apps/bondy_mail/src/bondy_mail_request.erl:675, …
Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/2 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Do you agree with this assessment?
Reference — by lens
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 — 2 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 — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X31 Test-only surface in a production module — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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.
Not included — 66 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.
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; this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container bondy-grafana exited (1); 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 — ~174456 lines of test source are present (.erl) 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 .erl suite was found but not re-run
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — N/A — too few peers to establish a naming convention (27614 declarations, no unit with a dominant convention).
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (203 value object(s))
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES2 Immutable events — not applicable — the code was read and holds no persisted event, so there is nothing for this check to judge
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'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: Elixir and Erlang has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 2 test file(s) reach none of 4 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 1% of this repository's production lines — erlang (182,440 lines), elixir (3,141 lines), clojure (1,294 lines), java (847 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — erlang (182,440 lines), elixir (3,141 lines), clojure (1,294 lines), python (406 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
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.
AX9 · CQS / query purity· Query handler writes persistent state on the read path · ×3
Query handler writes persistent state on the read path: bondy_connect_table_manager apps/bondy_connect_lib/src/bondy_connect_table_manager.erl:268— `bondy_connect_table_manager` has a `handle_call` query clause that reads a store and, on the not-found (cache-miss) branch, WRITES it — a get-or-create that mutates as a side effect of a read. A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the lazy-init write into a command.
Query handler writes persistent state on the read path: bondy_connect_table_manager apps/bondy_connect_lib/src/bondy_connect_table_manager.erl:280— `bondy_connect_table_manager` has a `handle_call` query clause that reads a store and, on the not-found (cache-miss) branch, WRITES it — a get-or-create that mutates as a side effect of a read. A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the lazy-init write into a command.
Query handler writes persistent state on the read path: bondy_connect_table_manager apps/bondy_connect_lib/src/bondy_connect_table_manager.erl:291— `bondy_connect_table_manager` has a `handle_call` query clause that reads a store and, on the not-found (cache-miss) branch, WRITES it — a get-or-create that mutates as a side effect of a read. A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the lazy-init write into a command.
Nondeterministic fold: bondy_oplog_instance apps/bondy_oplog/src/bondy_oplog_instance.erl:3313— `bondy_oplog_instance`'s event-replay reducer reads a wall clock / randomness / a peer process / persistence while reconstructing aggregate state — replaying the same events would rebuild DIFFERENT state each run. A fold must be a pure function of (state, event); stamp the timestamp/id into the event at raise-time and read it back in the fold.
TodoComment apps/bondy_wamp/src/bondy_wamp_cbor.erl:180— %% 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 apps/bondy_wamp/src/bondy_wamp_json.erl:216— %% 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 apps/bondy_router/src/bondy_auth_wamp_cryptosign.erl:88— %% 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 apps/bondy_router/src/bondy_auth_wamp_scram.erl:263— %% 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 apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:149— %% 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 apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:331— %% 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 REDACTED:497— %% 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 apps/bondy_mst/test/bondy_mst_leveled_store.erl:148— %% 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 apps/bondy_wamp/src/bondy_wamp_encoding.erl:557— %% TODO using bondy_wamp_cbor? — 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 apps/bondy_router/src/bondy_auth.erl:52— %% TODO change to — 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 apps/bondy_router/src/bondy_auth_wamp_scram.erl:46— %% TODO Fix this we should carry on with the challenge — 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 apps/bondy_router/src/bondy_bridge_relay_client.erl:1164— %% TODO join all realms — 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 apps/bondy_router/src/bondy_bridge_relay_client.erl:1179— %% TODO HELLO should include the Bondy Router Bridge Relay protocol — 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 apps/bondy_router/src/bondy_bridge_relay_manager.erl:493— %% TODO monitor pids and add them to 'started' — 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 apps/bondy_router/src/bondy_bridge_relay_server.erl:515— %% TODO forward_message or forward? — 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 apps/bondy_router/src/bondy_bridge_relay_server.erl:640— %% TODO take it from conf — 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 apps/bondy_router/src/bondy_bridge_relay_server.erl:1001— %% TODO we should spawn an exchange statem 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 apps/bondy_router/src/bondy_broker.erl:887— %% TODO disclose info only if feature is announced by Publishers, Brokers — 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 apps/bondy_router/src/bondy_broker.erl:922— %% TODO Validate if we need ack enabled — 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 apps/bondy_router/src/bondy_cache.erl:17— %% TODO Evict all caches for Session, User, Client and Realm once any of them are deleted — 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 apps/bondy_router/src/bondy_dealer.erl:1668— %% TODO instead of dequeuing, update the entry to reflect it was — 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 apps/bondy_router/src/bondy_dealer.erl:1784— %% TODO Shouldn't we restrict this operation to the peer who registered it? — 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 apps/bondy_router/src/bondy_dealer.erl:2915— %% TODO disclose info only if feature is announced by Callee, Dealer — 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 apps/bondy_router/src/bondy_event_wamp_publisher.erl:328— %% TODO Refresh any sessions' rbac_ctxt caches this user has in — 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 apps/bondy_router/src/bondy_http_gateway_api_spec_parser.erl:1811— %% TODO for other types — 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.
FileTooLong: src/bondy_oplog_instance.erl apps/bondy_oplog/src/bondy_oplog_instance.erl— FileTooLong — 4366 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 315 functions. The bar is 500 significant lines; this is 3866 over it, 8.73× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_db.erl apps/bondy_db/src/bondy_db.erl— FileTooLong — 2394 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 168 functions. The bar is 500 significant lines; this is 1894 over it, 4.79× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_dealer.erl apps/bondy_router/src/bondy_dealer.erl— FileTooLong — 2080 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 109 functions. The bar is 500 significant lines; this is 1580 over it, 4.16× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_realm.erl apps/bondy_router/src/bondy_realm.erl— FileTooLong — 2036 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 131 functions. The bar is 500 significant lines; this is 1536 over it, 4.07× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_oplog_applier.erl apps/bondy_oplog/src/bondy_oplog_applier.erl— FileTooLong — 1760 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 132 functions. The bar is 500 significant lines; this is 1260 over it, 3.52× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_log_wal.erl apps/bondy_log/src/bondy_log_wal.erl— FileTooLong — 1748 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 125 functions. The bar is 500 significant lines; this is 1248 over it, 3.50× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_connect_error.erl apps/bondy_connect_lib/src/bondy_connect_error.erl— FileTooLong — 1687 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 54 functions. The bar is 500 significant lines; this is 1187 over it, 3.37× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_mst.erl apps/bondy_mst/src/bondy_mst.erl— FileTooLong — 1606 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 123 functions. The bar is 500 significant lines; this is 1106 over it, 3.21× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_registry_store.erl apps/bondy_router/src/bondy_registry_store.erl— FileTooLong — 1472 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 92 functions. The bar is 500 significant lines; this is 972 over it, 2.94× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_connect_connection.erl apps/bondy_connect_sdk/src/bondy_connect_connection.erl— FileTooLong — 1406 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 120 functions. The bar is 500 significant lines; this is 906 over it, 2.81× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_prometheus_db.erl apps/bondy_telemetry_exporter/src/bondy_prometheus_db.erl— FileTooLong — 1373 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 60 functions. The bar is 500 significant lines; this is 873 over it, 2.75× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_rbac_user.erl apps/bondy_router/src/bondy_rbac_user.erl— FileTooLong — 1359 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 116 functions. The bar is 500 significant lines; this is 859 over it, 2.72× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: include/bondy_wamp.hrl apps/bondy_wamp/include/bondy_wamp.hrl— FileTooLong — 1217 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 717 over it, 2.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/bondy_mcp_http_handler.erl apps/bondy_mcp/src/bondy_mcp_http_handler.erl— FileTooLong — 1176 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 46 functions. The bar is 500 significant lines; this is 676 over it, 2.35× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_http_gateway_rest_handler.erl apps/bondy_router/src/bondy_http_gateway_rest_handler.erl— FileTooLong — 1107 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 68 functions. The bar is 500 significant lines; this is 607 over it, 2.21× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_mst_pack_store.erl apps/bondy_mst/src/bondy_mst_pack_store.erl— FileTooLong — 1071 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 83 functions. The bar is 500 significant lines; this is 571 over it, 2.14× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_wamp_protocol.erl apps/bondy_router/src/bondy_wamp_protocol.erl— FileTooLong — 1028 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 39 functions. The bar is 500 significant lines; this is 528 over it, 2.06× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_rbac.erl apps/bondy_router/src/bondy_rbac.erl— FileTooLong — 1007 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 75 functions. The bar is 500 significant lines; this is 507 over it, 2.01× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_mst_pack_writer.erl apps/bondy_mst/src/bondy_mst_pack_writer.erl— FileTooLong — 986 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 75 functions. The bar is 500 significant lines; this is 486 over it, 1.97× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_oplog_cell_apply.erl apps/bondy_oplog/src/bondy_oplog_cell_apply.erl— FileTooLong — 980 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 64 functions. The bar is 500 significant lines; this is 480 over it, 1.96× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_bridge_relay_client.erl apps/bondy_router/src/bondy_bridge_relay_client.erl— FileTooLong — 955 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 54 functions. The bar is 500 significant lines; this is 455 over it, 1.91× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_oplog_core.erl apps/bondy_oplog/src/bondy_oplog_core.erl— FileTooLong — 951 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 73 functions. The bar is 500 significant lines; this is 451 over it, 1.90× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_registry_ptrie.erl apps/bondy_router/src/bondy_registry_ptrie.erl— FileTooLong — 933 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 71 functions. The bar is 500 significant lines; this is 433 over it, 1.87× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_prometheus.erl apps/bondy_telemetry_exporter/src/bondy_prometheus.erl— FileTooLong — 925 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 425 over it, 1.85× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
FileTooLong: src/bondy_log_recovery.erl apps/bondy_log/src/bondy_log_recovery.erl— FileTooLong — 924 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 63 functions. The bar is 500 significant lines; this is 424 over it, 1.85× the bar. In this language a module is exactly one source file, so its length cannot be moved into sibling files of the same module. 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 one module has to be read whole to change one of them.
TooManyFunctions: bondy_oplog_config apps/bondy_oplog/src/bondy_oplog_config.erl:6— TooManyFunctions — 52 functions. The bar is 30 functions; this is 22 over it, 1.73× 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: bondy_oplog apps/bondy_oplog/src/bondy_oplog.erl:6— TooManyFunctions — 48 functions. The bar is 30 functions; this is 18 over it, 1.60× 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: bondy_http_gateway apps/bondy_router/src/bondy_http_gateway.erl:6— TooManyFunctions — 46 functions. The bar is 30 functions; this is 16 over it, 1.53× 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: bondy_connect_interval_set apps/bondy_connect_lib/src/bondy_connect_interval_set.erl:6— TooManyFunctions — 45 functions. The bar is 30 functions; this is 15 over it, 1.50× 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: bondy_context apps/bondy_router/src/bondy_context.erl:6— TooManyFunctions — 45 functions. The bar is 30 functions; this is 15 over it, 1.50× 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: bondy_mail_worker apps/bondy_mail/src/bondy_mail_worker.erl:6— TooManyFunctions — 41 functions. The bar is 30 functions; this is 11 over it, 1.37× 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: bondy_aae_reactor apps/bondy_router/src/bondy_aae_reactor.erl:6— TooManyFunctions — 38 functions. The bar is 30 functions; this is 8 over it, 1.27× 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: bondy_wamp_api_utils apps/bondy_router/src/bondy_wamp_api_utils.erl:6— TooManyFunctions — 38 functions. The bar is 30 functions; this is 8 over it, 1.27× 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: bondy_metrics apps/bondy_metrics/src/bondy_metrics.erl:6— TooManyFunctions — 37 functions. The bar is 30 functions; this is 7 over it, 1.23× 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: bondy_registry_partition apps/bondy_router/src/bondy_registry_partition.erl:6— TooManyFunctions — 37 functions. The bar is 30 functions; this is 7 over it, 1.23× 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: bondy_mst_pack_index apps/bondy_mst/src/bondy_mst_pack_index.erl:6— 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: bondy_oplog_origin_bans apps/bondy_oplog/src/bondy_oplog_origin_bans.erl:6— 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: bondy_alarm_api apps/bondy_router/src/bondy_alarm_api.erl:6— 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: bondy_cert_manager apps/bondy_router/src/bondy_cert_manager.erl:6— 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: bondy_router_utils apps/bondy_router/src/bondy_router_utils.erl:6— TooManyFunctions — 35 functions. The bar is 30 functions; this is 5 over it, 1.17× 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: bondy_telemetry apps/bondy_router/src/bondy_telemetry.erl:6— TooManyFunctions — 35 functions. The bar is 30 functions; this is 5 over it, 1.17× 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: bondy_wamp_cbor apps/bondy_wamp/src/bondy_wamp_cbor.erl:6— TooManyFunctions — 35 functions. The bar is 30 functions; this is 5 over it, 1.17× 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: bondy_mail_request apps/bondy_mail/src/bondy_mail_request.erl:6— TooManyFunctions — 34 functions. The bar is 30 functions; this is 4 over it, 1.13× 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: bondy_ref apps/bondy_router/src/bondy_ref.erl:6— TooManyFunctions — 34 functions. The bar is 30 functions; this is 4 over it, 1.13× 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: bondy_retained_message_manager apps/bondy_router/src/bondy_retained_message_manager.erl:6— TooManyFunctions — 34 functions. The bar is 30 functions; this is 4 over it, 1.13× 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: bondy_alarm_handler apps/bondy_router/src/bondy_alarm_handler.erl:6— TooManyFunctions — 33 functions. The bar is 30 functions; this is 3 over it, 1.10× 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: bondy_bridge_relay_manager apps/bondy_router/src/bondy_bridge_relay_manager.erl:6— TooManyFunctions — 33 functions. The bar is 30 functions; this is 3 over it, 1.10× 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: bondy_connect_client apps/bondy_connect_sdk/src/bondy_connect_client.erl:6— TooManyFunctions — 32 functions. The bar is 30 functions; this is 2 over it, 1.07× 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: bondy_connect_transport_longpoll apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:6— TooManyFunctions — 32 functions. The bar is 30 functions; this is 2 over it, 1.07× 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: bondy_mcp_wamp apps/bondy_mcp/src/bondy_mcp_wamp.erl:6— TooManyFunctions — 32 functions. The bar is 30 functions; this is 2 over it, 1.07× 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.
+ 5 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×18
Edited copy of a member (10 corresponding lines) apps/bondy_oplog/src/bondy_oplog_applier.erl:2855— apps/bondy_oplog/src/bondy_oplog_applier.erl:2855-2864 | apps/bondy_oplog/src/bondy_oplog_instance.erl:4037-4057 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_db/src/bondy_db.erl:3718— apps/bondy_db/src/bondy_db.erl:3718-3727 | apps/bondy_db/src/bondy_db.erl:3733-3745 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:1100— apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:1100-1111 | apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:1630-1639 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_router/src/bondy_router_utils.erl:447— apps/bondy_router/src/bondy_router_utils.erl:447-456 | apps/bondy_router/src/bondy_router_utils.erl:459-469 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_router/src/bondy_namespace_catalog.erl:976— apps/bondy_router/src/bondy_namespace_catalog.erl:976-985 | apps/bondy_router/src/bondy_namespace_catalog.erl:993-1003 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_router/src/bondy_rbac.erl:601— apps/bondy_router/src/bondy_rbac.erl:601-611 | apps/bondy_router/src/bondy_rbac.erl:626-635 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1159— apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1159-1168 | apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1171-1180 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_mcp/src/bondy_mcp_http_handler.erl:841— apps/bondy_mcp/src/bondy_mcp_http_handler.erl:841-852 | apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1257-1266 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_wamp/src/bondy_wamp_cbor.erl:531— apps/bondy_wamp/src/bondy_wamp_cbor.erl:531-540 | apps/bondy_wamp/src/bondy_wamp_cbor.erl:543-552 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:192— apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:192-201 | apps/bondy_oplog/src/bondy_oplog_crdt_pn_counter.erl:198-209 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_router/src/bondy_oauth_refresh_token.erl:43— apps/bondy_router/src/bondy_oauth_refresh_token.erl:43-52 | apps/bondy_router/src/bondy_oauth_refresh_token.erl:60-70 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_oplog/src/bondy_oplog_instance.erl:1222— apps/bondy_oplog/src/bondy_oplog_instance.erl:1222-1231 | apps/bondy_oplog/src/bondy_oplog_instance.erl:1240-1257 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1183— apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1183-1192 | apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1195-1208 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_router/src/bondy_registry.erl:628— apps/bondy_router/src/bondy_registry.erl:628-637 | apps/bondy_router/src/bondy_registry_partition.erl:500-509 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_router/src/bondy_registry_ptrie.erl:1544— apps/bondy_router/src/bondy_registry_ptrie.erl:1544-1553 | apps/bondy_router/src/bondy_registry_ptrie.erl:1564-1573 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_oplog/src/bondy_oplog_instance.erl:5219— apps/bondy_oplog/src/bondy_oplog_instance.erl:5219-5228 | apps/bondy_oplog/src/bondy_oplog_instance.erl:5274-5283 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:1018— apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:1018-1034 | apps/bondy_oplog/src/bondy_oplog_instance.erl:2879-2888 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) apps/bondy_oplog/src/bondy_oplog_peer_state.erl:331— apps/bondy_oplog/src/bondy_oplog_peer_state.erl:331-343 | apps/bondy_oplog/src/bondy_oplog_quarantine.erl:189-198 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×17
Edited copy of a member (11 corresponding lines) apps/bondy_router/src/bondy_registry_ptrie.erl:988— apps/bondy_router/src/bondy_registry_ptrie.erl:988-998 | apps/bondy_router/src/bondy_registry_ptrie.erl:1155-1165 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_registry.erl:84— apps/bondy_connect_sdk/src/bondy_connect_registry.erl:84-94 | apps/bondy_connect_sdk/src/bondy_connect_registry.erl:98-108 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_db/src/bondy_db.erl:1509— apps/bondy_db/src/bondy_db.erl:1509-1519 | apps/bondy_db/src/bondy_db.erl:1533-1545 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_db/src/bondy_relation.erl:363— apps/bondy_db/src/bondy_relation.erl:363-373 | apps/bondy_db/src/bondy_relation.erl:459-469 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_mst/src/bondy_mst_ets_store.erl:266— apps/bondy_mst/src/bondy_mst_ets_store.erl:266-276 | apps/bondy_mst/src/bondy_mst_map_store.erl:182-192 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_mcp/src/bondy_mcp_upstream.erl:748— apps/bondy_http_connector/src/bondy_http_connector_http_pool.erl:616-632 | apps/bondy_mcp/src/bondy_mcp_upstream.erl:748-758 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_log/src/bondy_log_recovery.erl:816— apps/bondy_log/src/bondy_log_recovery.erl:816-826 | apps/bondy_log/src/bondy_log_recovery.erl:829-841 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_log/src/bondy_log_reader.erl:468— apps/bondy_log/src/bondy_log_reader.erl:468-478 | apps/bondy_log/src/bondy_log_reader.erl:532-543 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_mst/src/bondy_mst.erl:1343— apps/bondy_mst/src/bondy_mst.erl:1343-1353 | apps/bondy_mst/src/bondy_mst.erl:1416-1426 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_db/src/bondy_relation.erl:396— apps/bondy_db/src/bondy_relation.erl:396-406 | apps/bondy_db/src/bondy_relation.erl:475-485 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_oplog/src/bondy_oplog_origin.erl:118— apps/bondy_oplog/src/bondy_oplog_origin.erl:118-131 | apps/bondy_oplog/src/bondy_oplog_origin_bans.erl:633-643 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_router/src/bondy_bridge_relay_manager.erl:93— apps/bondy_router/src/bondy_bridge_relay_manager.erl:93-103 | apps/bondy_router/src/bondy_bridge_relay_manager.erl:120-131 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_oplog/src/bondy_oplog_sync_session.erl:214— apps/bondy_oplog/src/bondy_oplog_sync_session.erl:214-224 | apps/bondy_oplog/src/bondy_oplog_sync_session.erl:673-688 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_oplog/src/bondy_oplog_origin.erl:169— apps/bondy_oplog/src/bondy_oplog_origin.erl:169-179 | apps/bondy_oplog/src/bondy_oplog_origin_bans.erl:708-718 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_connect_lib/src/bondy_connect_error.erl:833— apps/bondy_connect_lib/src/bondy_connect_error.erl:833-843 | apps/bondy_router/src/bondy_oauth_refresh_token.erl:168-179 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_oplog/src/bondy_oplog_instance.erl:5493— apps/bondy_oplog/src/bondy_oplog_instance.erl:5493-5507 | apps/bondy_oplog/src/bondy_oplog_high_water.erl:112-122 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) apps/bondy_mcp/src/bondy_mcp_gateway.erl:386— apps/bondy_mcp/src/bondy_mcp_gateway.erl:386-396 | apps/bondy_mcp/src/bondy_mcp_handshake.erl:700-712 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×17
Edited copy of a member (4 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_max_register.erl:94— apps/bondy_oplog/src/bondy_oplog_crdt_max_register.erl:94-97 | apps/bondy_oplog/src/bondy_oplog_crdt_min_register.erl:95-98 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_oplog/src/bondy_oplog_core_dispatcher.erl:231— apps/bondy_oplog/src/bondy_oplog_core_dispatcher.erl:231-234 | apps/bondy_oplog/src/bondy_oplog_core_dispatcher.erl:240-251 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_router/src/bondy_observer_cli_cluster.erl:182— apps/bondy_router/src/bondy_observer_cli_cluster.erl:182-185 | apps/bondy_router/src/bondy_observer_cli_sync.erl:359-362 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_router/src/bondy_password_scram.erl:188— apps/bondy_router/src/bondy_password_scram.erl:188-191 | apps/bondy_wamp/src/bondy_wamp_cra.erl:217-220 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_max_register.erl:139— apps/bondy_oplog/src/bondy_oplog_crdt_max_register.erl:139-142 | apps/bondy_oplog/src/bondy_oplog_crdt_min_register.erl:140-143 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_router/src/bondy_dealer.erl:504— apps/bondy_router/src/bondy_dealer.erl:504-508 | apps/bondy_router/src/bondy_registry.erl:196-199 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_router/src/bondy_event_manager.erl:146— apps/bondy_router/src/bondy_event_manager.erl:146-149 | apps/bondy_router/src/bondy_wamp_event_manager.erl:74-77 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_router/src/bondy_oauth_token.erl:1366— apps/bondy_router/src/bondy_oauth_token.erl:1366-1369 | apps/bondy_router/src/bondy_ticket.erl:1247-1250 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_max_register.erl:146— apps/bondy_oplog/src/bondy_oplog_crdt_max_register.erl:146-149 | apps/bondy_oplog/src/bondy_oplog_crdt_min_register.erl:147-150 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_router/src/bondy_admin_cluster_topology_http_handler.erl:21— apps/bondy_router/src/bondy_admin_cluster_topology_http_handler.erl:21-24 | apps/bondy_router/src/bondy_http_verify_handler.erl:127-130 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_telemetry_exporter/src/bondy_prometheus_collector.erl:385— apps/bondy_telemetry_exporter/src/bondy_prometheus_collector.erl:385-388 | apps/bondy_telemetry_exporter/src/bondy_prometheus_db.erl:1829-1834 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:524— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:524-527 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:455-458 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_oplog/src/bondy_oplog_applier.erl:2926— apps/bondy_oplog/src/bondy_oplog_applier.erl:2926-2931 | apps/bondy_oplog/src/bondy_oplog_instance.erl:4060-4063 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_router/src/bondy_aae_reactor.erl:543— apps/bondy_router/src/bondy_aae_reactor.erl:543-546 | apps/bondy_router/src/bondy_rbac_user.erl:1844-1847 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_router/src/bondy_aae_reactor.erl:549— apps/bondy_router/src/bondy_aae_reactor.erl:549-552 | apps/bondy_router/src/bondy_rbac_user.erl:1850-1853 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_router/src/bondy_rbac_group.erl:659— apps/bondy_router/src/bondy_rbac_group.erl:659-662 | apps/bondy_router/src/bondy_rbac_user.erl:1360-1363 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) apps/bondy_oplog/src/bondy_oplog_core_metrics.erl:269— apps/bondy_oplog/src/bondy_oplog_core_metrics.erl:269-272 | apps/bondy_oplog/src/bondy_oplog_latency.erl:263-266 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (6 lines × 2) apps/bondy_mst/src/bondy_mst.erl:1587— apps/bondy_mst/src/bondy_mst.erl:1587-1592 | apps/bondy_mst/src/bondy_mst.erl:1605-1610 — 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) apps/bondy_mst/src/bondy_mst.erl:2477— apps/bondy_mst/src/bondy_mst.erl:2477-2482 | apps/bondy_mst/src/bondy_mst.erl:2492-2497 — 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) apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:488— apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:488-493 | apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl:363-368 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl` and `apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl` as WHOLE FILES: this scan already matched 6 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 × 2) apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:257— apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:257-262 | apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:591-596 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:257` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:589` calls `handle_call` and `apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:255` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) apps/bondy_router/src/bondy_rbac_group.erl:848— apps/bondy_router/src/bondy_rbac_group.erl:848-853 | apps/bondy_router/src/bondy_rbac_user.erl:1940-1945 — before extracting anything, compare `apps/bondy_router/src/bondy_rbac_group.erl` and `apps/bondy_router/src/bondy_rbac_user.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_rbac_group.erl:848` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) apps/bondy_router/src/bondy_rbac_user.erl:1728— apps/bondy_router/src/bondy_rbac_user.erl:1728-1734 | apps/bondy_router/src/bondy_rbac_user.erl:1755-1760 — 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) apps/bondy_oplog/src/bondy_oplog_applier.erl:841— apps/bondy_oplog/src/bondy_oplog_applier.erl:841-846 | apps/bondy_oplog/src/bondy_oplog_instance.erl:1715-1720 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_applier.erl` and `apps/bondy_oplog/src/bondy_oplog_instance.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 71 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) apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:1549— apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:1549-1554 | apps/bondy_oplog/src/bondy_oplog_secondary_writer.erl:655-660 — 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) apps/bondy_oplog/src/bondy_oplog_crdt_rw_map.erl:306— apps/bondy_oplog/src/bondy_oplog_crdt_rw_map.erl:306-311 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_set.erl:229-234 — 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) apps/bondy_router/src/bondy_bridge_relay_client.erl:1006— apps/bondy_router/src/bondy_bridge_relay_client.erl:1006-1011 | apps/bondy_router/src/bondy_bridge_relay_server.erl:1132-1137 — before extracting anything, compare `apps/bondy_router/src/bondy_bridge_relay_client.erl` and `apps/bondy_router/src/bondy_bridge_relay_server.erl` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_bridge_relay_client.erl:1006` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) apps/bondy_router/src/bondy_bridge_relay_client.erl:1014— apps/bondy_router/src/bondy_bridge_relay_client.erl:1014-1019 | apps/bondy_router/src/bondy_bridge_relay_server.erl:1140-1145 — before extracting anything, compare `apps/bondy_router/src/bondy_bridge_relay_client.erl` and `apps/bondy_router/src/bondy_bridge_relay_server.erl` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_bridge_relay_client.erl:1014` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) apps/bondy_router/src/bondy_bridge_relay_client.erl:1071— apps/bondy_router/src/bondy_bridge_relay_client.erl:1071-1076 | apps/bondy_router/src/bondy_bridge_relay_server.erl:1205-1210 — before extracting anything, compare `apps/bondy_router/src/bondy_bridge_relay_client.erl` and `apps/bondy_router/src/bondy_bridge_relay_server.erl` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_bridge_relay_client.erl:1071` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) apps/bondy_router/src/bondy_broker.erl:1076— apps/bondy_router/src/bondy_broker.erl:1076-1081 | apps/bondy_router/src/bondy_dealer.erl:1486-1491 — 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) apps/bondy_router/src/bondy_event_logger.erl:40— apps/bondy_router/src/bondy_event_logger.erl:40-45 | apps/bondy_router/src/bondy_event_wamp_publisher.erl:75-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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_event_logger.erl:40` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) apps/bondy_mst/src/bondy_mst_pack_store.erl:1133— apps/bondy_mst/src/bondy_mst_pack_store.erl:1133-1138 | apps/bondy_mst/src/bondy_mst_pack_writer.erl:1509-1514 — 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) apps/bondy_router/src/bondy_rbac_group.erl:636— apps/bondy_router/src/bondy_rbac_group.erl:636-641 | apps/bondy_router/src/bondy_rbac_user.erl:1333-1338 — before extracting anything, compare `apps/bondy_router/src/bondy_rbac_group.erl` and `apps/bondy_router/src/bondy_rbac_user.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_rbac_group.erl:636` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `apps/bondy_router/src/bondy_rbac_group.erl:633` calls `page`, `stream` and `apps/bondy_router/src/bondy_rbac_user.erl:1332` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) apps/mops/src/mops.erl:592— apps/mops/src/mops.erl:592-597 | apps/mops/src/mops.erl:608-613 — 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) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:173— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:173-179 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:151-157 — before extracting anything, compare `apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl` and `apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 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) apps/bondy_db/src/bondy_db.erl:1993— apps/bondy_db/src/bondy_db.erl:1993-1999 | apps/bondy_db/src/bondy_db.erl:2057-2063 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_db/src/bondy_db.erl:1993` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) apps/bondy_mcp/src/bondy_mcp_wamp_api.erl:100— apps/bondy_mcp/src/bondy_mcp_wamp_api.erl:100-106 | apps/bondy_router/src/bondy_interface_api.erl:56-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_mcp/src/bondy_mcp_wamp_api.erl:100` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) apps/bondy_oplog/src/bondy_oplog_applier.erl:2181— apps/bondy_oplog/src/bondy_oplog_applier.erl:2181-2187 | apps/bondy_oplog/src/bondy_oplog_instance.erl:4224-4230 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_applier.erl` and `apps/bondy_oplog/src/bondy_oplog_instance.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 71 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) apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:542— apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:542-548 | apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:807-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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:542` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) apps/bondy_router/src/bondy_cert_manager_wamp_api.erl:62— apps/bondy_router/src/bondy_cert_manager_wamp_api.erl:62-68 | apps/bondy_router/src/bondy_cert_manager_wamp_api.erl:81-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_cert_manager_wamp_api.erl:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) apps/bondy_oplog/src/bondy_oplog_core_metrics.erl:293— apps/bondy_oplog/src/bondy_oplog_core_metrics.erl:293-299 | apps/bondy_oplog/src/bondy_oplog_latency.erl:303-309 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_core_metrics.erl:293` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:152— apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:152-158 | apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:873-879 — 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) apps/bondy_wamp/src/bondy_wamp_config.erl:44— apps/bondy_http_connector/src/bondy_http_connector_config.erl:53-59 | apps/bondy_wamp/src/bondy_wamp_config.erl:44-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 × 2) apps/bondy_log/src/bondy_log_scrubber.erl:159— apps/bondy_log/src/bondy_log_scrubber.erl:159-165 | apps/bondy_oplog/src/bondy_oplog_applier.erl:513-519 — 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) apps/bondy_mail/src/bondy_mail_status.erl:434— apps/bondy_mail/src/bondy_mail_status.erl:434-440 | apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:170-176 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_mail/src/bondy_mail_status.erl:434` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) apps/bondy_oplog/src/bondy_oplog_crdt_owned_reading.erl:167— apps/bondy_oplog/src/bondy_oplog_crdt_owned_reading.erl:167-173 | apps/bondy_oplog/src/bondy_oplog_crdt_pn_counter.erl:159-165 — 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) apps/bondy_router/src/bondy_http_transport_queue_manager.erl:69— apps/bondy_router/src/bondy_http_transport_queue_manager.erl:69-75 | apps/bondy_router/src/bondy_rpc_promise_manager.erl:54-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_http_transport_queue_manager.erl:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1167— apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1167-1173 | apps/bondy_mcp/src/bondy_mcp_stream.erl:373-379 — 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) apps/bondy_mst/src/bondy_mst.erl:368— apps/bondy_mst/src/bondy_mst.erl:368-374 | apps/bondy_mst/src/bondy_mst_pack_store.erl:344-356 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_mst/src/bondy_mst.erl:368` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) bench/lib/bench/concurrency.ex:177— bench/lib/bench/concurrency.ex:177-183 | bench/lib/bench/e2e.ex:175-181 — before extracting anything, compare `bench/lib/bench/concurrency.ex` and `bench/lib/bench/e2e.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bench/lib/bench/concurrency.ex:177` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×14
Edited copy of a member (12 corresponding lines) apps/bondy_wamp/src/bondy_wamp_encoding.erl:47— apps/bondy_wamp/src/bondy_wamp_encoding.erl:47-58 | apps/bondy_wamp/src/bondy_wamp_encoding.erl:63-74 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_oplog/src/bondy_oplog_core.erl:199— apps/bondy_oplog/src/bondy_oplog_core.erl:199-212 | apps/bondy_oplog/src/bondy_oplog_core.erl:387-398 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_router/src/bondy_realm.erl:1458— apps/bondy_router/src/bondy_realm.erl:1458-1470 | apps/bondy_router/src/bondy_realm.erl:1483-1494 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_oplog/src/bondy_oplog_core.erl:800— apps/bondy_oplog/src/bondy_oplog_core.erl:800-811 | apps/bondy_oplog/src/bondy_oplog_core.erl:815-830 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_db/src/bondy_db.erl:3147— apps/bondy_db/src/bondy_db.erl:3147-3162 | apps/bondy_db/src/bondy_relation.erl:413-424 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_router/src/bondy_registry_meta.erl:580— apps/bondy_router/src/bondy_registry_meta.erl:580-595 | apps/bondy_router/src/bondy_registry_meta.erl:808-819 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_raw.erl:125— apps/bondy_connect_sdk/src/bondy_connect_raw.erl:125-136 | apps/bondy_connect_sdk/src/bondy_connect_transport_ws.erl:176-189 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_log/src/bondy_log_recovery.erl:1272— apps/bondy_log/src/bondy_log_recovery.erl:1272-1283 | apps/bondy_mst/src/bondy_mst_pack_recovery.erl:144-155 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_router/src/bondy_registry_ptrie.erl:1377— apps/bondy_router/src/bondy_registry_ptrie.erl:1377-1391 | apps/bondy_router/src/bondy_registry_ptrie.erl:1449-1460 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_oplog/src/bondy_oplog_core_registry.erl:1190— apps/bondy_oplog/src/bondy_oplog_core_registry.erl:1190-1201 | apps/bondy_oplog/src/bondy_oplog_core_registry.erl:1265-1281 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_router/src/bondy_export.erl:1191— apps/bondy_router/src/bondy_export.erl:1191-1202 | apps/bondy_router/src/bondy_export.erl:1250-1261 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_oplog/src/bondy_oplog_core_registry.erl:737— apps/bondy_oplog/src/bondy_oplog_core_registry.erl:737-748 | apps/bondy_oplog/src/bondy_oplog_core_registry.erl:814-825 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_telemetry.erl:65— apps/bondy_connect_sdk/src/bondy_connect_telemetry.erl:65-76 | apps/bondy_router/src/bondy_telemetry.erl:474-485 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) apps/bondy_log/src/bondy_log_wal.erl:1088— apps/bondy_log/src/bondy_log_wal.erl:1088-1099 | apps/bondy_log/src/bondy_log_wal.erl:1102-1115 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (5 lines × 2) apps/bondy_mst/src/bondy_mst_pack_recovery.erl:253— apps/bondy_mst/src/bondy_mst_pack_recovery.erl:253-257 | apps/bondy_mst/src/bondy_mst_pack_writer.erl:1248-1252 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_mst/src/bondy_mst_pack_recovery.erl:253` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:333— apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:333-337 | apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl:197-204 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl` and `apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl` as WHOLE FILES: this scan already matched 6 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:75— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:75-79 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:98-103 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:154— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:154-160 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:134-138 — before extracting anything, compare `apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl` and `apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:154` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) apps/bondy_log/src/bondy_log_manifest.erl:355— apps/bondy_log/src/bondy_log_manifest.erl:355-359 | apps/bondy_log/src/bondy_log_state.erl:380-384 — 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) apps/bondy_log/src/bondy_log_scrubber.erl:211— apps/bondy_log/src/bondy_log_scrubber.erl:211-215 | apps/bondy_router/src/bondy_reclaimer.erl:153-157 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_log/src/bondy_log_scrubber.erl:211` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) apps/bondy_oplog/src/bondy_oplog_crdt_rw_nested_core.erl:145— apps/bondy_oplog/src/bondy_oplog_crdt_rw_nested_core.erl:145-149 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_set.erl:219-223 — 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) apps/bondy_router/src/bondy_oauth_token.erl:1359— apps/bondy_router/src/bondy_oauth_token.erl:1359-1363 | apps/bondy_router/src/bondy_ticket.erl:1240-1244 — 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) apps/bondy_router/src/bondy_rbac_group.erl:667— apps/bondy_router/src/bondy_rbac_group.erl:667-671 | apps/bondy_router/src/bondy_rbac_user.erl:1665-1669 — before extracting anything, compare `apps/bondy_router/src/bondy_rbac_group.erl` and `apps/bondy_router/src/bondy_rbac_user.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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) apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:858— apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:858-862 | apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl:776-780 — before extracting anything, compare `apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl` and `apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl:776` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) apps/bondy_router/src/bondy_wamp_api.erl:81— apps/bondy_router/src/bondy_wamp_api.erl:81-85 | apps/bondy_router/src/bondy_wamp_meta_api.erl:64-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_wamp_api.erl:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) apps/bondy_broker_bridge/src/channel_handler/email_adapter_mailgun2.erl:101— apps/bondy_broker_bridge/src/channel_handler/email_adapter_mailgun2.erl:101-105 | apps/bondy_broker_bridge/src/channel_handler/email_adapter_sendgrid.erl:121-125 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) apps/bondy_mst/src/bondy_mst.erl:2085— apps/bondy_mst/src/bondy_mst.erl:2085-2089 | apps/bondy_mst/src/bondy_mst.erl:2092-2096 — 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) apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:176— apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:176-180 | apps/bondy_oplog/src/bondy_oplog_crdt_pn_counter.erl:182-186 — 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.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×13
Edited copy of a member (9 corresponding lines) apps/bondy_router/src/bondy_realm.erl:1391— apps/bondy_router/src/bondy_realm.erl:1391-1399 | apps/bondy_router/src/bondy_realm.erl:1413-1423 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_oplog/src/bondy_oplog_applier.erl:2896— apps/bondy_oplog/src/bondy_oplog_applier.erl:2896-2904 | apps/bondy_oplog/src/bondy_oplog_instance.erl:1206-1214 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_connect_lib/src/bondy_connect_error.erl:442— apps/bondy_connect_lib/src/bondy_connect_error.erl:442-450 | apps/bondy_mst/src/bondy_mst.erl:1267-1276 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_db/src/bondy_db.erl:4072— apps/bondy_db/src/bondy_db.erl:4072-4080 | apps/bondy_log/src/bondy_log_recovery.erl:518-539 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) jepsen/jepsen.bondy/src/main/java/io/leapsight/jepsen/bondy/Utils.java:398— jepsen/jepsen.bondy/src/main/java/io/leapsight/jepsen/bondy/Utils.java:398-407 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:450-458 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_oplog/src/bondy_oplog_registry.erl:422— apps/bondy_oplog/src/bondy_oplog_registry.erl:422-430 | apps/bondy_oplog/src/bondy_oplog_registry.erl:445-453 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_oplog/src/bondy_oplog_core_registry.erl:1036— apps/bondy_oplog/src/bondy_oplog_core_registry.erl:1036-1046 | apps/bondy_oplog/src/bondy_oplog_core_registry.erl:1175-1183 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_router/src/bondy_aae_reactor_worker.erl:73— apps/bondy_router/src/bondy_aae_reactor_worker.erl:73-81 | apps/bondy_router/src/bondy_registry_partition.erl:511-519 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_router/src/bondy_registry_store.erl:1347— apps/bondy_router/src/bondy_registry_store.erl:1347-1355 | apps/bondy_router/src/bondy_registry_store.erl:1362-1375 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_oplog/src/bondy_oplog_db_overlay.erl:144— apps/bondy_oplog/src/bondy_oplog_db_overlay.erl:144-155 | apps/bondy_oplog/src/bondy_oplog_db_overlay.erl:173-181 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_oplog/src/bondy_oplog_index_spec.erl:361— apps/bondy_http_connector/src/bondy_http_connector_auth_generic.erl:346-356 | apps/bondy_oplog/src/bondy_oplog_index_spec.erl:361-369 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_router/src/bondy_reclaimer.erl:126— apps/bondy_router/src/bondy_reclaimer.erl:126-137 | apps/bondy_router/src/bondy_system_gc.erl:62-70 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) apps/bondy_mail/src/bondy_mail_worker_sup.erl:64— apps/bondy_mail/src/bondy_mail_worker_sup.erl:64-72 | apps/bondy_oplog/src/bondy_oplog_instance.erl:587-595 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) apps/bondy_connect_sdk/src/bondy_connect_config.erl:156— apps/bondy_connect_sdk/src/bondy_connect_config.erl:156-164 | apps/bondy_connect_sdk/src/bondy_connect_connection.erl:2152-2159 — 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) apps/bondy_db/src/bondy_db.erl:1686— apps/bondy_db/src/bondy_db.erl:1686-1693 | apps/bondy_db/src/bondy_db.erl:1921-1928 — 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) apps/bondy_oplog/src/bondy_oplog_applier.erl:2172— apps/bondy_oplog/src/bondy_oplog_applier.erl:2172-2179 | apps/bondy_oplog/src/bondy_oplog_instance.erl:4215-4222 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_applier.erl` and `apps/bondy_oplog/src/bondy_oplog_instance.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 71 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) apps/bondy_oplog/src/bondy_oplog_applier.erl:2897— apps/bondy_oplog/src/bondy_oplog_applier.erl:2897-2904 | apps/bondy_oplog/src/bondy_oplog_instance.erl:1207-1214 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_applier.erl` and `apps/bondy_oplog/src/bondy_oplog_instance.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 71 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) apps/bondy_oplog/src/bondy_oplog_crdt_g_set.erl:153— apps/bondy_oplog/src/bondy_oplog_crdt_g_set.erl:153-160 | apps/bondy_oplog/src/bondy_oplog_crdt_two_p_set.erl:181-188 — 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) apps/bondy_router/src/bondy_oauth2_api.erl:39— apps/bondy_router/src/bondy_oauth2_api.erl:39-46 | apps/bondy_router/src/bondy_oauth2_api.erl:60-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_oauth2_api.erl:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) apps/bondy_router/src/bondy_oauth2_api.erl:84— apps/bondy_router/src/bondy_oauth2_api.erl:84-91 | apps/bondy_router/src/bondy_oauth2_api.erl:105-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_oauth2_api.erl:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) apps/bondy_router/src/bondy_rbac_api.erl:232— apps/bondy_router/src/bondy_rbac_api.erl:232-239 | apps/bondy_router/src/bondy_rbac_api.erl:272-279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_rbac_api.erl:232` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) apps/bondy_router/src/bondy_registry_ptrie.erl:1052— apps/bondy_router/src/bondy_registry_ptrie.erl:1052-1059 | apps/bondy_router/src/bondy_registry_ptrie.erl:1065-1072 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_registry_ptrie.erl:1052` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:911— apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:911-918 | apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl:766-773 — before extracting anything, compare `apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl` and `apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl:766` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) apps/bondy_router/src/bondy_password.erl:298— apps/bondy_router/src/bondy_password.erl:298-307 | apps/bondy_router/src/bondy_password.erl:312-319 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_password.erl:298` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) apps/bondy_router/src/bondy_rbac_api.erl:54— apps/bondy_router/src/bondy_rbac_api.erl:54-61 | apps/bondy_router/src/bondy_realm_api.erl:50-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_rbac_api.erl:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) jepsen/jepsen.bondy/src/main/java/io/leapsight/jepsen/bondy/Utils.java:389— jepsen/jepsen.bondy/src/main/java/io/leapsight/jepsen/bondy/Utils.java:389-396 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:207-214 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×12
Edited copy of a member (7 corresponding lines) apps/bondy_mst/src/bondy_mst.erl:1516— apps/bondy_mst/src/bondy_mst.erl:1516-1526 | apps/bondy_mst/src/bondy_mst.erl:1531-1537 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_mcp/src/bondy_mcp_wamp.erl:335— apps/bondy_mcp/src/bondy_mcp_wamp.erl:335-341 | apps/bondy_mcp/src/bondy_mcp_wamp.erl:349-357 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_router/src/bondy_realm.erl:1335— apps/bondy_router/src/bondy_realm.erl:1335-1344 | apps/bondy_router/src/bondy_realm.erl:1349-1355 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_nested_core.erl:362— apps/bondy_oplog/src/bondy_oplog_crdt_nested_core.erl:362-368 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_nested_core.erl:152-159 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_router/src/bondy_password_cra.erl:124— apps/bondy_router/src/bondy_password_cra.erl:124-130 | apps/bondy_router/src/bondy_password_scram.erl:270-276 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_mcp/src/bondy_mcp_stream.erl:382— apps/bondy_mcp/src/bondy_mcp_stream.erl:382-388 | apps/bondy_router/src/bondy_wamp_meta_api.erl:295-301 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_router/src/bondy_rbac.erl:1627— apps/bondy_router/src/bondy_rbac.erl:1627-1633 | apps/bondy_router/src/bondy_rbac_source.erl:286-293 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_auth.erl:132— apps/bondy_connect_sdk/src/bondy_connect_auth.erl:132-138 | apps/bondy_connect_sdk/src/bondy_connect_session.erl:92-98 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:2021— apps/bondy_connect_sdk/src/bondy_connect_connection.erl:2021-2027 | apps/bondy_router/src/bondy_wamp_api_utils.erl:350-356 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_db/src/bondy_db_topology_memory_owner.erl:105— apps/bondy_db/src/bondy_db_topology_memory_owner.erl:105-112 | apps/bondy_log/src/bondy_log_wal.erl:483-489 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_router/src/bondy_rbac_user.erl:843— apps/bondy_router/src/bondy_rbac_user.erl:843-849 | apps/bondy_router/src/bondy_session.erl:719-725 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) apps/bondy_router/src/bondy_rbac_group.erl:767— apps/bondy_router/src/bondy_rbac_group.erl:767-774 | apps/bondy_router/src/bondy_rbac_user.erl:2138-2144 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×12
Edited copy of a member (5 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_rw_nested_core.erl:71— apps/bondy_oplog/src/bondy_oplog_crdt_rw_nested_core.erl:71-75 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_nested_core.erl:95-101 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1077— apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1077-1081 | apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1688-1692 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_mcp/src/bondy_mcp_gateway.erl:184— apps/bondy_mcp/src/bondy_mcp_gateway.erl:184-188 | apps/bondy_router/src/bondy_interface.erl:271-275 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_metrics/src/bondy_metrics.erl:566— apps/bondy_metrics/src/bondy_metrics.erl:566-570 | apps/bondy_router/src/bondy_aae_reactor.erl:182-186 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_db/src/bondy_db.erl:2344— apps/bondy_db/src/bondy_db.erl:2344-2348 | apps/bondy_router/src/bondy_aae_reactor.erl:700-706 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_router/src/bondy_oidc_provider.erl:211— apps/bondy_http_connector/src/bondy_http_connector_callee_handler.erl:390-400 | apps/bondy_router/src/bondy_oidc_provider.erl:211-215 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_mst/src/bondy_mst_pack_manifest.erl:434— apps/bondy_mst/src/bondy_mst_pack_manifest.erl:434-438 | apps/bondy_mst/src/bondy_mst_pack_store.erl:905-909 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_router/src/bondy_rbac_group.erl:322— apps/bondy_router/src/bondy_rbac_group.erl:322-326 | apps/bondy_router/src/bondy_rbac_user.erl:1194-1204 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_connect_lib/src/bondy_connect_table_manager.erl:153— apps/bondy_connect_lib/src/bondy_connect_table_manager.erl:153-157 | apps/bondy_metrics/src/bondy_metrics.erl:610-614 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_db/src/bondy_db.erl:2399— apps/bondy_db/src/bondy_db.erl:2399-2405 | apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:1460-1464 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_oplog/src/bondy_oplog_catalogue_cursor.erl:405— apps/bondy_oplog/src/bondy_oplog_catalogue_cursor.erl:405-410 | apps/bondy_oplog/src/bondy_oplog_peer_state.erl:311-315 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_aw_core.erl:87— apps/bondy_oplog/src/bondy_oplog_crdt_aw_core.erl:87-91 | apps/bondy_oplog/src/bondy_oplog_ctx_guard.erl:209-213 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 2) apps/bondy_db/src/bondy_db.erl:4193— apps/bondy_db/src/bondy_db.erl:4193-4201 | apps/bondy_db/src/bondy_db.erl:4207-4215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_db/src/bondy_db.erl:4193` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) apps/bondy_mst/src/bondy_mst_ets_store.erl:268— apps/bondy_mst/src/bondy_mst_ets_store.erl:268-276 | apps/bondy_mst/src/bondy_mst_map_store.erl:184-192 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) apps/bondy_oplog/src/bondy_oplog_applier.erl:2973— apps/bondy_oplog/src/bondy_oplog_applier.erl:2973-2981 | apps/bondy_oplog/src/bondy_oplog_instance.erl:4081-4089 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_applier.erl` and `apps/bondy_oplog/src/bondy_oplog_instance.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_applier.erl:2973` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:531— apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:531-539 | apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:791-799 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:531` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) apps/bondy_router/src/bondy_rbac.erl:1659— apps/bondy_router/src/bondy_rbac.erl:1659-1667 | apps/bondy_router/src/bondy_rbac_source.erl:638-646 — 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) apps/bondy_router/src/bondy_router_worker.erl:147— apps/bondy_router/src/bondy_router_worker.erl:147-155 | apps/bondy_router/src/bondy_router_worker.erl:202-210 — 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) apps/bondy_log/src/bondy_log_scrubber.erl:147— apps/bondy_log/src/bondy_log_scrubber.erl:147-155 | apps/bondy_oplog/src/bondy_oplog_applier.erl:501-509 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_log/src/bondy_log_scrubber.erl:147` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) apps/bondy_router/src/bondy_auth_oauth2.erl:33— apps/bondy_router/src/bondy_auth_oauth2.erl:33-42 | apps/bondy_router/src/bondy_auth_ticket.erl:32-40 — 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) apps/bondy_router/src/bondy_http_longpoll_handler.erl:180— apps/bondy_router/src/bondy_http_longpoll_handler.erl:180-188 | apps/bondy_router/src/bondy_http_sse_handler.erl:123-131 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 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) apps/bondy_db/src/bondy_db_sup.erl:31— apps/bondy_db/src/bondy_db_sup.erl:31-39 | apps/bondy_mst/src/bondy_mst_sup.erl:29-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_db/src/bondy_db_sup.erl:31` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:277— jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:277-285 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:408-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:277` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) apps/bondy_mcp/src/bondy_mcp_spec.erl:291— apps/bondy_mcp/src/bondy_mcp_spec.erl:291-299 | apps/bondy_mcp/src/bondy_mcp_spec.erl:342-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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_mcp/src/bondy_mcp_spec.erl:291` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×11
Edited copy of a member (16 corresponding lines) apps/bondy_wamp/src/bondy_wamp_cbor.erl:369— apps/bondy_wamp/src/bondy_wamp_cbor.erl:369-384 | apps/bondy_wamp/src/bondy_wamp_cbor.erl:513-528 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) apps/bondy_db/src/bondy_db_projection_leveled.erl:748— apps/bondy_db/src/bondy_db_projection_leveled.erl:748-765 | apps/bondy_db/src/bondy_db_projection_leveled.erl:770-785 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) apps/bondy_mst/src/bondy_mst.erl:1586— apps/bondy_mst/src/bondy_mst.erl:1586-1601 | apps/bondy_mst/src/bondy_mst.erl:1604-1620 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:164— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:164-179 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:142-157 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:301— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:301-319 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:275-290 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) apps/bondy_db/src/bondy_db.erl:2119— apps/bondy_db/src/bondy_db.erl:2119-2134 | apps/bondy_db/src/bondy_db.erl:2154-2174 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) apps/bondy_router/src/bondy_rbac_user.erl:1080— apps/bondy_router/src/bondy_rbac_user.erl:1080-1095 | apps/bondy_router/src/bondy_rbac_user.erl:1114-1129 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1686— apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1686-1701 | apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1705-1720 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1111— apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1111-1126 | apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1132-1152 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) apps/bondy_log/src/bondy_log_manifest.erl:120— apps/bondy_log/src/bondy_log_manifest.erl:120-136 | apps/bondy_mst/src/bondy_mst_pack_manifest.erl:149-164 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) apps/bondy_router/src/bondy_registry.erl:1056— apps/bondy_router/src/bondy_registry.erl:1056-1071 | apps/bondy_router/src/bondy_rpc_promise.erl:811-826 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×11
Edited copy of a member (8 corresponding lines) apps/bondy_router/src/bondy_session.erl:1122— apps/bondy_router/src/bondy_session.erl:1122-1129 | apps/bondy_router/src/bondy_session.erl:1132-1139 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) apps/bondy_mst/src/bondy_mst_store.erl:228— apps/bondy_mst/src/bondy_mst_store.erl:228-235 | apps/bondy_mst/src/bondy_mst_store.erl:276-287 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) apps/bondy_wamp/src/bondy_wamp_cbor.erl:229— apps/bondy_wamp/src/bondy_wamp_cbor.erl:229-236 | apps/bondy_wamp/src/bondy_wamp_json.erl:285-295 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_dispatch.erl:321— apps/bondy_connect_sdk/src/bondy_connect_dispatch.erl:321-328 | apps/bondy_connect_sdk/src/bondy_connect_dispatch.erl:408-421 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) apps/bondy_db/src/bondy_db_projection_leveled.erl:703— apps/bondy_db/src/bondy_db_projection_leveled.erl:703-710 | apps/bondy_db/src/bondy_db_projection_leveled.erl:712-719 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) apps/bondy_router/src/bondy_registry_meta.erl:198— apps/bondy_router/src/bondy_registry_meta.erl:198-205 | apps/bondy_router/src/bondy_registry_meta.erl:225-234 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) apps/bondy_router/src/bondy_http_longpoll_handler.erl:116— apps/bondy_router/src/bondy_http_longpoll_handler.erl:116-123 | apps/bondy_router/src/bondy_http_sse_handler.erl:64-71 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) apps/bondy_router/src/bondy_http_longpoll_handler.erl:258— apps/bondy_router/src/bondy_http_longpoll_handler.erl:258-265 | apps/bondy_router/src/bondy_http_sse_handler.erl:199-206 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) apps/bondy_router/src/bondy_http_longpoll_handler.erl:388— apps/bondy_router/src/bondy_http_longpoll_handler.erl:388-395 | apps/bondy_router/src/bondy_http_sse_handler.erl:269-276 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) REDACTED:70— REDACTED:70-77 | apps/bondy_broker_bridge/src/bondy_kafka_bridge.erl:375-384 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) bench/lib/bench/projection_leveled.ex:175— bench/lib/bench/projection_leveled.ex:175-182 | bench/lib/bench/projection_leveled.ex:186-193 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×10
Edited copy of a member (13 corresponding lines) apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1062— apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1062-1074 | apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1673-1685 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1521— apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1521-1533 | apps/bondy_mcp/src/bondy_mcp_stream.erl:393-408 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) apps/bondy_oplog/src/bondy_oplog_cell_frame.erl:143— apps/bondy_oplog/src/bondy_oplog_cell_frame.erl:143-156 | apps/bondy_oplog/src/bondy_oplog_cell_frame.erl:196-208 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) apps/bondy_router/src/bondy_rbac_group.erl:223— apps/bondy_router/src/bondy_rbac_group.erl:223-235 | apps/bondy_router/src/bondy_rbac_user.erl:545-561 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:499— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:499-519 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:440-452 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:333— apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:333-345 | apps/bondy_log/src/bondy_log_recovery.erl:1121-1133 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) apps/bondy_oplog/src/bondy_oplog_instance.erl:1630— apps/bondy_oplog/src/bondy_oplog_instance.erl:1630-1642 | apps/bondy_oplog/src/bondy_oplog_instance.erl:1674-1687 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) apps/bondy_router/src/bondy_export.erl:493— apps/bondy_router/src/bondy_export.erl:493-505 | apps/bondy_router/src/bondy_ticket.erl:1109-1123 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) apps/bondy_router/src/bondy_session_manager.erl:136— apps/bondy_router/src/bondy_session_manager.erl:136-148 | apps/bondy_router/src/bondy_session_manager.erl:166-179 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) apps/bondy_router/src/bondy_registry_rib.erl:344— apps/bondy_router/src/bondy_registry_rib.erl:344-356 | apps/bondy_router/src/bondy_registry_rib.erl:359-373 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×10
Edited copy of a member (3 corresponding lines) apps/bondy_metrics/src/bondy_metrics.erl:326— apps/bondy_metrics/src/bondy_metrics.erl:326-328 | apps/bondy_metrics/src/bondy_metrics.erl:346-348 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:482— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:482-484 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:425-427 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) apps/bondy_oplog/src/bondy_oplog_core_events.erl:163— apps/bondy_oplog/src/bondy_oplog_core_events.erl:163-165 | apps/bondy_oplog/src/bondy_oplog_core_registry.erl:689-700 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) apps/bondy_mcp/src/bondy_mcp_gateway.erl:354— apps/bondy_mcp/src/bondy_mcp_gateway.erl:354-356 | apps/bondy_router/src/bondy_http_gateway.erl:515-517 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) apps/bondy_router/src/bondy_bridge_relay.erl:693— apps/bondy_router/src/bondy_bridge_relay.erl:693-695 | apps/bondy_router/src/bondy_interface.erl:280-282 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) apps/bondy_router/src/bondy_broker.erl:176— apps/bondy_router/src/bondy_broker.erl:176-178 | apps/bondy_router/src/bondy_router_peer.erl:468-476 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) apps/bondy_mcp/src/bondy_mcp_sup.erl:107— apps/bondy_mcp/src/bondy_mcp_sup.erl:107-109 | apps/bondy_oplog/src/bondy_oplog_secondary_sup.erl:76-82 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) apps/bondy_router/src/bondy_rbac.erl:1654— apps/bondy_router/src/bondy_rbac.erl:1654-1656 | apps/bondy_router/src/bondy_rbac_source.erl:632-635 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_g_set.erl:149— apps/bondy_oplog/src/bondy_oplog_crdt_g_set.erl:149-151 | apps/bondy_oplog/src/bondy_oplog_crdt_two_p_set.erl:177-179 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) apps/bondy_router/src/bondy_oauth2_client.erl:82— apps/bondy_router/src/bondy_oauth2_client.erl:82-84 | apps/bondy_router/src/bondy_oauth2_resource_owner.erl:60-64 — These two members are one piece of code written twice and then edited apart: 3 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 (2 corresponding lines) · ×10
Edited copy of a member (2 corresponding lines) apps/bondy_connect_lib/src/bondy_connect_error.erl:1096— apps/bondy_connect_lib/src/bondy_connect_error.erl:1096-1097 | apps/bondy_mcp/src/bondy_mcp_wamp.erl:550-557 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:487— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:487-488 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:430-431 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:144— apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:144-145 | apps/bondy_oplog/src/bondy_oplog_crdt_pn_counter.erl:133-134 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) apps/bondy_db/src/bondy_db_projection_leveled.erl:800— apps/bondy_db/src/bondy_db_projection_leveled.erl:800-801 | apps/bondy_oplog/src/bondy_oplog_cell_frame.erl:219-223 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) apps/bondy_log/src/bondy_log_manifest.erl:368— apps/bondy_log/src/bondy_log_manifest.erl:368-371 | apps/bondy_mst/src/bondy_mst_pack_manifest.erl:445-446 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) apps/bondy_router/src/bondy_oauth_token.erl:1372— apps/bondy_router/src/bondy_oauth_token.erl:1372-1373 | apps/bondy_router/src/bondy_ticket.erl:1253-1254 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) apps/bondy_log/src/bondy_log_wal.erl:827— apps/bondy_log/src/bondy_log_wal.erl:827-830 | apps/bondy_oplog/src/bondy_oplog_gc_scheduler.erl:199-200 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) apps/bondy_mst/src/bondy_mst_crdt.erl:719— apps/bondy_mst/src/bondy_mst_crdt.erl:719-724 | apps/bondy_mst/src/bondy_mst_exchange.erl:476-477 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) apps/bondy_oplog/src/bondy_oplog_applier.erl:906— apps/bondy_oplog/src/bondy_oplog_applier.erl:906-907 | apps/bondy_oplog/src/bondy_oplog_instance.erl:1700-1701 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) apps/bondy_log/src/bondy_log_manifest.erl:296— apps/bondy_log/src/bondy_log_manifest.erl:296-299 | apps/bondy_mst/src/bondy_mst_pack_manifest.erl:399-400 — These two members are one piece of code written twice and then edited apart: 2 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 (14 corresponding lines) · ×9
Edited copy of a member (14 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_dw_flag.erl:124— apps/bondy_oplog/src/bondy_oplog_crdt_dw_flag.erl:124-137 | apps/bondy_oplog/src/bondy_oplog_crdt_ew_flag.erl:126-139 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) apps/bondy_oplog/src/bondy_oplog_transport_disterl.erl:52— apps/bondy_oplog/src/bondy_oplog_transport_disterl.erl:52-65 | apps/bondy_oplog/src/bondy_oplog_transport_partisan.erl:54-68 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) apps/bondy_mst/src/bondy_mst_pack_index.erl:282— apps/bondy_mst/src/bondy_mst_pack_index.erl:282-295 | apps/bondy_mst/src/bondy_mst_pack_tombstones.erl:172-185 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) apps/bondy_router/src/bondy_registry_store.erl:1526— apps/bondy_router/src/bondy_registry_store.erl:1526-1541 | apps/bondy_router/src/bondy_registry_store.erl:1548-1561 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1023— apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1023-1036 | apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1060-1073 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) apps/bondy_log/src/bondy_log_wal.erl:1278— apps/bondy_log/src/bondy_log_wal.erl:1278-1295 | apps/bondy_oplog/src/bondy_oplog_applier.erl:3127-3140 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1488— apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1488-1501 | apps/bondy_connect_sdk/src/bondy_connect_handler.erl:125-145 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1176— apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1176-1189 | apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1475-1488 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) apps/bondy_router/src/bondy_registry_rib.erl:636— apps/bondy_router/src/bondy_registry_rib.erl:636-649 | apps/bondy_router/src/bondy_registry_rib.erl:776-789 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×9
Edited copy of a member (6 corresponding lines) apps/bondy_router/src/bondy_registry_ptrie.erl:1030— apps/bondy_router/src/bondy_registry_ptrie.erl:1030-1035 | apps/bondy_router/src/bondy_registry_ptrie.erl:1168-1178 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) apps/bondy_log/src/bondy_log_wal.erl:2262— apps/bondy_log/src/bondy_log_wal.erl:2262-2267 | apps/bondy_log/src/bondy_log_wal.erl:2273-2278 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) apps/bondy_router/src/bondy_http_longpoll_handler.erl:106— apps/bondy_router/src/bondy_http_longpoll_handler.erl:106-113 | apps/bondy_router/src/bondy_http_sse_handler.erl:56-61 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl:790— apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl:790-795 | apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:882-887 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) apps/bondy_mcp/src/bondy_mcp_spec_parser.erl:253— apps/bondy_mcp/src/bondy_mcp_spec_parser.erl:253-258 | apps/bondy_mcp/src/bondy_mcp_upstream_sup.erl:63-74 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) apps/bondy_mcp/src/bondy_mcp_spec.erl:204— apps/bondy_mcp/src/bondy_mcp_spec.erl:204-209 | apps/bondy_mcp/src/bondy_mcp_upstream.erl:161-166 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) apps/bondy_router/src/bondy_oauth2_client.erl:115— apps/bondy_router/src/bondy_oauth2_client.erl:115-120 | apps/bondy_router/src/bondy_oauth2_resource_owner.erl:107-112 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) apps/bondy_mst/src/bondy_mst_pack_seal.erl:176— apps/bondy_mst/src/bondy_mst_pack_seal.erl:176-184 | apps/bondy_mst/src/bondy_mst_pack_writer.erl:1668-1673 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) apps/bondy_router/src/bondy_rbac.erl:1643— apps/bondy_router/src/bondy_rbac.erl:1643-1648 | apps/bondy_router/src/bondy_rbac_source.erl:618-623 — These two members are one piece of code written twice and then edited apart: 6 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 (19 corresponding lines) · ×8
Edited copy of a member (19 corresponding lines) apps/bondy_oplog/src/bondy_oplog_applier.erl:2170— apps/bondy_oplog/src/bondy_oplog_applier.erl:2170-2188 | apps/bondy_oplog/src/bondy_oplog_instance.erl:4213-4236 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1002— apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1002-1020 | apps/bondy_connect_sdk/src/bondy_connect_connection.erl:1039-1057 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) apps/bondy_router/src/bondy_oauth_refresh_token.erl:72— apps/bondy_router/src/bondy_oauth_refresh_token.erl:72-90 | apps/bondy_router/src/bondy_oauth_refresh_token.erl:114-133 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) apps/bondy_oplog/src/bondy_oplog_instance.erl:2203— apps/bondy_oplog/src/bondy_oplog_instance.erl:2203-2227 | apps/bondy_oplog/src/bondy_oplog_instance.erl:2238-2256 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) apps/bondy_mst/src/bondy_mst.erl:756— apps/bondy_mst/src/bondy_mst.erl:756-774 | apps/bondy_mst/src/bondy_mst.erl:798-818 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) apps/bondy_router/src/bondy_oauth_token.erl:708— apps/bondy_router/src/bondy_oauth_token.erl:708-727 | apps/bondy_router/src/bondy_ticket.erl:620-638 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) apps/bondy_router/src/bondy_rpc_promise.erl:762— apps/bondy_router/src/bondy_rpc_promise.erl:762-780 | apps/bondy_router/src/bondy_rpc_promise.erl:788-808 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) apps/bondy_router/src/bondy_cert_manager.erl:404— apps/bondy_router/src/bondy_cert_manager.erl:404-422 | apps/bondy_router/src/bondy_cert_manager.erl:601-619 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×7
Edited copy of a member (17 corresponding lines) apps/bondy_mst/src/bondy_mst.erl:1774— apps/bondy_mst/src/bondy_mst.erl:1774-1797 | apps/bondy_mst/src/bondy_mst.erl:2321-2337 — 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.
Edited copy of a member (17 corresponding lines) apps/bondy_log/src/bondy_log_idx.erl:503— apps/bondy_log/src/bondy_log_idx.erl:503-519 | apps/bondy_log/src/bondy_log_segment.erl:247-270 — 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.
Edited copy of a member (17 corresponding lines) apps/bondy_db/src/bondy_db_topology_per_entity.erl:118— apps/bondy_db/src/bondy_db_topology_per_entity.erl:118-134 | apps/bondy_db/src/bondy_db_topology_shared_shards.erl:134-150 — 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.
Edited copy of a member (17 corresponding lines) apps/bondy_mst/src/bondy_mst_pack_index.erl:298— apps/bondy_mst/src/bondy_mst_pack_index.erl:298-314 | apps/bondy_mst/src/bondy_mst_pack_tombstones.erl:192-208 — 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.
Edited copy of a member (17 corresponding lines) apps/bondy_log/src/bondy_log_wal.erl:2919— apps/bondy_log/src/bondy_log_wal.erl:2919-2941 | apps/bondy_log/src/bondy_log_wal.erl:2962-2978 — 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.
Edited copy of a member (17 corresponding lines) apps/bondy_mst/src/bondy_mst_pack_writer.erl:556— apps/bondy_mst/src/bondy_mst_pack_writer.erl:556-572 | apps/bondy_mst/src/bondy_mst_pack_writer.erl:1521-1542 — 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.
Edited copy of a member (17 corresponding lines) apps/bondy_mst/src/bondy_mst_map_store.erl:78— apps/bondy_mst/src/bondy_mst_map_store.erl:78-94 | apps/bondy_mst/src/bondy_mst_pack_store.erl:360-381 — 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 (15 corresponding lines) · ×7
Edited copy of a member (15 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:122— apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:122-136 | apps/bondy_oplog/src/bondy_oplog_crdt_pn_counter.erl:107-125 — 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.
Edited copy of a member (15 corresponding lines) apps/bondy_log/src/bondy_log_recovery.erl:542— apps/bondy_log/src/bondy_log_recovery.erl:542-559 | apps/bondy_log/src/bondy_log_recovery.erl:706-720 — 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.
Edited copy of a member (15 corresponding lines) apps/mops/src/mops.erl:234— apps/mops/src/mops.erl:234-248 | apps/mops/src/mops.erl:251-265 — 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.
Edited copy of a member (15 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:279— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:279-294 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:254-268 — 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.
Edited copy of a member (15 corresponding lines) apps/bondy_router/src/bondy_registry_ptrie.erl:1394— apps/bondy_router/src/bondy_registry_ptrie.erl:1394-1411 | apps/bondy_router/src/bondy_registry_ptrie.erl:1463-1477 — 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.
Edited copy of a member (15 corresponding lines) apps/bondy_router/src/bondy_auth_password.erl:32— apps/bondy_router/src/bondy_auth_password.erl:32-46 | apps/bondy_router/src/bondy_auth_wamp_cra.erl:32-50 — 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.
Edited copy of a member (15 corresponding lines) REDACTED:295— REDACTED:295-309 | apps/bondy_router/src/bondy_wamp_protocol.erl:969-983 — 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.
Duplicated block (12 lines × 2) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:508— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:508-519 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:441-452 — before extracting anything, compare `apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl` and `apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:508` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) apps/bondy_oplog/src/bondy_oplog_applier.erl:1807— apps/bondy_oplog/src/bondy_oplog_applier.erl:1807-1818 | apps/bondy_oplog/src/bondy_oplog_instance.erl:3762-3773 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_applier.erl` and `apps/bondy_oplog/src/bondy_oplog_instance.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_applier.erl:1807` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) apps/bondy_oplog/src/bondy_oplog_instance.erl:964— apps/bondy_oplog/src/bondy_oplog_instance.erl:964-977 | apps/bondy_oplog/src/bondy_oplog_instance.erl:5972-5983 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_instance.erl:964` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:351— apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:351-362 | apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:669-680 — 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) apps/bondy_router/src/bondy_realm.erl:3277— apps/bondy_router/src/bondy_realm.erl:3277-3288 | apps/bondy_router/src/bondy_realm.erl:3313-3324 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_realm.erl:3277` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) apps/bondy_router/src/bondy_subscribers_sup.erl:51— apps/bondy_http_connector/src/bondy_http_connector_callee_sup.erl:54-65 | apps/bondy_router/src/bondy_subscribers_sup.erl:51-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_http_connector/src/bondy_http_connector_callee_sup.erl:54` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:333— jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:333-344 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:384-395 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:333` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) apps/bondy_mst/src/bondy_mst.erl:1128— apps/bondy_mst/src/bondy_mst.erl:1128-1137 | apps/bondy_mst/src/bondy_mst.erl:1175-1184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_mst/src/bondy_mst.erl:1128` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) apps/bondy_router/src/bondy_bridge_relay_client.erl:1026— apps/bondy_router/src/bondy_bridge_relay_client.erl:1026-1035 | apps/bondy_router/src/bondy_bridge_relay_server.erl:1152-1161 — before extracting anything, compare `apps/bondy_router/src/bondy_bridge_relay_client.erl` and `apps/bondy_router/src/bondy_bridge_relay_server.erl` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_bridge_relay_client.erl:1026` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) apps/bondy_router/src/bondy_http_longpoll_handler.erl:126— apps/bondy_router/src/bondy_http_longpoll_handler.erl:126-135 | apps/bondy_router/src/bondy_http_sse_handler.erl:74-83 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 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) apps/bondy_router/src/bondy_http_longpoll_handler.erl:268— apps/bondy_router/src/bondy_http_longpoll_handler.erl:268-277 | apps/bondy_router/src/bondy_http_sse_handler.erl:209-218 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 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) apps/bondy_router/src/bondy_http_longpoll_handler.erl:398— apps/bondy_router/src/bondy_http_longpoll_handler.erl:398-407 | apps/bondy_router/src/bondy_http_sse_handler.erl:279-288 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 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) apps/bondy_router/src/bondy_broker.erl:134— apps/bondy_router/src/bondy_broker.erl:134-143 | apps/bondy_router/src/bondy_dealer.erl:357-366 — 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) bench/lib/bench/concurrency.ex:167— bench/lib/bench/concurrency.ex:167-176 | bench/lib/bench/e2e.ex:164-173 — before extracting anything, compare `bench/lib/bench/concurrency.ex` and `bench/lib/bench/e2e.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bench/lib/bench/concurrency.ex:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Swallowed exception (caught, then discarded) apps/bondy_router/src/bondy_data_validators.erl:315— `catch error:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) apps/bondy_router/src/bondy_data_validators.erl:344— `catch error:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) apps/bondy_mail/src/bondy_mail_request.erl:675— `catch error:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) apps/bondy_log/src/bondy_log_codec.erl:484— `catch error:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) apps/bondy_db/src/bondy_pagination.erl:155— `catch error:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) apps/bondy_connect_sdk/src/bondy_connect_auth_cra.erl:50— `catch error:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) apps/bondy_connect_sdk/src/bondy_connect_auth_cryptosign.erl:60— `catch error:_` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Duplicated block (14 lines × 2) REDACTED:143— REDACTED:143-156 | REDACTED:170-183 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:530— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:530-543 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:461-474 — before extracting anything, compare `apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl` and `apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 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) apps/bondy_log/src/bondy_log_io.erl:108— apps/bondy_log/src/bondy_log_io.erl:108-121 | apps/bondy_mst/src/bondy_mst_pack_seal.erl:291-304 — 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) apps/bondy_mst/src/bondy_mst.erl:2540— apps/bondy_mst/src/bondy_mst.erl:2540-2553 | apps/bondy_mst/src/bondy_mst.erl:2585-2598 — 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) apps/bondy_router/src/bondy_auth.erl:894— apps/bondy_router/src/bondy_auth.erl:894-907 | apps/bondy_router/src/bondy_auth.erl:925-938 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_auth.erl:894` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) apps/bondy_db/src/bondy_db_projection_leveled.erl:752— apps/bondy_db/src/bondy_db_projection_leveled.erl:752-765 | apps/bondy_db/src/bondy_db_projection_leveled.erl:772-785 — 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.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×5
Edited copy of a member (25 corresponding lines) apps/bondy_router/src/bondy_rbac_group.erl:829— apps/bondy_router/src/bondy_rbac_group.erl:829-853 | apps/bondy_router/src/bondy_rbac_user.erl:1912-1945 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) apps/bondy_router/src/bondy_bridge_relay_client.erl:1026— apps/bondy_router/src/bondy_bridge_relay_client.erl:1026-1055 | apps/bondy_router/src/bondy_bridge_relay_server.erl:1152-1176 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) apps/bondy_mst/src/bondy_mst_pack_recovery.erl:242— apps/bondy_mst/src/bondy_mst_pack_recovery.erl:242-266 | apps/bondy_mst/src/bondy_mst_pack_writer.erl:1236-1261 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) apps/bondy_router/src/bondy_rbac_group.erl:389— apps/bondy_router/src/bondy_rbac_group.erl:389-413 | apps/bondy_router/src/bondy_rbac_user.erl:710-743 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_conn_sup.erl:42— apps/bondy_connect_sdk/src/bondy_connect_conn_sup.erl:42-66 | apps/bondy_connect_sdk/src/bondy_connect_sup.erl:44-68 — These two members are one piece of code written twice and then edited apart: 25 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) · ×5
Edited copy of a member (18 corresponding lines) apps/bondy_wamp/src/bondy_wamp_cbor.erl:437— apps/bondy_wamp/src/bondy_wamp_cbor.erl:437-454 | apps/bondy_wamp/src/bondy_wamp_cbor.erl:457-475 — 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.
Edited copy of a member (18 corresponding lines) apps/bondy_db/src/bondy_relation.erl:343— apps/bondy_db/src/bondy_relation.erl:343-360 | apps/bondy_db/src/bondy_relation.erl:427-456 — 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.
Edited copy of a member (18 corresponding lines) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:73— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:73-90 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl:79-104 — 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.
Edited copy of a member (18 corresponding lines) apps/bondy_router/src/bondy_password_cra.erl:41— apps/bondy_router/src/bondy_password_cra.erl:41-58 | apps/bondy_router/src/bondy_password_scram.erl:64-87 — 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.
Edited copy of a member (18 corresponding lines) apps/bondy_router/src/bondy_rbac_source.erl:588— apps/bondy_router/src/bondy_rbac_source.erl:588-608 | apps/bondy_router/src/bondy_rbac_user.erl:1451-1468 — 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) · ×5
Edited copy of a member (22 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:115— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:115-149 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:108-129 — 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.
Edited copy of a member (22 corresponding lines) apps/bondy_router/src/bondy_http_longpoll_handler.erl:410— apps/bondy_router/src/bondy_http_longpoll_handler.erl:410-432 | apps/bondy_router/src/bondy_http_sse_handler.erl:291-312 — 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.
Edited copy of a member (22 corresponding lines) apps/bondy_telemetry_exporter/src/bondy_prometheus_collector.erl:60— apps/bondy_telemetry_exporter/src/bondy_prometheus_collector.erl:60-81 | apps/bondy_telemetry_exporter/src/bondy_prometheus_db.erl:167-191 — 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.
Edited copy of a member (22 corresponding lines) apps/bondy_router/src/bondy_session.erl:587— apps/bondy_router/src/bondy_session.erl:587-608 | apps/bondy_router/src/bondy_session.erl:612-633 — 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.
Edited copy of a member (22 corresponding lines) apps/bondy_oplog/src/bondy_oplog_instance.erl:961— apps/bondy_oplog/src/bondy_oplog_instance.erl:961-982 | apps/bondy_oplog/src/bondy_oplog_instance.erl:5962-5986 — 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.
Off the main sequence: bondy_cluster — bondy_cluster: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: bondy_json_rpc — bondy_json_rpc: 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: bondy_metrics — bondy_metrics: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: bondy_connect_lib — bondy_connect_lib: abstractness 0.07, instability 0.00, distance 0.93 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: bondy_mst — bondy_mst: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Outbound HTTP without resilience apps/bondy_broker_bridge/src/channel_handler/email_adapter_mailgun2.erl:124— `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience apps/bondy_broker_bridge/src/channel_handler/email_adapter_sendgrid.erl:144— `httpc:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience apps/bondy_http_connector/src/bondy_http_connector_auth_generic.erl:177— `hackney:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience apps/bondy_http_connector/src/bondy_http_connector_http_pool.erl:188— `hackney:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience apps/bondy_http_connector/src/bondy_http_connector_http_pool.erl:420— `hackney:request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:316— apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:316-337 | apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl:174-204 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_map.erl:144-165 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_set.erl:132-149 — 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) apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:410— apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:410-424 | apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl:268-282 | apps/bondy_oplog/src/bondy_oplog_crdt_ew_flag.erl:171-185 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_map.erl:231-245 — 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) apps/bondy_router/src/bondy_aae_reactor_sup.erl:69— apps/bondy_router/src/bondy_aae_reactor_sup.erl:69-110 | apps/bondy_router/src/bondy_jobs_sup.erl:49-87 | apps/bondy_router/src/bondy_oidc_refresh_sup.erl:67-107 | apps/bondy_router/src/bondy_registry_sup.erl:63-100 — 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) jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:276— jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:276-301 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:303-328 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:354-379 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:407-436 — 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.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×3
Edited copy of a member (28 corresponding lines) apps/bondy_wamp/src/bondy_wamp_cbor.erl:186— apps/bondy_wamp/src/bondy_wamp_cbor.erl:186-214 | apps/bondy_wamp/src/bondy_wamp_json.erl:242-269 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) apps/bondy_mst/src/bondy_mst.erl:1127— apps/bondy_mst/src/bondy_mst.erl:1127-1154 | apps/bondy_mst/src/bondy_mst.erl:1174-1202 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) apps/bondy_router/src/bondy_registry_ptrie.erl:739— apps/bondy_router/src/bondy_registry_ptrie.erl:739-773 | apps/bondy_router/src/bondy_registry_ptrie.erl:843-870 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×3
Edited copy of a member (23 corresponding lines) apps/bondy_db/src/bondy_db_topology_per_entity.erl:94— apps/bondy_db/src/bondy_db_topology_per_entity.erl:94-116 | apps/bondy_db/src/bondy_db_topology_shared_shards.erl:108-132 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:352— apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:352-374 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_map.erl:180-203 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) apps/bondy_router/src/bondy_aae_reactor_sup.erl:40— apps/bondy_router/src/bondy_aae_reactor_sup.erl:40-62 | apps/bondy_router/src/bondy_session_manager_sup.erl:29-51 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×3
Edited copies of one member (3 members, 9+ corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:203— apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:203-211 | apps/bondy_oplog/src/bondy_oplog_crdt_owned_reading.erl:246-254 | apps/bondy_oplog/src/bondy_oplog_crdt_pn_counter.erl:211-219 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) apps/bondy_oplog/src/bondy_oplog_core_registry.erl:527— apps/bondy_oplog/src/bondy_oplog_core_registry.erl:527-542 | apps/bondy_oplog/src/bondy_oplog_core_registry.erl:1146-1161 | apps/bondy_oplog/src/bondy_oplog_registry.erl:741-749 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) apps/bondy_router/src/bondy_jobs_sup.erl:32— apps/bondy_http_connector/src/bondy_http_connector_token_cache_sup.erl:64-72 | apps/bondy_router/src/bondy_jobs_sup.erl:32-42 | apps/bondy_router/src/bondy_oidc_refresh_sup.erl:47-60 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×3
Edited copies of one member (3 members, 8+ corresponding lines) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:120— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:120-127 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:139-146 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl:147-154 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) apps/bondy_router/src/bondy_registry_partition.erl:223— apps/bondy_router/src/bondy_registry_partition.erl:223-231 | apps/bondy_router/src/bondy_registry_partition.erl:277-284 | apps/bondy_router/src/bondy_registry_partition.erl:290-298 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) apps/bondy_router/src/bondy_oidc_handler.erl:56— apps/bondy_router/src/bondy_oidc_handler.erl:56-63 | apps/bondy_router/src/bondy_oidc_handler.erl:168-175 | apps/bondy_router/src/bondy_oidc_handler.erl:589-598 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (20 lines × 2) apps/bondy_router/src/bondy_rbac.erl:1604— apps/bondy_router/src/bondy_rbac.erl:1604-1623 | apps/bondy_router/src/bondy_rbac_source.erl:305-324 — 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 (20 lines × 2) apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:836— apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:836-855 | apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl:741-760 — before extracting anything, compare `apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl` and `apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl:741` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) apps/bondy_router/src/bondy_rbac.erl:919— apps/bondy_router/src/bondy_rbac.erl:919-938 | apps/bondy_router/src/bondy_rbac.erl:943-962 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_rbac.erl:919` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) apps/bondy_router/src/bondy_dealer.erl:1588— apps/bondy_router/src/bondy_dealer.erl:1588-1598 | apps/bondy_router/src/bondy_dealer.erl:1627-1637 — 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) apps/bondy_router/src/bondy_oidc_handler.erl:72— apps/bondy_router/src/bondy_oidc_handler.erl:72-82 | apps/bondy_router/src/bondy_oidc_handler.erl:305-315 — 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) apps/bondy_wamp/src/bondy_wamp_json.erl:370— apps/bondy_wamp/src/bondy_wamp_json.erl:370-380 | apps/bondy_wamp/src/bondy_wamp_json.erl:387-398 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_wamp/src/bondy_wamp_json.erl:370` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:354— apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:354-360 | apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:672-678 | apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:728-734 — 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 (7 lines × 3) apps/bondy_router/src/bondy_oauth2_api.erl:50— apps/bondy_router/src/bondy_oauth2_api.erl:50-56 | apps/bondy_router/src/bondy_oauth2_api.erl:95-101 | apps/bondy_router/src/bondy_rbac_api.erl:244-250 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_oauth2_api.erl:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:120— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:120-126 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:139-145 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl:147-153 — before extracting anything, compare `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl` and `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:120` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Change coupling: bondy_auth_password.erl ↔ bondy_wamp_protocol.erl apps/bondy_router/src/bondy_auth_password.erl:1— `apps/bondy_router/src/bondy_auth_password.erl` and `apps/bondy_router/src/bondy_wamp_protocol.erl` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `271ee638` Log the reason for a refused WAMP authentication; `0377154f` Fix a ticket authentication bug recently introduced. API changes to p… (at that commit the files were still `apps/bondy/src/bondy_auth_password.erl` and `apps/bondy/src/bondy_wamp_protocol.erl`); `1613edfd` fixed wamp_cra authentication bug introduced in recent API change; fi… (at that commit the files were still `apps/bondy/src/bondy_auth_password.erl` and `apps/bondy/src/bondy_wamp_protocol.erl`) — run `git show` on any of them.
Change coupling: bondy_oauth2_client.erl ↔ bondy_oauth2_resource_owner.erl apps/bondy_router/src/bondy_oauth2_client.erl:1— `apps/bondy_router/src/bondy_oauth2_client.erl` and `apps/bondy_router/src/bondy_oauth2_resource_owner.erl` change together 50% of the time (8 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 8 shared commits counted here, the most recent 3 are `d8c86d9f` fixes to oauth flows (at that commit the files were still `apps/bondy/src/bondy_oauth2_client.erl` and `apps/bondy/src/bondy_oauth2_resource_owner.erl`); `2233f339` prevent sensitive information to be exposed on OAuth2 APIs (at that commit the files were still `apps/bondy/src/bondy_oauth2_client.erl` and `apps/bondy/src/bondy_oauth2_resource_owner.erl`); `d211cf12` Fixed missing removal of OAuth tokens on user delete (at that commit the files were still `apps/bondy/src/bondy_api_client.erl` and `apps/bondy/src/bondy_api_resource_owner.erl`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) apps/bondy_router/src/bondy_rbac.erl:1118— apps/bondy_router/src/bondy_rbac.erl:1118-1160 | apps/bondy_router/src/bondy_rbac.erl:1227-1274 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) apps/bondy_broker_bridge/src/channel_handler/email_adapter_mailgun2.erl:101— apps/bondy_broker_bridge/src/channel_handler/email_adapter_mailgun2.erl:101-134 | apps/bondy_broker_bridge/src/channel_handler/email_adapter_sendgrid.erl:121-152 — These two members are one piece of code written twice and then edited apart: 32 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 (44 corresponding lines) · ×2
Edited copy of a member (44 corresponding lines) apps/bondy_mst/src/bondy_mst.erl:2060— apps/bondy_mst/src/bondy_mst.erl:2060-2104 | apps/bondy_mst/src/bondy_mst.erl:2238-2281 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (44 corresponding lines) REDACTED:206— REDACTED:206-250 | REDACTED:232-275 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) apps/bondy_db/src/bondy_db.erl:1663— apps/bondy_db/src/bondy_db.erl:1663-1693 | apps/bondy_db/src/bondy_db.erl:1905-1928 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1088— apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1088-1111 | apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1434-1464 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) apps/bondy_router/src/bondy_router_worker.erl:142— apps/bondy_router/src/bondy_router_worker.erl:142-170 | apps/bondy_router/src/bondy_router_worker.erl:197-225 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) apps/bondy_router/src/bondy_auth.erl:865— apps/bondy_router/src/bondy_auth.erl:865-907 | apps/bondy_router/src/bondy_auth.erl:910-938 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×2
Edited copies of one member (3 members, 18+ corresponding lines) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:50— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:50-67 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:34-52 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl:54-73 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 18+ corresponding lines) apps/bondy_mst/src/bondy_mst_pack_reader.erl:153— apps/bondy_mst/src/bondy_mst_pack_reader.erl:153-170 | apps/bondy_mst/src/bondy_mst_pack_store.erl:1177-1196 | apps/bondy_mst/src/bondy_mst_pack_store.erl:1448-1465 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) apps/bondy_router/src/bondy_router_peer.erl:278— apps/bondy_router/src/bondy_router_peer.erl:278-297 | apps/bondy_router/src/bondy_router_peer.erl:301-333 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) apps/bondy_router/src/bondy_bridge_relay_server.erl:610— apps/bondy_router/src/bondy_bridge_relay_server.erl:610-629 | apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:405-430 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 3+ corresponding lines) · ×2
Edited copies of one member (3 members, 3+ corresponding lines) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:134— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:134-136 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:153-155 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl:161-163 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 3+ corresponding lines) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:116— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:116-118 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:135-137 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl:143-145 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 2+ corresponding lines) · ×2
Edited copies of one member (3 members, 2+ corresponding lines) apps/bondy_log/src/bondy_log_wal.erl:365— apps/bondy_log/src/bondy_log_wal.erl:365-368 | apps/bondy_oplog/src/bondy_oplog_instance.erl:580-583 | apps/bondy_oplog/src/bondy_oplog_wal_mem.erl:148-149 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 2+ corresponding lines) apps/bondy_log/src/bondy_log_wal.erl:791— apps/bondy_log/src/bondy_log_wal.erl:791-794 | apps/bondy_oplog/src/bondy_oplog_instance.erl:2398-2401 | apps/bondy_oplog/src/bondy_oplog_wal_mem.erl:222-223 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (19–21 lines × 2) apps/bondy_oplog/src/bondy_oplog_applier.erl:1678— apps/bondy_oplog/src/bondy_oplog_applier.erl:1678-1696 | apps/bondy_oplog/src/bondy_oplog_instance.erl:3438-3458 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_applier.erl` and `apps/bondy_oplog/src/bondy_oplog_instance.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_instance.erl:3438` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–21 lines × 2) apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:227— apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:227-247 | apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:964-982 — 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 (19–20 lines × 2) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:450— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:450-469 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:396-414 — before extracting anything, compare `apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl` and `apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:450` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 2) apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:1097— apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:1097-1115 | apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:1157-1176 — 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 (18 lines × 2) apps/bondy_router/src/bondy_bridge_relay_server.erl:612— apps/bondy_router/src/bondy_bridge_relay_server.erl:612-629 | apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:413-430 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_bridge_relay_server.erl:612` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) apps/bondy_router/src/bondy_http_longpoll_handler.erl:450— apps/bondy_router/src/bondy_http_longpoll_handler.erl:450-467 | apps/bondy_router/src/bondy_http_sse_handler.erl:326-343 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_http_sse_handler.erl:326` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 3) apps/bondy_connect_sdk/src/bondy_connect_telemetry.erl:93— apps/bondy_connect_sdk/src/bondy_connect_telemetry.erl:93-108 | apps/bondy_mcp/src/bondy_mcp_wamp.erl:130-145 | apps/bondy_router/src/bondy_telemetry.erl:604-619 — 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 (16 lines × 3) apps/bondy_router/src/bondy_http_longpoll_handler.erl:281— apps/bondy_router/src/bondy_http_longpoll_handler.erl:281-296 | apps/bondy_router/src/bondy_http_longpoll_handler.erl:340-355 | apps/bondy_router/src/bondy_http_sse_handler.erl:222-237 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 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–16 lines × 2) apps/bondy_router/src/bondy_http_longpoll_handler.erl:410— apps/bondy_router/src/bondy_http_longpoll_handler.erl:410-425 | apps/bondy_router/src/bondy_http_sse_handler.erl:291-305 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 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–16 lines × 2) bench/lib/bench/concurrency.ex:242— bench/lib/bench/concurrency.ex:242-257 | bench/lib/bench/e2e.ex:459-473 — before extracting anything, compare `bench/lib/bench/concurrency.ex` and `bench/lib/bench/e2e.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 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–15 lines × 2) apps/bondy_db/src/bondy_db_topology_per_entity.erl:94— apps/bondy_db/src/bondy_db_topology_per_entity.erl:94-108 | apps/bondy_db/src/bondy_db_topology_shared_shards.erl:108-121 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–15 lines × 2) apps/bondy_router/src/bondy_rbac_group.erl:829— apps/bondy_router/src/bondy_rbac_group.erl:829-842 | apps/bondy_router/src/bondy_rbac_user.erl:1912-1926 — before extracting anything, compare `apps/bondy_router/src/bondy_rbac_group.erl` and `apps/bondy_router/src/bondy_rbac_user.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_rbac_group.erl:829` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–15 lines × 2) apps/bondy_router/src/bondy_rbac.erl:450— apps/bondy_router/src/bondy_rbac.erl:450-462 | apps/bondy_router/src/bondy_rbac.erl:1376-1390 — 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) apps/bondy_router/src/bondy_router_peer.erl:279— apps/bondy_router/src/bondy_router_peer.erl:279-291 | apps/bondy_router/src/bondy_router_peer.erl:302-316 — 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–14 lines × 2) apps/bondy_mst/src/bondy_mst_pack_writer.erl:1026— apps/bondy_mst/src/bondy_mst_pack_writer.erl:1026-1036 | apps/bondy_mst/src/bondy_mst_pack_writer.erl:1139-1152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_mst/src/bondy_mst_pack_writer.erl:1026` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–14 lines × 2) apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:1350— apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:1350-1363 | apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:1405-1415 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:1350` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) apps/bondy_oplog/src/bondy_oplog_instance.erl:2959— apps/bondy_oplog/src/bondy_oplog_instance.erl:2959-2971 | apps/bondy_oplog/src/bondy_oplog_instance.erl:2979-2991 — 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 × 2) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:32— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:32-44 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl:36-48 — before extracting anything, compare `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl` and `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 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 × 3) apps/bondy_mst/src/bondy_mst_ets_store.erl:217— apps/bondy_mst/src/bondy_mst_ets_store.erl:217-226 | apps/bondy_mst/src/bondy_mst_map_store.erl:141-150 | apps/bondy_mst/src/bondy_mst_pack_store.erl:523-532 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_mst/src/bondy_mst_ets_store.erl:217` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apps/bondy_mst/src/bondy_mst_ets_store.erl:227` calls `insert` and `apps/bondy_mst/src/bondy_mst_map_store.erl:151` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:465— apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:465-474 | apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl:348-357 | apps/bondy_oplog/src/bondy_oplog_crdt_struct.erl:459-468 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl` and `apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl` as WHOLE FILES: this scan already matched 6 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 (17 lines × 2) apps/bondy_router/src/bondy_task_catalogue.erl:175— apps/bondy_router/src/bondy_task_catalogue.erl:175-192 | apps/bondy_router/src/bondy_task_catalogue.erl:203-219 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_task_catalogue.erl:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) apps/bondy_router/src/bondy_task_catalogue.erl:296— apps/bondy_router/src/bondy_task_catalogue.erl:296-312 | apps/bondy_router/src/bondy_task_catalogue.erl:322-338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_task_catalogue.erl:296` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
bondy_oplog_instance.do_handle_call (cyclomatic 118) apps/bondy_oplog/src/bondy_oplog_instance.erl:2946— bondy_oplog_instance.do_handle_call has cyclomatic complexity 118 (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.
bondy_rbac_api.handle_call (cyclomatic 95) apps/bondy_router/src/bondy_rbac_api.erl:38— bondy_rbac_api.handle_call has cyclomatic complexity 95 (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.
bondy_prometheus_db.do_handle_event (cyclomatic 74) apps/bondy_telemetry_exporter/src/bondy_prometheus_db.erl:611— bondy_prometheus_db.do_handle_event has cyclomatic complexity 74 (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.
bondy_wamp_encoding.unpack (cyclomatic 66) apps/bondy_wamp/src/bondy_wamp_encoding.erl:285— bondy_wamp_encoding.unpack has cyclomatic complexity 66 (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.
mops.apply_custom_op (cyclomatic 56) apps/mops/src/mops.erl:582— mops.apply_custom_op has cyclomatic complexity 56 (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.
bondy_connect_error.convert (cyclomatic 43) apps/bondy_connect_lib/src/bondy_connect_error.erl:663— bondy_connect_error.convert has cyclomatic complexity 43 (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. This is NOT this file's highest cyclomatic complexity: bondy_connect_error.entry (cyclomatic 109) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
bondy_connect_connection.established (cyclomatic 42) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:478— bondy_connect_connection.established has cyclomatic complexity 42 (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.
bondy_connect_table_manager.handle_call (cyclomatic 34) apps/bondy_connect_lib/src/bondy_connect_table_manager.erl:229— bondy_connect_table_manager.handle_call has cyclomatic complexity 34 (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.
bondy_log_wal.handle_call (cyclomatic 34) apps/bondy_log/src/bondy_log_wal.erl:899— bondy_log_wal.handle_call has cyclomatic complexity 34 (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.
bondy_prometheus.handle_net_event (cyclomatic 33) apps/bondy_telemetry_exporter/src/bondy_prometheus.erl:652— bondy_prometheus.handle_net_event has cyclomatic complexity 33 (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.
bondy_oplog_responder.dispatch (cyclomatic 31) apps/bondy_oplog/src/bondy_oplog_responder.erl:179— bondy_oplog_responder.dispatch has cyclomatic complexity 31 (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.
bondy_bridge_relay_client.handle_event (cyclomatic 30) apps/bondy_router/src/bondy_bridge_relay_client.erl:555— bondy_bridge_relay_client.handle_event has cyclomatic complexity 30 (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.
bondy_bridge_relay_api.handle_call (cyclomatic 26) apps/bondy_router/src/bondy_bridge_relay_api.erl:30— bondy_bridge_relay_api.handle_call has cyclomatic complexity 26 (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.
bondy_http_transport_session.handle_call (cyclomatic 25) apps/bondy_router/src/bondy_http_transport_session.erl:514— bondy_http_transport_session.handle_call has cyclomatic complexity 25 (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.
bondy_bridge_relay_server.active (cyclomatic 24) apps/bondy_router/src/bondy_bridge_relay_server.erl:278— bondy_bridge_relay_server.active has cyclomatic complexity 24 (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.
fleet_smoke.runSubscriber (cyclomatic 24) harness/k6/fleet_smoke.js:255— fleet_smoke.runSubscriber has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 3 of the 24 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 273, 335, 345, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
bondy_dealer.forward_call (cyclomatic 23) apps/bondy_router/src/bondy_dealer.erl:911— bondy_dealer.forward_call has cyclomatic complexity 23 (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.
bondy_wamp_message.set_partial (cyclomatic 22) apps/bondy_wamp/src/bondy_wamp_message.erl:711— bondy_wamp_message.set_partial has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions — but note WHERE they are: these tests sit in guard sequences, and a guard is a restricted expression sublanguage that allows neither binding a local nor calling a function you wrote, so neither of those moves is available in place. Move the decision out of the guard instead: keep one clause with a permissive guard, compute the compound test in the body through named predicate functions, and dispatch on their result. Where the clauses genuinely differ by pattern rather than by test, keep the patterns and lift only the comma-conjunctions. This is NOT this file's highest cyclomatic complexity: bondy_wamp_message.is_message (cyclomatic 25) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
bondy_connect_connection.handle_common (cyclomatic 21) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:681— bondy_connect_connection.handle_common has cyclomatic complexity 21 (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.
bondy_prometheus_db.collect_leveled (cyclomatic 18) apps/bondy_telemetry_exporter/src/bondy_prometheus_db.erl:1424— bondy_prometheus_db.collect_leveled has cyclomatic complexity 18 (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.
bondy_ref.validate_target (cyclomatic 17) apps/bondy_router/src/bondy_ref.erl:443— bondy_ref.validate_target has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
bondy_ticket.verify (cyclomatic 17) apps/bondy_router/src/bondy_ticket.erl:356— bondy_ticket.verify has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
mops.eval_expr (cyclomatic 17) apps/mops/src/mops.erl:271— mops.eval_expr has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: mops.apply_op (cyclomatic 42) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
bondy_interface.load (cyclomatic 16) apps/bondy_router/src/bondy_interface.erl:200— bondy_interface.load has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Hotspot: apps/bondy_router/src/bondy_rbac_api.erl apps/bondy_router/src/bondy_rbac_api.erl:38— apps/bondy_router/src/bondy_rbac_api.erl changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 95 in bondy_rbac_api.handle_call at line 38. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:16:27 +00:00' --until='2026-11-13 21:16:27 +00:00' --full-history --no-merges -- apps/bondy_router/src/bondy_rbac_api.erl`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FixmeComment apps/bondy_router/src/bondy_router_peer.erl:470— %% FIXME we need to fix the wamp.hrl timeout — 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.
bondy_oplog_instance.do_handle_call (cognitive 47) apps/bondy_oplog/src/bondy_oplog_instance.erl:2946— bondy_oplog_instance.do_handle_call has cognitive complexity 47 (threshold 15). Drivers by points: match/switch 32 (42 pts), boolean chains 4, if/else 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.
bondy_prometheus_db.collect_leveled (cognitive 41) apps/bondy_telemetry_exporter/src/bondy_prometheus_db.erl:1424— bondy_prometheus_db.collect_leveled has cognitive complexity 41 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 7 (13 pts), match/switch 8 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bondy_rbac_api.handle_call (cognitive 35) apps/bondy_router/src/bondy_rbac_api.erl:38— bondy_rbac_api.handle_call has cognitive complexity 35 (threshold 15). Drivers by points: match/switch 28, loops 6, error handling 1. 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.
fleet_smoke.runSubscriber (cognitive 34) harness/k6/fleet_smoke.js:255— fleet_smoke.runSubscriber has cognitive complexity 34 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 11). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 273, 335, 345, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
bondy_oplog_responder.dispatch (cognitive 31) apps/bondy_oplog/src/bondy_oplog_responder.erl:179— bondy_oplog_responder.dispatch has cognitive complexity 31 (threshold 15). Drivers by points: match/switch 17 (24 pts), if/else 2 (4 pts), boolean chains 3 (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.
mops.apply_custom_op (cognitive 28) apps/mops/src/mops.erl:582— mops.apply_custom_op has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 18, loops 7 (9 pts), boolean chains 1 (nesting depth added 2). 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.
bondy_wamp_encoding.unpack (cognitive 24) apps/bondy_wamp/src/bondy_wamp_encoding.erl:285— bondy_wamp_encoding.unpack has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 24. To reduce it, name the conditions — but note WHERE they are: these tests sit in guard sequences, and a guard is a restricted expression sublanguage that allows neither binding a local nor calling a function you wrote, so neither of those moves is available in place. Move the decision out of the guard instead: keep one clause with a permissive guard, compute the compound test in the body through named predicate functions, and dispatch on their result. Where the clauses genuinely differ by pattern rather than by test, keep the patterns and lift only the comma-conjunctions.
bondy_oplog_cell_apply.unapplied_contexts (cognitive 21) apps/bondy_oplog/src/bondy_oplog_cell_apply.erl:1383— bondy_oplog_cell_apply.unapplied_contexts has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 4 (10 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bondy_prometheus.handle_net_event (cognitive 21) apps/bondy_telemetry_exporter/src/bondy_prometheus.erl:652— bondy_prometheus.handle_net_event has cognitive complexity 21 (threshold 15). Drivers by points: error handling 10, match/switch 5 (10 pts), boolean chains 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.
bondy_oplog_cell_utils.member_cells (cognitive 19) apps/bondy_oplog/src/bondy_oplog_cell_utils.erl:86— bondy_oplog_cell_utils.member_cells has cognitive complexity 19 (threshold 15). Drivers by points: if/else 2 (7 pts), loops 2 (5 pts), match/switch 3 (4 pts), boolean chains 3 (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.
bondy_auth.apply_authroles_cap (cognitive 19) apps/bondy_router/src/bondy_auth.erl:980— bondy_auth.apply_authroles_cap has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 6 (12 pts), if/else 1 (4 pts), loops 1 (3 pts) (nesting depth added 11). 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.
bondy_mcp_wamp.resolve_update_topic (cognitive 18) apps/bondy_mcp/src/bondy_mcp_wamp.erl:433— bondy_mcp_wamp.resolve_update_topic has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 8 (15 pts), error handling 1 (3 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.
bondy_rbac_user.remove (cognitive 17) apps/bondy_router/src/bondy_rbac_user.erl:653— bondy_rbac_user.remove has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (6 pts), loops 2 (4 pts), match/switch 1 (3 pts), boolean chains 2, error handling 2 (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.
bondy_log_scrubber.walk_all_segments (cognitive 16) apps/bondy_log/src/bondy_log_scrubber.erl:282— bondy_log_scrubber.walk_all_segments has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (6 pts), loops 3 (6 pts), error handling 2, match/switch 2 (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.
D4 · Code Duplication· Edited copy of a member (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:659— apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:659-711 | apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:718-768 — These two members are one piece of code written twice and then edited apart: 51 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 (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) apps/bondy_router/src/bondy_http_gateway_api.erl:36— apps/bondy_router/src/bondy_http_gateway_api.erl:36-83 | apps/bondy_router/src/bondy_interface_api.erl:41-82 — These two members are one piece of code written twice and then edited apart: 42 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 (64 corresponding lines) · ×1
Edited copy of a member (64 corresponding lines) apps/bondy_router/src/bondy_rpc_promise.erl:132— apps/bondy_router/src/bondy_rpc_promise.erl:132-195 | apps/bondy_router/src/bondy_rpc_promise.erl:209-275 — These two members are one piece of code written twice and then edited apart: 64 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 (63 corresponding lines) · ×1
Edited copy of a member (63 corresponding lines) apps/bondy_router/src/bondy_http_longpoll_handler.erl:191— apps/bondy_router/src/bondy_http_longpoll_handler.erl:191-255 | apps/bondy_router/src/bondy_http_sse_handler.erl:134-196 — These two members are one piece of code written twice and then edited apart: 63 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) apps/bondy_mst/src/bondy_mst.erl:2530— apps/bondy_mst/src/bondy_mst.erl:2530-2569 | apps/bondy_mst/src/bondy_mst.erl:2572-2614 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) apps/bondy_oplog/src/bondy_oplog_instance.erl:684— apps/bondy_oplog/src/bondy_oplog_instance.erl:684-747 | apps/bondy_oplog/src/bondy_oplog_instance.erl:812-864 — These two members are one piece of code written twice and then edited apart: 53 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 (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) apps/bondy_mst/src/bondy_mst_admin.erl:126— apps/bondy_mst/src/bondy_mst_admin.erl:126-160 | apps/bondy_mst/src/bondy_mst_admin.erl:228-269 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 26+ corresponding lines) · ×1
Edited copies of one member (4 members, 26+ corresponding lines) apps/bondy_mst/src/bondy_mst.erl:1623— apps/bondy_mst/src/bondy_mst.erl:1623-1654 | apps/bondy_mst/src/bondy_mst.erl:1657-1686 | apps/bondy_mst/src/bondy_mst.erl:1803-1828 | apps/bondy_mst/src/bondy_mst.erl:2340-2365 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:228— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:228-257 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:201-234 — These two members are one piece of code written twice and then edited apart: 30 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 (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) apps/bondy_db/src/bondy_db.erl:1992— apps/bondy_db/src/bondy_db.erl:1992-2028 | apps/bondy_db/src/bondy_db.erl:2056-2091 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) apps/bondy_router/src/bondy_http_gateway_api_spec_parser.erl:1939— apps/bondy_router/src/bondy_http_gateway_api_spec_parser.erl:1939-1979 | apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:1511-1557 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) apps/bondy_router/src/bondy_bridge_relay_client.erl:788— apps/bondy_router/src/bondy_bridge_relay_client.erl:788-821 | apps/bondy_router/src/bondy_bridge_relay_client.erl:824-856 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_sup.erl:15— apps/bondy_regulator/src/bondy_regulator_sup.erl:22-68 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_sup.erl:15-63 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 33+ corresponding lines) · ×1
Edited copies of one member (3 members, 33+ corresponding lines) REDACTED:80— REDACTED:80-112 | REDACTED:159-191 | REDACTED:186-218 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 33 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) apps/bondy_oplog/src/bondy_oplog_core.erl:531— apps/bondy_oplog/src/bondy_oplog_core.erl:531-554 | apps/bondy_oplog/src/bondy_oplog_core.erl:565-585 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:251— jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:251-274 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:330-352 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:381-404 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) apps/bondy_router/src/bondy_data_validators.erl:138— apps/bondy_router/src/bondy_data_validators.erl:138-164 | apps/bondy_router/src/bondy_data_validators.erl:274-306 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) apps/bondy_oplog/src/bondy_oplog_instance.erl:985— apps/bondy_oplog/src/bondy_oplog_instance.erl:985-1010 | apps/bondy_oplog/src/bondy_oplog_instance.erl:6010-6038 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) apps/bondy_mst/src/bondy_mst.erl:2130— apps/bondy_mst/src/bondy_mst.erl:2130-2146 | apps/bondy_mst/src/bondy_mst.erl:2383-2399 | apps/bondy_mst/src/bondy_mst_ets_store.erl:307-323 | apps/bondy_mst/src/bondy_mst_store.erl:485-502 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_tcp.erl:46— apps/bondy_connect_sdk/src/bondy_connect_transport_tcp.erl:46-55 | apps/bondy_connect_sdk/src/bondy_connect_transport_tls.erl:52-61 | apps/bondy_connect_sdk/src/bondy_connect_transport_uds.erl:50-59 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) apps/bondy_mst/src/bondy_mst_ets_store.erl:216— apps/bondy_mst/src/bondy_mst_ets_store.erl:216-229 | apps/bondy_mst/src/bondy_mst_map_store.erl:140-152 | apps/bondy_mst/src/bondy_mst_pack_store.erl:522-535 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:553— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:553-577 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:480-496 | apps/bondy_connect_sdk/src/bondy_connect_transport_ws.erl:332-343 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) apps/bondy_mcp/src/bondy_mcp_sup.erl:39— apps/bondy_mcp/src/bondy_mcp_sup.erl:39-54 | apps/bondy_mcp/src/bondy_mcp_sup.erl:64-79 | apps/bondy_mcp/src/bondy_mcp_sup.erl:90-105 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 6+ corresponding lines) · ×1
Edited copies of one member (4 members, 6+ corresponding lines) apps/bondy_router/src/bondy_registry_store.erl:1041— apps/bondy_router/src/bondy_registry_store.erl:1041-1046 | apps/bondy_router/src/bondy_registry_store.erl:1068-1077 | apps/bondy_router/src/bondy_registry_store.erl:1201-1210 | apps/bondy_router/src/bondy_registry_store.erl:1233-1242 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) apps/bondy_log/src/bondy_log_io.erl:106— apps/bondy_log/src/bondy_log_io.erl:106-121 | apps/bondy_mst/src/bondy_mst_io.erl:165-176 | apps/bondy_mst/src/bondy_mst_pack_seal.erl:288-304 | apps/bondy_mst/src/bondy_mst_pack_writer.erl:889-902 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) apps/bondy_router/src/bondy_registry_ptrie.erl:374— apps/bondy_router/src/bondy_registry_ptrie.erl:374-383 | apps/bondy_router/src/bondy_registry_ptrie.erl:404-411 | apps/bondy_router/src/bondy_registry_ptrie.erl:425-432 | apps/bondy_router/src/bondy_registry_ptrie.erl:444-451 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_registry.erl:141— apps/bondy_connect_sdk/src/bondy_connect_registry.erl:141-150 | apps/bondy_connect_sdk/src/bondy_connect_registry.erl:157-166 | apps/bondy_connect_sdk/src/bondy_connect_registry.erl:177-187 | apps/bondy_connect_sdk/src/bondy_connect_registry.erl:191-201 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 15+ corresponding lines) · ×1
Edited copies of one member (5 members, 15+ corresponding lines) apps/bondy_connect_sdk/src/bondy_connect_connections_sup.erl:39— apps/bondy_connect_sdk/src/bondy_connect_connections_sup.erl:39-55 | apps/bondy_connect_sdk/src/bondy_connect_handler_sup.erl:39-53 | apps/bondy_oplog/src/bondy_oplog_instance_dyn_sup.erl:151-165 | apps/bondy_router/src/bondy_http_transport_session_sup.erl:70-85 | apps/bondy_router/src/bondy_oidc_provider_sup.erl:47-64 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) apps/bondy_router/src/bondy_http_longpoll_handler.erl:522— apps/bondy_router/src/bondy_http_longpoll_handler.erl:522-536 | apps/bondy_router/src/bondy_http_sse_handler.erl:380-394 | apps/bondy_router/src/bondy_oidc_handler.erl:1042-1056 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 10+ corresponding lines) · ×1
Edited copies of one member (6 members, 10+ corresponding lines) apps/bondy_wamp/src/bondy_wamp_message.erl:231— apps/bondy_wamp/src/bondy_wamp_message.erl:231-244 | apps/bondy_wamp/src/bondy_wamp_message.erl:294-304 | apps/bondy_wamp/src/bondy_wamp_message.erl:362-372 | apps/bondy_wamp/src/bondy_wamp_message.erl:431-441 | apps/bondy_wamp/src/bondy_wamp_message.erl:464-473 | apps/bondy_wamp/src/bondy_wamp_message.erl:545-555 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:184— apps/bondy_oplog/src/bondy_oplog_crdt_g_counter.erl:184-186 | apps/bondy_oplog/src/bondy_oplog_crdt_g_set.erl:141-143 | apps/bondy_oplog/src/bondy_oplog_crdt_owned_reading.erl:198-200 | apps/bondy_oplog/src/bondy_oplog_crdt_pn_counter.erl:190-192 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 3+ corresponding lines) · ×1
Edited copies of one member (5 members, 3+ corresponding lines) apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:496— apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:496-498 | apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl:371-373 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_map.erl:314-319 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_set.erl:237-239 | apps/bondy_oplog/src/bondy_oplog_crdt_struct.erl:483-489 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) apps/bondy_log/src/bondy_log_io.erl:127— apps/bondy_log/src/bondy_log_io.erl:127-131 | apps/bondy_log/src/bondy_log_recovery.erl:202-206 | apps/bondy_oplog/src/bondy_oplog_bootstrap_lifecycle.erl:261-265 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) apps/bondy_oplog/src/bondy_oplog_catalogue_cursor.erl:438— apps/bondy_oplog/src/bondy_oplog_catalogue_cursor.erl:438-443 | apps/bondy_oplog/src/bondy_oplog_responder.erl:422-427 | apps/bondy_router/src/bondy_oidc_refresh_worker.erl:143-148 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (47–49 lines × 2) apps/bondy_router/src/bondy_http_longpoll_handler.erl:209— apps/bondy_router/src/bondy_http_longpoll_handler.erl:209-255 | apps/bondy_router/src/bondy_http_sse_handler.erl:148-196 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_http_sse_handler.erl:148` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (32–43 lines × 3) apps/bondy_router/src/bondy_bridge_relay_server.erl:1098— apps/bondy_router/src/bondy_bridge_relay_server.erl:1098-1129 | apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl:791-833 | apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl:707-738 — before extracting anything, compare `apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl` and `apps/bondy_router/src/bondy_wamp_ws_connection_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_bridge_relay_server.erl:1098` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (37 lines × 2) REDACTED:104— REDACTED:104-140 | REDACTED:131-167 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:104` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31–35 lines × 2) apps/bondy_router/src/bondy_rbac.erl:1124— apps/bondy_router/src/bondy_rbac.erl:1124-1154 | apps/bondy_router/src/bondy_rbac.erl:1234-1268 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_rbac.erl:1124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30–31 lines × 3) apps/bondy_router/src/bondy_http_longpoll_handler.erl:471— apps/bondy_router/src/bondy_http_longpoll_handler.erl:471-501 | apps/bondy_router/src/bondy_http_sse_handler.erl:347-377 | apps/bondy_router/src/bondy_http_sse_stream_handler.erl:184-213 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_http_sse_handler.erl:347` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24–28 lines × 2) apps/bondy_router/src/bondy_jobs_sup.erl:56— apps/bondy_router/src/bondy_jobs_sup.erl:56-79 | apps/bondy_router/src/bondy_oidc_refresh_sup.erl:72-99 — before extracting anything, compare `apps/bondy_router/src/bondy_jobs_sup.erl` and `apps/bondy_router/src/bondy_oidc_refresh_sup.erl` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_jobs_sup.erl:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2) apps/bondy_router/src/bondy_rpc_promise.erl:141— apps/bondy_router/src/bondy_rpc_promise.erl:141-167 | apps/bondy_router/src/bondy_rpc_promise.erl:218-244 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apps/bondy_router/src/bondy_rpc_promise.erl:245` calls `session_id` and `apps/bondy_router/src/bondy_rpc_promise.erl:169` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17–26 lines × 2) apps/bondy_router/src/bondy_http_longpoll_handler.erl:310— apps/bondy_router/src/bondy_http_longpoll_handler.erl:310-326 | apps/bondy_router/src/bondy_http_sse_handler.erl:239-264 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_http_sse_handler.erl:239` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) REDACTED:167— REDACTED:167-191 | REDACTED:194-218 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:688— apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:688-711 | apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:745-768 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:688` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18–24 lines × 2) apps/bondy_router/src/bondy_registry_ptrie.erl:741— apps/bondy_router/src/bondy_registry_ptrie.erl:741-764 | apps/bondy_router/src/bondy_registry_ptrie.erl:847-864 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_registry_ptrie.erl:741` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 3) apps/bondy_router/src/bondy_aae_reactor_sup.erl:84— apps/bondy_router/src/bondy_aae_reactor_sup.erl:84-106 | apps/bondy_router/src/bondy_jobs_sup.erl:61-83 | apps/bondy_router/src/bondy_oidc_refresh_sup.erl:81-103 — before extracting anything, compare `apps/bondy_router/src/bondy_jobs_sup.erl` and `apps/bondy_router/src/bondy_oidc_refresh_sup.erl` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_aae_reactor_sup.erl:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) REDACTED:229— REDACTED:229-250 | REDACTED:254-275 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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 (21 lines × 2) apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:1050— apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:1050-1070 | apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:1120-1140 — 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 (17–20 lines × 2) apps/bondy_connect_sdk/src/bondy_connect_connection.erl:511— apps/bondy_connect_sdk/src/bondy_connect_connection.erl:511-530 | apps/bondy_connect_sdk/src/bondy_connect_connection.erl:544-560 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_connect_sdk/src/bondy_connect_connection.erl:511` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 4) apps/bondy_router/src/bondy_aae_reactor_sup.erl:92— apps/bondy_router/src/bondy_aae_reactor_sup.erl:92-110 | apps/bondy_router/src/bondy_jobs_sup.erl:69-87 | apps/bondy_router/src/bondy_oidc_refresh_sup.erl:89-107 | apps/bondy_router/src/bondy_registry_sup.erl:82-100 — before extracting anything, compare `apps/bondy_router/src/bondy_jobs_sup.erl` and `apps/bondy_router/src/bondy_oidc_refresh_sup.erl` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_aae_reactor_sup.erl:92` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–19 lines × 2) apps/bondy_router/src/bondy_bridge_relay_client.erl:528— apps/bondy_router/src/bondy_bridge_relay_client.erl:528-546 | apps/bondy_router/src/bondy_bridge_relay_server.erl:491-507 — before extracting anything, compare `apps/bondy_router/src/bondy_bridge_relay_client.erl` and `apps/bondy_router/src/bondy_bridge_relay_server.erl` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_bridge_relay_client.erl:528` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 3) apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:266— apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:266-283 | apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:691-708 | apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:748-765 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_http_gateway_rest_handler.erl:266` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–18 lines × 2) apps/bondy_db/src/bondy_db.erl:887— apps/bondy_db/src/bondy_db.erl:887-904 | apps/bondy_db/src/bondy_db.erl:959-972 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_db/src/bondy_db.erl:887` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–17 lines × 2) apps/bondy_router/src/bondy_registry_ptrie.erl:1043— apps/bondy_router/src/bondy_registry_ptrie.erl:1043-1054 | apps/bondy_router/src/bondy_registry_ptrie.erl:1116-1132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_registry_ptrie.erl:1043` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 4) apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:410— apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:410-424 | apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl:268-282 | apps/bondy_oplog/src/bondy_oplog_crdt_ew_flag.erl:171-185 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_map.erl:231-245 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl` and `apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl` as WHOLE FILES: this scan already matched 6 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 (9–15 lines × 2) apps/bondy_log/src/bondy_log_wal.erl:1707— apps/bondy_log/src/bondy_log_wal.erl:1707-1721 | apps/bondy_log/src/bondy_log_wal.erl:1762-1770 — 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) apps/bondy_telemetry_exporter/src/bondy_prometheus_collector.erl:63— apps/bondy_telemetry_exporter/src/bondy_prometheus_collector.erl:63-77 | apps/bondy_telemetry_exporter/src/bondy_prometheus_db.erl:169-183 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_telemetry_exporter/src/bondy_prometheus_collector.erl:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `apps/bondy_telemetry_exporter/src/bondy_prometheus_collector.erl:61` calls `collect_bondy_metrics_families` and `apps/bondy_telemetry_exporter/src/bondy_prometheus_db.erl:167` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–14 lines × 2) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:322— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:322-335 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:293-304 — before extracting anything, compare `apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl` and `apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 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 (3–14 lines × 4) apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:322— apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:322-331 | apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl:182-195 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_map.erl:156-159 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_set.erl:140-142 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl` and `apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl` as WHOLE FILES: this scan already matched 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:331` calls `max`, `key_hlc` and `apps/bondy_oplog/src/bondy_oplog_crdt_rw_set.erl:142` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–13 lines × 3) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:101— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:101-110 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:115-127 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl:117-126 — before extracting anything, compare `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl` and `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 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–13 lines × 2) apps/mops/src/mops.erl:709— apps/mops/src/mops.erl:709-719 | apps/mops/src/mops.erl:728-740 — 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–12 lines × 3) apps/bondy_router/src/bondy_http_longpoll_handler.erl:49— apps/bondy_router/src/bondy_http_longpoll_handler.erl:49-59 | apps/bondy_router/src/bondy_http_sse_handler.erl:32-43 | apps/bondy_router/src/bondy_oidc_handler.erl:31-41 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 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 × 3) apps/bondy_router/src/bondy_http_longpoll_handler.erl:525— apps/bondy_router/src/bondy_http_longpoll_handler.erl:525-536 | apps/bondy_router/src/bondy_http_sse_handler.erl:383-394 | apps/bondy_router/src/bondy_oidc_handler.erl:1045-1056 — before extracting anything, compare `apps/bondy_router/src/bondy_http_longpoll_handler.erl` and `apps/bondy_router/src/bondy_http_sse_handler.erl` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 219 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–11 lines × 2) apps/bondy_oplog/src/bondy_oplog_core_metrics.erl:301— apps/bondy_oplog/src/bondy_oplog_core_metrics.erl:301-311 | apps/bondy_oplog/src/bondy_oplog_latency.erl:311-319 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_core_metrics.erl:301` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–10 lines × 2) apps/bondy_db/src/bondy_db.erl:2121— apps/bondy_db/src/bondy_db.erl:2121-2128 | apps/bondy_db/src/bondy_db.erl:2158-2167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_db/src/bondy_db.erl:2121` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–10 lines × 2) apps/bondy_mcp/src/bondy_mcp_client.erl:243— apps/bondy_mcp/src/bondy_mcp_client.erl:243-252 | apps/bondy_mcp/src/bondy_mcp_client.erl:269-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 (9 lines × 3) apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:462— apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl:462-471 | apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl:408-416 | apps/bondy_connect_sdk/src/bondy_connect_transport_ws.erl:296-305 — before extracting anything, compare `apps/bondy_connect_sdk/src/bondy_connect_transport_longpoll.erl` and `apps/bondy_connect_sdk/src/bondy_connect_transport_sse.erl` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 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) apps/bondy_wamp/src/bondy_wamp_cbor.erl:388— apps/bondy_wamp/src/bondy_wamp_cbor.erl:388-395 | apps/bondy_wamp/src/bondy_wamp_cbor.erl:397-404 | apps/bondy_wamp/src/bondy_wamp_cbor.erl:406-413 | apps/bondy_wamp/src/bondy_wamp_cbor.erl:415-422 | apps/bondy_wamp/src/bondy_wamp_cbor.erl:423-431 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_wamp/src/bondy_wamp_cbor.erl:388` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) apps/bondy_router/src/bondy_rbac_api.erl:42— apps/bondy_router/src/bondy_rbac_api.erl:42-49 | apps/bondy_router/src/bondy_rbac_api.erl:74-81 | apps/bondy_router/src/bondy_rbac_api.erl:126-133 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_rbac_api.erl:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–8 lines × 2) apps/bondy_mst/src/bondy_mst_pack_store.erl:663— apps/bondy_mst/src/bondy_mst_pack_store.erl:663-670 | apps/bondy_mst/src/bondy_mst_pack_store.erl:809-814 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_mst/src/bondy_mst_pack_store.erl:809` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 11) apps/bondy_router/src/bondy_rbac_api.erl:150— apps/bondy_router/src/bondy_rbac_api.erl:150-156 | apps/bondy_router/src/bondy_rbac_api.erl:161-167 | apps/bondy_router/src/bondy_rbac_api.erl:172-178 | apps/bondy_router/src/bondy_rbac_api.erl:183-189 | apps/bondy_router/src/bondy_rbac_api.erl:196-202 | apps/bondy_router/src/bondy_rbac_api.erl:209-215 | apps/bondy_router/src/bondy_rbac_api.erl:284-290 | apps/bondy_router/src/bondy_rbac_api.erl:295-301 | apps/bondy_router/src/bondy_rbac_api.erl:308-314 | apps/bondy_router/src/bondy_rbac_api.erl:321-327 | apps/bondy_router/src/bondy_rbac_api.erl:379-385 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_rbac_api.erl:150` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–7 lines × 3) apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:321— apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:321-326 | apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl:181-187 | apps/bondy_oplog/src/bondy_oplog_crdt_rw_map.erl:149-154 — before extracting anything, compare `apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl` and `apps/bondy_oplog/src/bondy_oplog_crdt_aw_set.erl` as WHOLE FILES: this scan already matched 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_crdt_aw_map.erl:321` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6–7 lines × 2) apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1522— apps/bondy_mcp/src/bondy_mcp_http_handler.erl:1522-1528 | apps/bondy_mcp/src/bondy_mcp_stream.erl:395-400 — 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 × 10) apps/bondy_router/src/bondy_oauth2_api.erl:41— apps/bondy_router/src/bondy_oauth2_api.erl:41-46 | apps/bondy_router/src/bondy_oauth2_api.erl:62-67 | apps/bondy_router/src/bondy_oauth2_api.erl:86-91 | apps/bondy_router/src/bondy_oauth2_api.erl:107-112 | apps/bondy_router/src/bondy_rbac_api.erl:44-49 | apps/bondy_router/src/bondy_rbac_api.erl:76-81 | apps/bondy_router/src/bondy_rbac_api.erl:128-133 | apps/bondy_router/src/bondy_rbac_api.erl:234-239 | apps/bondy_router/src/bondy_rbac_api.erl:274-279 | apps/bondy_router/src/bondy_rbac_api.erl:369-374 — there are 10 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 10 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_router/src/bondy_oauth2_api.erl:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:50— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:50-55 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:34-39 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl:54-59 — before extracting anything, compare `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl` and `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 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 × 12) apps/bondy_metrics/src/bondy_metrics.erl:178— apps/bondy_metrics/src/bondy_metrics.erl:178-186 | apps/bondy_oplog/src/bondy_oplog_core_dispatcher.erl:145-153 | apps/bondy_oplog/src/bondy_oplog_core_events.erl:105-113 | apps/bondy_oplog/src/bondy_oplog_core_registry.erl:427-435 | apps/bondy_oplog/src/bondy_oplog_index_rebuild.erl:125-133 | apps/bondy_oplog/src/bondy_oplog_instance_keeper.erl:93-101 | apps/bondy_oplog/src/bondy_oplog_origin_bans.erl:148-156 | apps/bondy_oplog/src/bondy_oplog_origin_retirement.erl:215-223 | apps/bondy_oplog/src/bondy_oplog_quarantine.erl:97-105 | apps/bondy_oplog/src/bondy_oplog_registry.erl:311-319 | apps/bondy_oplog/src/bondy_oplog_responder.erl:157-165 | apps/bondy_router/src/bondy_registry_meta.erl:388-396 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 12 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 12 times. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_metrics/src/bondy_metrics.erl:178` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apps/bondy_metrics/src/bondy_metrics.erl:188` calls `start_link`, `pid`, `term` and `apps/bondy_oplog/src/bondy_oplog_core_dispatcher.erl:155` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 5) apps/bondy_oplog/src/bondy_oplog_catalogue_cursor.erl:167— apps/bondy_oplog/src/bondy_oplog_catalogue_cursor.erl:167-175 | apps/bondy_oplog/src/bondy_oplog_core_metrics.erl:127-135 | apps/bondy_oplog/src/bondy_oplog_latency.erl:126-134 | apps/bondy_oplog/src/bondy_oplog_peer_state.erl:129-137 | apps/bondy_oplog/src/bondy_oplog_sync_scheduler.erl:418-426 — 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 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_oplog/src/bondy_oplog_catalogue_cursor.erl:167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `apps/bondy_oplog/src/bondy_oplog_catalogue_cursor.erl:165` calls `child_spec` and `apps/bondy_oplog/src/bondy_oplog_core_metrics.erl:125` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 7) apps/bondy_router/src/bondy_aae_reactor_worker.erl:65— apps/bondy_regulator/src/bondy_regulator_load.erl:175-181 | apps/bondy_regulator/src/bondy_regulator_memory.erl:244-250 | apps/bondy_router/src/bondy_aae_reactor_worker.erl:65-71 | apps/bondy_router/src/bondy_reclaimer.erl:118-124 | apps/bondy_router/src/bondy_retained_message_manager.erl:234-240 | apps/bondy_router/src/bondy_router_worker.erl:317-323 | apps/bondy_router/src/bondy_system_gc.erl:54-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_regulator/src/bondy_regulator_load.erl:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apps/bondy_router/src/bondy_aae_reactor_worker.erl:73` calls `handle_cast`, `safe_react` and `apps/bondy_regulator/src/bondy_regulator_load.erl:183` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 4) apps/bondy_router/src/bondy_jobs_worker.erl:126— apps/bondy_router/src/bondy_jobs_worker.erl:126-134 | apps/bondy_router/src/bondy_registry.erl:672-680 | apps/bondy_router/src/bondy_retained_message_manager.erl:256-264 | apps/bondy_router/src/bondy_router_worker.erl:389-397 — 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 4 call sites, so a change lands once.
Duplicated block (5 lines × 3) jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:33— jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl:33-37 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl:17-21 | jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_set.erl:37-41 — before extracting anything, compare `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_counter.erl` and `jepsen/bondy_mst_jepsen/src/bondy_mst_jepsen_http_handler.erl` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 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 lines × 3) jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:280— jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:280-301 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:307-328 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:358-379 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:280` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:279— jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:279-286 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:306-313 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:357-364 | jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:410-417 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jepsen/jepsen.bondymst/src/main/java/io/leapsight/jepsen/Utils.java:279` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Near-duplicate member pair (45 shared lines) bench/lib/bench/concurrency.ex:116— bench/lib/bench/concurrency.ex:116-200 | bench/lib/bench/e2e.ex:50-268 — These two members are variants of one another: 45 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.
Duplicated block (9–10 lines × 2) apps/bondy_mcp/src/bondy_mcp_spec.erl:282— apps/bondy_mcp/src/bondy_mcp_spec.erl:282-290 | apps/bondy_mcp/src/bondy_mcp_spec.erl:312-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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/bondy_mcp/src/bondy_mcp_spec.erl:282` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18–19 lines × 2) bench/lib/bench/concurrency.ex:204— bench/lib/bench/concurrency.ex:204-222 | bench/lib/bench/e2e.ex:370-387 — before extracting anything, compare `bench/lib/bench/concurrency.ex` and `bench/lib/bench/e2e.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 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–17 lines × 2) bench/lib/bench/concurrency.ex:129— bench/lib/bench/concurrency.ex:129-145 | bench/lib/bench/e2e.ex:93-106 — before extracting anything, compare `bench/lib/bench/concurrency.ex` and `bench/lib/bench/e2e.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 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–16 lines × 2) bench/lib/bench/concurrency.ex:147— bench/lib/bench/concurrency.ex:147-162 | bench/lib/bench/e2e.ex:139-152 — before extracting anything, compare `bench/lib/bench/concurrency.ex` and `bench/lib/bench/e2e.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (59 lines × 2 locations) harness/k6/pubsub_smoke.js:33— harness/k6/pubsub_smoke.js:33 · harness/k6/rpc_smoke.js:20 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (51 matched lines × 2 locations) · ×1
Duplicated block with local edits (51 matched lines × 2 locations) harness/k6/fleet_smoke.js:191— harness/k6/fleet_smoke.js:191 · harness/k6/fleet_smoke.js:267 — the two spans are one implementation copied and then locally edited — 458 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (19 lines × 2 locations) harness/k6/pubsub_smoke.js:101— harness/k6/pubsub_smoke.js:101 · harness/k6/rpc_smoke.js:95 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function (anonymous) (cyclomatic 18, cognitive 28) harness/k6/fleet_smoke.js:273— (anonymous) has cyclomatic complexity 18 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 12) harness/k6/rpc_smoke.js:70— (anonymous) has cyclomatic complexity 12 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
No test or lint script — test ✗ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~367 LoC) harness/k6/fleet_smoke.js— no import path from any entry point (1 application, 0 tooling, 2 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~119 LoC) harness/k6/rpc_smoke.js— no import path from any entry point (1 application, 0 tooling, 2 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@modelcontextprotocol/conformance' — Declared in apps/bondy_mcp/test/bondy_mcp_e2e_SUITE_data/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Duplicated predicate apps/bondy_router/src/bondy_http_longpoll_handler.erl:491— `Authid =:= ExpAuthid andalso Authrealm2 =:= ExpAuthrealm` appears character-identically in 3 files — apps/bondy_router/src/bondy_http_longpoll_handler.erl, apps/bondy_router/src/bondy_http_sse_handler.erl, apps/bondy_router/src/bondy_http_sse_stream_handler.erl. 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 apps/bondy_mail/src/bondy_mail_worker.erl:617— `Limit == deadline orelse Limit == max_retries` appears character-identically in 5 files — apps/bondy_mail/src/bondy_mail_worker.erl, apps/bondy_router/src/bondy_bridge_relay_client.erl, apps/bondy_router/src/bondy_bridge_relay_server.erl, apps/bondy_router/src/bondy_wamp_tcp_connection_handler.erl. 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 apps/bondy_router/src/bondy_aae_reactor.erl:551— `NewKeys =/= undefined andalso NewKeys =/= maps` appears character-identically in 2 files — apps/bondy_router/src/bondy_aae_reactor.erl, apps/bondy_router/src/bondy_rbac_user.erl. 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 apps/bondy_router/src/bondy_aae_reactor.erl:545— `NewPassword =/= undefined andalso NewPassword =/= maps` appears character-identically in 2 files — apps/bondy_router/src/bondy_aae_reactor.erl, apps/bondy_router/src/bondy_rbac_user.erl. 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 REDACTED:238— `Status == 401 orelse Status == 402 orelse Status == 404` appears character-identically in 2 files — REDACTED, REDACTED. 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 apps/bondy_router/src/bondy_registry_entry.erl:18— `X == registration orelse X == subscription` appears character-identically in 3 files — apps/bondy_router/src/bondy_registry_entry.erl, apps/bondy_router/src/bondy_registry_partition.erl, apps/bondy_router/src/bondy_registry_store.erl. 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 apps/bondy_router/src/bondy_password_cra.erl:47— `byte_size(Bytes) == salt_length() orelse error(badarg)` appears character-identically in 2 files — apps/bondy_router/src/bondy_password_cra.erl, apps/bondy_router/src/bondy_password_scram.erl. 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 apps/bondy_mail/src/bondy_mail.erl:168— `is_binary(RealmUri) andalso is_binary(Id)` appears character-identically in 2 files — apps/bondy_mail/src/bondy_mail.erl, apps/bondy_mail/src/bondy_mail_status.erl. 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 apps/bondy_mcp/src/bondy_mcp_spec_parser.erl:94— `not is_list(Entries) orelse Entries == []` appears character-identically in 2 files — apps/bondy_mcp/src/bondy_mcp_spec_parser.erl, apps/bondy_router/src/bondy_interface.erl. 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 harness/k6/fleet_smoke.js:45— `__ENV.WS_URL || 'ws://localhost:18080/ws'` appears character-identically in 3 files — harness/k6/fleet_smoke.js, harness/k6/pubsub_smoke.js, harness/k6/rpc_smoke.js. 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.
X31 · Test-only surface in a production module· Test-only surface in a production module · ×8
Test-only surface in a production module apps/bondy_http_connector/src/bondy_http_connector_callee_handler.erl:64— `bondy_http_connector_callee_handler:interpolate_path/2` is exported unconditionally, and the comment directly above the `-export` on this line says the exports below it are for testing. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. This arm read the comment, not the call graph: if the comment is right and only tests call it, wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module. If production code calls it, the comment is stale and wrapping the export would break the build — delete the comment and document the function as part of the module's API.
Test-only surface in a production module apps/bondy_http_connector/src/bondy_http_connector_http_pool.erl:118— `bondy_http_connector_http_pool:liveness_url/2` is exported unconditionally, and the comment directly above the `-export` on this line says the exports below it are for testing. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. This arm read the comment, not the call graph: if the comment is right and only tests call it, wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module. If production code calls it, the comment is stale and wrapping the export would break the build — delete the comment and document the function as part of the module's API.
Test-only surface in a production module apps/bondy_http_connector/src/bondy_http_connector_telemetry.erl:45— `bondy_http_connector_telemetry:classify_status/1` is exported unconditionally, and the comment directly above the `-export` on this line says the exports below it are for testing. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. This arm read the comment, not the call graph: if the comment is right and only tests call it, wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module. If production code calls it, the comment is stale and wrapping the export would break the build — delete the comment and document the function as part of the module's API.
Test-only surface in a production module apps/bondy_mst/src/bondy_mst_pack_codec.erl:112— `bondy_mst_pack_codec:magic/0` is exported unconditionally, and the comment directly above the `-export` on this line says the exports below it are for testing. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. This arm read the comment, not the call graph: if the comment is right and only tests call it, wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module. If production code calls it, the comment is stale and wrapping the export would break the build — delete the comment and document the function as part of the module's API.
Test-only surface in a production module apps/bondy_mst/src/bondy_mst_pack_manifest.erl:112— `bondy_mst_pack_manifest:encode/1` is exported unconditionally, and the comment directly above the `-export` on this line says the exports below it are for testing. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. This arm read the comment, not the call graph: if the comment is right and only tests call it, wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module. If production code calls it, the comment is stale and wrapping the export would break the build — delete the comment and document the function as part of the module's API.
Test-only surface in a production module apps/bondy_oplog/src/bondy_oplog_applier.erl:424— `bondy_oplog_applier:bootstrap_publish_decision/3` is exported unconditionally, and the comment directly above the `-export` on this line says the exports below it are for testing. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. This arm read the comment, not the call graph: if the comment is right and only tests call it, wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module. If production code calls it, the comment is stale and wrapping the export would break the build — delete the comment and document the function as part of the module's API.
Test-only surface in a production module apps/bondy_router/src/bondy_export.erl:194— `bondy_export:legacy_translate/4` is exported unconditionally, and the comment directly above the `-export` on this line says the exports below it are for testing. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. This arm read the comment, not the call graph: if the comment is right and only tests call it, wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module. If production code calls it, the comment is stale and wrapping the export would break the build — delete the comment and document the function as part of the module's API.
Test-only surface in a production module apps/bondy_router/src/bondy_http_gateway_api_spec_parser.erl:99— `bondy_http_gateway_api_spec_parser:mops_expressions/1` is exported unconditionally, and the comment directly above the `-export` on this line says the exports below it are for testing. Erlang has no visibility below `-export`, so this is part of the module's public contract: it cannot be changed without a compatibility argument. This arm read the comment, not the call graph: if the comment is right and only tests call it, wrapping the attribute in `-ifdef(TEST). … -endif.` keeps the test's access and removes it from the shipped module. If production code calls it, the comment is stale and wrapping the export would break the build — delete the comment and document the function as part of the module's API.
No ADRs found fly.toml:1— 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/`. ADRs are expected here because `fly.toml` makes this repository a deployable product (line 1).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 22 project(s) overshoot their size bounds, lowering Project Cohesion to 9.1/10. The most over is `apps/bondy_router` (72991 LoC, 165 module-visible types across 1 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
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.
README/code drift apps/bondy_mst/README.md:372— apps/bondy_mst/README.md links to `reference/`, but `apps/bondy_mst/reference` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
No dependency-update automation apps/bondy_mcp/test/bondy_mcp_e2e_SUITE_data/package.json:6— `apps/bondy_mcp/test/bondy_mcp_e2e_SUITE_data/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
Unused export 'NAME' harness/k6/lib/wamp.js:21— Nothing imports this binding — it is safe to review for removal.
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/2 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Outdated: benchee — `:benchee` is locked at 1.5.0 but 1.5.1 is the current stable release on hex.pm, and it already satisfies the `"~> 1.3"` requirement declared in apps/bondy_cbor/bench/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update benchee` and commit the updated mix.lock.
Outdated: benchee — `:benchee` is locked at 1.5.0 but 1.5.1 is the current stable release on hex.pm, and it already satisfies the `"~> 1.3"` requirement declared in bench/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update benchee` and commit the updated mix.lock.
Outdated: benchee_markdown — `:benchee_markdown` is locked at 0.3.3 but 0.3.4 is the current stable release on hex.pm, and it already satisfies the `"~> 0.3"` requirement declared in apps/bondy_cbor/bench/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update benchee_markdown` and commit the updated mix.lock.
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.
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 01a1dde1-d911-7519-b0a4-0783e44800db · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 41 · Warnings: 727 · Recommendations: 33 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 15-11-2026 @ 06:25 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.