Public report of hyperledger-identus/cloud-agent, published 17 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, 17 November 2026, 14:17 UTC · Survey ID cd_a65e66ff770d453e844ceea6f4601ed7
hyperledger-identus/cloud-agent
Measured 17 November 2026, 14:16 UTC, at code version ca9259d
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
CAI scoreAt risk
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 medium codebase: 49,434 lines of product code in 48 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Code Health, 50.8
Findings by how serious they are
75 critical542 serious52 minor
10 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
17 November 2026, 14:16 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. 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 ▸
65of 65 dimensions measured by tools.
648of 669 findings point to an exact file and line, so you can open each one in the code. The other 21 concern the repository as a whole, such as missing documentation.
65dimensions across 7 lenses, read from 49,434 lines of product code in 48 projects.
hyperledger-identus/cloud-agent is rated At risk because critical security findings are open, most of them leaked passwords or keys. It scores 56.3 out of 100, which the At risk rating leaves unchanged.
Code Health, at 50.8, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is recording design decisions, worth about 3.3 points. Declaring which values may be missing would lift Code Health itself, worth about 2.8 points.
Twenty-seven passwords or keys in the code's history and four in the code are open to anyone who can read the repository. Nine known security holes in the packages the code depends on can be used by attackers, and nine settings leave the servers or containers unsafe. Replacing each exposed password or key, updating the vulnerable packages and correcting the unsafe settings would close these risks. Correcting the flagged pipeline settings would fix the two weaknesses in the build pipeline's configuration, and the four pipeline steps that run downloads without checking them need each download checked against a known checksum first. Saving the change and the message together would take care of the 15 places where data is saved and a message sent separately.
The product code is 49,434 lines, about €82,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.
The weakest lenses score close to each other, so improving any of them moves the score.
Code composition: what the lines of code are
Product code 62%Tests 38%
Rebuild cost: about €82,000 · Estimate
Cost to rebuild
€27,000 to €140,000, for 452 to 1,433 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 49,434 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 1 No ADRs found finding(s) in ADR Quality — start with build.sbt.
Raises the score by about 3.3 points · Low effort · ADR Quality
2
Reconcile the README with reality: mercury/README.md links to `./Mercury-Mailbox-Mediator.md`, but `mercury/Mercury-Mailbox-Mediator.md` does not exist; mercury/README.md links to `./protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md`, but `mercury/protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md` does not exist; cloud-agent/service/README.md links to `./connect.md`, but `cloud-agent/service/connect.md` does not exist; cloud-agent/service/README.md links to `./issue.md`, but `cloud-agent/service/issue.md` does not exist; cloud-agent/service/README.md links to `./present-proof.md`, but `cloud-agent/service/present-proof.md` does not exist.
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2).
Raises the score by about 1.4 points · Low effort · REDACTED Scanning
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 €82,000 to build again, about 0.6 person-years of work. Its weakest lens is Code Health, at 50.8 (Adequate). 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 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 3.3 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 8% on every change. The history of the code shows how much it changes: about 1,418 lines over the last 90 days, which is about 5,751 lines a year. At that pace, the extra work comes to an estimated 0.5 to 3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
415 modules, with 608 dependencies between them. 10 loops run through 26 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 375 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
agent.walletapi.model.error uses shared.models, so a change to shared.models can break agent.walletapi.model.error, while a change to agent.walletapi.model.error can't break shared.models.
Position
Below the diagonal: agent.walletapi.model.error uses a module listed above it, which is the healthy direction.
castor.core.model.did uses shared.models, so a change to shared.models can break castor.core.model.did, while a change to castor.core.model.did can't break shared.models.
Position
Below the diagonal: castor.core.model.did uses a module listed above it, which is the healthy direction.
mercury.protocol.invitation.v2 uses mercury.model, so a change to mercury.model can break mercury.protocol.invitation.v2, while a change to mercury.protocol.invitation.v2 can't break mercury.model.
Position
Below the diagonal: mercury.protocol.invitation.v2 uses a module listed above it, which is the healthy direction.
pollux.core.model.error uses shared.models, so a change to shared.models can break pollux.core.model.error, while a change to pollux.core.model.error can't break shared.models.
Position
Below the diagonal: pollux.core.model.error uses a module listed above it, which is the healthy direction.
agent.walletapi.model uses mercury.model, so a change to mercury.model can break agent.walletapi.model, while a change to agent.walletapi.model can't break mercury.model.
Position
Below the diagonal: agent.walletapi.model uses a module listed above it, which is the healthy direction.
agent.walletapi.model uses shared.crypto, so a change to shared.crypto can break agent.walletapi.model, while a change to agent.walletapi.model can't break shared.crypto.
Position
Below the diagonal: agent.walletapi.model uses a module listed above it, which is the healthy direction.
agent.walletapi.model uses shared.models, so a change to shared.models can break agent.walletapi.model, while a change to agent.walletapi.model can't break shared.models.
Position
Below the diagonal: agent.walletapi.model uses a module listed above it, which is the healthy direction.
agent.walletapi.model uses castor.core.model.did, so a change to castor.core.model.did can break agent.walletapi.model, while a change to agent.walletapi.model can't break castor.core.model.did.
Position
Below the diagonal: agent.walletapi.model uses a module listed above it, which is the healthy direction.
connect.core.model uses shared.models, so a change to shared.models can break connect.core.model, while a change to connect.core.model can't break shared.models.
Position
Below the diagonal: connect.core.model uses a module listed above it, which is the healthy direction.
connect.core.model uses mercury.protocol.invitation.v2, so a change to mercury.protocol.invitation.v2 can break connect.core.model, while a change to connect.core.model can't break mercury.protocol.invitation.v2.
Position
Below the diagonal: connect.core.model uses a module listed above it, which is the healthy direction.
didcomm.controller uses mercury.model, so a change to mercury.model can break didcomm.controller, while a change to didcomm.controller can't break mercury.model.
Position
Below the diagonal: didcomm.controller uses a module listed above it, which is the healthy direction.
didcomm.controller uses shared.models, so a change to shared.models can break didcomm.controller, while a change to didcomm.controller can't break shared.models.
Position
Below the diagonal: didcomm.controller uses a module listed above it, which is the healthy direction.
didcomm.controller uses pollux.core.model.error, so a change to pollux.core.model.error can break didcomm.controller, while a change to didcomm.controller can't break pollux.core.model.error.
Position
Below the diagonal: didcomm.controller uses a module listed above it, which is the healthy direction.
mercury uses mercury.protocol.invitation.v2, so a change to mercury.protocol.invitation.v2 can break mercury, while a change to mercury can't break mercury.protocol.invitation.v2.
Position
Below the diagonal: mercury uses a module listed above it, which is the healthy direction.
mercury.protocol.issuecredential uses mercury.model, so a change to mercury.model can break mercury.protocol.issuecredential, while a change to mercury.protocol.issuecredential can't break mercury.model.
Position
Below the diagonal: mercury.protocol.issuecredential uses a module listed above it, which is the healthy direction.
mercury.protocol.issuecredential uses mercury.protocol.invitation.v2, so a change to mercury.protocol.invitation.v2 can break mercury.protocol.issuecredential, while a change to mercury.protocol.issuecredential can't break mercury.protocol.invitation.v2.
Position
Below the diagonal: mercury.protocol.issuecredential uses a module listed above it, which is the healthy direction.
mercury.protocol.presentproof uses mercury.model, so a change to mercury.model can break mercury.protocol.presentproof, while a change to mercury.protocol.presentproof can't break mercury.model.
Position
Below the diagonal: mercury.protocol.presentproof uses a module listed above it, which is the healthy direction.
mercury.protocol.presentproof uses mercury.protocol.invitation.v2, so a change to mercury.protocol.invitation.v2 can break mercury.protocol.presentproof, while a change to mercury.protocol.presentproof can't break mercury.protocol.invitation.v2.
Position
Below the diagonal: mercury.protocol.presentproof uses a module listed above it, which is the healthy direction.
pollux.vc.jwt uses castor.core.model.did, so a change to castor.core.model.did can break pollux.vc.jwt, while a change to pollux.vc.jwt can't break castor.core.model.did.
Position
Below the diagonal: pollux.vc.jwt uses a module listed above it, which is the healthy direction.
agent.walletapi.storage uses mercury.model, so a change to mercury.model can break agent.walletapi.storage, while a change to agent.walletapi.storage can't break mercury.model.
Position
Below the diagonal: agent.walletapi.storage uses a module listed above it, which is the healthy direction.
agent.walletapi.storage uses shared.models, so a change to shared.models can break agent.walletapi.storage, while a change to agent.walletapi.storage can't break shared.models.
Position
Below the diagonal: agent.walletapi.storage uses a module listed above it, which is the healthy direction.
agent.walletapi.storage uses castor.core.model.did, so a change to castor.core.model.did can break agent.walletapi.storage, while a change to agent.walletapi.storage can't break castor.core.model.did.
Position
Below the diagonal: agent.walletapi.storage uses a module listed above it, which is the healthy direction.
agent.walletapi.storage uses agent.walletapi.model, so a change to agent.walletapi.model can break agent.walletapi.storage, while a change to agent.walletapi.storage can't break agent.walletapi.model.
Position
Below the diagonal: agent.walletapi.storage uses a module listed above it, which is the healthy direction.
oid4vci.domain uses castor.core.model.did, so a change to castor.core.model.did can break oid4vci.domain, while a change to oid4vci.domain can't break castor.core.model.did.
Position
Below the diagonal: oid4vci.domain uses a module listed above it, which is the healthy direction.
agent.walletapi.service uses castor.core.model.error, so a change to castor.core.model.error can break agent.walletapi.service, while a change to agent.walletapi.service can't break castor.core.model.error.
Position
Below the diagonal: agent.walletapi.service uses a module listed above it, which is the healthy direction.
agent.walletapi.service uses mercury.model, so a change to mercury.model can break agent.walletapi.service, while a change to agent.walletapi.service can't break mercury.model.
Position
Below the diagonal: agent.walletapi.service uses a module listed above it, which is the healthy direction.
agent.walletapi.service uses shared.models, so a change to shared.models can break agent.walletapi.service, while a change to agent.walletapi.service can't break shared.models.
Position
Below the diagonal: agent.walletapi.service uses a module listed above it, which is the healthy direction.
agent.walletapi.service uses agent.walletapi.model.error, so a change to agent.walletapi.model.error can break agent.walletapi.service, while a change to agent.walletapi.service can't break agent.walletapi.model.error.
Position
Below the diagonal: agent.walletapi.service uses a module listed above it, which is the healthy direction.
agent.walletapi.service uses castor.core.model.did, so a change to castor.core.model.did can break agent.walletapi.service, while a change to agent.walletapi.service can't break castor.core.model.did.
Position
Below the diagonal: agent.walletapi.service uses a module listed above it, which is the healthy direction.
agent.walletapi.service uses agent.walletapi.model, so a change to agent.walletapi.model can break agent.walletapi.service, while a change to agent.walletapi.service can't break agent.walletapi.model.
Position
Below the diagonal: agent.walletapi.service uses a module listed above it, which is the healthy direction.
agent.walletapi.service uses mercury, so a change to mercury can break agent.walletapi.service, while a change to agent.walletapi.service can't break mercury.
Position
Below the diagonal: agent.walletapi.service uses a module listed above it, which is the healthy direction.
agent.walletapi.service uses agent.walletapi.storage, so a change to agent.walletapi.storage can break agent.walletapi.service, while a change to agent.walletapi.service can't break agent.walletapi.storage.
Position
Below the diagonal: agent.walletapi.service uses a module listed above it, which is the healthy direction.
agent.walletapi.service.handler uses castor.core.model.error, so a change to castor.core.model.error can break agent.walletapi.service.handler, while a change to agent.walletapi.service.handler can't break castor.core.model.error.
Position
Below the diagonal: agent.walletapi.service.handler uses a module listed above it, which is the healthy direction.
agent.walletapi.service.handler uses shared.models, so a change to shared.models can break agent.walletapi.service.handler, while a change to agent.walletapi.service.handler can't break shared.models.
Position
Below the diagonal: agent.walletapi.service.handler uses a module listed above it, which is the healthy direction.
agent.walletapi.service.handler uses agent.walletapi.model.error, so a change to agent.walletapi.model.error can break agent.walletapi.service.handler, while a change to agent.walletapi.service.handler can't break agent.walletapi.model.error.
Position
Below the diagonal: agent.walletapi.service.handler uses a module listed above it, which is the healthy direction.
agent.walletapi.service.handler uses castor.core.model.did, so a change to castor.core.model.did can break agent.walletapi.service.handler, while a change to agent.walletapi.service.handler can't break castor.core.model.did.
Position
Below the diagonal: agent.walletapi.service.handler uses a module listed above it, which is the healthy direction.
agent.walletapi.service.handler uses agent.walletapi.model, so a change to agent.walletapi.model can break agent.walletapi.service.handler, while a change to agent.walletapi.service.handler can't break agent.walletapi.model.
Position
Below the diagonal: agent.walletapi.service.handler uses a module listed above it, which is the healthy direction.
agent.walletapi.service.handler uses agent.walletapi.storage, so a change to agent.walletapi.storage can break agent.walletapi.service.handler, while a change to agent.walletapi.service.handler can't break agent.walletapi.storage.
Position
Below the diagonal: agent.walletapi.service.handler uses a module listed above it, which is the healthy direction.
agent.walletapi.sql uses mercury.model, so a change to mercury.model can break agent.walletapi.sql, while a change to agent.walletapi.sql can't break mercury.model.
Position
Below the diagonal: agent.walletapi.sql uses a module listed above it, which is the healthy direction.
agent.walletapi.sql uses shared.models, so a change to shared.models can break agent.walletapi.sql, while a change to agent.walletapi.sql can't break shared.models.
Position
Below the diagonal: agent.walletapi.sql uses a module listed above it, which is the healthy direction.
agent.walletapi.sql uses castor.core.model.did, so a change to castor.core.model.did can break agent.walletapi.sql, while a change to agent.walletapi.sql can't break castor.core.model.did.
Position
Below the diagonal: agent.walletapi.sql uses a module listed above it, which is the healthy direction.
agent.walletapi.sql uses agent.walletapi.model, so a change to agent.walletapi.model can break agent.walletapi.sql, while a change to agent.walletapi.sql can't break agent.walletapi.model.
Position
Below the diagonal: agent.walletapi.sql uses a module listed above it, which is the healthy direction.
agent.walletapi.sql uses agent.walletapi.storage, so a change to agent.walletapi.storage can break agent.walletapi.sql, while a change to agent.walletapi.sql can't break agent.walletapi.storage.
Position
Below the diagonal: agent.walletapi.sql uses a module listed above it, which is the healthy direction.
agent.walletapi.vault uses mercury.model, so a change to mercury.model can break agent.walletapi.vault, while a change to agent.walletapi.vault can't break mercury.model.
Position
Below the diagonal: agent.walletapi.vault uses a module listed above it, which is the healthy direction.
agent.walletapi.vault uses shared.models, so a change to shared.models can break agent.walletapi.vault, while a change to agent.walletapi.vault can't break shared.models.
Position
Below the diagonal: agent.walletapi.vault uses a module listed above it, which is the healthy direction.
agent.walletapi.vault uses castor.core.model.did, so a change to castor.core.model.did can break agent.walletapi.vault, while a change to agent.walletapi.vault can't break castor.core.model.did.
Position
Below the diagonal: agent.walletapi.vault uses a module listed above it, which is the healthy direction.
agent.walletapi.vault uses agent.walletapi.model, so a change to agent.walletapi.model can break agent.walletapi.vault, while a change to agent.walletapi.vault can't break agent.walletapi.model.
Position
Below the diagonal: agent.walletapi.vault uses a module listed above it, which is the healthy direction.
agent.walletapi.vault uses agent.walletapi.storage, so a change to agent.walletapi.storage can break agent.walletapi.vault, while a change to agent.walletapi.vault can't break agent.walletapi.storage.
Position
Below the diagonal: agent.walletapi.vault uses a module listed above it, which is the healthy direction.
pollux.core.model uses shared.models, so a change to shared.models can break pollux.core.model, while a change to pollux.core.model can't break shared.models.
Position
Below the diagonal: pollux.core.model uses a module listed above it, which is the healthy direction.
pollux.core.model uses castor.core.model.did, so a change to castor.core.model.did can break pollux.core.model, while a change to pollux.core.model can't break castor.core.model.did.
Position
Below the diagonal: pollux.core.model uses a module listed above it, which is the healthy direction.
pollux.core.model uses mercury.protocol.invitation.v2, so a change to mercury.protocol.invitation.v2 can break pollux.core.model, while a change to pollux.core.model can't break mercury.protocol.invitation.v2.
Position
Below the diagonal: pollux.core.model uses a module listed above it, which is the healthy direction.
pollux.core.model uses mercury.protocol.issuecredential, so a change to mercury.protocol.issuecredential can break pollux.core.model, while a change to pollux.core.model can't break mercury.protocol.issuecredential.
Position
Below the diagonal: pollux.core.model uses a module listed above it, which is the healthy direction.
pollux.core.model uses mercury.protocol.presentproof, so a change to mercury.protocol.presentproof can break pollux.core.model, while a change to pollux.core.model can't break mercury.protocol.presentproof.
Position
Below the diagonal: pollux.core.model uses a module listed above it, which is the healthy direction.
pollux.core.model uses pollux.vc.jwt, so a change to pollux.vc.jwt can break pollux.core.model, while a change to pollux.core.model can't break pollux.vc.jwt.
Position
Below the diagonal: pollux.core.model uses a module listed above it, which is the healthy direction.
pollux.core.model uses pollux.prex, so a change to pollux.prex can break pollux.core.model, while a change to pollux.core.model can't break pollux.prex.
Position
Below the diagonal: pollux.core.model uses a module listed above it, which is the healthy direction.
agent.server.jobs uses mercury.model, so a change to mercury.model can break agent.server.jobs, while a change to agent.server.jobs can't break mercury.model.
Position
Below the diagonal: agent.server.jobs uses a module listed above it, which is the healthy direction.
agent.server.jobs uses shared.crypto, so a change to shared.crypto can break agent.server.jobs, while a change to agent.server.jobs can't break shared.crypto.
Position
Below the diagonal: agent.server.jobs uses a module listed above it, which is the healthy direction.
agent.server.jobs uses shared.models, so a change to shared.models can break agent.server.jobs, while a change to agent.server.jobs can't break shared.models.
Position
Below the diagonal: agent.server.jobs uses a module listed above it, which is the healthy direction.
agent.server.jobs uses castor.core.model.did, so a change to castor.core.model.did can break agent.server.jobs, while a change to agent.server.jobs can't break castor.core.model.did.
Position
Below the diagonal: agent.server.jobs uses a module listed above it, which is the healthy direction.
agent.server.jobs uses mercury.protocol.invitation.v2, so a change to mercury.protocol.invitation.v2 can break agent.server.jobs, while a change to agent.server.jobs can't break mercury.protocol.invitation.v2.
Position
Below the diagonal: agent.server.jobs uses a module listed above it, which is the healthy direction.
agent.server.jobs uses pollux.core.model.error, so a change to pollux.core.model.error can break agent.server.jobs, while a change to agent.server.jobs can't break pollux.core.model.error.
Position
Below the diagonal: agent.server.jobs uses a module listed above it, which is the healthy direction.
agent.server.jobs uses connect.core.model, so a change to connect.core.model can break agent.server.jobs, while a change to agent.server.jobs can't break connect.core.model.
Position
Below the diagonal: agent.server.jobs uses a module listed above it, which is the healthy direction.
agent.server.jobs uses agent.walletapi.storage, so a change to agent.walletapi.storage can break agent.server.jobs, while a change to agent.server.jobs can't break agent.walletapi.storage.
Position
Below the diagonal: agent.server.jobs uses a module listed above it, which is the healthy direction.
agent.server.jobs uses agent.walletapi.service, so a change to agent.walletapi.service can break agent.server.jobs, while a change to agent.server.jobs can't break agent.walletapi.service.
Position
Below the diagonal: agent.server.jobs uses a module listed above it, which is the healthy direction.
agent.server.jobs uses pollux.core.model, so a change to pollux.core.model can break agent.server.jobs, while a change to agent.server.jobs can't break pollux.core.model.
Position
Below the diagonal: agent.server.jobs uses a module listed above it, which is the healthy direction.
iam.authentication.apikey uses shared.models, so a change to shared.models can break iam.authentication.apikey, while a change to iam.authentication.apikey can't break shared.models.
Position
Below the diagonal: iam.authentication.apikey uses a module listed above it, which is the healthy direction.
iam.authentication.apikey uses agent.walletapi.model, so a change to agent.walletapi.model can break iam.authentication.apikey, while a change to iam.authentication.apikey can't break agent.walletapi.model.
Position
Below the diagonal: iam.authentication.apikey uses a module listed above it, which is the healthy direction.
iam.authentication.apikey uses agent.walletapi.service, so a change to agent.walletapi.service can break iam.authentication.apikey, while a change to iam.authentication.apikey can't break agent.walletapi.service.
Position
Below the diagonal: iam.authentication.apikey uses a module listed above it, which is the healthy direction.
29→31 iam.authentication.apikey uses iam.authenticationpart of a loop✕
Connections
6 pairs of types, where a type in iam.authentication.apikey uses a type in iam.authentication.
iam.authentication.apikey uses iam.authentication, so a change to iam.authentication can break iam.authentication.apikey, while a change to iam.authentication.apikey can't break iam.authentication.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
pollux.core.model.schema uses pollux.core.model, so a change to pollux.core.model can break pollux.core.model.schema, while a change to pollux.core.model.schema can't break pollux.core.model.
Position
Below the diagonal: pollux.core.model.schema uses a module listed above it, which is the healthy direction.
iam.authentication uses shared.models, so a change to shared.models can break iam.authentication, while a change to iam.authentication can't break shared.models.
Position
Below the diagonal: iam.authentication uses a module listed above it, which is the healthy direction.
iam.authentication uses agent.walletapi.model, so a change to agent.walletapi.model can break iam.authentication, while a change to iam.authentication can't break agent.walletapi.model.
Position
Below the diagonal: iam.authentication uses a module listed above it, which is the healthy direction.
iam.authentication uses iam.authentication.apikey, so a change to iam.authentication.apikey can break iam.authentication, while a change to iam.authentication can't break iam.authentication.apikey.
Position
Below the diagonal: iam.authentication uses a module listed above it, which is the healthy direction.
31→33 iam.authentication uses iam.authentication.oidcpart of a loop✕
Connections
3 pairs of types, where a type in iam.authentication uses a type in iam.authentication.oidc.
iam.authentication uses iam.authentication.oidc, so a change to iam.authentication.oidc can break iam.authentication, while a change to iam.authentication can't break iam.authentication.oidc.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
pollux.core.repository uses shared.models, so a change to shared.models can break pollux.core.repository, while a change to pollux.core.repository can't break shared.models.
Position
Below the diagonal: pollux.core.repository uses a module listed above it, which is the healthy direction.
pollux.core.repository uses mercury.protocol.issuecredential, so a change to mercury.protocol.issuecredential can break pollux.core.repository, while a change to pollux.core.repository can't break mercury.protocol.issuecredential.
Position
Below the diagonal: pollux.core.repository uses a module listed above it, which is the healthy direction.
pollux.core.repository uses mercury.protocol.presentproof, so a change to mercury.protocol.presentproof can break pollux.core.repository, while a change to pollux.core.repository can't break mercury.protocol.presentproof.
Position
Below the diagonal: pollux.core.repository uses a module listed above it, which is the healthy direction.
pollux.core.repository uses pollux.vc.jwt, so a change to pollux.vc.jwt can break pollux.core.repository, while a change to pollux.core.repository can't break pollux.vc.jwt.
Position
Below the diagonal: pollux.core.repository uses a module listed above it, which is the healthy direction.
pollux.core.repository uses pollux.prex, so a change to pollux.prex can break pollux.core.repository, while a change to pollux.core.repository can't break pollux.prex.
Position
Below the diagonal: pollux.core.repository uses a module listed above it, which is the healthy direction.
pollux.core.repository uses pollux.core.model, so a change to pollux.core.model can break pollux.core.repository, while a change to pollux.core.repository can't break pollux.core.model.
Position
Below the diagonal: pollux.core.repository uses a module listed above it, which is the healthy direction.
pollux.core.repository uses pollux.core.model.schema, so a change to pollux.core.model.schema can break pollux.core.repository, while a change to pollux.core.repository can't break pollux.core.model.schema.
Position
Below the diagonal: pollux.core.repository uses a module listed above it, which is the healthy direction.
iam.authentication.oidc uses shared.models, so a change to shared.models can break iam.authentication.oidc, while a change to iam.authentication.oidc can't break shared.models.
Position
Below the diagonal: iam.authentication.oidc uses a module listed above it, which is the healthy direction.
iam.authentication.oidc uses agent.walletapi.model, so a change to agent.walletapi.model can break iam.authentication.oidc, while a change to iam.authentication.oidc can't break agent.walletapi.model.
Position
Below the diagonal: iam.authentication.oidc uses a module listed above it, which is the healthy direction.
iam.authentication.oidc uses iam.authentication, so a change to iam.authentication can break iam.authentication.oidc, while a change to iam.authentication.oidc can't break iam.authentication.
Position
Below the diagonal: iam.authentication.oidc uses a module listed above it, which is the healthy direction.
pollux.core.service uses mercury.model, so a change to mercury.model can break pollux.core.service, while a change to pollux.core.service can't break mercury.model.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.core.service uses shared.models, so a change to shared.models can break pollux.core.service, while a change to pollux.core.service can't break shared.models.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.core.service uses castor.core.model.did, so a change to castor.core.model.did can break pollux.core.service, while a change to pollux.core.service can't break castor.core.model.did.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.core.service uses pollux.core.model.error, so a change to pollux.core.model.error can break pollux.core.service, while a change to pollux.core.service can't break pollux.core.model.error.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.core.service uses shared.http, so a change to shared.http can break pollux.core.service, while a change to pollux.core.service can't break shared.http.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.core.service uses mercury.protocol.issuecredential, so a change to mercury.protocol.issuecredential can break pollux.core.service, while a change to pollux.core.service can't break mercury.protocol.issuecredential.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.core.service uses mercury.protocol.presentproof, so a change to mercury.protocol.presentproof can break pollux.core.service, while a change to pollux.core.service can't break mercury.protocol.presentproof.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.core.service uses pollux.vc.jwt, so a change to pollux.vc.jwt can break pollux.core.service, while a change to pollux.core.service can't break pollux.vc.jwt.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.core.service uses pollux.prex, so a change to pollux.prex can break pollux.core.service, while a change to pollux.core.service can't break pollux.prex.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in pollux.core.service uses a type in pollux.core.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
pollux.core.service uses pollux.core.model, so a change to pollux.core.model can break pollux.core.service, while a change to pollux.core.service can't break pollux.core.model.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.core.service uses pollux.core.model.schema, so a change to pollux.core.model.schema can break pollux.core.service, while a change to pollux.core.service can't break pollux.core.model.schema.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.core.service uses pollux.core.repository, so a change to pollux.core.repository can break pollux.core.service, while a change to pollux.core.service can't break pollux.core.repository.
Position
Below the diagonal: pollux.core.service uses a module listed above it, which is the healthy direction.
pollux.sql.repository uses shared.models, so a change to shared.models can break pollux.sql.repository, while a change to pollux.sql.repository can't break shared.models.
Position
Below the diagonal: pollux.sql.repository uses a module listed above it, which is the healthy direction.
pollux.sql.repository uses mercury.protocol.issuecredential, so a change to mercury.protocol.issuecredential can break pollux.sql.repository, while a change to pollux.sql.repository can't break mercury.protocol.issuecredential.
Position
Below the diagonal: pollux.sql.repository uses a module listed above it, which is the healthy direction.
pollux.sql.repository uses mercury.protocol.presentproof, so a change to mercury.protocol.presentproof can break pollux.sql.repository, while a change to pollux.sql.repository can't break mercury.protocol.presentproof.
Position
Below the diagonal: pollux.sql.repository uses a module listed above it, which is the healthy direction.
pollux.sql.repository uses pollux.vc.jwt, so a change to pollux.vc.jwt can break pollux.sql.repository, while a change to pollux.sql.repository can't break pollux.vc.jwt.
Position
Below the diagonal: pollux.sql.repository uses a module listed above it, which is the healthy direction.
pollux.sql.repository uses pollux.prex, so a change to pollux.prex can break pollux.sql.repository, while a change to pollux.sql.repository can't break pollux.prex.
Position
Below the diagonal: pollux.sql.repository uses a module listed above it, which is the healthy direction.
pollux.sql.repository uses pollux.core.model, so a change to pollux.core.model can break pollux.sql.repository, while a change to pollux.sql.repository can't break pollux.core.model.
Position
Below the diagonal: pollux.sql.repository uses a module listed above it, which is the healthy direction.
pollux.sql.repository uses pollux.core.model.schema, so a change to pollux.core.model.schema can break pollux.sql.repository, while a change to pollux.sql.repository can't break pollux.core.model.schema.
Position
Below the diagonal: pollux.sql.repository uses a module listed above it, which is the healthy direction.
pollux.sql.repository uses pollux.core.repository, so a change to pollux.core.repository can break pollux.sql.repository, while a change to pollux.sql.repository can't break pollux.core.repository.
Position
Below the diagonal: pollux.sql.repository uses a module listed above it, which is the healthy direction.
agent.server uses agent.walletapi.model.error, so a change to agent.walletapi.model.error can break agent.server, while a change to agent.server can't break agent.walletapi.model.error.
Position
Below the diagonal: agent.server uses a module listed above it, which is the healthy direction.
agent.server uses castor.core.model.did, so a change to castor.core.model.did can break agent.server, while a change to agent.server can't break castor.core.model.did.
Position
Below the diagonal: agent.server uses a module listed above it, which is the healthy direction.
agent.server uses connect.core.model, so a change to connect.core.model can break agent.server, while a change to agent.server can't break connect.core.model.
Position
Below the diagonal: agent.server uses a module listed above it, which is the healthy direction.
agent.server uses agent.walletapi.vault, so a change to agent.walletapi.vault can break agent.server, while a change to agent.server can't break agent.walletapi.vault.
Position
Below the diagonal: agent.server uses a module listed above it, which is the healthy direction.
agent.server uses pollux.core.model, so a change to pollux.core.model can break agent.server, while a change to agent.server can't break pollux.core.model.
Position
Below the diagonal: agent.server uses a module listed above it, which is the healthy direction.
agent.server uses iam.authentication.oidc, so a change to iam.authentication.oidc can break agent.server, while a change to agent.server can't break iam.authentication.oidc.
Position
Below the diagonal: agent.server uses a module listed above it, which is the healthy direction.
oid4vci.service uses shared.models, so a change to shared.models can break oid4vci.service, while a change to oid4vci.service can't break shared.models.
Position
Below the diagonal: oid4vci.service uses a module listed above it, which is the healthy direction.
oid4vci.service uses castor.core.model.did, so a change to castor.core.model.did can break oid4vci.service, while a change to oid4vci.service can't break castor.core.model.did.
Position
Below the diagonal: oid4vci.service uses a module listed above it, which is the healthy direction.
oid4vci.service uses pollux.vc.jwt, so a change to pollux.vc.jwt can break oid4vci.service, while a change to oid4vci.service can't break pollux.vc.jwt.
Position
Below the diagonal: oid4vci.service uses a module listed above it, which is the healthy direction.
oid4vci.service uses agent.walletapi.storage, so a change to agent.walletapi.storage can break oid4vci.service, while a change to oid4vci.service can't break agent.walletapi.storage.
Position
Below the diagonal: oid4vci.service uses a module listed above it, which is the healthy direction.
oid4vci.service uses oid4vci.domain, so a change to oid4vci.domain can break oid4vci.service, while a change to oid4vci.service can't break oid4vci.domain.
Position
Below the diagonal: oid4vci.service uses a module listed above it, which is the healthy direction.
oid4vci.service uses pollux.core.service, so a change to pollux.core.service can break oid4vci.service, while a change to oid4vci.service can't break pollux.core.service.
Position
Below the diagonal: oid4vci.service uses a module listed above it, which is the healthy direction.
issue.controller uses api.http.model, so a change to api.http.model can break issue.controller, while a change to issue.controller can't break api.http.model.
Position
Below the diagonal: issue.controller uses a module listed above it, which is the healthy direction.
issue.controller uses shared.models, so a change to shared.models can break issue.controller, while a change to issue.controller can't break shared.models.
Position
Below the diagonal: issue.controller uses a module listed above it, which is the healthy direction.
issue.controller uses castor.core.model.did, so a change to castor.core.model.did can break issue.controller, while a change to issue.controller can't break castor.core.model.did.
Position
Below the diagonal: issue.controller uses a module listed above it, which is the healthy direction.
issue.controller uses pollux.core.model, so a change to pollux.core.model can break issue.controller, while a change to issue.controller can't break pollux.core.model.
Position
Below the diagonal: issue.controller uses a module listed above it, which is the healthy direction.
issue.controller uses agent.server, so a change to agent.server can break issue.controller, while a change to issue.controller can't break agent.server.
Position
Below the diagonal: issue.controller uses a module listed above it, which is the healthy direction.
oid4vci.controller uses shared.models, so a change to shared.models can break oid4vci.controller, while a change to oid4vci.controller can't break shared.models.
Position
Below the diagonal: oid4vci.controller uses a module listed above it, which is the healthy direction.
oid4vci.controller uses oid4vci.domain, so a change to oid4vci.domain can break oid4vci.controller, while a change to oid4vci.controller can't break oid4vci.domain.
Position
Below the diagonal: oid4vci.controller uses a module listed above it, which is the healthy direction.
oid4vci.controller uses pollux.core.service, so a change to pollux.core.service can break oid4vci.controller, while a change to oid4vci.controller can't break pollux.core.service.
Position
Below the diagonal: oid4vci.controller uses a module listed above it, which is the healthy direction.
oid4vci.controller uses oid4vci.service, so a change to oid4vci.service can break oid4vci.controller, while a change to oid4vci.controller can't break oid4vci.service.
Position
Below the diagonal: oid4vci.controller uses a module listed above it, which is the healthy direction.
presentproof.controller uses api.http, so a change to api.http can break presentproof.controller, while a change to presentproof.controller can't break api.http.
Position
Below the diagonal: presentproof.controller uses a module listed above it, which is the healthy direction.
presentproof.controller uses api.http.model, so a change to api.http.model can break presentproof.controller, while a change to presentproof.controller can't break api.http.model.
Position
Below the diagonal: presentproof.controller uses a module listed above it, which is the healthy direction.
presentproof.controller uses mercury.model, so a change to mercury.model can break presentproof.controller, while a change to presentproof.controller can't break mercury.model.
Position
Below the diagonal: presentproof.controller uses a module listed above it, which is the healthy direction.
presentproof.controller uses shared.models, so a change to shared.models can break presentproof.controller, while a change to presentproof.controller can't break shared.models.
Position
Below the diagonal: presentproof.controller uses a module listed above it, which is the healthy direction.
presentproof.controller uses pollux.core.model.error, so a change to pollux.core.model.error can break presentproof.controller, while a change to presentproof.controller can't break pollux.core.model.error.
Position
Below the diagonal: presentproof.controller uses a module listed above it, which is the healthy direction.
presentproof.controller uses mercury.protocol.presentproof, so a change to mercury.protocol.presentproof can break presentproof.controller, while a change to presentproof.controller can't break mercury.protocol.presentproof.
Position
Below the diagonal: presentproof.controller uses a module listed above it, which is the healthy direction.
presentproof.controller uses pollux.core.model, so a change to pollux.core.model can break presentproof.controller, while a change to presentproof.controller can't break pollux.core.model.
Position
Below the diagonal: presentproof.controller uses a module listed above it, which is the healthy direction.
presentproof.controller uses agent.server, so a change to agent.server can break presentproof.controller, while a change to presentproof.controller can't break agent.server.
Position
Below the diagonal: presentproof.controller uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 50.8 · Adequate · gated by D2, X4, 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
A02:2025 — Security Misconfiguration
44
High / Critical
A07:2025 — Authentication Failures
32
High / Critical
A05:2025 — Injection
29
High / Critical
A03:2025 — Software Supply Chain Failures
24
High / Critical
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.sbt; Reconcile the README with reality: mercury/README.md links to `./Mercury-Mailbox-Mediator.md`, but `mercury/Mercury-Mailbox-Mediator.md` does not exist; mercury/README.md links to `./protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md`, but `mercury/protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md` does not exist; cloud-agent/service/README.md links to `./connect.md`, but `cloud-agent/service/connect.md` does not exist; cloud-agent/service/README.md links to `./issue.md`, but `cloud-agent/service/issue.md` does not exist; cloud-agent/service/README.md links to `./present-proof.md`, but `cloud-agent/service/present-proof.md` does not exist; On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.sbt.
Reconcile the README with reality: mercury/README.md links to `./Mercury-Mailbox-Mediator.md`, but `mercury/Mercury-Mailbox-Mediator.md` does not exist; mercury/README.md links to `./protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md`, but `mercury/protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md` does not exist; cloud-agent/service/README.md links to `./connect.md`, but `cloud-agent/service/connect.md` does not exist; cloud-agent/service/README.md links to `./issue.md`, but `cloud-agent/service/issue.md` does not exist; cloud-agent/service/README.md links to `./present-proof.md`, but `cloud-agent/service/present-proof.md` does not exist.
On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
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.
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 — 75
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 — 542
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 — 52
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
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 65 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 — 65 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, 648 of 669 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: this repository's production source spans .py, .scala, and our analyzer cannot run the .scala test suite(s) — so no coverage was collected for the repository as a whole. The Python half did build and run, and its own line coverage came back at 36.0% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
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 (.scala, .ts, .kt) and this repository declares an sbt build (repository root, 171 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — 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. Not scored — a Gradle build resolved 526 artifact(s) across its subprojects (423 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
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 an sbt build (build.sbt), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its sbt dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
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 package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
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.
D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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 an ADMISSION gap, not an environment fault: it declares a published package (cloud-agent/client/typescript/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismDIDService.scala`, `castor/src/main/scala/org/hyperledger/identus/castor/core/service/PrismNodeDIDService.scala`, `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/BackgroundJobError.scala`, `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala`, `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/DIDStateSyncBackgroundJobs.scala`, … (+38 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 60 commits in the last 90 days, yet 247 of 251 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
D41 Kernel & Syscall Confinement — 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. Infrastructure/charts/agent/templates/deployment.yaml:2, REDACTED:3 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
AX2 Stateful singletons — 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 Microsoft.Extensions.DependencyInjection singletons in C#, Spring/JSR-330/CDI singletons in Java and Kotlin, module state in Python request handlers, handler state in Go and Swift, Play controllers, Cask routes, Scalatra servlets, Finatra controllers, Akka/Pekko HTTP routes and JSR-330 singletons in Scala, Rails, Sinatra, Grape, Roda and Hanami handlers and Rack apps in Ruby, and module state in F# request handlers (Giraffe, Saturn, Falco, Oxpecker and Suave handlers and ASP.NET Core controllers) only, and this repository's product is written in Scala (Tapir) and Scala (ZIO HTTP), which was left unread, 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.
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 18 — an image could not be pulled) — holder-db Error context canceled apisix Error context canceled issuer-agent-postgres-exporter Error context canceled holder-agent-postgres-exporter Error context canceled node-db Error context canceled holder-agent Error context canceled Error response from daemon: manifest for hyperledgeridentus/identus-cloud-agent:1.25.0 not found: manifest unknown: manifest unknown; the earlier `compose pull` step reported: prism-node Error context canceled issuer-db Error context canceled holder-agent-postgres-exporter Error context canceled apisix Error context canceled Error response from daemon: manifest for hyperledgeridentus/identus-cloud-agent:1.25.0 not found: manifest unknown: manifest unknown; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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.
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.
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.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
16 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was IssueBackgroundJobs.performIssueCredentialExchange at 78. A further 1 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 PresentBackgroundJobs.performPresentProofExchange at 29 — they are counted neither in the figure above nor in this dimension's score.
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with IssueBackgroundJobs.performIssueCredentialExchange (cyclomatic 78). — Refactoring it lifts Cyclomatic Complexity from 7.0 to about 8.0/10.
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.
+ 99 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 17 bodies over 60 down to 60 or less in Cognitive Complexity — start with IssueBackgroundJobs.performIssueCredentialExchange (cognitive 300), CoordinateMediationPrograms.senderMediationRequestProgram (cognitive 249), CredentialServiceImpl.generateSDJWTCredential (cognitive 168). — 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 17 together lifts Cognitive Complexity from 2.0 to about 4.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.3 / 10Stronggated by 7 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 6 FileTooLong finding(s) in God Classes — start with CredentialServiceImpl.scala, PresentBackgroundJobs.scala, PresentationServiceImpl.scala. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 MethodTooLong finding(s) in God Classes — start with Connection.scala. — One of this dimension's main actionable groups (1 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.
57 duplicated block group(s) detected. 6.3 % of the production lines (3,110 of 49,434) are in a reported copy. A further 67 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5cloud-agent/service/server/src/main/scala/org/hyperledger/identus/castor/controller/DIDRegistrarController.scala:104
Edited copy of a member (17 corresponding lines) · ×5cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZioHttpClient.scala:14
Edited copy of a member (9 corresponding lines) · ×5mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:86
Edited copy of a member (15 corresponding lines) · ×4cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/apikey/ApiKeyAuthenticator.scala:17
Edited copy of a member (11 corresponding lines) · ×4pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:721
+ 68 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with DIDRegistrarController.scala, CredentialDefinitionControllerLogic.scala, CredentialDefinitionDidUrlResponse.scala. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with ZioHttpClient.scala, PresentationServiceImpl.scala, PaginationUtils.scala. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with ConnectionRequest.scala, NeoPrismClient.scala, VerifiableCredentialPayload.scala. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.0 / 10Stronggated by 5 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
48 production modules (Gradle+npm+Python+sbt), 0 dependency cycle(s), 3 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 3 module(s) off the main sequence, with abstractness counted on 42 of the 48 (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: polluxAnoncreds · ×2
Unstable project agent
Unstable project polluxCore
Unstable project vdrProxy
Off the main sequence: shared
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Unstable project agent finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project polluxCore 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 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.
2 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
REDACTED
What to do
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 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 16 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 3 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 1 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares an sbt build (build.sbt) and package.json, and the licences of those dependency graphs 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.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 251 of the 561 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
210 deducted task-comment markers across 49434 LoC (0.4/KLoC) → score 9.2. 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 176 TodoComment finding(s) in Explicit Debt — start with OIDCCredentialIssuerService.scala (16), IssueFormats.scala (8), ReportProblem.scala (7). — One of this dimension's main actionable groups (176 warning-level).
Resolve the 34 FixmeComment finding(s) in Explicit Debt — start with Openid4VCIProofJwtOps.scala (6), Events.kt (2), Agent.kt (2). — One of this dimension's main actionable groups (34 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.
2 of 2 documentation facets pass in full. 58 document(s) read across 46 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 build.sbt. — 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 names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
10 naming inconsistencies among 510 declarations measured against a convention their peers follow.
`DidCommID` spells `ID` where 747 names in the project spell it `Id` · ×2pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/DidCommID.scala:6
`findByID` spells `ID` where 747 names in the project spell it `Id` · ×2pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:110
`DidCommIDCodec` spells `ID` where 747 names in the project spell it `Id`cloud-agent/service/server/src/main/scala/org/hyperledger/identus/api/http/codec/DidCommIDCodec.scala:8
`toDidCommID` spells `ID` where 747 names in the project spell it `Id`cloud-agent/service/server/src/main/scala/org/hyperledger/identus/presentproof/controller/PresentProofController.scala:48
`isDidPRISM` spells `PRISM` where 49 names in the project spell it `Prism`mercury/resolver/src/main/scala/org/hyperledger/identus/resolvers/DidValidator.scala:19
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 `DidCommID` spells `ID` where 747 names in the project spell it `Id` finding(s) in Naming Consistency — start with DidCommID.scala (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 2 `findByID` spells `ID` where 747 names in the project spell it `Id` finding(s) in Naming Consistency — start with CredentialDefinition.scala, CredentialSchema.scala. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 `DidCommIDCodec` spells `ID` where 747 names in the project spell it… finding(s) in Naming Consistency — start with DidCommIDCodec.scala. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 4 build units (Gradle, Python, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionpackage.json:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
28 finding(s): 0 critical, 28 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 15 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 12 High secret finding(s) in Secrets (history) — start with REDACTED (6), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (12 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).
29 finding(s): 0 critical, 10 high, 5 medium, 14 low. 1 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 38 file(s) — `castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismDIDService.scala`, `castor/src/main/scala/org/hyperledger/identus/castor/core/service/PrismNodeDIDService.scala`, `cloud-agent/client/kotlin/gradlew` (line 72, line 178), `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala`, `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/apikey/ApiKeyAuthenticator.scala`, … (+33 more) — 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 6 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 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).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 35 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED (9), REDACTED (7). — One of this dimension's main actionable groups (35 warning-level).
Resolve the 9 High IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with PresentBackgroundJobs.scala. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 9 Change coupling finding(s) in Change Coupling — start with PresentationRepository.scala, CredentialRepository.scala, ConnectionServiceImpl.scala. — One of this dimension's main actionable groups (9 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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
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 4 platform declaration(s) and 26 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`ConnectionService` declares 16 abstract members: `createConnectionInvitation`, `receiveConnectionInvitation`, `acceptConnectionInvitation`, `markConnectionRequestSent`, `receiveConnectionRequest`, `acceptConnectionRequest`, `markConnectionResponseSent`, `markConnectionInvitationExpired`, `receiveConnectionResponse`, `findAllRecords`, `findRecordsByStates`, `findRecordsByStatesForAllWallets`, `findRecordById`, `findRecordByThreadId`, `deleteRecordById`, `reportProcessingFailure`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionService.scala:14
`CredentialRepository` declares 17 abstract members: `create`, `findAll`, `getById`, `findById`, `findByStates`, `findByStatesForAllWallets`, `findByThreadId`, `updateProtocolState`, `updateWithSubjectId`, `updateWithJWTRequestCredential`, `updateWithAnonCredsRequestCredential`, `updateWithIssueCredential`, `updateWithIssuedRawCredential`, `deleteById`, `findValidIssuedCredentials`, `findValidAnonCredsIssuedCredentials`, `updateAfterFail`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/repository/CredentialRepository.scala:10
`PresentationRepository` declares 16 abstract members: `createPresentationRecord`, `getPresentationRecords`, `findPresentationRecord`, `getPresentationRecordsByStates`, `getPresentationRecordsByStatesForAllWallets`, `findPresentationRecordByThreadId`, `getPresentationRecordByDIDCommID`, `updatePresentationRecordProtocolState`, `updateWithRequestPresentation`, `updateWithProposePresentation`, `updateWithSDJWTDisclosedClaims`, `updateWithPresentation`, `updatePresentationWithCredentialsToUse`, `updateSDJWTPresentationWithCredentialsToUse`, `updateAnoncredPresentationWithCredentialsToUse`, `updateAfterFail`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/repository/PresentationRepository.scala:9
`CredentialService` declares 27 abstract members: `createJWTIssueCredentialRecord`, `createSDJWTIssueCredentialRecord`, `createAnonCredsIssueCredentialRecord`, `getIssueCredentialRecords`, `getIssueCredentialRecordsByStates`, `getIssueCredentialRecordsByStatesForAllWallets`, `findById`, `getById`, `getIssueCredentialRecordByThreadId`, `receiveCredentialOffer`, `acceptCredentialOffer`, `generateJWTCredentialRequest`, `generateSDJWTCredentialRequest`, `generateAnonCredsCredentialRequest`, `receiveCredentialRequest`, `acceptCredentialRequest`, `generateJWTCredential`, `generateSDJWTCredential`, `generateAnonCredsCredential`, `receiveCredentialIssue`, `markOfferSent`, `markRequestSent`, `markCredentialSent`, `markCredentialOfferInvitationExpired`, `reportProcessingFailure`, `getJwtIssuer`, `getCredentialOfferInvitation`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialService.scala:24
`PresentationService` declares 38 abstract members: `extractIdFromCredential`, `createJwtPresentationRecord`, `createSDJWTPresentationRecord`, `createAnoncredPresentationRecord`, `getPresentationRecords`, `createJwtPresentationPayloadFromRecord`, `createPresentationFromRecord`, `createSDJwtPresentation`, `createAnoncredPresentationPayloadFromRecord`, `createAnoncredPresentation`, `getPresentationRecordsByStates`, `getPresentationRecordsByStatesForAllWallets`, `findPresentationRecord`, `findPresentationRecordByThreadId`, `receiveRequestPresentation`, `acceptRequestPresentation`, `acceptSDJWTRequestPresentation`, `acceptAnoncredRequestPresentation`, `rejectRequestPresentation`, `receiveProposePresentation`, `acceptProposePresentation`, `receivePresentation`, `acceptPresentation`, `rejectPresentation`, `markRequestPresentationSent`, `markRequestPresentationRejected`, `markProposePresentationSent`, `markPresentationSent`, `markPresentationGenerated`, `markPresentationVerified`, `markPresentationRejected`, `markPresentationAccepted`, `markPresentationVerificationFailed`, `updateWithSDJWTDisclosedClaims`, `verifyAnoncredPresentation`, `reportProcessingFailure`, `getRequestPresentationFromInvitation`, `markPresentationInvitationExpired`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationService.scala:18
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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 · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
`ConnectionServiceImpl.acceptConnectionInvitation` writes state (`connectionRepository.updateWithConnectionRequest`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:148
`ConnectionServiceImpl.acceptConnectionRequest` writes state (`connectionRepository.updateWithConnectionResponse`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:226
`CredentialServiceImpl.acceptCredentialOffer` writes state (`credentialRepository.updateWithSubjectId`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:504
`CredentialServiceImpl.generateCredentialRequest` writes state (`credentialRepository.updateWithJWTRequestCredential`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:699
`CredentialServiceImpl.generateAnonCredsCredentialRequest` writes state (`credentialRepository.updateWithAnonCredsRequestCredential`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:749
`CredentialServiceImpl.receiveCredentialRequest` writes state (`credentialRepository.updateWithJWTRequestCredential`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:802
`CredentialServiceImpl.acceptCredentialRequest` writes state (`credentialRepository.updateWithIssueCredential`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:820
`CredentialServiceImpl.markCredentialGenerated` writes state (`credentialRepository.updateWithIssueCredential`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:967
`PresentationServiceImpl.markPresentationGenerated` writes state (`presentationRepository.updateWithPresentation`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:51
`PresentationServiceImpl.acceptRequestPresentation` writes state (`presentationRepository.updatePresentationWithCredentialsToUse`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:825
`PresentationServiceImpl.acceptSDJWTRequestPresentation` writes state (`presentationRepository.updateSDJWTPresentationWithCredentialsToUse`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:853
`PresentationServiceImpl.acceptAnoncredRequestPresentation` writes state (`presentationRepository.updateAnoncredPresentationWithCredentialsToUse`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:907
`PresentationServiceImpl.receivePresentation` writes state (`presentationRepository.updateWithPresentation`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1001
`PresentationServiceImpl.acceptProposePresentation` writes state (`presentationRepository.updateWithRequestPresentation`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1024
`PresentationServiceImpl.receiveProposePresentation` writes state (`presentationRepository.updateWithProposePresentation`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1044
What to do
Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — cloud-agent/service/wallet-api/src/test/scala/org/hyperledger/identus/agent/walletapi/benchmark/KeyDerivation.scala:37
What to do
Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
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.
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.
mercury/README.md links to `./Mercury-Mailbox-Mediator.md`, but `mercury/Mercury-Mailbox-Mediator.md` 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. — mercury/README.md:5
mercury/README.md links to `./protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md`, but `mercury/protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md` 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. — mercury/README.md:8
cloud-agent/service/README.md links to `./connect.md`, but `cloud-agent/service/connect.md` 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. — cloud-agent/service/README.md:29
cloud-agent/service/README.md links to `./issue.md`, but `cloud-agent/service/issue.md` 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. — cloud-agent/service/README.md:35
cloud-agent/service/README.md links to `./present-proof.md`, but `cloud-agent/service/present-proof.md` 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. — cloud-agent/service/README.md:41
What to do
Reconcile the README with reality: mercury/README.md links to `./Mercury-Mailbox-Mediator.md`, but `mercury/Mercury-Mailbox-Mediator.md` does not exist; mercury/README.md links to `./protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md`, but `mercury/protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md` does not exist; cloud-agent/service/README.md links to `./connect.md`, but `cloud-agent/service/connect.md` does not exist; cloud-agent/service/README.md links to `./issue.md`, but `cloud-agent/service/issue.md` does not exist; cloud-agent/service/README.md links to `./present-proof.md`, but `cloud-agent/service/present-proof.md` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Readiness · Readiness — Whether behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.
Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.
Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`scorecard.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
Dependabot is configured but does not watch `gradle` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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 database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety9.6 / 10Exemplary✓ 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.
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.
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.
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 · Tooling6.7 / 10Adequate✓ 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.
`tests/performance-tests/agent-performance-tests-k6` is TypeScript, but a type error in it cannot fail anything this repository runs: its `webpack` script (`webpack`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — tests/performance-tests/agent-performance-tests-k6/package.json:26
What to do
Add eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ 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.
1 file(s) (~55 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.
2 file(s) (~74 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — cloud-agent/client/typescript
1 file(s) (~26 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — tests/didcomm-tests
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 the root 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. (×5) — package.json:8, package.json:9, package.json:13, …
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 · Security — Read from this repository's Scala source and the Java beside it: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. This repository serves HTTP itself (cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZHttp4sBlazeServer.scala:5 — `BlazeServerBuilder`), so its Scala source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Scala spelling appears in production source, not proven on every route. A Play application is credited the security headers Play's default `SecurityHeadersFilter` sends unless its build or configuration switches that filter off, and its cookies the HttpOnly flag Play sets by default.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — REDACTED:21
This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZHttp4sBlazeServer.scala:5 — `BlazeServerBuilder`.
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`).
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.3 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`validate` is public and takes `claimsJsonNode: JsonNode` from its caller, and it calls itself at line 37 with a piece of `claimsJsonNode`, not as a tail call the compiler turns into a loop — and nowhere in `validate` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `validate` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — shared/json/src/main/scala/org/hyperledger/identus/shared/json/JsonSchema.scala:37
`deserialize` is public and takes `schema: zio.json.ast.Json` from its caller, and it calls itself at line 156 with a piece of `schema`, not as a tail call the compiler turns into a loop — and nowhere in `deserialize` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `deserialize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — shared/json/src/main/scala/org/hyperledger/identus/shared/json/JsonSchema.scala:156
`json2Map` is public and takes `json: Json` from its caller, and it calls itself at line 49 with a piece of `json` (and at line 52), not as a tail call the compiler turns into a loop — and nowhere in `json2Map` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `json2Map` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — mercury/agent-didcommx/src/main/scala/org/hyperledger/identus/mercury/model/Conversions.scala:49
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. 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.
`case _: Exception` 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. (×2) — castor/src/main/scala/org/hyperledger/identus/castor/core/util/UriUtils.scala:101, castor/src/main/scala/org/hyperledger/identus/castor/core/util/UriUtils.scala:112
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`error` at line 131 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — infrastructure/utils/python/github-helpers/github_helpers/cli.py:131
`info` at line 195 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — infrastructure/utils/python/github-helpers/github_helpers/cli.py:195
`error` at line 215 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — infrastructure/utils/python/github-helpers/github_helpers/cli.py:215
Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
No build over this repository's 548 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
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.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 63 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: this repository's Kotlin 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; this repository's Scala 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 TypeScript 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 — 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
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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
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 18 — an image could not be pulled) — holder-db Error context canceled apisix Error context canceled issuer-agent-postgres-exporter Error context canceled holder-agent-postgres-exporter Error context canceled node-db Error context canceled holder-agent Error context canceled Error response from daemon: manifest for hyperledgeridentus/identus-cloud-agent:1.25.0 not found: manifest unknown: manifest unknown; the earlier `compose pull` step reported: prism-node Error context canceled issuer-db Error context canceled holder-agent-postgres-exporter Error context canceled apisix Error context canceled Error response from daemon: manifest for hyperledgeridentus/identus-cloud-agent:1.25.0 not found: manifest unknown: manifest unknown; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~30896 lines of test source are present (.scala, .ts, .kt) 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 .scala suite was found but not re-run
D12 Dependency Hygiene — Not scored — a Gradle build resolved 526 artifact(s) across its subprojects (423 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
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.
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"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .kt, .py, .scala source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 43 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
DM1 Domain Modelling — applicable but not scored (3 signals for this style, 2 needed — the count is met but a required primary signal is absent): 384 value object(s); 11 domain event(s); its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a domain structure with no aggregate, domain event or strongly-typed id in it: a CRUD / clean-architecture model, measured but not claimed as DDD; a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
P9 Domain vs controller coverage — coverage data present for 4 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 23 test file(s) reach none of 2 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
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
X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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 — 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 — no C# was loaded; this repository's Scala, Python and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Kotlin request outside a suspend function has no caller's cancellation to honour
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
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
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
X25 Inert configuration knob — 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
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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.
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.
Dual write (no outbox): ConnectionServiceImpl.acceptConnectionInvitation connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:148— `ConnectionServiceImpl.acceptConnectionInvitation` writes state (`connectionRepository.updateWithConnectionRequest`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): ConnectionServiceImpl.acceptConnectionRequest connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:226— `ConnectionServiceImpl.acceptConnectionRequest` writes state (`connectionRepository.updateWithConnectionResponse`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): CredentialServiceImpl.acceptCredentialOffer pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:504— `CredentialServiceImpl.acceptCredentialOffer` writes state (`credentialRepository.updateWithSubjectId`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): CredentialServiceImpl.generateCredentialRequest pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:699— `CredentialServiceImpl.generateCredentialRequest` writes state (`credentialRepository.updateWithJWTRequestCredential`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): CredentialServiceImpl.generateAnonCredsCredentialRequest pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:749— `CredentialServiceImpl.generateAnonCredsCredentialRequest` writes state (`credentialRepository.updateWithAnonCredsRequestCredential`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): CredentialServiceImpl.receiveCredentialRequest pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:802— `CredentialServiceImpl.receiveCredentialRequest` writes state (`credentialRepository.updateWithJWTRequestCredential`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): CredentialServiceImpl.acceptCredentialRequest pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:820— `CredentialServiceImpl.acceptCredentialRequest` writes state (`credentialRepository.updateWithIssueCredential`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): CredentialServiceImpl.markCredentialGenerated pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:967— `CredentialServiceImpl.markCredentialGenerated` writes state (`credentialRepository.updateWithIssueCredential`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): PresentationServiceImpl.markPresentationGenerated pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:51— `PresentationServiceImpl.markPresentationGenerated` writes state (`presentationRepository.updateWithPresentation`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): PresentationServiceImpl.acceptRequestPresentation pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:825— `PresentationServiceImpl.acceptRequestPresentation` writes state (`presentationRepository.updatePresentationWithCredentialsToUse`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): PresentationServiceImpl.acceptSDJWTRequestPresentation pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:853— `PresentationServiceImpl.acceptSDJWTRequestPresentation` writes state (`presentationRepository.updateSDJWTPresentationWithCredentialsToUse`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): PresentationServiceImpl.acceptAnoncredRequestPresentation pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:907— `PresentationServiceImpl.acceptAnoncredRequestPresentation` writes state (`presentationRepository.updateAnoncredPresentationWithCredentialsToUse`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): PresentationServiceImpl.receivePresentation pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1001— `PresentationServiceImpl.receivePresentation` writes state (`presentationRepository.updateWithPresentation`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): PresentationServiceImpl.acceptProposePresentation pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1024— `PresentationServiceImpl.acceptProposePresentation` writes state (`presentationRepository.updateWithRequestPresentation`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Dual write (no outbox): PresentationServiceImpl.receiveProposePresentation pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1044— `PresentationServiceImpl.receiveProposePresentation` writes state (`presentationRepository.updateWithProposePresentation`) AND publishes an event (`messageProducer.produce`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change.
Boundary-crossing change coupling: PresentBackgroundJobs.scala ↔ PresentationServiceNotifier.scala cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:1— `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala` (context cloud-agent) and `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceNotifier.scala` (context pollux) sit in DIFFERENT parts of the tree yet change together 83% of the time (10 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `e6581911` build: fix typo in repository causing flaky scalafmt (#1575); `5e005560` fix: Add disclose claims to presentation record credential type SDJW…; `c18385c8` fix: Preserve Presentation Format (#1363) — run `git show` on any of them.
TodoComment tests/performance-tests/agent-performance-tests-k6/src/scenarios/default.ts:25— // TODO: this threshold is too high, it should be adjusted to the actual performance requirements to lower value — 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 tests/integration-tests/src/test/kotlin/config/services/Agent.kt:20— //TODO: leave only one config alias — 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 shared/predef/src/main/scala/org/hyperledger/identus/Predef.scala:17— // TODO review and try to REMOVE — 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 shared/predef/src/main/scala/org/hyperledger/identus/Predef.scala:23— // TODO Open tickets and REMOVE — 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 shared/crypto/src/test/scala/org/hyperledger/identus/shared/crypto/ApolloSpec.scala:205— // TODO: Uncomment tests when KMP apollo supports BIP32 fully — 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:13— // TODO "23.1.0.2" // https://mvnrepository.com/artifact/dev.zio/zio-interop-cats
TodoComment REDACTED:20— // scala-steward:off // TODO "1.10.5" — 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:21— // scala-steward:off // TODO "0.23.16" — 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:45— // scala-steward:off //TODO 1.3.2 need to fix: — 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:53— // scala-steward:off //TODO: >=9.38 breaking change — 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:54— // scala-steward:off //TODO 24.0.3 // update all quay.io/keycloak/keycloak — 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 pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/DidResolver.scala:39— // TODO: this probably should not be an instant, it should be a string — 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 pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/JWTVerification.scala:150— // TODO Implement other key 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.
TodoComment pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/JWTVerification.scala:222— // TODO Implement other key 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.
TodoComment pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:102— //TODO: refactor to use the new CredentialSchemaRef — 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 pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiablePresentationPayload.scala:626— // TODO: verify revocation status of credentials inside the presentation — 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 pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialRepository.scala:580— // TODO Move to config — 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 pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcPresentationRepository.scala:565— // TODO Move to config — 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 pollux/core/src/test/scala/org/hyperledger/identus/pollux/core/repository/CredentialRepositoryInMemory.scala:356— // TODO Move to config — 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 pollux/core/src/test/scala/org/hyperledger/identus/pollux/core/repository/CredentialRepositorySpecSuite.scala:17— // TODO Move to config — 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 pollux/core/src/test/scala/org/hyperledger/identus/pollux/core/repository/PresentationRepositoryInMemory.scala:412— // TODO Move to config — 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 pollux/core/src/test/scala/org/hyperledger/identus/pollux/core/repository/PresentationRepositorySpecSuite.scala:17— // TODO Move to config — 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 pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcPresentationRepository.scala:21— // TODO: replace with actual implementation — 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 pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/CompactFormat.scala:32— // TODO make error type — 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 pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/CompactFormat.scala:62— // TODO make error type — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/integration-tests/src/test/kotlin/models/Events.kt:35— // FIXME: rollback to PresentationStatus when Status is fixed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/integration-tests/src/test/kotlin/models/Events.kt:39— // FIXME: delete this class when PresentationStatus.Status is fixed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/integration-tests/src/test/kotlin/config/services/Agent.kt:62— // FIXME: hardcode port 10001 just to avoid invalid URL 'http://host.docker.internal:'
FixmeComment tests/integration-tests/src/test/kotlin/config/services/Agent.kt:65— // FIXME: hardcode port 10002 just to avoid invalid URL 'http://host.docker.internal:'
FixmeComment shared/predef/src/main/scala/org/hyperledger/identus/Predef.scala:20— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/JWTVerification.scala:194— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cloud-agent/service/server/src/main/scala/org/hyperledger/identus/oid4vci/domain/Openid4VCIProofJwtOps.scala:51— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cloud-agent/service/server/src/main/scala/org/hyperledger/identus/oid4vci/domain/Openid4VCIProofJwtOps.scala:61— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cloud-agent/service/server/src/main/scala/org/hyperledger/identus/oid4vci/domain/Openid4VCIProofJwtOps.scala:70— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment REDACTED:170— // FIXME: split shared DB stuff as subproject? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiablePresentationPayload.scala:273— //FIXME THIS WILL NOT WORK like that — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment pollux/core/src/test/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImplSpec.scala:101— // FIXME: update the assertion when when CredentialOffer attachment is realized — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment pollux/core/src/test/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImplSpec.scala:182— // FIXME: update the assertion when when CredentialOffer attachment is realized — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment pollux/core/src/test/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceSpec.scala:502— // assertTrue(updateRecord.requestPresentationData == Some(requestPresentation)) && // FIXME: enabling them make the test fail. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment pollux/core/src/test/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceSpec.scala:628— // assertTrue(updateRecord.requestPresentationData == Some(requestPresentation)) && // FIXME: enabling them make the test fail. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1128— // FIXME copy payload will probably not work for anoncreds! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1146— // FIXME !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment pollux/anoncreds/src/main/scala/org/hyperledger/identus/pollux/anoncreds/AnoncredLib.scala:182— // FIXME its always return false .... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment pollux/anoncreds/src/main/scala/org/hyperledger/identus/pollux/anoncreds/Models.scala:48— //FIXME use same names as in https://hyperledger.github.io/anoncreds-spec/#term:schemas
FixmeComment mercury/protocol-report-problem/src/main/scala/org/hyperledger/identus/mercury/protocol/reportproblem/v1/ReportProblem.scala:70— // case other extends Where // FIXME enum: cloud | edge | wire | agency | .. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/RequestPresentation.scala:41— // AtalaPrism Extension! //FIXME REMOVE — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment mercury/protocol-issue-credential/src/test/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredentialSpec.scala:19— // FIXME !!! THIS WILL FAIL! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment mercury/agent-didcommx/src/test/scala/org/hyperledger/identus/mercury/model/UnpackMessageImpSpec.scala:54— // FIXME fail — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment connect/core/src/test/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImplSpec.scala:191— // FIXME: Should the service return an Option while we have dedicated "not found" error for that case !? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cloud-agent/service/server/src/main/scala/org/hyperledger/identus/oid4vci/CredentialIssuerServerEndpoints.scala:29— // FIXME: this entity should be checked — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Change coupling: PresentationRepository.scala ↔ PresentationService.scala pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/repository/PresentationRepository.scala:1— `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/repository/PresentationRepository.scala` and `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationService.scala` change together 91% of the time (10 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `5e005560` fix: Add disclose claims to presentation record credential type SDJW…; `d22745fc` fix: add reportProcessingFailure back in PresentationRepository (#1232); `13e24473` fix: Present Error Handling (Part 1: Repo Changes) (#1172) — run `git show` on any of them.
Change coupling: CredentialRepository.scala ↔ CredentialService.scala pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/repository/CredentialRepository.scala:1— `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/repository/CredentialRepository.scala` and `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialService.scala` change together 79% of the time (11 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `693dcc45` feat: Default Backend API to Array Of Credential Schema (#1366); `b813faf5` fix: KeyID from String to Opaque Type and presentation job cleanup (…; `c0db5c8a` fix(pollux): add pagination at db level for getCredentialRecords (#586) (at that commit the files were still `pollux/lib/core/src/main/scala/io/iohk/atala/pollux/core/repository/CredentialRepository.scala` and `pollux/lib/core/src/main/scala/io/iohk/atala/pollux/core/service/CredentialService.scala`) — run `git show` on any of them.
Change coupling: ConnectionServiceImpl.scala ↔ JdbcConnectionRepository.scala connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:1— `connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala` and `connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/JdbcConnectionRepository.scala` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `7c31a9d4` feat: Handle Error Notify webhooks ATL-6934 (#1279); `71c776ba` feat: Accept goal and goalCode to create connection invitation (#785) (at that commit the files were still `connect/lib/core/src/main/scala/io/iohk/atala/connect/core/service/ConnectionServiceImpl.scala` and `connect/lib/sql-doobie/src/main/scala/io/iohk/atala/connect/sql/repository/JdbcConnectionRepository.scala`); `9a97c7a6` feat(prism-agent): expose connect/issue/presentation records 'thid' a… (at that commit the files were still `connect/lib/core/src/main/scala/io/iohk/atala/connect/core/service/ConnectionServiceImpl.scala` and `connect/lib/sql-doobie/src/main/scala/io/iohk/atala/connect/sql/repository/JdbcConnectionRepository.scala`) — run `git show` on any of them.
Change coupling: ConnectBackgroundJobs.scala ↔ PresentBackgroundJobs.scala cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:1— `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala` and `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala` change together 56% of the time (10 of the 18 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `7c31a9d4` feat: Handle Error Notify webhooks ATL-6934 (#1279); `52e31b07` fix(prism-agent): incorrect present proof metric name and remove conn… (at that commit the files were still `prism-agent/service/server/src/main/scala/io/iohk/atala/agent/server/jobs/ConnectBackgroundJobs.scala` and `prism-agent/service/server/src/main/scala/io/iohk/atala/agent/server/jobs/BackgroundJobs.scala`); `6a26bb78` fix(prism-agent): infinite loop in proof presentation execution (#540) (at that commit the files were still `prism-agent/service/server/src/main/scala/io/iohk/atala/agent/server/jobs/ConnectBackgroundJobs.scala` and `prism-agent/service/server/src/main/scala/io/iohk/atala/agent/server/jobs/BackgroundJobs.scala`) — run `git show` on any of them.
Change coupling: Modules.scala ↔ ManagedDIDServiceImpl.scala cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/Modules.scala:1— `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/Modules.scala` and `cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `7c57df0f` fix: LOG_LEVEL environment variable and cleanup logging entries (#1562); `dfb75778` feat: Configurations load improvement (#954) (at that commit the files were still `prism-agent/service/server/src/main/scala/io/iohk/atala/agent/server/Modules.scala` and `prism-agent/service/wallet-api/src/main/scala/io/iohk/atala/agent/walletapi/service/ManagedDIDServiceImpl.scala`); `3d4aacdd` fix(prism-agent): introduce generic secret store for CD (#727) (at that commit the files were still `prism-agent/service/server/src/main/scala/io/iohk/atala/agent/server/Modules.scala` and `prism-agent/service/wallet-api/src/main/scala/io/iohk/atala/agent/walletapi/service/ManagedDIDServiceImpl.scala`) — run `git show` on any of them.
Change coupling: PresentationService.scala ↔ JdbcPresentationRepository.scala pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationService.scala:1— `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationService.scala` and `pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcPresentationRepository.scala` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `5e005560` fix: Add disclose claims to presentation record credential type SDJW…; `d22745fc` fix: add reportProcessingFailure back in PresentationRepository (#1232); `13e24473` fix: Present Error Handling (Part 1: Repo Changes) (#1172) — run `git show` on any of them.
Change coupling: CredentialService.scala ↔ JdbcCredentialRepository.scala pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialService.scala:1— `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialService.scala` and `pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialRepository.scala` change together 52% of the time (12 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `693dcc45` feat: Default Backend API to Array Of Credential Schema (#1366); `b813faf5` fix: KeyID from String to Opaque Type and presentation job cleanup (…; `c0db5c8a` fix(pollux): add pagination at db level for getCredentialRecords (#586) (at that commit the files were still `pollux/lib/core/src/main/scala/io/iohk/atala/pollux/core/service/CredentialService.scala` and `pollux/lib/sql-doobie/src/main/scala/io/iohk/atala/pollux/sql/repository/JdbcCredentialRepository.scala`) — run `git show` on any of them.
Change coupling: PresentBackgroundJobs.scala ↔ PresentProofControllerImpl.scala cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:1— `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala` and `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/presentproof/controller/PresentProofControllerImpl.scala` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `e6581911` build: fix typo in repository causing flaky scalafmt (#1575); `54b7b5b7` feat: add feature flag to enable/disable support for Anoncred (backen…; `c18385c8` fix: Preserve Presentation Format (#1363) — run `git show` on any of them.
Change coupling: ProtoModelHelper.scala ↔ DIDService.scala castor/src/main/scala/org/hyperledger/identus/castor/core/model/ProtoModelHelper.scala:1— `castor/src/main/scala/org/hyperledger/identus/castor/core/model/ProtoModelHelper.scala` and `castor/src/main/scala/org/hyperledger/identus/castor/core/service/DIDService.scala` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `e1a5af20` feat: support NeoPRISM as node backend (#1693); `8384fe39` feat(castor): add support for context in DID document & operation (#489) (at that commit the files were still `castor/lib/core/src/main/scala/io/iohk/atala/castor/core/model/ProtoModelHelper.scala` and `castor/lib/core/src/main/scala/io/iohk/atala/castor/core/service/DIDService.scala`); `5ed09785` fix(castor): fix unintended ordering behavior when parsing long-form … (at that commit the files were still `castor/lib/core/src/main/scala/io/iohk/atala/castor/core/model/ProtoModelHelper.scala` and `castor/lib/core/src/main/scala/io/iohk/atala/castor/core/service/DIDService.scala`) — run `git show` on any of them.
FileTooLong: service/CredentialServiceImpl.scala pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala— FileTooLong — 1320 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: CredentialServiceImpl (80-1569). The bar is 500 significant lines; this is 820 over it, 2.64× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: jobs/PresentBackgroundJobs.scala cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala— FileTooLong — 1199 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 699 over it, 2.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: service/PresentationServiceImpl.scala pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala— FileTooLong — 1110 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 610 over it, 2.22× 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: REDACTED/VerifiableCredentialPayload.scala pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala— FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 132 over it, 1.26× 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: jobs/IssueBackgroundJobs.scala cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala— FileTooLong — 608 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 108 over it, 1.22× 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: repository/JdbcCredentialRepository.scala pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialRepository.scala— FileTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: JdbcCredentialRepository (23-577). The bar is 500 significant lines; this is 7 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5
Members sharing a duplicated core (4 members, 50+ identical tokens) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/castor/controller/DIDRegistrarController.scala:104— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/castor/controller/DIDRegistrarController.scala:104-120 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/event/controller/EventController.scala:50-66 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/wallet/http/controller/WalletManagementController.scala:51-66 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/prex/controller/PresentationExchangeController.scala:41-55 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:21— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:21-38 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:40-53 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerLogic.scala:21-38 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerLogic.scala:40-53 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/http/CredentialDefinitionDidUrlResponse.scala:18— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/http/CredentialDefinitionDidUrlResponse.scala:18-37 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/http/CredentialDefinitionDidUrlResponse.scala:47-67 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/http/CredentialSchemaDidUrlResponse.scala:18-38 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/http/CredentialSchemaDidUrlResponse.scala:49-67 — 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) pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:133— pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:133-159 | pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:167-189 | pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:196-215 | pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:236-255 — 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) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:161— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:161-177 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:188-206 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:148-167 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:178-199 — 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 (17 corresponding lines) · ×5
Edited copy of a member (17 corresponding lines) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZioHttpClient.scala:14— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZioHttpClient.scala:14-30 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZioHttpClient.scala:33-56 — 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) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:993— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:993-1012 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1036-1052 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/api/util/PaginationUtils.scala:21— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/api/util/PaginationUtils.scala:21-38 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/api/util/PaginationUtils.scala:45-61 — 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) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/sql/JdbcWalletNonSecretStorage.scala:57— cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/sql/JdbcWalletNonSecretStorage.scala:57-73 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcPresentationExchangeRepository.scala:44-60 — 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) mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/Presentation.scala:74— mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/Presentation.scala:74-90 | mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/RequestPresentation.scala:51-67 — 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 (9 corresponding lines) · ×5
Edited copy of a member (9 corresponding lines) mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:86— mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:86-94 | mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionResponse.scala:84-92 — 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) castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:106— castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:106-116 | castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:185-193 — 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) pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:672— pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:672-680 | pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:682-690 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/oid4vci/domain/Openid4VCIProofJwtOps.scala:49— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/oid4vci/domain/Openid4VCIProofJwtOps.scala:49-57 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/oid4vci/domain/Openid4VCIProofJwtOps.scala:68-77 — 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) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1002— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1002-1010 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1066-1074 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/apikey/ApiKeyAuthenticator.scala:17— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/apikey/ApiKeyAuthenticator.scala:17-34 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/oidc/KeycloakAuthenticator.scala:79-93 — 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) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:965— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:965-979 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:47-65 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:99— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:99-115 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerImpl.scala:129-143 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/IssueControllerImpl.scala:49— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/IssueControllerImpl.scala:49-63 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/presentproof/controller/PresentProofControllerImpl.scala:37-51 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×4
Edited copy of a member (11 corresponding lines) pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:721— pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:721-732 | pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:847-857 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/BackgroundJobsHelper.scala:225— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/BackgroundJobsHelper.scala:225-235 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:1101-1111 — 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) vdr/neoprism/src/main/scala/org/hyperledger/identus/agent/vdr/neoprism/NeoPrismVdrService.scala:104— vdr/neoprism/src/main/scala/org/hyperledger/identus/agent/vdr/neoprism/NeoPrismVdrService.scala:104-114 | vdr/neoprism/src/main/scala/org/hyperledger/identus/agent/vdr/neoprism/NeoPrismVdrService.scala:135-145 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/apikey/ApiKeyAuthenticatorImpl.scala:56— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/apikey/ApiKeyAuthenticatorImpl.scala:56-67 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/apikey/ApiKeyAuthenticatorImpl.scala:69-79 — 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.
Duplicated block (9 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/IssueControllerImpl.scala:130— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/IssueControllerImpl.scala:130-138 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/IssueControllerImpl.scala:165-173 — 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 `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/IssueControllerImpl.scala:130` 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) mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredential.scala:27— mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredential.scala:27-35 | mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/RequestCredential.scala:17-25 — 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) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:768— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:768-776 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1407-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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:768` 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) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:198— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:198-206 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:191-199 — 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 `pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:198` 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) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:176— cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:176-183 | cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:218-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:184` calls `validateInternalKeyRemoval` and `cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:226` 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 (8 lines × 2) mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:87— mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:87-94 | mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionResponse.scala:85-92 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:87` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/Presentation.scala:42— mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/Presentation.scala:42-49 | mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/ProposePresentation.scala:27-34 — 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) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:161— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:161-168 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:188-195 — 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 `pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:161` 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) castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:53— castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:53-59 | castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:103-109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:51` calls `validateUniquePublicKeyId`, `validateUniqueServiceId` and `castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:102` 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 (7 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:53— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:53-59 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:53-59 — 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 `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:53` 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) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1410— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1410-1416 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1425-1431 — 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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1410` 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) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:171— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:171-177 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:161-167 — 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 `pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:171` 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.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×3
Edited copy of a member (21 corresponding lines) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/Oid4vciAuthenticator.scala:35— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/Oid4vciAuthenticator.scala:35-55 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/oidc/KeycloakAuthenticatorImpl.scala:21-43 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:693— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:693-723 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:770-790 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/sql/JdbcDIDSecretStorage.scala:97— cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/sql/JdbcDIDSecretStorage.scala:97-120 | cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/sql/JdbcWalletSecretStorage.scala:39-59 — 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 copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) pollux/prex/src/main/scala/org/hyperledger/identus/pollux/prex/PresentationSubmissionVerification.scala:184— pollux/prex/src/main/scala/org/hyperledger/identus/pollux/prex/PresentationSubmissionVerification.scala:184-197 | pollux/prex/src/main/scala/org/hyperledger/identus/pollux/prex/PresentationSubmissionVerification.scala:202-215 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:669— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:669-682 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:1083-1096 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:123— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:123-136 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerImpl.scala:151-164 — 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 (8 corresponding lines) · ×3
Edited copy of a member (8 corresponding lines) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:36— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:36-43 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerImpl.scala:42-49 — 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) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:101— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:101-108 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:87-94 — 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) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:133— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:133-140 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:120-127 — 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 (6 corresponding lines) · ×3
Edited copy of a member (6 corresponding lines) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialDefinitionServiceImpl.scala:112— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialDefinitionServiceImpl.scala:112-117 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialSchemaServiceImpl.scala:39-44 — 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) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/primitives/UriString.scala:12— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/primitives/UriString.scala:12-17 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/primitives/UrlString.scala:11-16 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/http/IssueCredentialOfferInvitation.scala:29— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/http/IssueCredentialOfferInvitation.scala:29-34 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/presentproof/controller/http/OOBPresentationInvitation.scala:29-34 — 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.
Duplicated block (12 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:42— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:42-53 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerLogic.scala:42-53 — before extracting anything, compare `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala` and `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerLogic.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:42` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:185— cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:185-196 | cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:226-237 — 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 before the matched lines, `cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:184` calls `validateInternalKeyRemoval` and `cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:225` 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 (12 lines × 2) mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/Presentation.scala:95— mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/Presentation.scala:95-106 | mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/ProposePresentation.scala:65-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/Presentation.scala:95` 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.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×3
Recursive walk over a caller-supplied document has no depth cap shared/json/src/main/scala/org/hyperledger/identus/shared/json/JsonSchema.scala:37— `validate` is public and takes `claimsJsonNode: JsonNode` from its caller, and it calls itself at line 37 with a piece of `claimsJsonNode`, not as a tail call the compiler turns into a loop — and nowhere in `validate` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `validate` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap shared/json/src/main/scala/org/hyperledger/identus/shared/json/JsonSchema.scala:156— `deserialize` is public and takes `schema: zio.json.ast.Json` from its caller, and it calls itself at line 156 with a piece of `schema`, not as a tail call the compiler turns into a loop — and nowhere in `deserialize` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `deserialize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap mercury/agent-didcommx/src/main/scala/org/hyperledger/identus/mercury/model/Conversions.scala:49— `json2Map` is public and takes `json: Json` from its caller, and it calls itself at line 49 with a piece of `json` (and at line 52), not as a tail call the compiler turns into a loop — and nowhere in `json2Map` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `json2Map` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:47— castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:47-65 | castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:99-117 — 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:145— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:145-163 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerImpl.scala:173-192 — 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 (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:843— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:843-867 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:878-911 — 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) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialRepository.scala:463— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialRepository.scala:463-487 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialRepository.scala:491-520 — 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 (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/DidJWT.scala:67— pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/DidJWT.scala:67-78 | pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/DidJWT.scala:91-103 — 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) castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:319— castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:319-330 | castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:334-345 — 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.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) mercury/protocol-invitation/src/main/scala/org/hyperledger/identus/mercury/protocol/invitation/OutOfBand.scala:12— mercury/protocol-invitation/src/main/scala/org/hyperledger/identus/mercury/protocol/invitation/OutOfBand.scala:12-18 | mercury/protocol-outofband-login/src/main/scala/org/hyperledger/identus/mercury/protocol/outofbandlogin/Utils.scala:15-21 — 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) connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:287— connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:287-293 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1221-1229 — 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 (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/vault/VaultGenericSecretStorage.scala:38— cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/vault/VaultGenericSecretStorage.scala:38-47 | cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/vault/VaultDIDSecretStorage.scala:68-77 — 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) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialDefinitionRepository.scala:35— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialDefinitionRepository.scala:35-44 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialSchemaRepository.scala:31-40 — 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 (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialDefinitionServiceImpl.scala:119— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialDefinitionServiceImpl.scala:119-123 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialSchemaServiceImpl.scala:111-115 — 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) pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:658— pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:658-662 | pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiablePresentationPayload.scala:329-333 — 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 (29 lines × 2) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:106— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:106-134 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:146-174 — 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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:106` 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 (29 lines × 2) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialDefinitionRepository.scala:80— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialDefinitionRepository.scala:80-109 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialSchemaRepository.scala:83-111 — 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 `pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialDefinitionRepository.scala:80` 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 (21 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:177— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:177-197 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerImpl.scala:206-226 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/verification/VcVerificationServiceImpl.scala:53— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/verification/VcVerificationServiceImpl.scala:53-73 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/verification/VcVerificationServiceImpl.scala:103-123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/verification/VcVerificationServiceImpl.scala:53` 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 (16 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:23— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:23-38 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerLogic.scala:23-38 — before extracting anything, compare `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala` and `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerLogic.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:23` 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 (16 lines × 2) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1180— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1180-1195 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1250-1265 — 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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1180` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1196` calls `getJwtIssuer` and `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1266` 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 (11 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/Oid4vciAuthenticator.scala:43— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/Oid4vciAuthenticator.scala:43-53 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/oidc/KeycloakAuthenticatorImpl.scala:30-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:148— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:148-158 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:178-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala: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 (10 lines × 3) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/vdr/PrismNodeVdrOperationSigner.scala:161— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/vdr/PrismNodeVdrOperationSigner.scala:161-170 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/vdr/PrismNodeVdrOperationSigner.scala:189-198 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/vdr/PrismNodeVdrOperationSigner.scala:215-224 — 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 `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/vdr/PrismNodeVdrOperationSigner.scala:161` 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 × 3) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:56— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:56-65 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:827-836 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:859-868 — 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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:56` 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:844— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:844-853 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:879-888 — 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 `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:844` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:913— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:913-922 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1003-1012 — 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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:913` 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) mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:86— mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:86-92 | mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionResponse.scala:84-90 | mercury/protocol-report-problem/src/main/scala/org/hyperledger/identus/mercury/protocol/reportproblem/v2/ReportProblem.scala:222-228 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:86` 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) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:827— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:827-833 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:858-865 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:912-919 — 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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:858` 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) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/http/IssueCredentialRecord.scala:113— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/http/IssueCredentialRecord.scala:113-118 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/presentproof/controller/http/PresentationStatus.scala:77-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/http/IssueCredentialRecord.scala:113` 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 (6 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:166— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerImpl.scala:166-171 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerImpl.scala:195-200 — 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.
Off the main sequence: polluxAnoncreds — polluxAnoncreds: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: protocolInvitation — protocolInvitation: abstractness 0.07, instability 0.17, distance 0.76 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Swallowed exception (caught, then discarded) castor/src/main/scala/org/hyperledger/identus/castor/core/util/UriUtils.scala:101— `case _: Exception` 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) castor/src/main/scala/org/hyperledger/identus/castor/core/util/UriUtils.scala:112— `case _: Exception` 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.
IssueBackgroundJobs.performIssueCredentialExchange (cyclomatic 78) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:66— IssueBackgroundJobs.performIssueCredentialExchange has cyclomatic complexity 78 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
IssueControllerImpl.createCredentialOfferRecord (cyclomatic 27) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/IssueControllerImpl.scala:92— IssueControllerImpl.createCredentialOfferRecord has cyclomatic complexity 27 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CoordinateMediationPrograms.senderMediationRequestProgram (cyclomatic 27) mercury/agent/src/main/scala/org/hyperledger/identus/mercury/CoordinateMediationPrograms.scala:26— CoordinateMediationPrograms.senderMediationRequestProgram has cyclomatic complexity 27 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialServiceImpl.generateSDJWTCredential (cyclomatic 25) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1242— CredentialServiceImpl.generateSDJWTCredential has cyclomatic complexity 25 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationReceived.handleJWT (cyclomatic 24) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:1123— PresentationReceived.handleJWT has cyclomatic complexity 24 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This is NOT this file's highest cyclomatic complexity: PresentBackgroundJobs.performPresentProofExchange (cyclomatic 29) 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 method is counted neither in this dimension's figures nor in its score.
PresentationReceived.handleSDJWT (cyclomatic 22) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:1240— PresentationReceived.handleSDJWT has cyclomatic complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This is NOT this file's highest cyclomatic complexity: PresentBackgroundJobs.performPresentProofExchange (cyclomatic 29) 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 method is counted neither in this dimension's figures nor in its score.
DidUrlResolver.resolve (cyclomatic 22) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/uriResolvers/DidUrlResolver.scala:15— DidUrlResolver.resolve has cyclomatic complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialVerification.verifyCredentialStatus (cyclomatic 22) pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:541— CredentialVerification.verifyCredentialStatus has cyclomatic complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
MessagingService.makeMessage (cyclomatic 20) mercury/agent-didcommx/src/main/scala/org/hyperledger/identus/mercury/MessagingService.scala:31— MessagingService.makeMessage has cyclomatic complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ConnectBackgroundJobs.performExchange (cyclomatic 19) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:61— ConnectBackgroundJobs.performExchange has cyclomatic complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
VdrServiceImpl.layer (cyclomatic 19) vdr/proxy/src/main/scala/org/hyperledger/identus/agent/vdr/VdrService.scala:173— VdrServiceImpl.layer has cyclomatic complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
IssueControllerImpl.validatePrismDID (cyclomatic 17) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/IssueControllerImpl.scala:362— IssueControllerImpl.validatePrismDID has cyclomatic complexity 17 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CreateOperationValidator.validate (cyclomatic 16) castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:47— CreateOperationValidator.validate has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (UpdateOperationValidator.validate) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
UpdateOperationValidator.validate (cyclomatic 16) castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:99— UpdateOperationValidator.validate has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (CreateOperationValidator.validate) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
StatusListJobs.updateStatusList (cyclomatic 16) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/StatusListJobs.scala:72— StatusListJobs.updateStatusList has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
OperationFactory.makeUpdateOperation (cyclomatic 16) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/util/OperationFactory.scala:87— OperationFactory.makeUpdateOperation has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
IssueBackgroundJobs.performIssueCredentialExchange (cognitive 300) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:66— IssueBackgroundJobs.performIssueCredentialExchange has cognitive complexity 300 (threshold 15). Drivers by points: loops 59 (270 pts), if/else 6 (25 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 231). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CoordinateMediationPrograms.senderMediationRequestProgram (cognitive 249) mercury/agent/src/main/scala/org/hyperledger/identus/mercury/CoordinateMediationPrograms.scala:26— CoordinateMediationPrograms.senderMediationRequestProgram has cognitive complexity 249 (threshold 15). Drivers by points: loops 20 (210 pts), match/switch 3 (39 pts) (nesting depth added 226). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialServiceImpl.generateSDJWTCredential (cognitive 168) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1242— CredentialServiceImpl.generateSDJWTCredential has cognitive complexity 168 (threshold 15). Drivers by points: loops 14 (105 pts), match/switch 5 (62 pts), if/else 1 (nesting depth added 148). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
IssueControllerImpl.createCredentialOfferRecord (cognitive 132) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/IssueControllerImpl.scala:92— IssueControllerImpl.createCredentialOfferRecord has cognitive complexity 132 (threshold 15). Drivers by points: loops 20 (113 pts), match/switch 2 (10 pts), if/else 2 (9 pts) (nesting depth added 108). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialVerification.verifyCredentialStatus (cognitive 132) pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiableCredentialPayload.scala:541— CredentialVerification.verifyCredentialStatus has cognitive complexity 132 (threshold 15). Drivers by points: loops 16 (100 pts), if/else 6 (27 pts), match/switch 1 (5 pts) (nesting depth added 109). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationReceived.handleJWT (cognitive 127) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:1123— PresentationReceived.handleJWT has cognitive complexity 127 (threshold 15). Drivers by points: loops 17 (104 pts), match/switch 4 (21 pts), if/else 2 (nesting depth added 104). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CreateOperationValidator.validate (cognitive 120) castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:47— CreateOperationValidator.validate has cognitive complexity 120 (threshold 15). Drivers by points: loops 15 (120 pts) (nesting depth added 105). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (UpdateOperationValidator.validate) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
UpdateOperationValidator.validate (cognitive 120) castor/src/main/scala/org/hyperledger/identus/castor/core/util/DIDOperationValidator.scala:99— UpdateOperationValidator.validate has cognitive complexity 120 (threshold 15). Drivers by points: loops 15 (120 pts) (nesting depth added 105). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (CreateOperationValidator.validate) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PresentationReceived.handleSDJWT (cognitive 113) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:1240— PresentationReceived.handleSDJWT has cognitive complexity 113 (threshold 15). Drivers by points: loops 16 (95 pts), match/switch 3 (17 pts), if/else 1 (nesting depth added 93). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CloudAgentApp.run (cognitive 91) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/CloudAgentApp.scala:33— CloudAgentApp.run has cognitive complexity 91 (threshold 15). Drivers by points: loops 13 (91 pts) (nesting depth added 78). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
VdrServiceImpl.layer (cognitive 86) vdr/proxy/src/main/scala/org/hyperledger/identus/agent/vdr/VdrService.scala:173— VdrServiceImpl.layer has cognitive complexity 86 (threshold 15). Drivers by points: loops 10 (55 pts), match/switch 3 (19 pts), if/else 2 (11 pts), boolean chains 1 (nesting depth added 70). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialServiceImpl.generateJWTCredential (cognitive 78) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1176— CredentialServiceImpl.generateJWTCredential has cognitive complexity 78 (threshold 15). Drivers by points: loops 12 (78 pts) (nesting depth added 66). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
StatusListJobs.updateStatusList (cognitive 73) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/StatusListJobs.scala:72— StatusListJobs.updateStatusList has cognitive complexity 73 (threshold 15). Drivers by points: loops 11 (57 pts), match/switch 2 (15 pts), boolean chains 1 (nesting depth added 59). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ManagedDIDServiceImpl.updateManagedDID (cognitive 69) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:168— ManagedDIDServiceImpl.updateManagedDID has cognitive complexity 69 (threshold 15). Drivers by points: loops 11 (66 pts), match/switch 1 (3 pts) (nesting depth added 57). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialServiceImpl.generateCredentialRequest (cognitive 66) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:677— CredentialServiceImpl.generateCredentialRequest has cognitive complexity 66 (threshold 15). Drivers by points: loops 11 (66 pts) (nesting depth added 55). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ConnectBackgroundJobs.performExchange (cognitive 64) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:61— ConnectBackgroundJobs.performExchange has cognitive complexity 64 (threshold 15). Drivers by points: loops 12 (46 pts), if/else 5 (15 pts), boolean chains 2, match/switch 1 (nesting depth added 44). 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.
DidUrlResolver.resolve (cognitive 62) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/uriResolvers/DidUrlResolver.scala:15— DidUrlResolver.resolve has cognitive complexity 62 (threshold 15). Drivers by points: loops 9 (45 pts), match/switch 3 (16 pts), boolean chains 1 (nesting depth added 49). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialSchemaServiceImpl.update (cognitive 52) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialSchemaServiceImpl.scala:55— CredentialSchemaServiceImpl.update has cognitive complexity 52 (threshold 15). Drivers by points: loops 8 (36 pts), match/switch 2 (13 pts), if/else 2 (3 pts) (nesting depth added 40). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationServiceImpl.verifyAnoncredPresentation (cognitive 50) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1156— PresentationServiceImpl.verifyAnoncredPresentation has cognitive complexity 50 (threshold 15). Drivers by points: loops 8 (34 pts), if/else 4 (10 pts), match/switch 2 (6 pts) (nesting depth added 36). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PrismNodeVdrService.read (cognitive 49) vdr/prism-node/src/main/scala/org/hyperledger/identus/agent/vdr/PrismNodeVdrService.scala:110— PrismNodeVdrService.read has cognitive complexity 49 (threshold 15). Drivers by points: loops 8 (36 pts), if/else 4 (12 pts), match/switch 1 (nesting depth added 36). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
MessagingService.makeMessage (cognitive 48) mercury/agent-didcommx/src/main/scala/org/hyperledger/identus/mercury/MessagingService.scala:31— MessagingService.makeMessage has cognitive complexity 48 (threshold 15). Drivers by points: loops 8 (36 pts), match/switch 3 (12 pts) (nesting depth added 37). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
MessagingService.consumeWithRetryStrategy (cognitive 48) shared/core/src/main/scala/org/hyperledger/identus/shared/messaging/MessagingService.scala:21— MessagingService.consumeWithRetryStrategy has cognitive complexity 48 (threshold 15). Drivers by points: loops 10 (41 pts), match/switch 1 (7 pts) (nesting depth added 37). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialIssuerControllerImpl.issueJwtCredential (cognitive 47) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/oid4vci/controller/CredentialIssuerController.scala:162— CredentialIssuerControllerImpl.issueJwtCredential has cognitive complexity 47 (threshold 15). Drivers by points: loops 8 (44 pts), match/switch 2 (3 pts) (nesting depth added 37). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
IssueControllerImpl.validatePrismDID (cognitive 46) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/issue/controller/IssueControllerImpl.scala:362— IssueControllerImpl.validatePrismDID has cognitive complexity 46 (threshold 15). Drivers by points: loops 9 (36 pts), match/switch 1 (6 pts), if/else 2 (4 pts) (nesting depth added 34). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialDefinitionServiceImpl.create (cognitive 46) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialDefinitionServiceImpl.scala:42— CredentialDefinitionServiceImpl.create has cognitive complexity 46 (threshold 15). Drivers by points: loops 9 (45 pts), match/switch 1 (nesting depth added 36). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationServiceImpl.createAnoncredPresentationPayloadFromCredential (cognitive 46) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:694— PresentationServiceImpl.createAnoncredPresentationPayloadFromCredential has cognitive complexity 46 (threshold 15). Drivers by points: loops 8 (36 pts), match/switch 2 (8 pts), if/else 2 (nesting depth added 34). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationPending.findHolderPrivateKeyFromCredentials (cognitive 44) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:871— PresentationPending.findHolderPrivateKeyFromCredentials has cognitive complexity 44 (threshold 15). Drivers by points: loops 8 (36 pts), match/switch 1 (8 pts) (nesting depth added 35). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
MessagingService.send (cognitive 44) mercury/agent-didcommx/src/main/scala/org/hyperledger/identus/mercury/MessagingService.scala:117— MessagingService.send has cognitive complexity 44 (threshold 15). Drivers by points: loops 8 (36 pts), if/else 2 (5 pts), match/switch 1 (3 pts) (nesting depth added 33). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationPending.createPrismDIDIssuerFromPresentationCredentials (cognitive 41) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:836— PresentationPending.createPrismDIDIssuerFromPresentationCredentials has cognitive complexity 41 (threshold 15). Drivers by points: loops 8 (36 pts), match/switch 1 (5 pts) (nesting depth added 32). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Verifier.handleRequestPending (cognitive 40) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:982— Verifier.handleRequestPending has cognitive complexity 40 (threshold 15). Drivers by points: loops 8 (31 pts), if/else 2 (8 pts), boolean chains 1 (nesting depth added 29). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialServiceImpl.createAnonCredsCredential (cognitive 40) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1394— CredentialServiceImpl.createAnonCredsCredential has cognitive complexity 40 (threshold 15). Drivers by points: loops 7 (28 pts), match/switch 2 (10 pts), if/else 2 (nesting depth added 29). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
JdbcCredentialStatusListRepository.incrementAndGetStatusListIndex (cognitive 39) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialStatusListRepository.scala:51— JdbcCredentialStatusListRepository.incrementAndGetStatusListIndex has cognitive complexity 39 (threshold 15). Drivers by points: loops 8 (32 pts), match/switch 1 (6 pts), if/else 1 (nesting depth added 29). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
OID4VCIIssuerMetadataServiceImpl.createCredentialConfiguration (cognitive 37) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/OID4VCIIssuerMetadataService.scala:141— OID4VCIIssuerMetadataServiceImpl.createCredentialConfiguration has cognitive complexity 37 (threshold 15). Drivers by points: loops 7 (28 pts), match/switch 2 (8 pts), if/else 1 (nesting depth added 27). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationServiceImpl.createSDJwtPresentationFromRecord (cognitive 36) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:101— PresentationServiceImpl.createSDJwtPresentationFromRecord has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 4 other methods here (PresentationServiceImpl.createPresentationFromRecord, PresentationServiceImpl.acceptRequestPresentation, PresentationServiceImpl.acceptSDJWTRequestPresentation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PresentationServiceImpl.createPresentationFromRecord (cognitive 36) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:142— PresentationServiceImpl.createPresentationFromRecord has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 4 other methods here (PresentationServiceImpl.createSDJwtPresentationFromRecord, PresentationServiceImpl.acceptRequestPresentation, PresentationServiceImpl.acceptSDJWTRequestPresentation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PresentationServiceImpl.acceptRequestPresentation (cognitive 36) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:811— PresentationServiceImpl.acceptRequestPresentation has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 4 other methods here (PresentationServiceImpl.createSDJwtPresentationFromRecord, PresentationServiceImpl.createPresentationFromRecord, PresentationServiceImpl.acceptSDJWTRequestPresentation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PresentationServiceImpl.acceptSDJWTRequestPresentation (cognitive 36) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:837— PresentationServiceImpl.acceptSDJWTRequestPresentation has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 4 other methods here (PresentationServiceImpl.createSDJwtPresentationFromRecord, PresentationServiceImpl.createPresentationFromRecord, PresentationServiceImpl.acceptRequestPresentation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PresentationServiceImpl.acceptAnoncredRequestPresentation (cognitive 36) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:886— PresentationServiceImpl.acceptAnoncredRequestPresentation has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 4 other methods here (PresentationServiceImpl.createSDJwtPresentationFromRecord, PresentationServiceImpl.createPresentationFromRecord, PresentationServiceImpl.acceptRequestPresentation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 5 times rather than 5 independent problems. Splitting this body alone leaves the other 4 exactly as they are. Where these are variations on one operation, the change that clears all 5 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ManagedDIDServiceImpl.deactivateManagedDID (cognitive 33) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:207— ManagedDIDServiceImpl.deactivateManagedDID has cognitive complexity 33 (threshold 15). Drivers by points: loops 9 (31 pts), match/switch 1 (2 pts) (nesting depth added 23). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Prover.handlePresentationGenerated (cognitive 32) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:914— Prover.handlePresentationGenerated has cognitive complexity 32 (threshold 15). Drivers by points: loops 7 (24 pts), if/else 2 (7 pts), boolean chains 1 (nesting depth added 22). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
VaultKVClientImpl.vaultTokenRefreshLogic (cognitive 32) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/vault/VaultClient.scala:73— VaultKVClientImpl.vaultTokenRefreshLogic has cognitive complexity 32 (threshold 15). Drivers by points: loops 8 (32 pts) (nesting depth added 24). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialServiceImpl.receiveCredentialIssue (cognitive 31) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:833— CredentialServiceImpl.receiveCredentialIssue has cognitive complexity 31 (threshold 15). Drivers by points: loops 7 (26 pts), match/switch 1 (4 pts), if/else 1 (nesting depth added 22). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
UriUtils.normalizeUri (cognitive 30) castor/src/main/scala/org/hyperledger/identus/castor/core/util/UriUtils.scala:19— UriUtils.normalizeUri has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 3 (6 pts), error handling 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletManagementServiceImpl.createWallet (cognitive 29) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/WalletManagementServiceImpl.scala:26— WalletManagementServiceImpl.createWallet has cognitive complexity 29 (threshold 15). Drivers by points: loops 6 (21 pts), match/switch 3 (8 pts) (nesting depth added 20). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationServiceImpl.receiveRequestPresentation (cognitive 29) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:489— PresentationServiceImpl.receiveRequestPresentation has cognitive complexity 29 (threshold 15). Drivers by points: loops 6 (21 pts), match/switch 3 (6 pts), if/else 2 (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationServiceImpl.createPresentationFromIssuedCredential (cognitive 29) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:550— PresentationServiceImpl.createPresentationFromIssuedCredential has cognitive complexity 29 (threshold 15). Drivers by points: loops 6 (21 pts), match/switch 1 (7 pts), if/else 1 (nesting depth added 21). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationReceived.handleAnoncred (cognitive 28) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:1305— PresentationReceived.handleAnoncred has cognitive complexity 28 (threshold 15). Drivers by points: loops 8 (28 pts) (nesting depth added 20). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
StatusListJobs.sendRevocationNotificationMessage (cognitive 28) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/StatusListJobs.scala:148— StatusListJobs.sendRevocationNotificationMessage has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 pts) (nesting depth added 21). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
DIDCommControllerImpl.unpackMessage (cognitive 28) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/didcomm/controller/DIDCommControllerImpl.scala:70— DIDCommControllerImpl.unpackMessage has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 pts) (nesting depth added 21). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PrismNodeVdrOperationSigner.selectDid (cognitive 28) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/vdr/PrismNodeVdrOperationSigner.scala:35— PrismNodeVdrOperationSigner.selectDid has cognitive complexity 28 (threshold 15). Drivers by points: loops 4 (14 pts), match/switch 4 (13 pts), if/else 1 (nesting depth added 19). 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.
ConnectionServiceImpl.acceptConnectionRequest (cognitive 28) connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:215— ConnectionServiceImpl.acceptConnectionRequest has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 pts) (nesting depth added 21). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialServiceImpl.generateAnonCredsCredentialRequest (cognitive 28) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:723— CredentialServiceImpl.generateAnonCredsCredentialRequest has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 pts) (nesting depth added 21). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationPending.handle_JWT_VC (cognitive 26) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:685— PresentationPending.handle_JWT_VC has cognitive complexity 26 (threshold 15). Drivers by points: loops 8 (26 pts) (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentBackgroundJobs.handleMessage (cognitive 25) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:75— PresentBackgroundJobs.handleMessage has cognitive complexity 25 (threshold 15). Drivers by points: loops 6 (21 pts), match/switch 1 (4 pts) (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
StatusListJobs.updateBitStringForCredentialAndNotify (cognitive 25) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/StatusListJobs.scala:119— StatusListJobs.updateBitStringForCredentialAndNotify has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (10 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OperationFactory.makeUpdateOperation (cognitive 25) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/util/OperationFactory.scala:87— OperationFactory.makeUpdateOperation has cognitive complexity 25 (threshold 15). Drivers by points: match/switch 7 (18 pts), if/else 3 (4 pts), loops 2 (3 pts) (nesting depth added 13). 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.
CredentialServiceImpl.receiveCredentialOffer (cognitive 25) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:370— CredentialServiceImpl.receiveCredentialOffer has cognitive complexity 25 (threshold 15). Drivers by points: loops 6 (21 pts), match/switch 1 (3 pts), if/else 1 (nesting depth added 17). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialServiceImpl.acceptCredentialOffer (cognitive 25) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:493— CredentialServiceImpl.acceptCredentialOffer has cognitive complexity 25 (threshold 15). Drivers by points: loops 7 (22 pts), match/switch 1 (2 pts), if/else 1 (nesting depth added 16). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
MainApp.run (cognitive 24) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/MainApp.scala:115— MainApp.run has cognitive complexity 24 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 6 (9 pts) (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationPending.handleAnoncred (cognitive 24) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:792— PresentationPending.handleAnoncred has cognitive complexity 24 (threshold 15). Drivers by points: loops 6 (23 pts), match/switch 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ManagedDIDServiceWithEventNotificationImpl.computeNewDIDStateFromDLTAndPersist (cognitive 24) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceWithEventNotificationImpl.scala:34— ManagedDIDServiceWithEventNotificationImpl.computeNewDIDStateFromDLTAndPersist has cognitive complexity 24 (threshold 15). Drivers by points: loops 7 (24 pts) (nesting depth added 17). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialStatusListServiceImpl.revokeByIssueCredentialRecordId (cognitive 23) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialStatusListServiceImpl.scala:35— CredentialStatusListServiceImpl.revokeByIssueCredentialRecordId has cognitive complexity 23 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 4 (8 pts) (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationPending.handle_SD_JWT_VC (cognitive 21) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:762— PresentationPending.handle_SD_JWT_VC has cognitive complexity 21 (threshold 15). Drivers by points: loops 7 (21 pts) (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
KeycloakPermissionManagementService.grantWalletToUser (cognitive 21) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authorization/keycloak/admin/KeycloakPermissionManagementService.scala:27— KeycloakPermissionManagementService.grantWalletToUser has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (KeycloakPermissionManagementService.revokeWalletFromUser) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
KeycloakPermissionManagementService.revokeWalletFromUser (cognitive 21) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authorization/keycloak/admin/KeycloakPermissionManagementService.scala:110— KeycloakPermissionManagementService.revokeWalletFromUser has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (KeycloakPermissionManagementService.grantWalletToUser) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ManagedDIDServiceImpl.createAndStoreDID (cognitive 21) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/ManagedDIDServiceImpl.scala:150— ManagedDIDServiceImpl.createAndStoreDID has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ConnectionServiceImpl.receiveConnectionInvitation (cognitive 21) connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:107— ConnectionServiceImpl.receiveConnectionInvitation has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (ConnectionServiceImpl.acceptConnectionInvitation) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ConnectionServiceImpl.acceptConnectionInvitation (cognitive 21) connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:139— ConnectionServiceImpl.acceptConnectionInvitation has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (ConnectionServiceImpl.receiveConnectionInvitation) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CredentialSchema.validateAnonCredsClaims (cognitive 21) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/schema/CredentialSchema.scala:173— CredentialSchema.validateAnonCredsClaims has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (10 pts), match/switch 2 (9 pts), if/else 2 (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CredentialServiceImpl.createAnonCredsIssueCredentialRecord (cognitive 21) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:298— CredentialServiceImpl.createAnonCredsIssueCredentialRecord has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (CredentialServiceImpl.receiveCredentialRequest, CredentialServiceImpl.acceptCredentialRequest) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CredentialServiceImpl.receiveCredentialRequest (cognitive 21) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:788— CredentialServiceImpl.receiveCredentialRequest has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (CredentialServiceImpl.createAnonCredsIssueCredentialRecord, CredentialServiceImpl.acceptCredentialRequest) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CredentialServiceImpl.acceptCredentialRequest (cognitive 21) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:811— CredentialServiceImpl.acceptCredentialRequest has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (CredentialServiceImpl.createAnonCredsIssueCredentialRecord, CredentialServiceImpl.receiveCredentialRequest) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PresentationServiceImpl.createJwtPresentationPayloadFromRecord (cognitive 21) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:67— PresentationServiceImpl.createJwtPresentationPayloadFromRecord has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 3 other methods here (PresentationServiceImpl.receivePresentation, PresentationServiceImpl.acceptProposePresentation, PresentationServiceImpl.receiveProposePresentation) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PresentationServiceImpl.receivePresentation (cognitive 21) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:991— PresentationServiceImpl.receivePresentation has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 3 other methods here (PresentationServiceImpl.createJwtPresentationPayloadFromRecord, PresentationServiceImpl.acceptProposePresentation, PresentationServiceImpl.receiveProposePresentation) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PresentationServiceImpl.acceptProposePresentation (cognitive 21) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1014— PresentationServiceImpl.acceptProposePresentation has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 3 other methods here (PresentationServiceImpl.createJwtPresentationPayloadFromRecord, PresentationServiceImpl.receivePresentation, PresentationServiceImpl.receiveProposePresentation) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PresentationServiceImpl.receiveProposePresentation (cognitive 21) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1034— PresentationServiceImpl.receiveProposePresentation has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 3 other methods here (PresentationServiceImpl.createJwtPresentationPayloadFromRecord, PresentationServiceImpl.receivePresentation, PresentationServiceImpl.acceptProposePresentation) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
NeoPrismVdrService.update (cognitive 21) vdr/neoprism/src/main/scala/org/hyperledger/identus/agent/vdr/neoprism/NeoPrismVdrService.scala:96— NeoPrismVdrService.update has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (NeoPrismVdrService.delete) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
NeoPrismVdrService.delete (cognitive 21) vdr/neoprism/src/main/scala/org/hyperledger/identus/agent/vdr/neoprism/NeoPrismVdrService.scala:130— NeoPrismVdrService.delete has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (NeoPrismVdrService.update) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PrismNodeVdrService.update (cognitive 21) vdr/prism-node/src/main/scala/org/hyperledger/identus/agent/vdr/PrismNodeVdrService.scala:85— PrismNodeVdrService.update has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (PrismNodeVdrService.delete) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PrismNodeVdrService.delete (cognitive 21) vdr/prism-node/src/main/scala/org/hyperledger/identus/agent/vdr/PrismNodeVdrService.scala:148— PrismNodeVdrService.delete has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (PrismNodeVdrService.update) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
KeycloakPermissionManagementService.listWalletPermissions (cognitive 20) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authorization/keycloak/admin/KeycloakPermissionManagementService.scala:156— KeycloakPermissionManagementService.listWalletPermissions has cognitive complexity 20 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 3 (5 pts) (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ConnectionServiceImpl.receiveConnectionRequest (cognitive 20) connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceImpl.scala:186— ConnectionServiceImpl.receiveConnectionRequest has cognitive complexity 20 (threshold 15). Drivers by points: loops 6 (17 pts), if/else 2 (3 pts) (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
InMemoryProducer.produce (cognitive 20) shared/core/src/main/scala/org/hyperledger/identus/shared/messaging/kafka/InMemoryMessagingService.scala:81— InMemoryProducer.produce has cognitive complexity 20 (threshold 15). Drivers by points: loops 7 (19 pts), match/switch 1 (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
NeoPrismVdrService.read (cognitive 20) vdr/neoprism/src/main/scala/org/hyperledger/identus/agent/vdr/neoprism/NeoPrismVdrService.scala:116— NeoPrismVdrService.read has cognitive complexity 20 (threshold 15). Drivers by points: loops 5 (15 pts), match/switch 2 (5 pts) (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ConnectBackgroundJobs.handleMessage (cognitive 19) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:35— ConnectBackgroundJobs.handleMessage has cognitive complexity 19 (threshold 15). Drivers by points: loops 6 (19 pts) (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
IssueBackgroundJobs.handleMessage (cognitive 19) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:35— IssueBackgroundJobs.handleMessage has cognitive complexity 19 (threshold 15). Drivers by points: loops 6 (19 pts) (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
JwtPresentation.verify (cognitive 19) pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiablePresentationPayload.scala:622— JwtPresentation.verify has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 6 (9 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PrismDID.fromString (cognitive 18) castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDID.scala:57— PrismDID.fromString has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (14 pts), if/else 3, match/switch 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
NeoPrismClientImpl.getDIDData (cognitive 18) castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:118— NeoPrismClientImpl.getDIDData has cognitive complexity 18 (threshold 15). Drivers by points: loops 5 (15 pts), match/switch 1 (2 pts), if/else 1 (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
BackgroundJobsHelper.createJwtVcIssuer (cognitive 18) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/BackgroundJobsHelper.scala:64— BackgroundJobsHelper.createJwtVcIssuer has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (10 pts), match/switch 2 (7 pts), boolean chains 1 (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PresentationSubmissionVerification.extractSubmissionEntry (cognitive 18) pollux/prex/src/main/scala/org/hyperledger/identus/pollux/prex/PresentationSubmissionVerification.scala:158— PresentationSubmissionVerification.extractSubmissionEntry has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (5 pts), match/switch 1 (3 pts) (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
JWTVerification.extractPublicKey (cognitive 18) pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/JWTVerification.scala:223— JWTVerification.extractPublicKey has cognitive complexity 18 (threshold 15). Drivers by points: loops 5 (15 pts), match/switch 1 (3 pts) (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
InMemoryConsumer.consume (cognitive 18) shared/core/src/main/scala/org/hyperledger/identus/shared/messaging/kafka/InMemoryMessagingService.scala:37— InMemoryConsumer.consume has cognitive complexity 18 (threshold 15). Drivers by points: loops 5 (13 pts), match/switch 3 (5 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PrismVdrLogic.fetchLatestHead (cognitive 18) vdr/core/src/main/scala/org/hyperledger/identus/agent/vdr/PrismVdrLogic.scala:52— PrismVdrLogic.fetchLatestHead has cognitive complexity 18 (threshold 15). Drivers by points: loops 5 (15 pts), match/switch 1 (3 pts) (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
BitString.encoded (cognitive 17) pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/revocation/BitString.scala:22— BitString.encoded has cognitive complexity 17 (threshold 15). Drivers by points: loops 6 (17 pts) (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
WebhookPublisher.pollAndNotify (cognitive 16) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/notification/WebhookPublisher.scala:59— WebhookPublisher.pollAndNotify has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (15 pts), boolean chains 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
KeycloakAuthenticatorImpl.authenticate (cognitive 16) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/authentication/oidc/KeycloakAuthenticatorImpl.scala:21— KeycloakAuthenticatorImpl.authenticate has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (14 pts), if/else 2 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ConnectionRequest.fromMessage (cognitive 16) mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:45— ConnectionRequest.fromMessage has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 2 (7 pts), loops 3 (6 pts), if/else 3 (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.
ConnectionResponse.fromMessage (cognitive 16) mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionResponse.scala:41— ConnectionResponse.fromMessage has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 2 (7 pts), loops 3 (6 pts), if/else 3 (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.
TrustPing.fromMessage (cognitive 16) mercury/protocol-trust-ping/src/main/scala/org/hyperledger/identus/mercury/protocol/trustping/TrustPing.scala:44— TrustPing.fromMessage has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 2 (7 pts), loops 3 (6 pts), if/else 3 (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.
CredentialServiceImpl.validateRequestCredentialDataProof (cognitive 16) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1484— CredentialServiceImpl.validateRequestCredentialDataProof has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), match/switch 3 (6 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
JwtPresentation.verifyHolderBinding (cognitive 16) pollux/vc-jwt/src/main/scala/org/hyperledger/identus/pollux/vc/jwt/VerifiablePresentationPayload.scala:492— JwtPresentation.verifyHolderBinding has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 4 (7 pts), match/switch 1 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
BlockfrostPrismDriverProvider.createIndexerDirectories (cognitive 16) vdr/blockfrost/src/main/scala/org/hyperledger/identus/agent/vdr/blockfrost/BlockfrostPrismDriverProvider.scala:64— BlockfrostPrismDriverProvider.createIndexerDirectories has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (6 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PrismNodeVdrService.verify (cognitive 16) vdr/prism-node/src/main/scala/org/hyperledger/identus/agent/vdr/PrismNodeVdrService.scala:171— PrismNodeVdrService.verify has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (6 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
MethodTooLong: Connection.fromDomain cloud-agent/service/server/src/main/scala/org/hyperledger/identus/connect/controller/http/Connection.scala:72— MethodTooLong — fromDomain runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1526— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:1526-1568 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:1313-1356 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (49 corresponding lines) · ×1
Edited copy of a member (49 corresponding lines) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/verification/VcVerificationServiceImpl.scala:52— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/verification/VcVerificationServiceImpl.scala:52-100 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/verification/VcVerificationServiceImpl.scala:102-153 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:186— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:186-216 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:258-292 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:214— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:214-246 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:263-296 — 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 copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:39— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:39-59 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:38-60 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:78-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 29+ corresponding lines) · ×1
Edited copies of one member (3 members, 29+ corresponding lines) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:71— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:71-99 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:104-140 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:144-180 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 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, 24+ corresponding lines) · ×1
Edited copies of one member (3 members, 24+ corresponding lines) mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:46— mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionRequest.scala:46-71 | mercury/protocol-connection/src/main/scala/org/hyperledger/identus/mercury/protocol/connection/ConnectionResponse.scala:42-67 | mercury/protocol-trust-ping/src/main/scala/org/hyperledger/identus/mercury/protocol/trustping/TrustPing.scala:45-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 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, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:814— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:814-836 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:841-868 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:889-922 — 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 copies of one member (5 members, 19+ corresponding lines) · ×1
Edited copies of one member (5 members, 19+ corresponding lines) mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredential.scala:90— mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredential.scala:90-111 | mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/OfferCredential.scala:104-125 | mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/ProposeCredential.scala:80-100 | mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/RequestCredential.scala:72-93 | mercury/protocol-revocation-notification/src/main/scala/org/hyperledger/identus/mercury/protocol/revocationnotificaiton/RevocationNotification.scala:60-78 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 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, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/vdr/PrismNodeVdrOperationSigner.scala:161— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/vdr/PrismNodeVdrOperationSigner.scala:161-178 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/vdr/PrismNodeVdrOperationSigner.scala:189-205 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/vdr/PrismNodeVdrOperationSigner.scala:215-230 — 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 copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredentialInvitation.scala:17— mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredentialInvitation.scala:17-32 | mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/PresentProofInvitation.scala:17-32 — 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 copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/vault/VaultDIDSecretStorage.scala:16— cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/vault/VaultDIDSecretStorage.scala:16-26 | cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/vault/VaultDIDSecretStorage.scala:41-52 | cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/vault/VaultGenericSecretStorage.scala:13-24 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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, 39+ corresponding lines) · ×1
Edited copies of one member (3 members, 39+ corresponding lines) connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/JdbcConnectionRepository.scala:148— connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/JdbcConnectionRepository.scala:148-186 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialRepository.scala:196-241 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcPresentationRepository.scala:253-297 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 39 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, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/Presentation.scala:92— mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/Presentation.scala:92-106 | mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/ProposePresentation.scala:61-76 | mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/RequestPresentation.scala:70-83 | mercury/protocol-report-problem/src/main/scala/org/hyperledger/identus/mercury/protocol/reportproblem/v2/ReportProblem.scala:53-66 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceNotifier.scala:84— connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionServiceNotifier.scala:84-91 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceNotifier.scala:222-229 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceNotifier.scala:212-219 — 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.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/verification/VcVerificationServiceImpl.scala:218— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/verification/VcVerificationServiceImpl.scala:218-235 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/verification/VcVerificationServiceImpl.scala:268-285 — 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 copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredential.scala:51— mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredential.scala:51-62 | mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/OfferCredential.scala:54-65 | mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/RequestCredential.scala:40-51 — 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 (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/OfferCredential.scala:29— mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/OfferCredential.scala:29-37 | mercury/protocol-report-problem/src/main/scala/org/hyperledger/identus/mercury/protocol/reportproblem/v2/ReportProblem.scala:222-231 | mercury/protocol-revocation-notification/src/main/scala/org/hyperledger/identus/mercury/protocol/revocationnotificaiton/RevocationNotification.scala:16-23 | mercury/protocol-trust-ping/src/main/scala/org/hyperledger/identus/mercury/protocol/trustping/TrustPing.scala:16-22 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/ControllerHelper.scala:57— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/ControllerHelper.scala:57-59 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/presentproof/controller/PresentProofController.scala:49-51 — 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 (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/JdbcConnectionRepository.scala:219— connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/JdbcConnectionRepository.scala:219-222 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcCredentialRepository.scala: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 (33–40 lines × 2) connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/JdbcConnectionRepository.scala:149— connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/JdbcConnectionRepository.scala:149-181 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/JdbcPresentationRepository.scala:254-293 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (22 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:505— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:505-526 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:556-577 — 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 `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:505` 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 (18–19 lines × 3) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:286— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:286-304 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:335-352 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:383-401 — 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 `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:286` 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–19 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:587— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:587-604 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:636-654 — 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 `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:587` 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–18 lines × 4) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/http/CredentialDefinitionDidUrlResponse.scala:22— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/http/CredentialDefinitionDidUrlResponse.scala:22-37 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/http/CredentialDefinitionDidUrlResponse.scala:50-67 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/http/CredentialSchemaDidUrlResponse.scala:23-38 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/http/CredentialSchemaDidUrlResponse.scala:52-67 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/http/CredentialDefinitionDidUrlResponse.scala:22` 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 (16–17 lines × 3) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:77— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:77-92 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:113-129 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:153-169 — 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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:77` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–15 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZioHttpClient.scala:18— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZioHttpClient.scala:18-30 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZioHttpClient.scala:42-56 — 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 `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZioHttpClient.scala:18` 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–15 lines × 2) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:202— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:202-216 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:279-292 — 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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:202` 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 × 3) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala:60— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala:60-73 | connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/Migrations.scala:60-73 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/Migrations.scala:61-74 — before extracting anything, compare `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala` and `connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/Migrations.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredentialInvitation.scala:19— mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredentialInvitation.scala:19-32 | mercury/protocol-present-proof/src/main/scala/org/hyperledger/identus/mercury/protocol/presentproof/PresentProofInvitation.scala:19-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `mercury/protocol-issue-credential/src/main/scala/org/hyperledger/identus/mercury/protocol/issuecredential/IssueCredentialInvitation.scala:19` 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 (13 lines × 3) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala:76— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala:76-88 | connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/Migrations.scala:76-88 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/Migrations.scala:77-89 — before extracting anything, compare `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala` and `connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/Migrations.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:203— pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:203-215 | pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:243-255 — 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 `pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:203` 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 (10–12 lines × 2) pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:148— pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:148-159 | pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:180-189 — 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 `pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:148` calls `Failure` and `pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:180` 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 (8–10 lines × 4) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:701— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:701-708 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:751-758 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:969-976 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationServiceImpl.scala:53-62 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 7) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:207— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:207-231 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:233-257 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:259-283 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:446-454 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:536-560 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:562-586 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:588-612 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/PresentBackgroundJobs.scala:207` 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 (7–9 lines × 4) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:704— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:704-710 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:754-760 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:822-830 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:972-978 — 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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:704` 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–9 lines × 4) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:22— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:22-29 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:41-49 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerLogic.scala:22-29 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerLogic.scala:41-49 — before extracting anything, compare `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala` and `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialschema/controller/CredentialSchemaControllerLogic.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/credentialdefinition/controller/CredentialDefinitionControllerLogic.scala:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–8 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:120— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:120-125 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/IssueBackgroundJobs.scala:422-429 — 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 `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala:120` 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 × 5) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:518— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:518-524 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:705-711 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:755-761 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:823-831 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:973-979 — 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 `pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialServiceImpl.scala:518` 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–9 lines × 2) cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/handler/DIDCreateHandler.scala:60— cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/handler/DIDCreateHandler.scala:60-67 | cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/handler/DIDUpdateHandler.scala:116-124 — 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 `cloud-agent/service/wallet-api/src/main/scala/org/hyperledger/identus/agent/walletapi/service/handler/DIDCreateHandler.scala:60` 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 (11–12 lines × 4) pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:165— pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:165-175 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:192-202 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:154-165 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:184-195 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:177— pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:177-182 | pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:206-211 | pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:246-251 — 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 `pollux/sd-jwt/src/main/scala/org/hyperledger/identus/pollux/sdjwt/SDJWT.scala:177` 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 (3–5 lines × 4) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/castor/controller/DIDRegistrarController.scala:116— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/castor/controller/DIDRegistrarController.scala:116-120 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/event/controller/EventController.scala:62-66 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/iam/wallet/http/controller/WalletManagementController.scala:62-66 | cloud-agent/service/server/src/main/scala/org/hyperledger/identus/pollux/prex/controller/PresentationExchangeController.scala:49-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/castor/controller/DIDRegistrarController.scala:116` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala:18— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala:18-32 | connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/Migrations.scala:18-32 — before extracting anything, compare `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala` and `connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/Migrations.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala:35— cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala:35-45 | connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/Migrations.scala:35-45 | pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/repository/Migrations.scala:36-46 — before extracting anything, compare `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/sql/Migrations.scala` and `connect/sql-doobie/src/main/scala/org/hyperledger/identus/connect/sql/repository/Migrations.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/IssueCredentialRecord.scala:70— pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/IssueCredentialRecord.scala:70-74 | pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/PresentationRecord.scala:41-45 — 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.
Unstable project vdrProxy — vdrProxy has instability 0.88 with 1 dependents.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
P3 · Security & performance tooling· SAST runs, but gates no merge · ×1
SAST runs, but gates no merge — `scorecard.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
No 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.
R6 · Tooling· Type errors in this package cannot fail any build or CI step · ×1
Type errors in this package cannot fail any build or CI step tests/performance-tests/agent-performance-tests-k6/package.json:26— `tests/performance-tests/agent-performance-tests-k6` is TypeScript, but a type error in it cannot fail anything this repository runs: its `webpack` script (`webpack`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles.
Unused dependency '@commitlint/cli' package.json:8— Declared in the root 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.
Unused dependency '@commitlint/config-conventional' package.json:9— Declared in the root 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.
Unused dependency 'conventional-changelog-conventionalcommits' package.json:13— Declared in the root 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.
Unused dependency 'gradle-semantic-release-plugin' package.json:14— Declared in the root 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.
Unused dependency 'pinst' package.json:16— Declared in the root 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.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked tests/didcomm-tests/package.json:11— tests/didcomm-tests/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
Fat interface: ConnectionService (16 abstract members) connect/core/src/main/scala/org/hyperledger/identus/connect/core/service/ConnectionService.scala:14— `ConnectionService` declares 16 abstract members: `createConnectionInvitation`, `receiveConnectionInvitation`, `acceptConnectionInvitation`, `markConnectionRequestSent`, `receiveConnectionRequest`, `acceptConnectionRequest`, `markConnectionResponseSent`, `markConnectionInvitationExpired`, `receiveConnectionResponse`, `findAllRecords`, `findRecordsByStates`, `findRecordsByStatesForAllWallets`, `findRecordById`, `findRecordByThreadId`, `deleteRecordById`, `reportProcessingFailure`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: CredentialRepository (17 abstract members) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/repository/CredentialRepository.scala:10— `CredentialRepository` declares 17 abstract members: `create`, `findAll`, `getById`, `findById`, `findByStates`, `findByStatesForAllWallets`, `findByThreadId`, `updateProtocolState`, `updateWithSubjectId`, `updateWithJWTRequestCredential`, `updateWithAnonCredsRequestCredential`, `updateWithIssueCredential`, `updateWithIssuedRawCredential`, `deleteById`, `findValidIssuedCredentials`, `findValidAnonCredsIssuedCredentials`, `updateAfterFail`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: PresentationRepository (16 abstract members) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/repository/PresentationRepository.scala:9— `PresentationRepository` declares 16 abstract members: `createPresentationRecord`, `getPresentationRecords`, `findPresentationRecord`, `getPresentationRecordsByStates`, `getPresentationRecordsByStatesForAllWallets`, `findPresentationRecordByThreadId`, `getPresentationRecordByDIDCommID`, `updatePresentationRecordProtocolState`, `updateWithRequestPresentation`, `updateWithProposePresentation`, `updateWithSDJWTDisclosedClaims`, `updateWithPresentation`, `updatePresentationWithCredentialsToUse`, `updateSDJWTPresentationWithCredentialsToUse`, `updateAnoncredPresentationWithCredentialsToUse`, `updateAfterFail`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: CredentialService (27 abstract members) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/CredentialService.scala:24— `CredentialService` declares 27 abstract members: `createJWTIssueCredentialRecord`, `createSDJWTIssueCredentialRecord`, `createAnonCredsIssueCredentialRecord`, `getIssueCredentialRecords`, `getIssueCredentialRecordsByStates`, `getIssueCredentialRecordsByStatesForAllWallets`, `findById`, `getById`, `getIssueCredentialRecordByThreadId`, `receiveCredentialOffer`, `acceptCredentialOffer`, `generateJWTCredentialRequest`, `generateSDJWTCredentialRequest`, `generateAnonCredsCredentialRequest`, `receiveCredentialRequest`, `acceptCredentialRequest`, `generateJWTCredential`, `generateSDJWTCredential`, `generateAnonCredsCredential`, `receiveCredentialIssue`, `markOfferSent`, `markRequestSent`, `markCredentialSent`, `markCredentialOfferInvitationExpired`, `reportProcessingFailure`, `getJwtIssuer`, `getCredentialOfferInvitation`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: PresentationService (38 abstract members) pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/service/PresentationService.scala:18— `PresentationService` declares 38 abstract members: `extractIdFromCredential`, `createJwtPresentationRecord`, `createSDJWTPresentationRecord`, `createAnoncredPresentationRecord`, `getPresentationRecords`, `createJwtPresentationPayloadFromRecord`, `createPresentationFromRecord`, `createSDJwtPresentation`, `createAnoncredPresentationPayloadFromRecord`, `createAnoncredPresentation`, `getPresentationRecordsByStates`, `getPresentationRecordsByStatesForAllWallets`, `findPresentationRecord`, `findPresentationRecordByThreadId`, `receiveRequestPresentation`, `acceptRequestPresentation`, `acceptSDJWTRequestPresentation`, `acceptAnoncredRequestPresentation`, `rejectRequestPresentation`, `receiveProposePresentation`, `acceptProposePresentation`, `receivePresentation`, `acceptPresentation`, `rejectPresentation`, `markRequestPresentationSent`, `markRequestPresentationRejected`, `markProposePresentationSent`, `markPresentationSent`, `markPresentationGenerated`, `markPresentationVerified`, `markPresentationRejected`, `markPresentationAccepted`, `markPresentationVerificationFailed`, `updateWithSDJWTDisclosedClaims`, `verifyAnoncredPresentation`, `reportProcessingFailure`, `getRequestPresentationFromInvitation`, `markPresentationInvitationExpired`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
README/code drift mercury/README.md:5— mercury/README.md links to `./Mercury-Mailbox-Mediator.md`, but `mercury/Mercury-Mailbox-Mediator.md` 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.
README/code drift mercury/README.md:8— mercury/README.md links to `./protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md`, but `mercury/protocol-mercury-mailbox/Mercury-Mailbox-Protocol.md` 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.
README/code drift cloud-agent/service/README.md:29— cloud-agent/service/README.md links to `./connect.md`, but `cloud-agent/service/connect.md` 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.
README/code drift cloud-agent/service/README.md:35— cloud-agent/service/README.md links to `./issue.md`, but `cloud-agent/service/issue.md` 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.
README/code drift cloud-agent/service/README.md:41— cloud-agent/service/README.md links to `./present-proof.md`, but `cloud-agent/service/present-proof.md` 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.
Interpolated log message defeats structured logging infrastructure/utils/python/github-helpers/github_helpers/cli.py:131— `error` at line 131 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging infrastructure/utils/python/github-helpers/github_helpers/cli.py:195— `info` at line 195 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging infrastructure/utils/python/github-helpers/github_helpers/cli.py:215— `error` at line 215 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
D21 · Naming Consistency· `DidCommID` spells `ID` where 747 names in the project spell it `Id` · ×2
`DidCommID` spells `ID` where 747 names in the project spell it `Id` pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/DidCommID.scala:6— 747 of 756 names in project repository spell the token `Id` (747 of 756; unit: names in project repository containing `Id`). Peers: org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:25); org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:27); SignedPrismDIDOperation.toAtalaOperationId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDIDOperation.scala:41); DIDService.getScheduledDIDOperationDetail(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/DIDService.scala:16); NeoPrismClient.isOperationIndexed(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:58). Rename to `DidCommId`. [rule N6]
`DidCommID` spells `ID` where 747 names in the project spell it `Id` pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/DidCommID.scala:7— 747 of 756 names in project repository spell the token `Id` (747 of 756; unit: names in project repository containing `Id`). Peers: org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:25); org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:27); SignedPrismDIDOperation.toAtalaOperationId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDIDOperation.scala:41); DIDService.getScheduledDIDOperationDetail(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/DIDService.scala:16); NeoPrismClient.isOperationIndexed(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:58). Rename to `DidCommId`. [rule N6]
D21 · Naming Consistency· `findByID` spells `ID` where 747 names in the project spell it `Id` · ×2
`findByID` spells `ID` where 747 names in the project spell it `Id` pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialDefinition.scala:110— 747 of 756 names in project repository spell the token `Id` (747 of 756; unit: names in project repository containing `Id`). Peers: org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:25); org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:27); SignedPrismDIDOperation.toAtalaOperationId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDIDOperation.scala:41); DIDService.getScheduledDIDOperationDetail(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/DIDService.scala:16); NeoPrismClient.isOperationIndexed(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:58). Rename to `findById`. [rule N6]
`findByID` spells `ID` where 747 names in the project spell it `Id` pollux/sql-doobie/src/main/scala/org/hyperledger/identus/pollux/sql/model/db/CredentialSchema.scala:97— 747 of 756 names in project repository spell the token `Id` (747 of 756; unit: names in project repository containing `Id`). Peers: org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:25); org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:27); SignedPrismDIDOperation.toAtalaOperationId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDIDOperation.scala:41); DIDService.getScheduledDIDOperationDetail(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/DIDService.scala:16); NeoPrismClient.isOperationIndexed(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:58). Rename to `findById`. [rule N6]
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: REDACTED, shared/core/src/main/scala/org/hyperledger/identus/shared/db/ContextAwareTask.scala. Pair on, review, or document these before any departure.
No ADRs found build.sbt:607— 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 `build.sbt` makes this repository a deployable product (line 607).
D21 · Naming Consistency· `DidCommIDCodec` spells `ID` where 747 names in the project spell it `Id` · ×1
`DidCommIDCodec` spells `ID` where 747 names in the project spell it `Id` cloud-agent/service/server/src/main/scala/org/hyperledger/identus/api/http/codec/DidCommIDCodec.scala:8— 747 of 756 names in project repository spell the token `Id` (747 of 756; unit: names in project repository containing `Id`). Peers: org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:25); org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:27); SignedPrismDIDOperation.toAtalaOperationId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDIDOperation.scala:41); DIDService.getScheduledDIDOperationDetail(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/DIDService.scala:16); NeoPrismClient.isOperationIndexed(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:58). Rename to `DidCommIdCodec`. [rule N6]
D21 · Naming Consistency· `toDidCommID` spells `ID` where 747 names in the project spell it `Id` · ×1
`toDidCommID` spells `ID` where 747 names in the project spell it `Id` cloud-agent/service/server/src/main/scala/org/hyperledger/identus/presentproof/controller/PresentProofController.scala:48— 747 of 756 names in project repository spell the token `Id` (747 of 756; unit: names in project repository containing `Id`). Peers: org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:25); org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:27); SignedPrismDIDOperation.toAtalaOperationId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDIDOperation.scala:41); DIDService.getScheduledDIDOperationDetail(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/DIDService.scala:16); NeoPrismClient.isOperationIndexed(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:58). Rename to `toDidCommId`. [rule N6]
D21 · Naming Consistency· `isDidPRISM` spells `PRISM` where 49 names in the project spell it `Prism` · ×1
`isDidPRISM` spells `PRISM` where 49 names in the project spell it `Prism` mercury/resolver/src/main/scala/org/hyperledger/identus/resolvers/DidValidator.scala:19— 49 of 50 names in project repository spell the token `Prism` (49 of 50; unit: names in project repository containing `Prism`). Peers: org.hyperledger.identus.castor.core.model.did.CanonicalPrismDID (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDID.scala:104); org.hyperledger.identus.castor.core.model.did.LongFormPrismDID (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDID.scala:108); org.hyperledger.identus.castor.core.model.did.SignedPrismDIDOperation (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDIDOperation.scala:32); org.hyperledger.identus.castor.core.service.NeoPrismConfig (castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:15); org.hyperledger.identus.castor.core.service.NeoPrismSubmissionResult (castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:18). Rename to `isDidPrism`. [rule N6]
D21 · Naming Consistency· `NotValidDidCommID` spells `ID` where 747 names in the project spell it `Id` · ×1
`NotValidDidCommID` spells `ID` where 747 names in the project spell it `Id` pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/model/error/PresentationError.scala:170— 747 of 756 names in project repository spell the token `Id` (747 of 756; unit: names in project repository containing `Id`). Peers: org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:25); org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:27); SignedPrismDIDOperation.toAtalaOperationId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDIDOperation.scala:41); DIDService.getScheduledDIDOperationDetail(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/DIDService.scala:16); NeoPrismClient.isOperationIndexed(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:58). Rename to `NotValidDidCommId`. [rule N6]
D21 · Naming Consistency· `getPresentationRecordByDIDCommID` spells `ID` where 747 names in the project spell it `Id` · ×1
`getPresentationRecordByDIDCommID` spells `ID` where 747 names in the project spell it `Id` pollux/core/src/main/scala/org/hyperledger/identus/pollux/core/repository/PresentationRepository.scala:30— 747 of 756 names in project repository spell the token `Id` (747 of 756; unit: names in project repository containing `Id`). Peers: org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:25); org.hyperledger.identus.castor.core.model.did.DIDMethodSpecificId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/DID.scala:27); SignedPrismDIDOperation.toAtalaOperationId (castor/src/main/scala/org/hyperledger/identus/castor/core/model/did/PrismDIDOperation.scala:41); DIDService.getScheduledDIDOperationDetail(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/DIDService.scala:16); NeoPrismClient.isOperationIndexed(operationId) (castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismClient.scala:58). Rename to `getPresentationRecordByDIDCommId`. [rule N6]
D21 · Naming Consistency· `UpdateManagedDIDServiceAction` spells `DID` where 15 names in the project spell it `Did` · ×1
`UpdateManagedDIDServiceAction` spells `DID` where 15 names in the project spell it `Did` cloud-agent/client/typescript/models/UpdateManagedDIDServiceAction.ts:4— 15 of 16 names in project identus-cloud-agent spell the token `Did` (15 of 16; unit: names in project identus-cloud-agent containing `Did`). Peers: Actor.longFormDid (tests/performance-tests/agent-performance-tests-k6/src/actors/Actor.ts:14); Holder.holderDidTemplate (tests/performance-tests/agent-performance-tests-k6/src/actors/Holder.ts:25); Holder.createUnpublishedDid (tests/performance-tests/agent-performance-tests-k6/src/actors/Holder.ts:47); Issuer.issuerDidTemplate (tests/performance-tests/agent-performance-tests-k6/src/actors/Issuer.ts:30); Issuer.createUnpublishedDid (tests/performance-tests/agent-performance-tests-k6/src/actors/Issuer.ts:69). Rename to `UpdateManagedDidServiceAction`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion package.json:1— `(repository root)` (48723 LoC, 2305 module-visible types across 149 directories) overshoots its size bounds. 1 of 4 build unit(s) (Gradle, Python, npm) overshoot their size bounds, lowering Project Cohesion to 5.0/10. 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
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
Disabled test cloud-agent/service/wallet-api/src/test/scala/org/hyperledger/identus/agent/walletapi/benchmark/KeyDerivation.scala:37— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
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.
P3 · Security & performance tooling· Dependabot does not watch gradle · ×1
Dependabot does not watch gradle REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
No security response headers detected REDACTED:21— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
No app-layer HTTPS enforcement detected — This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/http/ZHttp4sBlazeServer.scala:5 — `BlazeServerBuilder`.
X5 · Nullable reference types· Scala's null is not held to the type system everywhere · ×1
Scala's null is not held to the type system everywhere — No build over this repository's 548 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
Off the main sequence: shared — shared: abstractness 0.14, instability 0.00, distance 0.86 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 43 file(s) — `castor/src/main/scala/org/hyperledger/identus/castor/core/service/NeoPrismDIDService.scala`, `castor/src/main/scala/org/hyperledger/identus/castor/core/service/PrismNodeDIDService.scala`, `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/BackgroundJobError.scala`, `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/ConnectBackgroundJobs.scala`, `cloud-agent/service/server/src/main/scala/org/hyperledger/identus/agent/server/jobs/DIDStateSyncBackgroundJobs.scala`, … (+38 more) — so the PII/GDPR sweep did not cover them at all.
runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
Run 01a1e9dd-fbb7-7d1f-a419-c58657bedbfd · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 75 · Warnings: 542 · Recommendations: 51 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 14:16 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.